Specifications include, but are not limited to: o Data may only be used in such a way as to accomplish the assigned task or as directed by CU. o The solution must provide a mechanism for CU to control user and system-level access to all functions of the hosted system where applicable. ▪ Most systems will require the use of CU’s existing and future 2fa solutions. o The solution must provide a mechanism for CU to monitor the system status, including accurately, but not limited to, the up/down status of the hosted system. Offeror will provide the required expertise to assist CU in the analysis and understanding of the technical logs for the solution they are proposing. Offer will provide required expertise to assist CU in determining best practice approaches to and in the creation of dashboards and reporting required by Clemson's SOC and NOC to achieve viable levels of monitoring of the technical solution. o The offeror must not store any CU data in a facility (or cloud, storage device, laptop, etc) outside of the United States. ▪ Or release any data for any reason outside of the United States ▪ Or allow access to data from outside the United States unless express permission is granted o The solution must provide a mechanism to allow CU to receive data files for consumption by, but not limited to, the current (or future) CU Data Warehouse and similar systems. The offeror must design this transfer in a way that allows it to be scheduled and fully automated as well as fully controlled by CU. Data in transit must be encrypted or use a secure encrypted link...
