140 likes | 150 Views
Get latest updates on CUI program, agency implementations, Federal Acquisition Regulation, and security safeguards. Learn about controlled environments and electronic barriers for protecting CUI.
E N D
Outline • A brief overview of the CUI program; • An update on agency implementation efforts; • The status and plans for a CUI Federal Acquisition Regulation Rule; • CUI Industry Day; and, • Time for Questions and Answers.
Information Security Reform • Clarifies what to protect • Defines safeguarding • Reinforces existing LRGWP • Promotes authorized information sharing
Implementation Efforts • Implementation is underway. • Most agencies will publish policy in the next 12-18 months. • After policy is published implementation will happen more quickly than prior to publication. • Pending Actions by CUI team: • Creation of CUI position description (PD) • Creation of CUI Registry Committee • Creation of new Training Videos
Federal Acquisition Regulation (FY19) “This FAR rule is necessary to ensure uniform implementation of the requirements of the CUI program in contracts across the government, thereby avoiding potentially inconsistent agency-level action.” –Unified Agenda Certification = Asserting compliance Documentation = Describing compliance Validation = Verifying compliance
Controlled Environments • Controlled environment is any area or space an authorized holder deems to have adequate physical or procedural controls (e.g., barriers and managed access controls) for protecting CUI from unauthorized access or disclosure. Reception Area used to control access to workspace.
Assessing physical environments • Going beyond gates, guns, and guards: Internal security • Who works in the space? • Who has access to the space during and after business hours? • Do individual workspaces (cubes & offices) have adequate safeguards to prevent access (locking cabinets, drawers, or overhead bins)? • Suitable for sensitive discussions?
Assessing electronic Environments Limit and control access to CUI within the workforce by establishing electronic barriers.
The New CUI Coversheet Changed from OF 901 to SF 901 This does not make the coversheet mandatory. It means that if you use a coversheet you must use this one (unless there is a specific one authorized or required by Law, regulation, or Governmentwide Policy) https://www.archives.gov/cui/additional-tools https://www.gsa.gov/cdnstatic/SF901-18a.pdf?forceDownload=1
Legacy Information and Markings All legacy information is not automatically CUI. Agencies must determine what legacy information qualifies as CUI Contractors do not have “legacy information” as such. Contractors should protect all information they have received in accordance with the contract that covers that information.
NIST SP 800-171 Rev 1 https://csrc.nist.gov/publications/detail/sp/800-171/rev-1/final
DOD Procurement toolbox https://dodprocurementtoolbox.com/site-pages/cybersecurity-dod-acquisition-regulations
Q6: When must the requirements in DFARS clause 252.204-7012 be implemented? A6: The requirements in DFARS clause 252.204-7012 must be implemented when covered defense information is processed, stored, or transits through an information system that is owned, or operated by or for, the contractor, or when performance of the contract involves operationally critical support. The solicitation/contract shall indicate when performance of the contract will involve, or is expected to involve, covered defense information or operationally critical support. All covered defense information provided to the contractor by the Government will be marked or otherwise identified in the contract, task order, or delivery order.
Upcoming CUI Events Next Webinar: CUI Program Update for Stakeholders July, 17 2019 (1-3 pm) Online If you missed it: NIST CUI Security Requirements Workshop • Recording can be found at: https://www.nist.gov/news-events/events/2018/10/controlled-unclassified-information-security-requirements-workshop