Data Sensitivity Clause Samples

POPULAR SAMPLE Copied 1 times
Data Sensitivity. 4.9.1 Data exchanged between CSD and Contractor must be limited to the data fields included on Data Transfer Rules documents posted on the Providers’ Website. No personal financial information, (e.g., credit card, bank account numbers), shall be stored or exchanged in the data exchange sessions. 4.9.2 Data exchanged between CSD and Contractor must be limited to the data fields as requested within the web applications. No personal financial information (e.g., credit card, bank account numbers), shall be stored or exchanged in the data exchange sessions. 4.9.3 Data exchanged between CSD and Contractor via email communication must have all personally identifying information (PII) and other sensitive information redacted before the document is sent. Alternately, Contractor is to encrypt any attachments that have sensitive data using encryption tools and configurations as required by CSD. 4.9.4 Access to the above-mentioned data must only be given to authorized personnel to complete essential duties. Authorized personnel are to log into these systems using their own assigned credentials (i.e., no login account sharing). Upon departure of personnel with assigned credentials, the Contractor will remove the employee’s access to the systems as soon as possible.
Data Sensitivity. The sensitivity of all data filed is Sensitive But Unclassified (SBU).
Data Sensitivity unclassified but Sensitive, up to and including “High” level of sensitivity as defined by National Institute of Standards and Technology (NIST) SP800-60 Volume 2, section D.14.4 “Health Care Delivery Services Information type”.
Data Sensitivity. The sensitivity of the data transmitted over the connection is Controlled Unclassified Information (CUI). {Specify the sensitivity level of the information that will be handled through the interconnection, including the highest level of sensitivity involved and the most restrictive protection measures required.}{E.
Data Sensitivity. The data is categorized as Moderate based on FIPS 199 Standards for Security Categorization of Federal Information and Information Systems and the guidance of NIST SP 800-60 Guide for Mapping Types of Information and Information Systems to Security Categories. This data categorization matches the overall system security categorization found in the EGS systems security plan. No classified data shall be exchanged between the two systems. But the data exchanged may be proprietary to the proposal record. The EGS system contains personally identifiable information (PII) and proprietary business information that should be disseminated only to those within your agency with a need to know the information in the course of their official duties. Such information when output in any form from the EGS system must be handled and protected in accordance with applicable federal laws and Executive Orders (including Executive Order 13556 of November 4, 2010, Controlled Unclassified Information and its implementing guidance), as well as agency directives, policies, regulations, standards, and operational requirements. Appropriate means shall be used to protect unauthorized disclosure of proposal data in accordance with all federal laws.
Data Sensitivity. Data shared under this Agreement will include unclassified but Sensitive, up to and including “High” level of sensitivity as defined by National Institute of Standards and Technology (NIST) SP800-60 Volume 2, section D.14.4 “Health Care Delivery Services Information type”.
Data Sensitivity. [Enter the sensitivity or classification level of the information to be exchanged, in particular, the highest sensitivity (i.e., Privacy Act, Trade Secret Act, Law Enforcement Sensitive, Sensitive-But-Unclassified, etc.) or classification (Confidential, Secret, Top Secret) and most restrictive protection requirements for information to be handled through the interconnection.]
Data Sensitivity. The sensitivity of data exchanged between HUD and Organization B is personally identifiable information (PII).
Data Sensitivity. VENDOR and CAFS exchange loan borrower data.

Related to Data Sensitivity

  • Substance Abuse Treatment Information Substance abuse treatment information shall be maintained in compliance with 42 C.F.R. Part 2 if the Party or subcontractor(s) are Part 2 covered programs, or if substance abuse treatment information is received from a Part 2 covered program by the Party or subcontractor(s).

  • Data Encryption 2.1. For all COUNTY data, The CONTRACTOR shall encrypt all non-public data in transit regardless of the transit mechanism. 2.2. For all COUNTY data, if the CONTRACTOR stores sensitive personally identifiable or otherwise confidential information, this data shall be encrypted at rest. Examples are social security number, date of birth, driver’s license number, financial data, federal/state tax information, and hashed passwords. 2.3. For all COUNTY data, the CONTRACTOR’S encryption shall be consistent with validated cryptography standards as specified in National Institute of Standards and Technology Security Requirements as outlined at ▇▇▇▇://▇▇▇▇▇▇▇.▇▇▇▇.▇▇▇/nistpubs/Legacy/SP/nistspecialpublication800-111.pdf

  • Sensitive data Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.

  • Screening Services Disclosure to Applicant Pursuant to MN Statute 504B.173, the tenant screening service that we use is the following: Rental History Reports ▇▇▇▇ ▇. ▇▇▇▇ ▇▇▇▇▇▇, #▇▇▇ ▇▇▇▇▇, ▇▇ ▇▇▇▇▇ (▇▇▇) ▇▇▇-▇▇▇▇ Applicant Screening Criteria, upon which the decision to rent to the Applicant is based, will be applied to the information provided in this application and the information gathered from the screening report and/or background check we obtain. If we reject your rental application pursuant to Minnesota Statutes and local laws, we will notify you within 14 days of such rejection, identifying the criteria you failed to meet. We are not obligated to return your application fee or deposit except as provided in MN Statute 504B.173 and local laws.

  • Protocol The attached Protocol shall be an integral part of this Agreement.