Ensure Systems Manager Parameter Store uses SecureString for sensitive data
Sensitive parameters (passwords, API keys, connection strings) should use SecureString type with KMS encryption, not String type.
Security Impact
Unencrypted parameters expose sensitive data to anyone with SSM read permissions and in CloudTrail logs.
How to Remediate
Migrate sensitive String parameters to SecureString type. Use KMS customer managed keys for encryption. Enable versioning.
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 Systems 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, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-ssm-4
- Service
- AWS Systems Manager
- Category
- Secrets Management
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated AWS Systems Manager Checks
View all checksEnsure Systems Manager managed instances are compliant with patch baselines
Ensure Systems Manager Session Manager is used instead of SSH/RDP
Ensure Session Manager has logging enabled to S3 and CloudWatch
Ensure Systems Manager documents do not contain hardcoded credentials
Ensure Systems Manager Run Command output is encrypted