Skip to content
PATHBREAK
Attack paths Compliance How it works Attack map Pricing Blog
EnglishEspañolFrançaisDeutsch日本語한국어العربية
Log in Request a demo
Attack paths Compliance How it works Attack map Pricing Blog
EnglishEspañolFrançaisDeutsch日本語한국어العربية
Log in Request a demo
The Pathbreak Attack Map for AWS / Secrets Manager
Data access Secrets Manager T1555.006

Read Secrets Manager secret

Can read a Secrets Manager secret value.

Grants escalation on its own.

secretsmanager:GetSecretValue
Key takeaway

On its own, secretsmanager:GetSecretValue can read a Secrets Manager secret value. On a wide resource scope that alone reaches the data itself.

GetSecretValue reads data 01 Attacker principal 02 Data store 03 Data read
How an attacker moves from this permission.
Explore this in Pathbreak

Why it is dangerous

A principal can call secretsmanager:GetSecretValue to read the secret, verified against both the principal's identity policy and the secret's resource policy. A secret frequently holds another principal's long-term credentials (DB passwords, API keys, IAM access keys), so reading it is both the objective and a lateral-movement multiplier, control of the secret can become control of a new identity.

In MITRE ATT&CK terms this maps to T1555.006, Credentials from Password Stores: Cloud Secrets Management Stores, under the credential access tactic. AWS records it in CloudTrail as GetSecretValue. The call is quiet against normal activity, so it is easy to miss without a rule for it.

Detection

GetSecretValue

Prerequisites

secretsmanager:GetSecretValue on the secret (from identity OR the secret's resource policy); kms:Decrypt on the encrypting key for a customer-managed CMK.

MITRE ATT&CK

T1555.006 · Credentials from Password Stores: Cloud Secrets Management Stores

Tactic

Credential Access

Breaking the path

A control that would remove it: Scope the secret's resource policy and the principal's secretsmanager:GetSecretValue; rotate exposed secrets.

Whether to apply it depends on how the permission is used in your environment, so it is a business decision rather than an automatic fix. The same permission can be load-bearing in one account and pure risk in another.

Pathbreak confirms whether this path resolves in your account, ranks it against the others by how much it opens up, and uses your threat model and business context to show which paths are worth cutting.

Questions

What does secretsmanager:GetSecretValue allow?

Can read a Secrets Manager secret value.

Can secretsmanager:GetSecretValue escalate privileges on its own?

Yes. Held on a broad enough resource it reaches the data itself with no other permission.

How is read Secrets Manager secret detected?

Watch for GetSecretValue in CloudTrail. The call is quiet against normal activity, so it is easy to miss without a rule for it.

How do you break this path?

A control that would remove it is: Scope the secret's resource policy and the principal's secretsmanager:GetSecretValue; rotate exposed secrets. Whether to apply it depends on how the permission is used in your account, so it is a business decision rather than an automatic fix.

Which MITRE ATT&CK technique is this?

T1555.006, Credentials from Password Stores: Cloud Secrets Management Stores, under the credential access tactic.

Related paths

Same techniqueRecursively dump SSM SecureString pathssm:GetParametersByPathSame techniqueRead SSM SecureString parameterssm:GetParameterSame techniqueRead Glue connection JDBC credentialsglue:GetConnectionSame serviceSelf-grant secret read via resource policysecretsmanager:PutResourcePolicySame serviceRead a secret granted to an external AWS accountSecrets Manager

References

  • https://attack.mitre.org/techniques/T1555/006/

Find this in your own account

We run a read-only scan of one AWS account and show you which of these paths exist, ranked by blast radius, with the change that breaks each one. First validated paths within the hour.

Request a free scan Watch the 7-minute walkthrough
PATHBREAK

Validated AWS attack paths, and the change that breaks each one.

Platform

Overview Attack paths How it works Pricing Attack map Threat actors Demo pathbreak-audit

Company

About Request a demo hello@pathbreak.io

Registered office

60 High Street
Wimbledon
London, England
SW19 5EE

Pathbreak Ltd · Company No. 17265710
© 2026 Pathbreak Ltd. All rights reserved.
Terms Privacy Security Trust
pathbreak.io