Skip to main content

💼 AC-4 Information Flow Enforcement

  • ID: /frameworks/nist-sp-800-53-r5/ac/04

Description​

Enforce approved authorizations for controlling the flow of information within the system and between connected systems based on [Assignment: organization-defined information flow control policies].

Similar​

  • Sections
    • /frameworks/aws-fsbp-v1.0.0/auto-scaling/05
    • /frameworks/aws-fsbp-v1.0.0/cloudfront/03
    • /frameworks/aws-fsbp-v1.0.0/cloudfront/07
    • /frameworks/aws-fsbp-v1.0.0/cloudfront/08
    • /frameworks/aws-fsbp-v1.0.0/cloudfront/10
    • /frameworks/aws-fsbp-v1.0.0/dms/01
    • /frameworks/aws-fsbp-v1.0.0/dms/09
    • /frameworks/aws-fsbp-v1.0.0/documentdb/03
    • /frameworks/aws-fsbp-v1.0.0/ec2/01
    • /frameworks/aws-fsbp-v1.0.0/ec2/02
    • /frameworks/aws-fsbp-v1.0.0/ec2/09
    • /frameworks/aws-fsbp-v1.0.0/ec2/10
    • /frameworks/aws-fsbp-v1.0.0/ec2/15
    • /frameworks/aws-fsbp-v1.0.0/ec2/18
    • /frameworks/aws-fsbp-v1.0.0/ec2/19
    • /frameworks/aws-fsbp-v1.0.0/ec2/25
    • /frameworks/aws-fsbp-v1.0.0/ec2/55
    • /frameworks/aws-fsbp-v1.0.0/ec2/56
    • /frameworks/aws-fsbp-v1.0.0/ec2/57
    • /frameworks/aws-fsbp-v1.0.0/ec2/58
    • /frameworks/aws-fsbp-v1.0.0/ec2/60
    • /frameworks/aws-fsbp-v1.0.0/ecs/02
    • /frameworks/aws-fsbp-v1.0.0/eks/01
    • /frameworks/aws-fsbp-v1.0.0/elasticache/05
    • /frameworks/aws-fsbp-v1.0.0/elasticache/07
    • /frameworks/aws-fsbp-v1.0.0/elb/01
    • /frameworks/aws-fsbp-v1.0.0/elb/02
    • /frameworks/aws-fsbp-v1.0.0/elb/03
    • /frameworks/aws-fsbp-v1.0.0/elb/08
    • /frameworks/aws-fsbp-v1.0.0/elb/17
    • /frameworks/aws-fsbp-v1.0.0/emr/01
    • /frameworks/aws-fsbp-v1.0.0/emr/02
    • /frameworks/aws-fsbp-v1.0.0/emr/04
    • /frameworks/aws-fsbp-v1.0.0/es/02
    • /frameworks/aws-fsbp-v1.0.0/es/03
    • /frameworks/aws-fsbp-v1.0.0/es/08
    • /frameworks/aws-fsbp-v1.0.0/lambda/01
    • /frameworks/aws-fsbp-v1.0.0/msk/01
    • /frameworks/aws-fsbp-v1.0.0/neptune/03
    • /frameworks/aws-fsbp-v1.0.0/opensearch/02
    • /frameworks/aws-fsbp-v1.0.0/opensearch/03
    • /frameworks/aws-fsbp-v1.0.0/opensearch/08
    • /frameworks/aws-fsbp-v1.0.0/rds/01
    • /frameworks/aws-fsbp-v1.0.0/rds/02
    • /frameworks/aws-fsbp-v1.0.0/rds/23
    • /frameworks/aws-fsbp-v1.0.0/redshift/01
    • /frameworks/aws-fsbp-v1.0.0/redshift/02
    • /frameworks/aws-fsbp-v1.0.0/redshift/07
    • /frameworks/aws-fsbp-v1.0.0/s3/01
    • /frameworks/aws-fsbp-v1.0.0/s3/02
    • /frameworks/aws-fsbp-v1.0.0/s3/03
    • /frameworks/aws-fsbp-v1.0.0/s3/05
    • /frameworks/aws-fsbp-v1.0.0/s3/19
    • /frameworks/aws-fsbp-v1.0.0/sagemaker/01
    • /frameworks/aws-fsbp-v1.0.0/sagemaker/02
    • /frameworks/aws-fsbp-v1.0.0/service-catalog/01
    • /frameworks/aws-fsbp-v1.0.0/ssm/04
  • Internal
    • ID: dec-c-14fd0afc

Similar Sections (Take Policies From)​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [AutoScaling.5] Amazon EC2 instances launched using Auto Scaling group launch configurations should not have Public IP addresses11no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [CloudFront.3] CloudFront distributions should require encryption in transit11no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [CloudFront.7] CloudFront distributions should use custom SSL/TLS certificates11no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [CloudFront.8] CloudFront distributions should use SNI to serve HTTPS requests11no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [CloudFront.10] CloudFront distributions should not use deprecated SSL protocols between edge locations and custom origins11no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DMS.1] Database Migration Service replication instances should not be public11no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DMS.9] DMS endpoints should use SSL11no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DocumentDB.3] Amazon DocumentDB manual cluster snapshots should not be publicno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.1] Amazon EBS snapshots should not be publicly restorable1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.2] VPC default security groups should not allow inbound or outbound traffic1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.9] Amazon EC2 instances should not have a public IPv4 address1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.10] Amazon EC2 should be configured to use VPC endpoints that are created for the Amazon EC2 service1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.15] Amazon EC2 subnets should not automatically assign public IP addresses1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.18] Security groups should only allow unrestricted incoming traffic for authorized portsno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.19] Security groups should not allow unrestricted access to ports with high risk10no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.25] Amazon EC2 launch templates should not assign public IPs to network interfacesno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.55] VPCs should be configured with an interface endpoint for ECR APIno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.56] VPCs should be configured with an interface endpoint for Docker Registryno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.57] VPCs should be configured with an interface endpoint for Systems Managerno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.58] VPCs should be configured with an interface endpoint for Systems Manager Incident Manager Contactsno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.60] VPCs should be configured with an interface endpoint for Systems Manager Incident Managerno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ECS.2] ECS services should not have public IP addresses assigned to them automaticallyno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EKS.1] EKS cluster endpoints should not be publicly accessibleno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ElastiCache.5] ElastiCache replication groups should be encrypted in transit1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ElastiCache.7] ElastiCache clusters should not use the default subnet groupno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.1] Application Load Balancer should be configured to redirect all HTTP requests to HTTPSno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.2] Classic Load Balancers with SSL/HTTPS listeners should use a certificate provided by AWS Certificate Managerno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.3] Classic Load Balancer listeners should be configured with HTTPS or TLS terminationno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.8] Classic Load Balancers with SSL listeners should use a predefined security policy that has strong AWS Configurationno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.17] Application and Network Load Balancers with listeners should use recommended security policiesno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EMR.1] Amazon EMR cluster primary nodes should not have public IP addressesno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EMR.2] Amazon EMR block public access setting should be enabledno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EMR.4] Amazon EMR security configurations should be encrypted in transitno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ES.2] Elasticsearch domains should not be publicly accessible1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ES.3] Elasticsearch domains should encrypt data sent between nodes1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ES.8] Connections to Elasticsearch domains should be encrypted using the latest TLS security policyno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Lambda.1] Lambda function policies should prohibit public accessno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [MSK.1] MSK clusters should be encrypted in transit among broker nodesno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Neptune.3] Neptune DB cluster snapshots should not be publicno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Opensearch.2] OpenSearch domains should not be publicly accessible1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Opensearch.3] OpenSearch domains should encrypt data sent between nodes1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Opensearch.8] Connections to OpenSearch domains should be encrypted using the latest TLS security policyno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.1] RDS snapshot should be private11no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.2] RDS DB Instances should prohibit public access, as determined by the PubliclyAccessible configuration11no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.23] RDS instances should not use a database engine default port11no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Redshift.1] Amazon Redshift clusters should prohibit public accessno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Redshift.2] Connections to Amazon Redshift clusters should be encrypted in transit1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Redshift.7] Redshift clusters should use enhanced VPC routingno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.1] S3 general purpose buckets should have block public access settings enabled1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.2] S3 general purpose buckets should block public read access2no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.3] S3 general purpose buckets should block public write access2no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.5] S3 general purpose buckets should require requests to use SSL11no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.19] S3 access points should have block public access settings enabled1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [SageMaker.1] Amazon SageMaker AI notebook instances should not have direct internet accessno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [SageMaker.2] SageMaker AI notebook instances should be launched in a custom VPCno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ServiceCatalog.1] Service Catalog portfolios should be shared within an AWS organization onlyno data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [SSM.4] SSM documents should not be publicno data

Similar Sections (Give Policies To)​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 FedRAMP High Security Controls → 💼 AC-4 Information Flow Enforcement (M)(H)23789no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events149no data
💼 NIST CSF v2.0 → 💼 ID.AM-03: Representations of the organization's authorized network communication and internal and external network data flows are maintained76no data
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected156no data
💼 NIST CSF v2.0 → 💼 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage103no data

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 AC-4(1) Information Flow Enforcement _ Object Security and Privacy Attributesno data
💼 AC-4(2) Information Flow Enforcement _ Processing Domains3133no data
💼 AC-4(3) Information Flow Enforcement _ Dynamic Information Flow Controlno data
💼 AC-4(4) Information Flow Enforcement _ Flow Control of Encrypted Informationno data
💼 AC-4(5) Information Flow Enforcement _ Embedded Data Types11no data
💼 AC-4(6) Information Flow Enforcement _ Metadatano data
💼 AC-4(7) Information Flow Enforcement _ One-way Flow Mechanismsno data
💼 AC-4(8) Information Flow Enforcement _ Security and Privacy Policy Filtersno data
💼 AC-4(9) Information Flow Enforcement _ Human Reviewsno data
💼 AC-4(10) Information Flow Enforcement _ Enable and Disable Security or Privacy Policy Filtersno data
💼 AC-4(11) Information Flow Enforcement _ Configuration of Security or Privacy Policy Filtersno data
💼 AC-4(12) Information Flow Enforcement _ Data Type Identifiersno data
💼 AC-4(13) Information Flow Enforcement _ Decomposition into Policy-relevant Subcomponentsno data
💼 AC-4(14) Information Flow Enforcement _ Security or Privacy Policy Filter Constraints22no data
💼 AC-4(15) Information Flow Enforcement _ Detection of Unsanctioned Information910no data
💼 AC-4(16) Information Flow Enforcement _ Information Transfers on Interconnected Systemsno data
💼 AC-4(17) Information Flow Enforcement _ Domain Authenticationno data
💼 AC-4(18) Information Flow Enforcement _ Security Attribute Bindingno data
💼 AC-4(19) Information Flow Enforcement _ Validation of Metadatano data
💼 AC-4(20) Information Flow Enforcement _ Approved Solutionsno data
💼 AC-4(21) Information Flow Enforcement _ Physical or Logical Separation of Information Flows3752no data
💼 AC-4(22) Information Flow Enforcement _ Access Onlyno data
💼 AC-4(23) Information Flow Enforcement _ Modify Non-releasable Informationno data
💼 AC-4(24) Information Flow Enforcement _ Internal Normalized Formatno data
💼 AC-4(25) Information Flow Enforcement _ Data Sanitizationno data
💼 AC-4(26) Information Flow Enforcement _ Audit Filtering Actions9no data
💼 AC-4(27) Information Flow Enforcement _ Redundant/independent Filtering Mechanismsno data
💼 AC-4(28) Information Flow Enforcement _ Linear Filter Pipelinesno data
💼 AC-4(29) Information Flow Enforcement _ Filter Orchestration Enginesno data
💼 AC-4(30) Information Flow Enforcement _ Filter Mechanisms Using Multiple Processesno data
💼 AC-4(31) Information Flow Enforcement _ Failed Content Transfer Preventionno data
💼 AC-4(32) Information Flow Enforcement _ Process Requirements for Information Transferno data

Policies (39)​

PolicyLogic CountFlagsCompliance
🛡️ AWS API Gateway API Route Authorization Type is not configured🟢1🟢 x6no data
🛡️ AWS API Gateway REST API Stage is not configured to use an SSL certificate for authentication🟢1🟢 x6no data
🛡️ AWS CloudFront Web Distribution Cache Behaviors allow unencrypted traffic🟢1🟢 x6no data
🛡️ AWS CloudFront Web Distribution uses default SSL/TLS certificate🟢1🟢 x6no data
🛡️ AWS CloudFront Web Distribution uses Dedicated IP for SSL🟢1🟢 x6no data
🛡️ AWS CloudFront Web Distribution uses outdated SSL protocols with Custom Origins🟢1🟢 x6no data
🛡️ AWS DMS Endpoint doesn't use SSL🟢1🟢 x6no data
🛡️ AWS DMS Replication Instance is publicly accessible🟢1🟢 x6no data
🛡️ AWS EBS Snapshot is publicly accessible🟢1🟢 x6no data
🛡️ AWS EC2 Auto Scaling Group behind ELB assigns public IP to instances🟢1🟢 x6no data
🛡️ AWS EC2 Default Security Group does not restrict all traffic🟢1🟢 x6no data
🛡️ AWS EC2 Instance with an auto-assigned public IP address is in a default subnet🟢1🟢 x6no data
🛡️ AWS EC2 Security Group allows public IPv4 (0.0.0.0/0) access to admin ports🟢1🟢 x6no data
🛡️ AWS EC2 Security Group allows public IPv6 (::/0) access to admin ports🟢1🟢 x6no data
🛡️ AWS EC2 Security Group allows unrestricted CIFS traffic🟢1🟢 x6no data
🛡️ AWS EC2 Security Group allows unrestricted FTP traffic🟢1🟢 x6no data
🛡️ AWS EC2 Security Group allows unrestricted RPC traffic🟢1🟢 x6no data
🛡️ AWS EC2 Security Group allows unrestricted SMTP traffic🟢1🟢 x6no data
🛡️ AWS EC2 Security Group allows unrestricted traffic to MSSQL🟢1🟢 x6no data
🛡️ AWS EC2 Security Group allows unrestricted traffic to MySQL🟢1🟢 x6no data
🛡️ AWS EC2 Security Group allows unrestricted traffic to PostgreSQL🟢1🟢 x6no data
🛡️ AWS EC2 Security Group allows unrestricted Telnet traffic🟢1🟢 x6no data
🛡️ AWS ElastiCache Replication Group is not encrypted in-transit🟢1🟢 x6no data
🛡️ AWS OpenSearch Domain has a public endpoint🟢1🟢 x6no data
🛡️ AWS OpenSearch Domain Node To Node Encryption is not enabled🟢1🟢 x6no data
🛡️ AWS RDS Instance is publicly accessible and in an unrestricted public subnet🟢1🟢 x6no data
🛡️ AWS RDS Instance uses default endpoint port🟢1🟢 x6no data
🛡️ AWS RDS Snapshot is publicly accessible🟢1🟢 x6no data
🛡️ AWS Redshift Cluster is not required to use encryption in transit🟢1🟢 x6no data
🛡️ AWS S3 Access Point is not configured to block public access🟢1🟢 x6no data
🛡️ AWS S3 Bucket ACL allows public read or write access🟢1🟢 x6no data
🛡️ AWS S3 Bucket is not configured to block public access🟢1🟢 x6no data
🛡️ AWS S3 Bucket Policy allows public read or write access🟢1🟢 x6no data
🛡️ AWS S3 Bucket Policy is not set to deny HTTP requests🟢1🟢 x6no data
🛡️ AWS VPC is not configured with a VPC Endpoint for Amazon EC2 service🟢1🟢 x6no data
🛡️ AWS VPC Subnet Map Public IP On Launch is enabled🟢1🟢 x6no data
🛡️ Azure App Service Authentication is disabled and Basic Authentication is enabled🟢1🟢 x6no data
🛡️ Azure App Service Basic Authentication is enabled🟢⚪🟢 x2, ⚪ x1no data
🛡️ Azure Subscription Network Watcher is not enabled in every available region🟢1🟢 x6no data

Internal Rules​

RulePoliciesFlags
✉️ dec-x-5fa71eac1
✉️ dec-x-629108da1
✉️ dec-x-843426501
✉️ dec-x-ca52f63a2
✉️ dec-x-d5fbfc401
✉️ dec-x-d9d39f211
✉️ dec-x-e02b5fdd1
✉️ dec-x-ec547a7c1
✉️ dec-x-f937c35f1