Data Sensitivity Sample Clauses

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”.
AutoNDA by SimpleDocs
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, i.e., credit card, bank account numbers, shall be stored or exchanged in the data exchange sessions.
Data Sensitivity. The sensitivity of all data filed is Sensitive But Unclassified (SBU).
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. 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. [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 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.g. Data being transferred contains personal information protected by the Privacy Act of 1974 and sensitive financial information. etc. Include which encryption is being used including the mode of operation, and the package name where applicable.}
AutoNDA by SimpleDocs
Data Sensitivity. VENDOR and CAFS exchange loan borrower data. For test, the vendor should not provide any data that would be Sensitive-But-Unclassified (SBU). For SOE/production Privacy Act data traverse this connection. Though the data classification is Sensitive-But-Unclassified (SBU), its sensitivity demands strong measures to provide a high level of confidence that is confidentiality, integrity, and availability are preserved
Data Sensitivity. The sensitivity of data exchanged between HUD and Organization B is personally identifiable information (PII).

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).

  • 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.

  • Handling Sensitive Personal Information and Breach Notification A. As part of its contract with HHSC Contractor may receive or create sensitive personal information, as section 521.002 of the Business and Commerce Code defines that phrase. Contractor must use appropriate safeguards to protect this sensitive personal information. These safeguards must include maintaining the sensitive personal information in a form that is unusable, unreadable, or indecipherable to unauthorized persons. Contractor may consult the “Guidance to Render Unsecured Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals” issued by the U.S. Department of Health and Human Services to determine ways to meet this standard.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Budget Information Funding Source Funding Year of Appropriation Budget List Number Amount EPIC 18-19 301.001F $500,000 EPIC 20-21 301.001H $500,000 R&D Program Area: EDMFO: EDMF TOTAL: $ 1,000,000 Explanation for “Other” selection Reimbursement Contract #: Federal Agreement #:

  • Safety Data Sheets If specified by City in the solicitation or otherwise required by this Contract, Contractor must send with each shipment one (1) copy of the Safety Data Sheet (SDS) for each item shipped. Failure to comply with this procedure will be cause for immediate termination of the Contract for violation of safety procedures.

  • ODUF Physical File Characteristics 6.2.1 The ODUF will be distributed to Dialtone & More via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non- compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Alert Information As Alerts delivered via SMS, email and push notifications are not encrypted, we will never include your passcode or full account number. You acknowledge and agree that Alerts may not be encrypted and may include your name and some information about your accounts, and anyone with access to your Alerts will be able to view the contents of these messages.

  • Data To permit evaluation of requests under paragraph (c) of this clause based on unreasonable cost, the Contractor shall include the following information and any applicable supporting data based on the survey of suppliers: Foreign and Domestic Construction Materials Cost Comparison Construction material description Unit of measure Quantity Cost (dollars) * Item 1: Foreign construction material Domestic construction material Item 2 Foreign construction material Domestic construction material [List name, address, telephone number, and contact for suppliers surveyed. Attach copy of response; if oral, attach summary.] [Include other applicable supporting information.] (*Include all delivery costs to the construction site.]

Time is Money Join Law Insider Premium to draft better contracts faster.