Ensure Secrets Manager secrets are used instead of hardcoded credentials
Applications should retrieve credentials from Secrets Manager instead of hardcoding them.
Security Impact
Hardcoded credentials cannot be rotated and may be exposed in version control.
How to Remediate
Update applications to retrieve secrets using AWS SDK. Remove hardcoded credentials from code.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all AWS Secrets Manager resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-secretsmanager-8
- Service
- AWS Secrets Manager
- Category
- Credential Management
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated AWS Secrets Manager Checks
View all checksEnsure Secrets Manager secrets have automatic rotation enabled
Ensure Secrets Manager secrets are encrypted with KMS CMK
Ensure Secrets Manager secrets have resource policies
Ensure Secrets Manager secrets are not publicly accessible
Ensure Secrets Manager rotation is tested