AWS Well-Architected Security Pillar
Infrastructure Protection

AWS Well-Architected Security Pillar SEC05-BP03: Implement inspection-based protection

Use deep packet inspection through AWS Network Firewall, Gateway Load Balancer with third-party appliances or service mesh to inspect and filter traffic for threats.

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

What else in your programme already covers this

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

FedRAMP High · 7 controls

  • SC-5 Denial-of-Service Protection
  • SC-7(4) External Telecommunications Services
  • SC-7(8) Route Traffic to Authenticated Proxy Servers
  • SI-4 System Monitoring
  • SI-4(1) System Monitoring | System-wide Intrusion Detection System (SI-4(1))
  • SI-4(18) System Monitoring | Analyze Traffic and Covert Exfiltration (SI-4(18))
  • SI-4(4) Inbound and Outbound Communications Traffic

FedRAMP Moderate · 7 controls

  • SC-5 Denial-of-Service Protection
  • SC-7(4) External Telecommunications Services
  • SC-7(8) Route Traffic to Authenticated Proxy Servers
  • SI-4 System Monitoring
  • SI-4(1) System Monitoring | System-wide Intrusion Detection System (SI-4(1))
  • SI-4(18) System Monitoring | Analyze Traffic and Covert Exfiltration (SI-4(18))
  • SI-4(4) Inbound and Outbound Communications Traffic

ISO 27002:2022 · 4 controls

  • 8.20 Networks security
  • 8.21 Security of network services
  • 8.23 Web filtering
  • 8.7 Protection against malware

NIST SP 800-53 Rev 5 · 4 controls

  • ASBv3-NS-4 Deploy intrusion detection/intrusion prevention systems (IDS/IPS)
  • ASBv3-NS-6 Deploy web application firewall
  • NS-3 Deploy firewall at the edge of enterprise network

CIS Controls v8 · 3 controls

  • CIS-13.10 Perform Application Layer Filtering
  • CIS-13.3 Deploy a Network Intrusion Detection Solution
  • CIS-13.8 Deploy a Network Intrusion Prevention Solution

ISO 27001:2022 · 3 controls

  • 8.20 Networks security
  • 8.21 Security of network services
  • 8.23 Web filtering

NIST SP 800-171 Rev 3 · 3 controls

PCI DSS 4.0 · 3 controls

  • 11.5.1 11.5.1 IDS/IPS monitoring of CDE traffic
  • 11.5.1.1 11.5.1.1 Service providers detect covert malware channels
  • 6.4.2 6.4.2 Automated web attack detection and prevention
  • ASD37-07 Web content filtering (Excellent)
  • ASD37-32 Network-based IDS/IPS (Limited)

C5 (Germany) · 2 controls

  • C5-COS-01 Technical safeguards
  • C5-COS-03 Monitoring of connections in the Cloud Service Provider's network

CMMC 2.0 · 2 controls

  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

NIST SP 800-161 Rev 1 · 2 controls

  • AUCDR-IS-5 Limit, prevent, detect and remove malware

HIPAA Security Rule · 1 control

SOC 2 · 1 control

  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary

UK Cyber Essentials · 1 control

  • CE-MP.3 Anti-Malware Scans Files on Access and Web Pages

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 Infrastructure Protection

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

AWS Well-Architected Security Pillar SEC05-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 54 it maps to, and the evidence behind each claim, over MCP and REST.