💼 SC-8(1) Transmission Confidentiality and Integrity | Cryptographic Protection

• Contextual name: 💼 SC-8(1) Transmission Confidentiality and Integrity | Cryptographic Protection
• ID: /frameworks/nist-sp-800-53-r5/sc/08/01
• Located in: 💼 SC-8 Transmission Confidentiality and Integrity

Description

Implement cryptographic mechanisms to [Selection (one or more): prevent unauthorized disclosure of information; detect changes to information] during transmission.

Similar

• Sections
  • /frameworks/aws-fsbp-v1.0.0/api-gateway/02
  • /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/09
  • /frameworks/aws-fsbp-v1.0.0/elasticache/05
  • /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/04
  • /frameworks/aws-fsbp-v1.0.0/es/03
  • /frameworks/aws-fsbp-v1.0.0/es/08
  • /frameworks/aws-fsbp-v1.0.0/msk/01
  • /frameworks/aws-fsbp-v1.0.0/opensearch/03
  • /frameworks/aws-fsbp-v1.0.0/opensearch/08
  • /frameworks/aws-fsbp-v1.0.0/redshift/02
  • /frameworks/aws-fsbp-v1.0.0/s3/05
• Internal
  • ID: dec-c-b79f2081

Similar Sections (Take Policies From)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [APIGateway.2] API Gateway REST API stages should be configured to use SSL certificates for backend authentication"		1	1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [CloudFront.3] CloudFront distributions should require encryption in transit
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [CloudFront.7] CloudFront distributions should use custom SSL/TLS certificates
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [CloudFront.8] CloudFront distributions should use SNI to serve HTTPS requests
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [CloudFront.10] CloudFront distributions should not use deprecated SSL protocols between edge locations and custom origins
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DMS.9] DMS endpoints should use SSL
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ElastiCache.5] ElastiCache replication groups should be encrypted in transit
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.1] Application Load Balancer should be configured to redirect all HTTP requests to HTTPS
💼 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 Manager
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.3] Classic Load Balancer listeners should be configured with HTTPS or TLS termination
💼 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 Configuration
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.17] Application and Network Load Balancers with listeners should use recommended security policies
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EMR.4] Amazon EMR security configurations should be encrypted in transit
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ES.3] Elasticsearch domains should encrypt data sent between nodes
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ES.8] Connections to Elasticsearch domains should be encrypted using the latest TLS security policy
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [MSK.1] MSK clusters should be encrypted in transit among broker nodes
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Opensearch.3] OpenSearch domains should encrypt data sent between nodes
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Opensearch.8] Connections to OpenSearch domains should be encrypted using the latest TLS security policy
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Redshift.2] Connections to Amazon Redshift clusters should be encrypted in transit
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.5] S3 general purpose buckets should require requests to use SSL		1	1

Similar Sections (Give Policies To)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 FedRAMP High Security Controls → 💼 SC-8(1) Cryptographic Protection (L)(M)(H)		6	10
💼 FedRAMP Low Security Controls → 💼 SC-8(1) Cryptographic Protection (L)(M)(H)			10

Sub Sections

Section	Sub Sections	Internal Rules	Policies	Flags

Policies (10)

Policy	Logic Count	Flags
📝 AWS API Gateway REST API Stage is not configured to use an SSL certificate for authentication 🟢	1	🟢 x6
📝 AWS S3 Bucket Policy is not set to deny HTTP requests 🟢	1	🟢 x6
📝 Azure App Service FTP deployments are not disabled 🟢	1	🟢 x6
📝 Azure App Service HTTPS Only configuration is not enabled 🟢	1	🟢 x6
📝 Azure MySQL Flexible Server require_secure_transport Parameter is not set to ON 🟢	1	🟢 x6
📝 Azure MySQL Flexible Server TLS Version is not set to TLS 1.2 🟢	1	🟢 x6
📝 Azure PostgreSQL Flexible Server require_secure_transport Parameter is not set to ON 🟢	1	🟢 x6
📝 Azure PostgreSQL Single Server Enforce SSL Connection is not set enabled 🟢	1	🟢 x6
📝 Azure Storage Account Minimum TLS Version is not set to TLS 1.2 or higher 🟢	1	🟢 x6
📝 Azure Storage Account Secure Transfer Required is not enabled 🟢	1	🟢 x6

Internal Rules

Rule	Policies	Flags
✉️ dec-x-14f5fc25	1
✉️ dec-x-75db76ad	1
✉️ dec-x-995424b7	2
✉️ dec-x-aeac09d6	1
✉️ dec-x-b94bd368	1
✉️ dec-x-c0a7793e	1
✉️ dec-x-d5fbfc40	1
✉️ dec-x-d95ea48b	1