TGIC CyberSecurity for Government Contractor Information Systems TGIC

TGIC Cyber-Security for Government Contractor Information Systems TGIC June and July 2017 Presentations kauf. CAN. com

Regulatory Overview • FAR 4. 10 – sets forth basic requirements for safeguarding of contractor information systems. – Requires clause 52. 204 -21 in solicitations and contracts when the contractor or subcontractor (at any tier) may have federal contract information residing in or transiting though its information systems. 52. 204 -21(a) definitions 52. 204 -21(b) checklist of safeguard procedures 52. 204 -21(c) substance of this clause flows down to subcontractors kauf. CAN. com

DFARS 252. 204 -7008 Compliance (a) Definitions (b) Follow DFARS 252. 204 -7012 security requirements DFARS 252. 204 -7012(b)(2) Offeror must follow NIST (Nat’l. Insti. Of Standards and Tech. ) Special Publication (SP) 800 -171, Protecting Controlled Unclassified Information in Nonfederal Information Systems… Implement by Dec. 31, 2017. kauf. CAN. com

DFARS 252. 204 -7012(c) Cyber reporting Review evidence of compromise Report the incident to Do. D Allow Do. D access to assess the compromise DFARS 239. 76 Cloud Computing Follow regarding Declaration of offeror’s intent to use Cloud Computing, and relevant procedures. Recommendations: Implement an enforceable plan based on NIST requirements and the definitions and checklist of clause 52. 204 -21, including flow down to subcontractors. kauf. CAN. com

Final FAR Rule: Basic Safeguarding of Contractor Information Systems – New clause (FAR 52. 204 -21) in solicitations and contracts when the contractor or subcontractor at any tier may have Federal Contract Information (“FCI”) residing in or transiting through its information system. – Federal Contract Information: non-public information provided by or developed for the Government in connection with the contract, excluding “simple transactional information, such as necessary to process payment. ” kauf. CAN. com

B. Final FAR Rule: Basic Safeguarding of Contractor Information Systems – – 81 Fed. Reg. 30, 439 (May 16, 2016) (effective June 15, 2016) Outline basic network safeguards and standardize rudimentary security procedures Page 6 kauf. CAN. com

What Safeguards Does the FAR Require? 1. Limit access to authorized users. 2. Limit info system access to the types of transactions and functions that authorized users are permitted to execute. 3. Verify controls on connections to external info systems. 4. Impose controls on info that is posted or processed on publicly accessible info systems. 5. Identify info system users and devices and those acting on behalf of users or devices. kauf. CAN. com

FAR Requirements (Con't) 6. Verify identities of users, processes and devices before access to info systems is allowed. 7. Sanitize or destroy info system media containing contract info before disposal or reuse. 8. Limit physical access to info systems, equipment, and operating environments to authorized individuals and devices. 9. Escort visitors and monitor visitor activity, maintain audit logs of physical access, control and manage physical access devices. kauf. CAN. com

FAR Requirements (Con't) 10. Monitor, control & protect organizational communications at external boundaries and key internal boundaries. 11. Implement sub networks for publicly accessible system components that are physically or logically separated from internal networks. 12. Identify, report (internally) and correct info and system flaws in a timely manner. kauf. CAN. com

FAR Requirements (Con't) 13. Provide protection from malicious code at appropriate locations within organization’s info systems. 14. Update malicious code protection mechanisms when new releases are available. 15. Perform periodic scans of the info systems and real-time scans of files from external sources as files are downloaded, opened or executed. kauf. CAN. com

DFARS REQUIRES MORE KEY FAR - DFAR Differences: 1. FAR excludes COTS (commercial off-the-shelf) contracts. 2. FAR applies to info systems on which Fed Contract Info transits or resides. DFARS applies to both covered defense info itself and the info system on which it transits or resides. 3. DFARS requires somewhat more extensive security controls - NIST SP 800 -171 or alternative but equally secure measures - need written approval of Do. D CIO. Page 11 kauf. CAN. com

DFAR Rule February 2013: EO 13, 636 (“Improving Critical Infrastructure Cybersecurity”) • Establish cybersecurity framework by creating technical standards • National Institute of Standards and Technology (“NIST”) November 2013: DFAR Rule • Cybersecurity measures imposed on defense contractors • “adequate security” for “systems” that handle “unclassified controlled technical information” (UCTI) (military or space application) Page 12 kauf. CAN. com

DFAR Rule • Utilize NIST standards (NIST SP 800 -53) • Incident reporting (72 hours) • Investigate and preserve data 2015 – DFAR Interim Rule (Safeguarding Covered Defense Information and Cyber Incident Reporting) (effective December 2015) • Extended date of full compliance to December 31, 2017 Page 13 kauf. CAN. com

A. DFARS Interim Rule — Safeguarding Covered Defense Information and Cyber Incident Reporting – DFARS 252. 204 -7012 expanded to include all “covered defense information” • Covered Defense Information (“CDI”): controlled technical information, critical information, export controlled information, or any information that law or policy requires safeguarding or controls—very broad, encompasses most contracts – Must comply with security requirements outlined in National Institute of Standards and Technology (NIST) SP 800 -171 (110 controls) Page 14 kauf. CAN. com

DFARS – DFARS 252. 204 -7012 clause includes requirement that contractors must report incidents within 72 hours – Reportable incidents involve compromise of CDI, covered contractor systems, or actions that limit the ability to perform “operationally critical support” Contractor should register for a Do. D-approved medium assurance certificate for incident reporting (see http: //iase. disa. mil/pki/eca/Pages/index. aspx) Page 15 kauf. CAN. com

DFARS Interim Rule — Safeguarding Covered Defense Information and Cyber Incident Reporting – Clause must be flowed down to subcontractors handling CDI – Contractor must report to Do. D within 30 days of any non-compliance with new security requirements and what substitute measures are in place – Full compliance mandated no later than December 31, 2017 Page 16 kauf. CAN. com

Relationship of FAR to DFARS FAR clause provides basic requirements for almost any government information stored and processed by a contractor FAR clause explicitly states it is not to diminish other more stringent security requirements—acts as a supplement Both clauses will likely be included—CO should make known use of Covered Defense Information ("CDI") early in the process Both clauses are required to be "flowed down" to subcontractors • DFARS is only required to be "flowed down" when CDI is necessary for performance of the subcontract Page 17 kauf. CAN. com

Time Is Not On Your Side! Some deadlines that have already passed: January 2017 – Have system security plan (SSP) in place Other deadlines that are fast approaching: December 31, 2017 DFARS 252. 204. 7012 Compliance - Safeguarding Controlled Defense Information (CDI) Page 18 kauf. CAN. com

Related Legal Issues 1. Allowability of cyber security compliance costs 2. Bid Protests based on cyber security issues 3. Performance evaluations 4. Protection of intellectual property and trade secrets when disclosing cyber attacks 5. Insurance for cyber attacks 6. Be prepared for post-cyber attack report events (i. e. investigation, seizure of hardware, have back-ups) Page 19 kauf. CAN. com

Potential Contractor Liability Issues: - Breach of contract liability – including breach of express and implied certifications - Negligence liability for release of certain personal info - False Claims Act (“FCA”) Liability • Recent Supreme Court decision* made it easier to incur FCA liability when non-compliant with cybersecurity measures • Could be liable even when not making an express certification but “knowingly fails to disclose. . . noncompliance with a statutory, regulatory, or contractual requirement. ” • *Universal Health Servs. v. United States, ex rel. Escobar, 136 S. Ct. 1989 (2016) Page 20 kauf. CAN. com

Liability Protection • Designated “operationally critical contractors” can receive liability protection under 10 USC 391 for reporting cyber incidents • Definition: a contractor designated as a critical source of supply for airlift, deployment, or sustainment of a military contingency operation • Protection does not apply if designated contractor engaged in willful misconduct or to achieve a wrongful purpose or acted without legal or factual justification Page 21 kauf. CAN. com

Much of this is not new to certain Do. D activities which have addressed spillage of classified and confidential (i. e. , PII or Personal Identification Information, such as social security numbers, home addresses, etc. ) for a number of years in contract provisions, including anticipated damages to correct spillage. White House action in this area is likely to increase rules and further guidance in this area. Questions? Page 22 kauf. CAN. com