03.01.17E Detection of Unsanctioned CUI

Statement

• Examine CUI for the presence of {{ insert: param, A.03.01.17E.ODP.01 }} when transferring information between different security domains.

• Prohibit the transfer of the CUI defined in 03.01.17E.a in accordance with the {{ insert: param, A.03.01.17E.ODP.02 }}.

Guidance

Unsanctioned information includes malicious code, information that is inappropriate for release from the source network, information that is not authorized to be stored or processed on the system, or executable code that could disrupt or harm services or systems on the destination network. 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

when transferring information between different security domains, information is examined for the presence of {{ insert: param, A.03.01.17E.ODP.01 }}.

Assessment objective

the transfer of CUI defined in 03.01.17E.a is prohibited in accordance with {{ insert: param, A.03.01.17E.ODP.02 }}.

Assessment method

• Access control policy information flow control policies procedures addressing information flow enforcement system design documentation system configuration settings and associated documentation list of unsanctioned information types and associated information system audit records system security plan other relevant documents or records

Assessment method

• Organizational personnel with information security responsibilities system developers

Assessment method

• Mechanisms implementing information flow enforcement policy

1. Vue d’ensemble

1.1 Références

1.2 Exigences identifiées

1.3 Réglementations associées

2. Exigences identifiées

3. Réglementations associées

Tickets liés

• NIST -

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