Skip to main content

💼 AC-4(21) Information Flow Enforcement | Physical or Logical Separation of Information Flows

  • Contextual name: 💼 AC-4(21) Information Flow Enforcement | Physical or Logical Separation of Information Flows
  • ID: /frameworks/nist-sp-800-53-r5/ac/04/21
  • Located in: 💼 AC-4 Information Flow Enforcement

Description

Separate information flows logically or physically using [Assignment: organization-defined mechanisms and/or techniques] to accomplish [Assignment: organization-defined required separations by types of information].

Similar

  • Sections
    • /frameworks/aws-fsbp-v1.0.0/api-gateway/04
    • /frameworks/aws-fsbp-v1.0.0/auto-scaling/05
    • /frameworks/aws-fsbp-v1.0.0/cloudfront/06
    • /frameworks/aws-fsbp-v1.0.0/dms/01
    • /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/17
    • /frameworks/aws-fsbp-v1.0.0/ec2/18
    • /frameworks/aws-fsbp-v1.0.0/ec2/19
    • /frameworks/aws-fsbp-v1.0.0/ec2/21
    • /frameworks/aws-fsbp-v1.0.0/ec2/23
    • /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/07
    • /frameworks/aws-fsbp-v1.0.0/elb/12
    • /frameworks/aws-fsbp-v1.0.0/elb/14
    • /frameworks/aws-fsbp-v1.0.0/emr/01
    • /frameworks/aws-fsbp-v1.0.0/emr/02
    • /frameworks/aws-fsbp-v1.0.0/es/02
    • /frameworks/aws-fsbp-v1.0.0/lambda/01
    • /frameworks/aws-fsbp-v1.0.0/neptune/03
    • /frameworks/aws-fsbp-v1.0.0/network-firewall/06
    • /frameworks/aws-fsbp-v1.0.0/opensearch/02
    • /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/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/19
    • /frameworks/aws-fsbp-v1.0.0/sagemaker/01
    • /frameworks/aws-fsbp-v1.0.0/sagemaker/02
    • /frameworks/aws-fsbp-v1.0.0/ssm/04
    • /frameworks/aws-fsbp-v1.0.0/waf/02
    • /frameworks/aws-fsbp-v1.0.0/waf/03
    • /frameworks/aws-fsbp-v1.0.0/waf/08
  • Internal
    • ID: dec-c-0c06ffcb

Similar Sections (Take Policies From)

SectionSub SectionsInternal RulesPoliciesFlags
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [APIGateway.4] API Gateway should be associated with a WAF Web ACL11
💼 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 addresses11
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [CloudFront.6] CloudFront distributions should have WAF enabled
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DMS.1] Database Migration Service replication instances should not be public11
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DocumentDB.3] Amazon DocumentDB manual cluster snapshots should not be public
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.1] Amazon EBS snapshots should not be publicly restorable1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.2] VPC default security groups should not allow inbound or outbound traffic1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.9] Amazon EC2 instances should not have a public IPv4 address1
💼 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 service1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.15] Amazon EC2 subnets should not automatically assign public IP addresses1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.17] Amazon EC2 instances should not use multiple ENIs
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.18] Security groups should only allow unrestricted incoming traffic for authorized ports
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.19] Security groups should not allow unrestricted access to ports with high risk10
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.21] Network ACLs should not allow ingress from 0.0.0.0/0 to port 22 or port 33891
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.23] Amazon EC2 Transit Gateways should not automatically accept VPC attachment requests1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.25] Amazon EC2 launch templates should not assign public IPs to network interfaces
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.55] VPCs should be configured with an interface endpoint for ECR API
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.56] VPCs should be configured with an interface endpoint for Docker Registry
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.57] VPCs should be configured with an interface endpoint for Systems Manager
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.58] VPCs should be configured with an interface endpoint for Systems Manager Incident Manager Contacts
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.60] VPCs should be configured with an interface endpoint for Systems Manager Incident Manager
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ECS.2] ECS services should not have public IP addresses assigned to them automatically
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EKS.1] EKS cluster endpoints should not be publicly accessible
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ElastiCache.7] ElastiCache clusters should not use the default subnet group
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.12] Application Load Balancer should be configured with defensive or strictest desync mitigation mode
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.14] Classic Load Balancer should be configured with defensive or strictest desync mitigation mode
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EMR.1] Amazon EMR cluster primary nodes should not have public IP addresses
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EMR.2] Amazon EMR block public access setting should be enabled
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ES.2] Elasticsearch domains should not be publicly accessible
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Lambda.1] Lambda function policies should prohibit public access
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Neptune.3] Neptune DB cluster snapshots should not be public
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [NetworkFirewall.6] Stateless Network Firewall rule group should not be empty
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Opensearch.2] OpenSearch domains should not be publicly accessible
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.1] RDS snapshot should be private11
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.2] RDS DB Instances should prohibit public access, as determined by the PubliclyAccessible configuration11
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.23] RDS instances should not use a database engine default port11
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Redshift.1] Amazon Redshift clusters should prohibit public access
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Redshift.7] Redshift clusters should use enhanced VPC routing
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.1] S3 general purpose buckets should have block public access settings enabled1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.2] S3 general purpose buckets should block public read access
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.3] S3 general purpose buckets should block public write access
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.19] S3 access points should have block public access settings enabled
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [SageMaker.1] Amazon SageMaker AI notebook instances should not have direct internet access
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [SageMaker.2] SageMaker AI notebook instances should be launched in a custom VPC
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [SSM.4] SSM documents should not be public
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [WAF.2] AWS WAF Classic Regional rules should have at least one condition
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [WAF.3] AWS WAF Classic Regional rule groups should have at least one rule
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [WAF.8] AWS WAF Classic global web ACLs should have at least one rule or rule group

Similar Sections (Give Policies To)

SectionSub SectionsInternal RulesPoliciesFlags
💼 FedRAMP High Security Controls → 💼 AC-4(21) Physical or Logical Separation of Information Flows (M)(H)1146

Sub Sections

SectionSub SectionsInternal RulesPoliciesFlags

Policies (46)

PolicyLogic CountFlags
📝 AWS API Gateway REST API Stage is not associated with a WAF Web ACL 🟢1🟢 x6
📝 AWS CloudFront Web Distribution Default Root Object is not configured 🟢1🟢 x6
📝 AWS DMS Replication Instance is publicly accessible 🟢1🟢 x6
📝 AWS EBS Snapshot is publicly accessible 🟢1🟢 x6
📝 AWS EC2 Auto Scaling Group behind ELB assigns public IP to instances 🟢1🟢 x6
📝 AWS EC2 Default Security Group does not restrict all traffic 🟢1🟢 x6
📝 AWS EC2 Instance with an auto-assigned public IP address is in a default subnet 🟢1🟢 x6
📝 AWS EC2 Security Group allows public IPv4 (0.0.0.0/0) access to admin ports 🟢1🟢 x6
📝 AWS EC2 Security Group allows public IPv6 (::/0) access to admin ports 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted CIFS traffic 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted DNS traffic 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted FTP traffic 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted ICMP traffic 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted NetBIOS traffic 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted RPC traffic 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted SMTP traffic 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted traffic to MongoDB 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted traffic to MSSQL 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted traffic to MySQL 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted traffic to Oracle DBMS 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted traffic to PostgreSQL 🟢1🟢 x6
📝 AWS EC2 Security Group allows unrestricted Telnet traffic 🟢1🟢 x6
📝 AWS IAM Policy allows full administrative privileges 🟢1🟢 x6
📝 AWS RDS Instance is publicly accessible and in an unrestricted public subnet 🟢1🟢 x6
📝 AWS RDS Instance uses default endpoint port 🟢1🟢 x6
📝 AWS RDS Snapshot is publicly accessible 🟢1🟢 x6
📝 AWS S3 Bucket is not configured to block public access 🟢1🟢 x6
📝 AWS VPC is not configured with a VPC Endpoint for Amazon EC2 service 🟢1🟢 x6
📝 AWS VPC Network ACL exposes admin ports to public internet ports 🟢1🟢 x6
📝 AWS VPC Subnet Map Public IP On Launch is enabled 🟢1🟢 x6
📝 AWS VPC Transit Gateway Auto Accept Shared Attachments is enabled 🟢1🟢 x6
📝 Azure Cosmos DB Account Private Endpoints are not used 🟢1🟢 x6
📝 Azure Cosmos DB Account Virtual Network Filter is not enabled 🟢1🟢 x6
📝 Azure Cosmos DB Entra ID Client Authentication is not used 🟢🟢 x3
📝 Azure Key Vault Private Endpoints are not used 🟢1🟢 x6
📝 Azure Managed Disk Public Network Access is not disabled 🟢1🟢 x6
📝 Azure Network Security Group allows public access to HTTP(S) ports 🟢1🟢 x6
📝 Azure Network Security Group allows public access to RDP port 🟢1🟢 x6
📝 Azure Network Security Group allows public access to SSH port 🟢1🟢 x6
📝 Azure PostgreSQL Flexible Server Firewall Rules allow access to Azure services 🟢1🟢 x6
📝 Azure SQL Database allows ingress from 0.0.0.0/0 (ANY IP) 🟢1🟢 x6
📝 Azure SQL Server Public Network Access is not disabled 🟢1🟢 x6
📝 Azure Storage Account Allow Blob Anonymous Access is enabled 🟢1🟢 x6
📝 Azure Storage Account Cross Tenant Replication is enabled 🟢1🟢 x6
📝 Azure Storage Account Default Network Access Rule is not set to Deny 🟢1🟢 x6
📝 Azure Storage Account Private Endpoints are not used 🟢1🟢 x6

Internal Rules

RulePoliciesFlags
✉️ dec-x-3e379c671
✉️ dec-x-4c15a09f1
✉️ dec-x-4f30f24e1
✉️ dec-x-4f944d131
✉️ dec-x-6eab9b881
✉️ dec-x-11c3009f1
✉️ dec-x-14bf01f31
✉️ dec-x-42a090841
✉️ dec-x-46a83a301
✉️ dec-x-157aa4b91
✉️ dec-x-0289e9c91
✉️ dec-x-293ab45b1
✉️ dec-x-397dd59e1
✉️ dec-x-599c86b41
✉️ dec-x-807a37c91
✉️ dec-x-66358b451
✉️ dec-x-083928f51
✉️ dec-x-637372481
✉️ dec-x-843426501
✉️ dec-x-a7d8f0e71
✉️ dec-x-b4d3d9dc2
✉️ dec-x-b17c005c1
✉️ dec-x-b33429051
✉️ dec-x-bcae85fb2
✉️ dec-x-bf1f13f61
✉️ dec-x-bfdadcc41
✉️ dec-x-ca1c0c0d1
✉️ dec-x-d127f4071
✉️ dec-x-e02b5fdd1
✉️ dec-x-ec547a7c1
✉️ dec-x-ecd99f881
✉️ dec-x-f4cc003a1
✉️ dec-x-f12d78aa1
✉️ dec-x-f937c35f1
✉️ dec-z-c82c9f971
✉️ dec-z-dbeeed9f1
✉️ dec-z-f778950c1