Title

The ALG that is part of a CDS must enforce information flow control based on organization-defined metadata. (Cat II impact)

Discussion

Enforcing allowed information flows based on metadata enables simpler and more effective flow control. Metadata is information used to describe the characteristics of data. Metadata can include structural metadata describing data structures (e.g., data format, syntax, and semantics) or descriptive metadata describing data contents (e.g., age, location, telephone number). Information flow control regulates where information is allowed to travel within a network and between hosts, as opposed to who is allowed to access the information. Information flow enforcement mechanisms, such as cross domain solutions, compare metadata attached to the data and respond appropriately (e.g., allow, block, quarantine, or alert administrator). Organization-defined metadata used for flow control in CDS systems depend on the environment, data, and security boundaries. Organizations implementing CDS must follow the DoD-required process of testing, baselining, and risk assessment to ensure the rigor and accuracy necessary to rely upon a CDS for cross domain security.

Check Content

If the ALG is not part of a CDS, this is not applicable. Verify that policy filters exist that enforce traffic flow inbound and outbound across the controlled security boundary based on organization-defined metadata. If the ALG does not control traffic based on organization-defined metadata, this is a finding.

Fix Text

If the ALG is part of a CDS, configure inbound or outbound policy filters to enforce traffic flow across the controlled security boundary based on organization-defined metadata.

Additional Identifiers

Rule ID: SV-68735r1_rule

Vulnerability ID: V-54489

Group Title: SRG-NET-000280-ALG-000080

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.