AC-4 Information Flow Enforcement
Control
Enforce approved authorizations for controlling the flow of information within the system and between connected systems based on [Assignment: information flow control policies].
Discussion
Information flow control regulates where information can travel within a system and between systems (in contrast to who is allowed to access the information) and without regard to subsequent accesses to that information. Flow control restrictions include blocking external traffic that claims to be from within the organization, keeping export-controlled information from being transmitted in the clear to the Internet, restricting web requests that are not from the internal web proxy server, and limiting information transfers between organizations based on data structures and content. Transferring information between organizations may require an agreement specifying how the information flow is enforced (see [CA-3](#ca-3) ). Transferring information between systems in different security or privacy domains with different security or privacy policies introduces the risk that such transfers violate one or more domain security or privacy policies. In such situations, information owners/stewards provide guidance at designated policy enforcement points between connected systems. Organizations consider mandating specific architectural solutions to enforce specific security and privacy policies. Enforcement includes prohibiting information transfers between connected systems (i.e., allowing access only), verifying write permissions before accepting information from another security or privacy domain or connected system, employing hardware mechanisms to enforce one-way information flows, and implementing trustworthy regrading mechanisms to reassign security or privacy attributes and labels.
Organizations commonly employ information flow control policies and enforcement mechanisms to control the flow of information between designated sources and destinations within systems and between connected systems. Flow control is based on the characteristics of the information and/or the information path. Enforcement occurs, for example, in boundary protection devices that employ rule sets or establish configuration settings that restrict system services, provide a packet-filtering capability based on header information, or provide a message-filtering capability based on message content. Organizations also consider the trustworthiness of filtering and/or inspection mechanisms (i.e., hardware, firmware, and software components) that are critical to information flow enforcement. Control enhancements 3 through 32 primarily address cross-domain solution needs that focus on more advanced filtering techniques, in-depth analysis, and stronger flow enforcement mechanisms implemented in cross-domain products, such as high-assurance guards. Such capabilities are generally not available in commercial off-the-shelf products. Information flow enforcement also applies to control plane traffic (e.g., routing and DNS).
Control enhancements (32)
- AC-4(1)Object Security and Privacy Attributes
- AC-4(2)Processing Domains
- AC-4(3)Dynamic Information Flow Control
- AC-4(4)Flow Control of Encrypted InformationHIGH
- AC-4(5)Embedded Data Types
- AC-4(6)Metadata
- AC-4(7)One-way Flow Mechanisms
- AC-4(8)Security and Privacy Policy Filters
- AC-4(9)Human Reviews
- AC-4(10)Enable and Disable Security or Privacy Policy Filters
- AC-4(11)Configuration of Security or Privacy Policy Filters
- AC-4(12)Data Type Identifiers
- AC-4(13)Decomposition into Policy-relevant Subcomponents
- AC-4(14)Security or Privacy Policy Filter Constraints
- AC-4(15)Detection of Unsanctioned Information
- AC-4(16)Information Transfers on Interconnected Systems
- AC-4(17)Domain Authentication
- AC-4(18)Security Attribute Binding
- AC-4(19)Validation of Metadata
- AC-4(20)Approved Solutions
- AC-4(21)Physical or Logical Separation of Information Flows
- AC-4(22)Access Only
- AC-4(23)Modify Non-releasable Information
- AC-4(24)Internal Normalized Format
- AC-4(25)Data Sanitization
- AC-4(26)Audit Filtering Actions
- AC-4(27)Redundant/Independent Filtering Mechanisms
- AC-4(28)Linear Filter Pipelines
- AC-4(29)Filter Orchestration Engines
- AC-4(30)Filter Mechanisms Using Multiple Processes
- AC-4(31)Failed Content Transfer Prevention
- AC-4(32)Process Requirements for Information Transfer
Related controls
Need AC-4 implemented and evidenced?
We assess where you stand against this control, document the gap, and build the remediation plan your auditor and your board will both accept.
Control catalog and framework text on this page is reproduced from official NIST publications — a public-domain work of the U.S. Government (17 U.S.C. §105). Maverc commentary, groupings, and readiness guidance are our own and are not part of any NIST publication.
