# VPC Service Controls folder membership and folder rules reach GA

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

Google Cloud announced on 30 September 2026 that VPC Service Controls now supports Google Cloud folders and organizations as resources in ingress and egress rules, and folder membership in service perimeters, both generally available. A folder member protects all projects and subfolders beneath it.

Google Cloud logged two VPC Service Controls features as generally available on 30 September 2026. The first supports Google Cloud folders and organizations as resources in ingress and egress rules, which the release note says lets you create rules that allow access to and from protected resources and bypass common resource size limitations. The second supports folders as members of service perimeters.

Google documents that a folder configured as a perimeter member automatically protects all projects and subfolders in that hierarchy. For a guardrail owner, that means new projects created under the folder fall inside the perimeter without a separate update. The change applies to perimeter scope only and does not change what individual IAM roles allow.

## Related pages

- [ECS extends CPU and memory IAM condition keys to RunTask](/news/ecs-cpu-memory-condition-keys-runtask/)
- [VPC Service Controls perimeters can be edited with deleted principals](/news/vpc-sc-deleted-principals-in-perimeters-preview/)
- [Lambda functions now accept full IAM resource-based policies](/news/lambda-full-iam-resource-based-policies/)
- [All of them](/news/)

## Sources

- https://cloud.google.com/vpc-service-controls/docs/release-notes (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/news/vpc-sc-folders-organizations-in-rules-ga/
