Tinker & The Primes 2017 Innovating Together

Transcription

1 Tinker & The Primes 2017 Innovating Together Protecting Controlled Unclassified Information Systems and Organizations Larry Findeiss Bid Assistance Coordinator Oklahoma s Procurement Technical Assistance Center (PTAC) larry.findeiss@tulssatech.edu Geoff Wilson Principal Security Consultant True Digital Security geoff.wilson@truedigitalsecurity.com X 103

2 Tinker & The Primes 2017 Innovating Together Protecting Controlled Unclassified Information Systems and Organizations Executive Order November 4, 2010 This order establishes an open and uniform program for managing information that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Government-wide policies, excluding information that is classified under Executive Order of December 29, 2009, or the Atomic Energy Act, as amended.. To address these problems, this order establishes a program for managing this information, hereinafter described as Controlled Unclassified Information, that emphasizes the openness and uniformity of Government-wide practice.. approve categories and subcategories of CUI and associated markings to be applied uniformly throughout the executive branch. establish and maintain a public CUI registry reflecting authorized CUI categories and subcategories, associated markings, and applicable safeguarding, dissemination, and decontrol procedures.

3 Tinker & The Primes 2017 Innovating Together Protecting Controlled Unclassified Information Systems and Organizations NIST Special Publication Security and Privacy Controls for Federal Information Systems and Organization April 2013 The selection and implementation of security controls for information systems 1 and organizations are important tasks that can have major implications on the operations 2 and assets of organizations 3 as well as the welfare of individuals and the Nation. Security controls are the safeguards/countermeasures prescribed for information systems or organizations that are designed to: (i) protect the confidentiality, integrity, and availability of information that is processed, stored, and transmitted by those systems/organizations; and (ii) satisfy a set of defined security requirements. Federal Information Security Modernization Act of 2014 (FISMA 2014) Codifying Department of Homeland Security (DHS) authority to administer the implementation of information security policies for non-national security federal Executive Branch systems, including providing technical assistance and deploying technologies to such systems he selection and implementation of security controls for information systems 1 and organizations are important tasks

4 Tinker & The Primes 2017 Innovating Together Protecting Controlled Unclassified Information Systems and Organizations CUI Registry National Archives ( ) create a public registry of authorized categories, subcategories, and markings of CUI and their definitions, along with applicable safeguarding, dissemination, and decontrol procedures. Categories of CUI most likely in Defense Contracts (other than IT) are: Controlled Technical Information - means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. Export Control - Unclassified information concerning certain items, commodities, technology, software, or other information whose export could reasonably be expected to adversely affect the United States national security and nonproliferation objectives Procurement and Acquisition - Material and information relating to, or associated with, the acquisition and procurement of goods and services, including but not limited to, cost or pricing data, contract information, indirect costs and direct labor rates.

5 Tinker & The Primes 2017 Innovating Together Protecting Controlled Unclassified Information Systems and Organizations NIST Special Publication June 2015, now Revision 1 December 2016 Today the federal government is relying on external service providers to help carry out a wide range of federal missions and business functions using state-of-the-practice information systems. Many federal contractors, for example, routinely process, store, and transmit sensitive federal information in their systems to support the delivery of essential products and services to federal agencies.protection of sensitive federal information while residing in nonfederal systems and organizations is of paramount importance to federal agencies and can directly impact the ability of the federal government to successfully carry out its designated missions and business operations, including those missions and functions related to the critical infrastructure. The purpose of this publication is to provide federal agencies with recommended security requirements for protecting the confidentiality of CUI when the CUI is resident in a nonfederal system and organization.

6 Tinker & The Primes 2017 Innovating Together Protecting Controlled Unclassified Information Systems and Organizations FAR Basic Safeguarding of Covered Contractor Information Systems June 2016 Information System - information resources organized for the collections, processing, maintenance, use, sharing, dissemination or disposition of information. Covered Contractor Information System information system that is owned or operated by a contractor that processes, stores or transmits Federal contract information. Safeguarding measures or controls that are prescribed to protect information systems Safeguarding requirements and procedures. Contractor shall apply the following basic safeguarding requirements and procedures Limit System Users Access Authenticate/Verify user identities Implement separate sub-networks Limit Access to authorized functions Sanitize/destroy media for disposal Identify, report and correct flaws Verify/Control System Connections Limit physical access to systems Protect from malicious codes Control use of Public systems Escort/monitor visitor activity Update malicious code protection Identify system users and uses Monitor/control communications Perform periodic system scans

7 Tinker & The Primes 2017 Innovating Together Protecting Controlled Unclassified Information Systems and Organizations DFAR Compliance with Safeguarding Covered Defense Information Controls The security requirement required by contract clause shall be implemented for all covered defense information on all covered contractor systems that support the performance of this contract. DFAR Safeguarding Covered Defense Information and Cyber Incident Reporting Covered defense information unclassified controlled technical information or other information, as described in Controlled Unclassified Information (CUI) Registry that requires safeguarding or dissemination controls.and is (1) Marked or otherwise identified and provided. or (2) Collected, developed, received, transmitted used or stored in support of performance of the contract. AND system shall be subject to the security requirements in NIST SP as soon as practical but not later than December 31, 2017.for contracts awarded prior to October 1, 2017, Contractor shall notify the DOD CIO within 30 days of contract award of any security requirements.not implemented at time of award AND Rapidly report cyber incidents

8

9 Motivation for Protecting CUI Breaches are inevitable and unfortunately occur often CUI breach must be reported to DoD A breach of CUI can affect your ability to do business with the DoD The protection of Controlled Unclassified Information (CUI) resident in nonfederal systems and organizations is of paramount importance to federal agencies and can directly impact the ability of the federal government to successfully conduct its assigned missions and business operations (NIST ).

10 NIST Special Publication Rev control families, 110 controls

11 NIST SP : Not Only Applicable To You Your service providers and subcontractors that can access your CUI must also be compliant Ensure cloud-based service providers that store, process, or transmit any covered defense information meet the FedRAMP Moderate baseline and comply with DFAR requirements (c) through (g) Subcontracts that will involve covered defense information must include the DFAR clause and must involve the prime contractor (or next higher-tier subcontractor) when requesting a compliance variance and when reporting an incident. See DFAR for more detail

12 Six Primary Compliance Challenges Shifting Target Meshing with InfoSec Program Maintaining Compliance Vague Requirements Not Enough Time Tight Budget

13 Shifting Target Revision 1 of NIST SP introduced requirement Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems. Contractors must stay updated on latest regulatory changes

14 Meshing With Your InfoSec Program NIST compliance a comprehensive security program NIST does not address policies, procedures, third-party management, and other critical security controls You will likely have information or systems outside of CUI that you care about

15 Meshing With Your InfoSec Program SOC 2 Strong Passwords Risk Assessment Process PCI-DSS Password Strength Annual Risk Assessment Access Control Standards Periodic Risk Assessments

16 Meshing With Your InfoSec Program SOC 2 PCI-DSS ABC-AC-001 Strong Passwords Risk Assessment Process Password Strength Annual Risk Assessment ABC Company will require strong passwords. Access Control Standards Periodic Risk Assessments ABC-RA-001 ABC Company will conduct an annual organization-wide risk assessment.

17 Maintaining Compliance Compliance is an ongoing process that must be managed It is currently unclear how or when contractors will be audited Regardless, DoD expects you to become and remain compliant What processes need to exist to remain compliant?

18 External Influences Improvement Maintaining Compliance Test Plan Communicate Test Plan Analyze Execute Communicate Analyze Execute Information Security Program Time

19 Maintaining Compliance Desired State high Current State Trust Me Tell Me Show Me Prove To Me Effort low developing Maturity full

20 Maintaining Compliance Track each requirement. For example: NIST Control Control Family Requirement Control Description(s) Control Owner Access Control Limit unsuccessful logon attempts. Windows default domain policy is configured for to lockout accounts for 15 minutes after 5 unsuccessful logon attempts Steve Control Test Procedures Attempt to login with an invalid password and confirm a lockout of 15 minutes is in place (example) Test Frequency Supporting Documents Evidence Annual Control Record, Default Domain Policy Export Annual control test results

21 Maintaining Compliance Create a Security Plan Let risk be your guide! Make progress on your top risks each year Set calendar reminders Every security plan will be different Management Activities Scheduled Security Activities Control Tests

22 Maintaining Compliance Activities JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC Control Tests ID.AM - ID.RM PR.AC - PR.IP PR.MA - DE.DP RS.RP - RC.CO Committee Meeting Risk Assessment Security Plan Update Pen Test FW Ruleset Review Training X X X X X X Phishing Test X X X X IRP Table Top DR Table Top X X X X X

23 Vague Requirements How would you address these requirements? 3.4 CONFIGURATION MANAGEMENT Basic Security Requirements: Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles Establish and enforce security configuration settings for information technology products employed in organizational systems.

24 How would you address these requirements? Look to security best practice; Appendix D of maps to and ISO/IEC Assess the unique risk to your organization Get an expert opinion Vague Requirements

25 Not Enough Time Perform a Compliance Gap Assessment Take a prioritized approach to remediating the highest risk gaps first Establish a POA&M and be able to produce evidence of progress Don t reinvent the wheel For example, utilize CIS or Microsoft security baselines configurations to address Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles. Seek advice from the professionals

26 Tight Budget Some controls are going to require money Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts. Minimize the scope using segmentation and isolation. The effort and associated budget can be significantly reduced For instance, Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. If the organization can use firewall rules to isolate CUI to a network segment that does not have publicly accessible system components, this requirement becomes trivial to meet.

27 How TRUE Digital Security Can Help TRUE walks you through the process of becoming compliant Compliance Gap Assessments Customized control catalog for your unique environment utilizing expert guidance on best practices Risk Assessments (control ) Vulnerability Scanning/Penetration Testing (control ) 27

28 Free Bonus Materials me for: Free NIST Compliance Management Utility (Excel) Copy of these slides Free no-obligation consultation

29 Tinker & The Primes 2017 Innovating Together Protecting Controlled Unclassified Information Systems and Organizations Larry Findeiss Bid Assistance Coordinator Oklahoma s Procurement Technical Assistance Center (PTAC) Larry.Findeiss@tulsatech.edu Geoff Wilson Principal Security Consultant True Digital Security geoff.wilson@truedigitalsecurity.com X 103