You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Data Exfiltration: flag snapshot, export and batch secret-read actions #654
The Data Exfiltration finding flags five actions (READ_ONLY_DATA_EXFILTRATION_ACTIONS in cloudsplaining/shared/constants.py): s3:GetObject, ssm:GetParameter, ssm:GetParameters, ssm:GetParametersByPath and secretsmanager:GetSecretValue.
The DataExfiltration risk definition in the same file also says rds:CopyDBSnapshot and rds:CreateDBSnapshot "can be used to exfiltrate RDS database contents", but neither is in the list,
so a policy that allows them on * is not flagged.
Proposed additions
Secret and parameter reads (the same shape as the existing entries):
Action
Why
secretsmanager:BatchGetSecretValue
Returns the values of up to 20 secrets in one call.
ssm:GetParameterHistory
Returns a parameter's past values, decrypted when WithDecryption is set.
Snapshot, copy and export. Each puts a full copy of a data store where it can be shared with
another account or downloaded:
I opened #668 for this: the snapshot/export actions and ssm:GetParameterHistory are reported under the existing Data Exfiltration finding. I left secretsmanager:BatchGetSecretValue out (it can only be granted on * and AWS also requires GetSecretValue per secret, so it would flag correctly scoped policies); the PR explains this, and I'm happy to add it if you prefer.
Activity
devteamaegis commentedon Nov 4, 2026
I opened #668 for this: the snapshot/export actions and
ssm:GetParameterHistoryare reported under the existing Data Exfiltration finding. I leftsecretsmanager:BatchGetSecretValueout (it can only be granted on*and AWS also requiresGetSecretValueper secret, so it would flag correctly scoped policies); the PR explains this, and I'm happy to add it if you prefer.