💼 SC-36 Distributed Processing and Storage

• Contextual name: 💼 SC-36 Distributed Processing and Storage
• ID: /frameworks/nist-sp-800-53-r5/sc/36
• Located in: 💼 SC System And Communications Protection

Description

Distribute the following processing and storage components across multiple [Selection: physical locations; logical domains]: [Assignment: organization-defined processing and storage components].

Similar

• Sections
  • /frameworks/aws-fsbp-v1.0.0/auto-scaling/02
  • /frameworks/aws-fsbp-v1.0.0/auto-scaling/06
  • /frameworks/aws-fsbp-v1.0.0/cloudfront/04
  • /frameworks/aws-fsbp-v1.0.0/dynamodb/01
  • /frameworks/aws-fsbp-v1.0.0/ec2/20
  • /frameworks/aws-fsbp-v1.0.0/elasticache/03
  • /frameworks/aws-fsbp-v1.0.0/elb/09
  • /frameworks/aws-fsbp-v1.0.0/elb/10
  • /frameworks/aws-fsbp-v1.0.0/elb/13
  • /frameworks/aws-fsbp-v1.0.0/es/06
  • /frameworks/aws-fsbp-v1.0.0/es/07
  • /frameworks/aws-fsbp-v1.0.0/lambda/05
  • /frameworks/aws-fsbp-v1.0.0/opensearch/06
  • /frameworks/aws-fsbp-v1.0.0/rds/05
  • /frameworks/aws-fsbp-v1.0.0/rds/15
  • /frameworks/aws-fsbp-v1.0.0/sagemaker/04
• Internal
  • ID: dec-c-ffb23b69

Similar Sections (Take Policies From)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [AutoScaling.2] Amazon EC2 Auto Scaling group should cover multiple Availability Zones
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [AutoScaling.6] Auto Scaling groups should use multiple instance types in multiple Availability Zones
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [CloudFront.4] CloudFront distributions should have origin failover configured
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DynamoDB.1] DynamoDB tables should automatically scale capacity with demand
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.20] Both VPN tunnels for an AWS Site-to-Site VPN connection should be up
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ElastiCache.3] ElastiCache replication groups should have automatic failover enabled
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.9] Classic Load Balancers should have cross-zone load balancing enabled
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.10] Classic Load Balancer should span multiple Availability Zones
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.13] Application, Network and Gateway Load Balancers should span multiple Availability Zones
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ES.6] Elasticsearch domains should have at least three data nodes
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ES.7] Elasticsearch domains should be configured with at least three dedicated master nodes
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Lambda.5] VPC Lambda functions should operate in multiple Availability Zones
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Opensearch.6] OpenSearch domains should have at least three data nodes
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.5] RDS DB instances should be configured with multiple Availability Zones		1	1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.15] RDS DB clusters should be configured for multiple Availability Zones
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [SageMaker.4] SageMaker AI endpoint production variants should have an initial instance count greater than 1

Similar Sections (Give Policies To)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 NIST CSF v2.0 → 💼 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations			5

Sub Sections

Section	Sub Sections	Internal Rules	Policies	Flags
💼 SC-36(1) Distributed Processing and Storage _ Polling Techniques
💼 SC-36(2) Distributed Processing and Storage _ Synchronization

Policies (1)

Policy	Logic Count	Flags
📝 AWS RDS Instance Multi-AZ Deployment is not enabled 🟢	1	🟢 x6