AWS Well-Architected Security Pillar
Data Protection

AWS Well-Architected Security Pillar SEC09-BP03: Authenticate network communications

Confirm who is on each end of traffic between services, applications and users by choosing protocols with built-in authentication, TLS or IPsec for example.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 39 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 4 controls

FedRAMP High · 3 controls

  • IA-2(8) Access to Accounts Replay Resistant
  • IA-3 Device Identification and Authentication
  • SC-23 Session Authenticity

FedRAMP Moderate · 3 controls

  • IA-2(8) Access to Accounts Replay Resistant
  • IA-3 Device Identification and Authentication
  • SC-23 Session Authenticity

NIST SP 800-171 Rev 3 · 3 controls

  • 03.05.02 Device Identification and Authentication
  • 03.13.08 Transmission Confidentiality and Integrity
  • 03.13.15 Session Authenticity
  • ANSSI-HYG-21 Use Secure Protocols Wherever They Exist
  • ANSSI-HYG-32 Secure the Network Connection of Devices Used for Mobile Working

C5 (Germany) · 2 controls

  • C5-COS-02 Security requirements for connections in the Cloud Service Provider's network
  • C5-CRY-02 Encryption of data for transmission (transport encryption)

HIPAA Security Rule · 2 controls

ISO 27001:2022 · 2 controls

  • 8.21 Security of network services
  • 8.5 Secure authentication

ISO 27002:2022 · 2 controls

  • 8.21 Security of network services
  • 8.5 Secure authentication

ISO 27701:2019 · 2 controls

  • 7.4.9 PII transmission controls
  • 8.4.3 PII transmission controls

NIST SP 800-161 Rev 1 · 2 controls

  • 161R1-IA-3 Device Identification and Authentication
  • 161R1-IA-9 Service Identification and Authentication

NIST SP 800-66 Rev 2 · 2 controls

  • IM-4 Authenticate server and services

CIS Controls v8 · 1 control

  • CIS-12.6 Use of Secure Network Management and Communication Protocols

CMMC 2.0 · 1 control

PCI DSS 4.0 · 1 control

  • 4.2.1 4.2.1 Strong cryptography safeguards PAN over public networks

SOC 2 · 1 control

  • SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Data Protection

You are reading one control. How much of AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC09-BP03 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 39 it maps to, and the evidence behind each claim, over MCP and REST.