Infrastructure & systems
ImplementedContainer / infra / cloud
Hardening of Dockerfile / compose / nginx and Terraform infrastructure-as-code (misconfiguration, privileges, exposure, IAM escalation).
Family facts
- Code
- FAM-INFRA
- Status
- ready — code maturity
- Availability
- available — whether it is offerable
- Ingest
- pull — how a target enters
- Rules of Engagement
- Not required
- Kind
- Family (a selectable assessment)
What it decides
Whether an infrastructure misconfiguration opens a real attack path — for example what an IAM escalation actually enables.
How it works
It analyzes container and IaC definitions structurally and contextualizes a misconfiguration inside an attack path rather than listing it in isolation — a permissive setting matters because of what it enables downstream.
Coverage is explicit: a recognized-but-unparsed format is reported as partial, never as a silent “clean”.
Declared limits
Infrastructure-as-code supported today = Terraform HCL2. CloudFormation and Azure ARM are built and validated but not yet integrated; .tf.json is recognized but not parsed.
References
References point to public, well-known technical sources for further study.
Related articles