Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VPC-SC Ingress/Egress policy controls #329

Open
lbg-avass opened this issue Aug 17, 2021 · 1 comment
Open

VPC-SC Ingress/Egress policy controls #329

lbg-avass opened this issue Aug 17, 2021 · 1 comment

Comments

@lbg-avass
Copy link

**VPC-SC new Ingress/Egress feature is to replace perimeter bridges, to simplify the the connection between projects from different environments or even outside the organisation.
This allow for misconfigurations:

  • Unauthorised cross environments
  • Unauthorised All Services
  • Unauthorised All Method
  • Unauthorised All Rules
    **

Detailed Description

https://cloud.google.com/vpc-service-controls/docs/ingress-egress-rules
Requirements:
Controls for the following:

  • Unauthorised cross environments
  • Unauthorised All Services
  • Unauthorised All Method
  • Unauthorised All Rules

Context

This is critical, to prevent data exfiltration, due to malicious or misconfigurations

Possible Implementation

@lbg-avass
Copy link
Author

Primary contact email: [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant