High severity
SSH or RDP open to 0.0.0.0/0
Management ports reachable from any address on the internet.
Updated
What it looks like in each cloud
A security group rule allowing ingress from 0.0.0.0/0 or ::/0 on port 22, 3389 or all ports.
A VPC firewall rule with source range 0.0.0.0/0 permitting tcp:22 or tcp:3389, including the default-allow-ssh and default-allow-rdp rules on the default network.
A network security group inbound rule with source Any on 22 or 3389, or a VM with a public IP and no NSG.
Why it matters
Open management ports are brute-forced and scanned for known vulnerabilities within minutes of appearing. Combined with a weak key or an unpatched service they are a direct route to the host.
How it happens
A rule is opened for troubleshooting from a home address and widened to any because the address changed. Default networks ship with permissive rules. A public IP is attached to a VM that only needed outbound access.
How to check
List every ingress rule whose source is the whole internet and whose port range includes 22, 3389, database ports or all ports, and map each to the instances it applies to.
How to fix it
Restrict the source to known ranges, or remove the public path altogether and use a bastion, VPN, or the cloud's session-based access (Systems Manager, IAP, Azure Bastion).
Frameworks that require this
The controls this issue falls under. AKRIBOS reports the finding once and maps it to each framework you have in scope.
CIS Benchmarks
AWS Foundations 5.2 and 5.3 (no ingress from 0.0.0.0/0 or ::/0 to administrative ports); Google Cloud Foundations 3.6 and 3.7; Azure Foundations 6.x (RDP and SSH not open from the internet).
SOC 2
CC6.6 (network boundaries and external threats).
ISO/IEC 27001
A.8.20 Networks security, A.8.21 Security of network services.
DORA
Art. 9(4)(b) network and infrastructure management, segregation.
NIS2
Art. 21(2)(e) security in systems acquisition and maintenance; 21(2)(a) information system security.
PCI DSS v4
Req. 1.3 and 1.4 (traffic between trusted and untrusted networks), 2.2.7 (encrypted administrative access).
NIST CSF 2.0
PR.IR-01 (networks protected from unauthorised access).
BSI C5
COS (network segmentation and controlled traffic).
DNB Good Practice Information Security
Network security (controlled connections from untrusted networks).
How AKRIBOS handles it
AKRIBOS finds this during a read-only review of every connected account, project and subscription, shows the exact resource and setting behind the finding, and ranks it by the attack path it enables rather than in isolation. The fix is proposed as CLI commands or Terraform for you to review and approve, and the approval is recorded in the audit trail together with the compliance controls it satisfies.
Related issues
Storage bucket open to the internet
CriticalObject storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.
Read moreRoot or owner account without MFA
CriticalThe most privileged identity in the account protected by a password alone.
Read moreDatabase reachable from the internet
CriticalA managed database with a public address and a firewall that lets the world in.
Read moreAttackers don't wait for your next audit. Neither does AKRIBOS.
Connect AWS, Google Cloud or Azure and get your first review today.
