SECURITY & OPSEC Sample Clauses
The SECURITY & OPSEC clause establishes requirements and standards for maintaining the confidentiality, integrity, and availability of sensitive information and systems. It typically outlines the security measures that must be implemented, such as access controls, encryption, and regular security assessments, and may specify protocols for reporting and responding to security incidents. The core function of this clause is to protect both parties from data breaches and operational vulnerabilities, thereby reducing the risk of unauthorized access or disclosure of critical information.
POPULAR SAMPLE Copied 4 times
SECURITY & OPSEC. All PAH shall comply with DFARS 252.204-7012 (Oct 2016): Safeguarding Covered Defense Information and Cyber Incident Reporting when applicable. Covered Defense Information (CDI) will be identified at the Project Agreement level. The MCDC Member shall comply with DFARS 252.204-7012 (Oct 2016): Safeguarding Covered Defense Information and Cyber Incident Reporting, which includes implementing on its covered contractor information systems the security requirements specified by DFARS 252.204-7012. Nothing in this paragraph shall be interpreted to foreclose the MCDC Member's right to seek alternate means of complying with the security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171 (as contemplated in DFARS 252.204-7008 (Compliance with Safeguarding Covered Defense Information Controls) (Oct 2016) and DFARS 252.204-7012 (Safeguarding Covered Defense Information and Cyber Incident Reporting (Oct 2016)). Work performed by a PAH under a Project Agreement may involve access to Controlled Unclassified Information (CUI). All Controlled Unclassified Information (CUI) developed under this Agreement will be managed in accordance with DoD Manual 5200.01, Volume 4 dated February 24, 2012. Contractor personnel shall comply with applicable Technology Protection Plans (TPP), Interim Program Protection Plans (IPPP) and/or Program Protection Plans (PPP). If a project involves a Controlled Unclassified Information (CUI) effort, the below listed Department of Defense Directives, Federal Acquisition Regulation (FAR) and the Defense Federal Acquisition Regulation Supplement (DFARS), and ARDEC clauses will be incorporated into the Project Agreements by reference with the same force and effect as if they were given in full text.
(1) Each project Scope of Work will be provided by the Agreements Officer Representative (AOR) to the Joint Project Manager- Medical Countermeasure Systems Office for dissemination to the appropriate Fort ▇▇▇▇▇▇▇ COMSEC officer prior to award for review.
(2) Each project Scope of Work will be subject to Ft. ▇▇▇▇▇▇▇ policy and procedure according to DoD 5220.22- M, (National Industrial Security Program Operating Manual, NISPOM), as deemed applicable and appropriate during the security review process and prior to award. Additional COMSEC requirements may be required at other locations/facilities (based on service/command requirements).
(3) Specific applicable policies, instructions, and regulations will be ...
SECURITY & OPSEC. The below language shall be used as Paragraph 6 of Article XVII in Regeneron’s Base Agreement: Access and General Protection/Security Policy and Procedures. This standard language text is applicable to ALL PAH employees working on critical program information or covered defense information related to Operation Warp Speed (OWS), and to those with an area of performance within an Army controlled installation, facility or area. PAH employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The PAH also shall provide all information required for background checks necessary to access critical program information or covered defense information related to OWS, and to meet installation access requirements to be accomplished by installation ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇ Office, Director of Emergency Services or Security Office. The PAH workforce must comply with all personal identity verification requirements as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this agreement, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in PAH security matters or processes.
SECURITY & OPSEC. The below language shall be used as Paragraph 6 of Article XVII in the Project Agreement Holder's Base Agreement: Access and General Protection/Security Policy and Procedures. This standard language text is applicable to ALL Project Agreement Holder employees working on critical program information or covered defense information related to Operation Warp Speed (OWS), and to those with an area of performance within an Army controlled installation, facility or area. Project Agreement Holder employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The Project Agreement Holder also shall provide all information required for background checks necessary to access critical program information or covered defense information related to OWS, and to meet installation access requirements to be accomplished by installation ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇ Office, Director of Emergency Services or Security Office. The Project Agreement Holder workforce must comply with all personal identity verification requirements as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this agreement, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in Project Agreement Holder security matters or processes.