Use AWS Network Firewall for enterprises: Egress & ingress inspection
summary
GE replaces EC2 squid proxy fleets with AWS Network Firewall across a distributed model covering hundreds of AWS accounts and tens of thousands of compute instances, pushing shared managed lists, limiting stateless rules so alerts aren’t lost, and offering an allowlist exemption process. Route table rotation takes a minute or two per change and migration largely succeeds: compliance checks pass, security ops gain telemetry, and ops stop constant image churn. Delegated firewall administration and tighter ingress integration remain next steps.
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:59GE Corporate Cyber team
- 3:00Limited inspection capabilities
- 4:36Prioritizing compliance and risk reduction
- 6:28Automate deployment of AWS Network Firewall
- 8:17Inspection capabilities that meet or exceed our policy
related talks
50mAWS Well-Architected for network security
44mElevando la postura de seguridad con AWS Network Firewall
51mNetwork inspection design patterns that scale
58mAWS Cloud WAN service insertion: Simplifying network inspection
47mNetwork operations management and governance
31mProtecting Networks and Applications on AWS
33mNetwork and application protection on AWS
32mGet started with AWS networking: Set up, secure, & monitor global networks