Security in Secrets
Who may do what (IAM), what is recorded, and how a secret is protected.
IAM actions
Secrets is regionless. A secret's resource name is rn:ews::<org>:secrets:secret/<id>, a source's
rn:ews::<org>:secrets:source/<id>, an environment's rn:ews::<org>:secrets:environment/<id>.
Actions on one secret are checked against that secret's resource name, so a policy can name one
secret; list and create actions are checked on the service.
| Action | Access | What it allows |
|---|---|---|
secrets:ListSecrets | Read | List secrets (metadata only) |
secrets:GetSecret | Read | Describe a secret |
secrets:GetSecretValue | Read · sensitive | Retrieve the decrypted value of a secret |
secrets:CreateSecret | Write | Create a secret |
secrets:UpdateSecret | Write · destructive | Update a secret’s settings (not its value — that is RotateSecret) |
secrets:DeleteSecret | Write · destructive | Delete a secret |
secrets:ListSecretVersions | Read | List the versions of a secret |
secrets:RotateSecret | Write · destructive | Rotate a secret to a new value |
secrets:RollbackSecret | Write · destructive | Roll a secret back to an earlier version |
secrets:ListSecretGrants | Read | List which consumers a secret is granted to |
secrets:GrantSecret | Write | Grant a consumer access to a secret |
secrets:RevokeSecretGrant | Write · destructive | Revoke a consumer’s access to a secret |
secrets:GetSecretAccessLog | Read | Read the access log of a secret |
secrets:ListSecretSources | Read | List connected secret sources and their sync status (never the credential) |
secrets:CreateSecretSource | Write | Connect an external secret manager (e.g. a 1Password service account) |
secrets:UpdateSecretSource | Write · destructive | Rename a source, replace its credential or change its refresh interval |
secrets:DeleteSecretSource | Write · destructive | Disconnect a secret source |
secrets:UseSecretSource | Write | Resolve references through a source (create synced secrets, check references) |
secrets:SyncSecret | Write · destructive | Refresh synced secrets from their source now |
secrets:ListSecretEnvironments | Read | List the secrets environments of the organization |
secrets:CreateSecretEnvironment | Write | Add a secrets environment |
secrets:UpdateSecretEnvironment | Write | Rename a secrets environment or change its place in the promotion order |
secrets:DeleteSecretEnvironment | Write · destructive | Delete an empty secrets environment |
secrets:PromoteSecret | Write · destructive | Copy a secret’s active value (or source reference) into another environment |
secrets:CompareSecretValues | Read · sensitive | Compare secret values across environments (equal or not; never the values) |
Generated from the service’s IAM descriptor. Sensitive reads hand over secret material or source code and are recorded in the audit log like writes; destructive writes delete, overwrite or revoke.
secrets:GetSecretValueis the one action that hands over a value. It is sensitive: the generated read-only policies leave it out, and refusals are recorded in the audit log.secrets:CompareSecretValuessays whether two values are equal, never what they are. It is sensitive too.- Rotating, rolling back, granting and revoking each have their own action, separate from
secrets:UpdateSecret(description, group, rotation interval). secrets:UseSecretSourceis needed to make the platform resolve a reference through a source, separately fromsecrets:CreateSecret: a source's credential usually sees far more than one app needs.- A grant is necessary, not sufficient: for a workflow, the person who started the run also needs
secrets:GetSecretValueon the secret. - Setting an app's secrets environment needs
deploy:UpdateApp; the app flow needsdeploy:DescribeApp.
In the console, most controls you may not use stay visible and say which action they need. Some
do not: the actions on a source's row (Sync now, Test connection, Rename, Replace
token, Disconnect) are refused only when you use them, and without
secrets:ListSecretSources or secrets:ListSecretEnvironments the Sources or
Environments page shows only that your policies do not grant it.
Audit
Every write is recorded in the audit log with its outcome, and so are reads of a value and value
comparisons, allowed or refused (a matrix or diff records one refused comparison per request).
Reading a secret's access log (secrets:GetSecretAccessLog) is recorded only when refused. Separately, each secret's access log
records every read of its value: who or what, which version, when. See
See who has read a secret.
Encryption
Values are encrypted with AES-256-GCM under your KMS key, and every version is kept encrypted. See Keys and encryption. No list, describe, flow, matrix or log response contains a value, and sync errors carry the reference and the provider's error, never a value.