AC-4—Information Flow Enforcement
>Control Description
>DoD Impact Level Requirements
No specific parameter values or requirements for this impact level.
>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).
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).
>Programmatic Queries
Related Services
CLI Commands
aws ec2 describe-flow-logsaws ec2 describe-security-groups --query 'SecurityGroups[*].{ID:GroupId,Name:GroupName,Rules:IpPermissions}'aws ec2 describe-network-aclsaws ec2 describe-vpc-peering-connections>Related Controls
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of AC-4 (Information Flow Enforcement)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring AC-4?
- •How frequently is the AC-4 policy reviewed and updated, and what triggers policy changes?
- •What training or awareness programs ensure personnel understand their responsibilities related to AC-4?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce AC-4 requirements.
- •What automated tools, systems, or technologies are deployed to implement AC-4?
- •How is AC-4 integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce AC-4 requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of AC-4?
- •What audit logs, records, reports, or monitoring data validate AC-4 compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of AC-4 effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate AC-4 compliance?
Ask AI
Configure your API key to use AI features.