Public Data Security Sample Clauses

Public Data Security. Contractor agrees to protect and maintain the security of Public Data with protection that is at least as good as or better than that maintained by the State of Utah which will be provided by an Eligible User upon Contractor’s request. These security measures included but are not limited to maintaining secure environments that are patched and up to date with all appropriate security updates as designated (ex. Microsoft Notification). Eligible User reserves the right to determine if Contractor’s level of protection adequately meets the Eligible User’s security requirements.
View SourceView Similar (5)
Public Data Security. Contractor agrees to protect and maintain the security of Public Data with protection that is at least as good as or better than that maintained by the State of Utah which will be provided by an Eligible User upon Contractor’s request. These security measures included but are not limited to maintaining secure environments that are patched and up to date with all appropriate security updates as designated (ex. Microsoft Notification). Eligible User reserves the right to determine if Contractor’s level of protection adequately meets the Eligible User’s security requirements. Public Data Transmission: Contractor agrees that any and all transmission or exchange of system application data with the Eligible Users and State of Utah and/or any other parties expressly designated by the State of Utah, shall take place via secure means (ex. HTTPS or FTPS).
View SourceView Similar (4)
Public Data Security. When Contractor expressly agrees to provide security services (e.g., Managed Security Services), Contractor agrees to protect and maintain the security of Public Data with protection that is at least as good as or better than that maintained by the State of Utah which will be provided by an Eligible User upon Contractor’s request. These security measures included but are not limited to maintaining secure environments that are patched and up to date with all appropriate security updates as designated (ex. Microsoft Notification). Eligible User reserves the right to determine if Contractor’s level of protection adequately meets the Eligible User’s security requirements.
View Source

Related to Public Data Security

  • Electronic Data 7.1.1 The parties recognize that Contract Documents, including drawings, specifications and three-dimensional modeling (such as Building Information Models) and other Work Product may be transmitted among Owner, Design-Builder and others in electronic media as an alternative to paper hard copies (collectively “Electronic Data”).

  • Data Security The Provider agrees to utilize administrative, physical, and technical safeguards designed to protect Student Data from unauthorized access, disclosure, acquisition, destruction, use, or modification. The Provider shall adhere to any applicable law relating to data security. The provider shall implement an adequate Cybersecurity Framework based on one of the nationally recognized standards set forth set forth in Exhibit “F”. Exclusions, variations, or exemptions to the identified Cybersecurity Framework must be detailed in an attachment to Exhibit “H”. Additionally, Provider may choose to further detail its security programs and measures that augment or are in addition to the Cybersecurity Framework in Exhibit “F”. Provider shall provide, in the Standard Schedule to the DPA, contact information of an employee who ▇▇▇ may contact if there are any data security concerns or questions.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.

  • Electronic Data Interchange (EDI This standard establishes the data contents of the Invoice Transaction Set (810) for use within the context of an EDI environment. This transaction set can be used for invoicing via the AN for catalog and non-catalog goods and services.

  • Electronic Data Interchange If both Parties elect to facilitate business activities hereunder by electronically sending and receiving data in agreed formats (also referred to as Electronic Data Interchange or “EDI”) in substitution for conventional paper-based documents, the terms and conditions of this Agreement shall apply to such EDI activities.