03.01.12E Physical or Logical Separation of CUI Flows

Statement

Separate CUI flows logically or physically using {{ insert: param, A.03.01.12E.ODP.01 }}.

Guidance

Enforcing the separation of information flows associated with defined types of data can enhance protection by ensuring that CUI is not commingled while in transit and by enabling flow control by transmission paths that are not otherwise achievable. This requirement enhances SP 800-171 requirement 03.01.03.

Statement

• (includes preempt) Ensure that the threat event does not have an impact.

  • Reduce likelihood of occurrence and/or reduce likelihood of impact.

  • The adversary’s efforts or resources cannot be applied or are wasted.

• (includes exert) Make it more difficult for threat events to cause adverse impacts or consequences.

  • Reduce likelihood of impact and reduce level of impact.

  • Adversary activities are restricted in scope, fail to achieve full effect, do not take place in accordance with adversary timeline, or require greater resources than adversary had planned.

Assessment objective

CUI flows are logically or physically separated using {{ insert: param, A.03.01.12E.ODP.01 }}.

Assessment method

• Information flow enforcement policy information flow control policies procedures addressing information flow enforcement system design documentation system configuration settings and associated documentation list of required separation of information flows by information types list of mechanisms and/or techniques used to logically or physically separate information flows system audit records system security plan other relevant documents or records

Assessment method

• Organizational personnel with information flow enforcement responsibilities system/network administrators organizational personnel with information security responsibilities system developers

Assessment method

• Mechanisms implementing information flow enforcement functions

1. Visão geral

1.1 Referências

1.2 Requisitos identificados

1.3 Regulamentos relacionados

2. Requisitos identificados

3. Regulamentos relacionados

Pedidos ligados

• NIST -

  https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final