Supported frameworks
| Framework | ID | Version |
|---|---|---|
| CIS AWS Foundations Benchmark | cis-aws | v2.0 |
| CIS GCP Foundations Benchmark | cis-gcp | v2.0 |
| CIS Azure Foundations Benchmark | cis-azure | v2.0 |
| SOC 2 Type II | soc2 | — |
| NIST SP 800-53 | nist-800-53 | Rev 5 |
| PCI-DSS | pci-dss | v3.2.1 |
| HIPAA Security Rule | hipaa | — |
How a control works
Each control defines what to check and how to interpret the result:check expression is evaluated against each resource’s latest configuration snapshot. If it returns false, the control fails for that resource.
How an assessment runs
When an assessment runs (on schedule or triggered manually):- InfraAudit fetches all active resources of the types required by each enabled control.
- It evaluates each control’s check expression against the resource’s cached configuration.
- It stores pass/fail results with a link to the specific resource.
- It calculates a compliance score:
passed_controls / total_controls.
Control-to-resource mapping
Failed controls link directly to the resources that caused the failure. For large accounts, a single failing control might affect many resources. The assessment detail view shows:- Control title and description
- Pass/fail status
- For failures: the list of resources that failed, with a link to each resource’s detail page
Compliance scores
InfraAudit calculates scores at several levels:- Per-control score — pass or fail for each control
- Per-framework score — percentage of controls passing within a framework
- Per-provider score — percentage of controls passing for each connected cloud account
- Aggregate score — weighted average across all connected providers
- By-category breakdown — scores grouped by category (IAM, logging, storage, networking, etc.)