Ensure Systems Manager Session Manager is used instead of SSH/RDP
Session Manager provides secure access to instances without opening inbound ports, bastion hosts, or managing SSH keys, with full audit logging.
Security Impact
SSH/RDP with exposed ports increase attack surface. SSH key management is error-prone and lacks audit trails.
How to Remediate
Enable Session Manager. Remove SSH (port 22) and RDP (port 3389) from security group inbound rules. Use IAM for access control.
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, NIST 800-53, Zero Trust compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-ssm-2
- Service
- AWS Systems Manager
- Category
- Access Control
- 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 Session Manager has logging enabled to S3 and CloudWatch
Ensure Systems Manager Parameter Store uses SecureString for sensitive data
Ensure Systems Manager documents do not contain hardcoded credentials
Ensure Systems Manager Run Command output is encrypted