Security Guardrails
Infrastream is secure by default. The network is default-deny. Each application has an identity that starts with no permissions. The platform generates the firewall rules and encrypts traffic between services. You cannot deploy a resource that opts out.
The Security Framework describes each layer. This page covers the part that is yours.
Shared responsibility
- Infrastream secures the cloud. It secures the network, identities, encryption, infrastructure configuration and deployment pipelines.
- You secure the code. You secure the application logic and its third-party dependencies.
You must do these actions:
- Write secure code. Identity-Aware Proxy (IAP) handles authentication for a route. Your code must still decide what a verified user may do.
- Scan and update your third-party libraries.
- Never put credentials in source. Declare a secret in a manifest and read it from an environment variable or a mounted file. See Manage Secrets.
Authentication on a route
Each HttpRoute or GrpcRoute rule can require a sign-in. Use type: IDENTITY_PROVIDER for customers and type: INTERNAL for staff tools. See Adopt a Repository, DNS and Sign-in.
Your own access
Access to a project has three tiers: administrators, contributors and viewers. The tiers differ only in what they can do with data. No tier can change infrastructure, read a secret payload or grant itself more access. See Access Tiers.