In order to meet PCI DSS requirements, a customer wants to ensure that all outbound traffic is authorized. Which two cloud offerings meet this requirement without additional compensating controls? (Choose two.)
Answer is CD
because the doc mentions the following: "App Engine ingress firewall rules are available, but egress rules are not currently available:" and "Compute Engine and GKE are the preferred alternatives."
It is CD.
App Engine ingress firewall rules are available, but egress rules are not currently available. Per requirements 1.2.1 and 1.3.4, you must ensure that all outbound traffic is authorized. SAQ A-EP and SAQ D–type merchants must provide compensating controls or use a different Google Cloud product. Compute Engine and GKE are the preferred alternatives.
https://cloud.google.com/solutions/pci-dss-compliance-in-gcp
PCI DSS (Payment Card Industry Data Security Standard) requires strict control over outbound traffic, meaning that only explicitly authorized traffic is allowed to leave the environment. Both App Engine and Cloud Functions are fully managed serverless platforms where Google handles the network configuration, including restrictions on outbound connections. Outbound traffic in these environments can be controlled without additional compensating controls because Google ensures compliance by managing the network restrictions and underlying infrastructure.
While the older answers (CD) were correct based on previous limitations, App Engine now supports egress controls.This means you can configure rules to manage outbound traffic, making it suitable for meeting PCI DSS requirements without needing extra compensating controls.
Today this question does not have an specific answer it seems that compute engine and gke wound need additional steps to setup and functions and app engine it’s possible to just set egress so I would go with this pair
AB
With App Engine, you can ingress firewall rules and egress traffic controls .
You can use Cloud Functions ingress and egress network settings.
AB makes sense if we are talking about controlling ingress and egress traffic
have a look 👀 at https://cloud.google.com/security/compliance/pci-dss#:~:text=The%20scope%20of%20the%20PCI,products%20against%20the%20PCI%20DSS.
there are multiple answers!
Answer is CD:
https://cloud.google.com/architecture/pci-dss-compliance-in-gcp#securing_your_network
Securing your network
To secure inbound and outbound traffic to and from your payment-processing app network, you need to create the following:
Compute Engine firewall rules
A Compute Engine virtual private network (VPN) tunnel
A Compute Engine HTTPS load balancer
For creating your VPC, we recommend Cloud NAT for an additional layer of network security. There are many powerful options available to secure networks of both Compute Engine and GKE instances.
hey. can anyone explain why isn't A correct? the decumantion mentions app engine as an option but not compute engine
https://cloud.google.com/architecture/pci-dss-compliance-in-gcp
IMO, this question was posted in 2020.
and later, Google released egress control for serverless VPC.
so currently App engine also are compliant in PCI.
I think this question is outdated
Answer is CD
For App Engine, the App Engine firewall only applies to incoming traffic routed to your app or service.
https://cloud.google.com/appengine/docs/flexible/understanding-firewalls
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
KILLMAD
Highly Voted 4 years, 8 months agorafaelc
4 years, 8 months agoBPzen
Most Recent 6 days, 12 hours agoluamail78
1 month, 1 week agoKiroo
7 months, 2 weeks agotechdsmart
9 months, 2 weeks agorottzy
1 year, 1 month agoGCBC
1 year, 2 months agostandm
1 year, 6 months agomahi9
1 year, 8 months agocivilizador
1 year, 9 months agoGCParchitect2022
1 year, 10 months agoBrosh
1 year, 11 months agodeony
1 year, 5 months agodeony
1 year, 5 months agoLittleivy
2 years ago[Removed]
1 year, 4 months agoAzureDP900
2 years agoGCP72
2 years, 2 months agojordi_194
2 years, 9 months agoDebasishLowes
3 years, 8 months ago