Infrastructure
Cloud misconfiguration
Cloud misconfiguration, public resource exposure
Overly permissive cloud settings expose services, data or administration interfaces to unauthorised access.
Fiche de sensibilisationPrête à diffuser à vos équipes ou clients
MIGHT YOU BE AFFECTED?
Turn knowledge into action.
How does this work?
Network rules, access policies or resource settings may allow the public or unexpected identities to access an asset that should be restricted.
REAL-WORLD EXAMPLE
« A managed cloud database is accidentally configured to accept connections from any internet address instead of a small administrative network. »
Typical sequence
- 1A permissive rule or policy is deployed to a cloud resource.
- 2An outsider discovers the exposed service or data.
- 3Unauthorised access or exploitation becomes possible.
- 4The exposure persists until corrected or detected.
Warning signs
- Firewall or security-group rules allowing 0.0.0.0/0 for sensitive ports.
- Storage buckets or dashboards unexpectedly accessible to the public.
- Cloud security posture alerts about excessive permissions.
- Resources that can be accessed without the intended identity controls.
How to protect yourself
- Define secure defaults in reviewed Infrastructure as Code.
- Continuously assess configurations with CSPM and policy-as-code checks.
- Apply private networking, narrow firewall rules and least-privilege identities.
- Audit changes and alert when sensitive resources become public.
If you think you are affected
Close the exposure immediately without destroying evidence. Review audit logs and accessed data, rotate any reachable secrets, assess possible unauthorised access and correct the configuration baseline.
Last updated: 8 October 2026