Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
ec2_networkacl_allow_ingress_tcp_port_22Provider: AWS
Service:
ec2Severity: MEDIUM
Categories:
internet-exposedResource type:
AwsEc2NetworkAclWhat this check verifies
VPC network ACLs are evaluated for inbound rules that permit0.0.0.0/0 to access SSH on TCP 22 at the subnet boundary.
Risk
An ACL allowing Internet-wide SSH erodes defense in depth. Systems reachable onTCP 22 face brute-force, credential stuffing, reconnaissance, and SSH exploit attempts.
Changes to routes or security groups can create direct exposure, enabling unauthorized access and lateral movement, undermining confidentiality and integrity.
Recommendation
Apply least privilege at the subnet layer:- Do not allow
0.0.0.0/0toTCP 22 - Restrict SSH to trusted sources, or avoid direct SSH via Session Manager or a bastion behind VPN
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://support.icompaas.com/support/solutions/articles/62000233578-ensure-no-network-acls-allow-ingress-from-0-0-0-0-0-to-ssh-port-22
- https://docs.aws.amazon.com/vpc/latest/userguide/vpc-network-acls.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = ec2_networkacl_allow_ingress_tcp_port_22. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks