Security

Security isn't a bolt-on. It's built into every layer.

You need SaaS convenience but can't hand over your cloud credentials. Your team is growing but secret sprawl is growing faster. Auditors want a trail for every infrastructure change.

Secrets management, identity and access control, and full audit trails are built into every layer of Planton — from how credentials are stored to how infrastructure changes are executed.

secret resolution

▶ Resolving secrets for GcpCloudSqlInstance/production-db
 
db-password → gcp-secret-manager ✓
api-key → aws-secrets-manager ✓
tls-cert → hashicorp-vault ✓
 
⏳ Injecting at execution boundary...
✓ 3 secrets resolved. Zero plaintext.

5+

Secret Backends

0

Plaintext Secrets

100%

Changes Audited

0

Implicit Trust

Secrets Management

Store secrets encrypted at rest. Reference them by name, not by value — no plaintext in manifests, no secrets in environment variables, no credentials in CI logs.

SecretRef pattern — reference secrets by name in resource specs, never inline values

Encrypted storage with provider-native encryption at rest

Execution-time resolution — secrets are injected only when the stack job runs

SecretRef Pattern

apiVersion: kubernetes.openmcf.org/v1
kind: GcpCloudSqlInstance
metadata:
  name: production-db
spec:
  databasePassword:
    secretRef:
      name: db-password
      backend: gcp-secret-manager

Runner Trust Model

Runner executes IaC and operations in YOUR cloud. Credentials are resolved via your cloud provider's native IAM. The Planton control plane never sees them.

Just-in-time credential resolution via native cloud IAM — no long-lived secrets

Runner runs in your VPC with your security policies and network controls

Encrypted tunnel between Runner and control plane with verified identity on both sides

Runner (your VPC)

IRSA (AWS)
Workload Identity (GCP)
Managed Identity (Azure)

Encrypted Tunnel

Verified identity
Outbound only

Planton Control Plane

Never sees cloud credentials
Orchestration only

Security at every layer of the stack

From secrets storage to zero-trust networking — every security control is native, not bolted on.

Multi-Backend Secrets

Bring your own secrets backend. Or use Planton's managed backend to get started in seconds.

AWS SM
GCP SM
Azure KV
Vault
K8s Secrets

Identity & Access

Human users and machine identities share one unified identity model. Fine-grained, relationship-driven access control.

IdentityAccount
Service Accounts
API Keys (SHA-256)
Org-Scoped RBAC
Env-Level AuthZ
Relationship-Driven

Connection Security

All connections use typed SecretRef fields. OAuth tokens rotate automatically. GitHub App installations with zero user-managed secrets.

SecretRef
OAuth Rotation
GitHub App
Scoped RBAC

Zero-Trust Architecture

Encrypted tunnels with cryptographic identity for every Runner. No implicit trust between any component.

Crypto Identity
JWT Auth
Per-Service AuthZ
No Implicit Trust

Every change has a story

Version history with Git-like commit messages. Color-coded diffs. Searchable audit log across all resources.

planton cloud-resource

$ planton cloud-resource versions my-postgres
 
VERSION AUTHOR MESSAGE DATE
v7 alice@company.com Enable HA for prod DB 2026-03-24
v6 bob@company.com Increase storage to 500GB 2026-03-20
v5 ci-bot Rotate database password 2026-03-15
v4 alice@company.com Add read replica 2026-03-10
 
$ planton cloud-resource diff my-postgres v6 v7
- highAvailability: false
+ highAvailability: true

Version History

Git-like commit messages for every resource modification. Know who changed what and why.

Color-Coded Diffs

Compare any two versions of a resource with clear add/remove/update highlighting.

Searchable Audit Log

Search across all resources, environments, and identities. Stack job logs preserved for every execution.

Built-in Security

See how Planton secures your infrastructure

Secrets management, identity and access, audit trails, zero-trust networking — all native to the platform.


©2026 Planton Cloud Inc. All Rights Reserved.