VPC Service Controls feature (Status:
Preview):
VPC Service Controls supports retrieving and updating service perimeters that
contain deleted IAM principals. When you enable this feature, you can manage
perimeters that contain deleted user, group, or service account identities
without triggering the The email address is invalid or non-existent error.
For more information, see Supported identities for ingress and egress rules.
]]>Preview stage support for the following integration:
]]>Generally available (GA) support for the following integrations:
General availability support for the following integration:
]]>VPC Service Controls feature (Status: Preview): Support for optimizing service perimeters using the VPC Service Controls recommender is available.
The recommender detects architectural risks and perimeter misconfigurations, including the following:
Critical resources at risk of exfiltration: Identifies active and sensitive services (such as BigQuery and Cloud Storage) operating outside service perimeters.
Unconfigured VPC accessible services: Identifies perimeters that leave APIs unrestricted from within the security boundary.
Misconfigured VPC accessible services: Identifies mismatches between allowed accessible APIs and restricted services inside a perimeter.
For more information, see Optimize perimeters with recommender.
]]>VPC Service Controls feature: The VPC Service Controls service patterns
feature is
generally available.
You can use service patterns to explicitly configure which Google APIs (both
supported and unsupported) can be accessed from VPC networks
within a service perimeter when using the private VIP (private.googleapis.com)
or a Private Service Connect endpoint with the all-apis bundle.
For more information, see VPC Service Controls service patterns.
]]>General availability support for the following integration:
]]>Preview stage support for the following integration:
]]>VPC Service Controls feature: Support for using the following identities in ingress and egress rules to allow access to resources protected by a service perimeter is generally available:
For more information, see Configure identity groups and third-party identities in ingress and egress rules and Supported identities for ingress and egress rules.
]]>General availability support for the following integration:
]]>General availability support for the following integration:
]]>Preview stage support for the following integration:
]]>Preview stage support for the following integration:
]]>Preview stage support for the following integration:
]]>VPC Service Controls feature: Support for using IAM roles in ingress and egress rules to allow access to resources protected by a service perimeter is generally available. This feature includes the following updates:
You can use the gcloud access-context-manager supported-permissions describe
command to check the support status of an IAM role.
You can use the gcloud access-context-manager supported-permissions list
command to retrieve the complete list of all supported permissions.
For more information, see Configure IAM roles in ingress and egress rules.
]]>Preview stage support for the following integration:
Preview stage support for the following integration:
]]>Preview stage support for the following integration:
]]>General availability support for the following integration:
]]>Preview stage support for the following integration:
]]>Preview stage support for the following integration:
]]>General availability support for the following integration:
VPC Service Controls feature (Status: Preview): VPC Service Controls supports the following identities in ingress and egress rules to allow access to resources protected by a service perimeter:
Agent identities
SPIFFE formats for third-party workforce and workload identities
This feature is available in Preview.
For more information, see Supported identities for ingress and egress rules.
]]>General availability support for the following integration:
]]>Preview stage support for the following integration:
]]>Preview stage support for the following integration:
]]>Preview stage support for the following integration:
]]>Preview stage support for the following integration:
]]>General availability support for the following integration:
]]>General availability support for the following integration:
]]>Preview stage support for the following integration:
]]>General availability support for the following integration:
]]>Preview stage support for the following integration:
]]>