Per documentation the Cloud NGFW service (aka control plane) requires access to the AWS Secrets Manager for accessing the private keys to decrypt traffic. And, in either situation how are they maintaining the isolation?Įqually important is how they decrypt traffic for inspection. if your traffic is commingled with other customers). It’s not clear if Palo Alto is running either a single tenant or multi-tenant dataplane (i.e. It then goes to the Palo Alto stack for inspection and then returns back.
The Palo Alto Cloud Next-Gen Firewall solution, both in the distributed mode and centralized mode, requires that your traffic leaves your VPC and AWS account boundary through the VPC endpoint. Visibility & Protection for Cloud Servicesġ) Ownership and Control of Traffic & Encryption Keys.Protection for All Applications, Including Web Apps.
Ownership and Control of Traffic & Encryption Keys.Sending your traffic and encryption keys outside your cloud account boundaries raises significant compliance concerns for a product/service built on combining legacy technologies and no compliance certifications.Īnd now, here is my detailed analysis of seven key requirements for network security in public clouds that Palo Alto Networks Cloud NGFW completely misses: 7 Items to Review in Evaluating the Palo Alto Networks Cloud NGFW And, static policies based on IP addresses mean you are back to the world of opening a ticket to make an app go live. Multiple security consoles and separate solutions for multi-cloud means security teams will spend lots of time setting up and maintaining network security infrastructure. Lack of advanced protections for web applications, visibility to existing traffic flows, and protections for the 100s of cloud services leaves a lot of exposed attack surface. These technical gaps of Palo Alto Networks Cloud NGFW can be distilled into three primary business impacts that potential customers should be aware of: Porous Security In this blog, I’ll explore the critical gaps of the PAN Cloud NGFW offering. This is a detailed follow-up to our initial analysis of the Palo Alto Networks Cloud NGFW for AWS announcement.
0 kommentar(er)
