Skip to main content

Compliance Overview

Infracast provides continuous compliance monitoring against industry frameworks, government standards, and security benchmarks β€” 1,241 automated rules across 35 YAML packs, all hot-reloadable without redeployment.

Supported Frameworks​

US Federal & DoD​

FrameworkRulesDescription
NIST 800-53 Rev 594Federal security standard β€” comprehensive technical & operational controls
NIST 800-171 r2114CUI protection for DoD contractors β€” all 110 requirements across 14 families
DFARS 252.204-701219Safeguarding Covered Defense Information and cyber incident reporting (72-hour DoD notification)
FAR 52.204-21/23/25/2730Federal Acquisition Regulation baseline safeguarding β€” applies to ALL federal contractors handling FCI
FedRAMP Moderate34Cloud services for federal agencies β€” moderate baseline
FedRAMP High32Cloud services for federal agencies β€” high baseline
CMMC Level 232DoD supply chain cybersecurity β€” 110 practices

DISA STIGs​

STIGRules
RHEL 961
Windows Server 202260
Ubuntu 22.0433
AWS39
Windows 1029
PostgreSQL25
SQL Server22
STIG Total269

Industry Standards​

FrameworkRulesDescription
ISO 27001:202241Information security management β€” Annex A controls
PCI-DSS v4.032Payment card industry β€” all 12 requirements
HIPAA28Healthcare data protection β€” Security Rule
SOC 226Service organization controls β€” Trust Service Criteria

CIS Benchmarks​

BenchmarkRules
AWS Foundations53
Azure52
GCP50
Kubernetes34
Microsoft 36523
CIS Total212

International & Sector-Specific​

FrameworkRulesDescription
GDPR38EU General Data Protection Regulation
NIS228EU Network & Information Security Directive
IRAP29Australian Information Security Registered Assessors Program
CSA CCM v429Cloud Security Alliance Cloud Controls Matrix
NIST CSF 2.027NIST Cybersecurity Framework β€” Identify through Recover
DORA26EU Digital Operational Resilience Act
NERC CIP28Critical infrastructure protection β€” energy sector
SOX IT22Sarbanes-Oxley β€” IT general controls
UK Cyber Essentials22UK government baseline security standard
LGPD20Brazil Lei Geral de ProteΓ§Γ£o de Dados
PIPEDA18Canada Personal Information Protection

Total: 1,241+ rules across 35 YAML packs β€” all hot-reloadable Β· 23+ compliance frameworks incl. 11 international

Dynamic Rule Management​

All compliance rules are defined in YAML and can be updated without redeployment:

# Example: rules/nist-800-53/ac-3.yaml
id: NIST-AC-3
framework: nist-800-53
title: "Access Enforcement"
severity: HIGH
node_types:
- aws.s3.bucket
condition: "public_access_block.enabled == true"
remediation: "Enable S3 Block Public Access settings at the bucket and account level"
mappings:
- framework: cis-aws
control: "2.1.5"
- framework: pci-dss-v4
control: "1.3.1"
- framework: soc2
control: "CC6.1"

Hot-Reload​

Push rule updates without downtime:

# Reload all rule packs immediately
POST /api/v1/rules/reload

# Response
{
"status": "ok",
"packs_reloaded": 35,
"rules_loaded": 1241,
"duration_ms": 142
}

Per-Tenant Rule Overrides​

Each tenant can customize rules independently:

Override TypeDescription
DisableTurn off a rule that doesn't apply to this tenant
Severity ChangePromote or demote severity (e.g. MEDIUM β†’ HIGH)
Timed SuppressionSuppress findings for a set window (e.g. maintenance, remediation sprint)
# Tenant override example
tenant: acme-corp
overrides:
- rule_id: CIS-AWS-5.2
action: suppress
reason: "Legacy network migration in progress"
expires: 2026-06-30
approved_by: ciso@acme-corp.com
- rule_id: NIST-SC-7
action: severity_change
severity: CRITICAL
reason: "Internal policy β€” border protection is critical"

How It Works​

Rule Evaluation​

Each compliance rule is a check against your infrastructure graph:

// Example rule: CIS AWS 5.2 β€” No security groups allow 0.0.0.0/0 to SSH
rule := Rule{
ID: "CIS-AWS-5.2",
Framework: "CIS AWS Foundations",
Severity: "HIGH",
NodeTypes: []string{"aws.ec2.security_group"},
Condition: "ingress_rules contains (port=22, cidr='0.0.0.0/0')",
Remediation: "Restrict SSH access to known CIDR ranges",
}

Evaluation Pipeline​

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Discovery │───▢│ Rule Engine │───▢│ Findings β”‚
β”‚ (nodes) β”‚ β”‚ (1,094 rules)β”‚ β”‚ (violations) β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
β”Œβ”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”
β”‚ Control β”‚
β”‚ Mappings β”‚
│ NIST→CIS→PCI│
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Control Inheritance​

Many rules map to multiple frameworks:

Rule: "S3 bucket public access blocked"
β”œβ”€β”€ NIST 800-53 AC-3 (Access Enforcement)
β”œβ”€β”€ CIS AWS 2.1.5 (S3 Block Public Access)
β”œβ”€β”€ PCI-DSS 1.3.1 (Network Segmentation)
└── SOC 2 CC6.1 (Logical Access)

One finding can satisfy (or fail) multiple framework controls.

Assessment & Questionnaire System​

For controls requiring human input, Infracast ships a full Assessment & Questionnaire System with 20 pre-built questionnaire templates across 4 languages:

LanguageTemplates
English (EN)All 20
German (DE)All 20
French (FR)All 20
Portuguese (PT)All 20

Templates cover common attested controls: security awareness training, incident response testing, vendor risk reviews, business continuity testing, and more. Templates are customizable per tenant and can be versioned in git.

Attestations​

Not all controls can be automated. Some require human attestation:

Automated vs Attested​

TypeExampleHow Assessed
AutomatedS3 encryption enabledRule checks node property
AttestedSecurity training completedHuman uploads evidence
HybridIncident response testedRule + evidence upload

Managing Attestations​

  1. Navigate to Compliance β†’ Attestations
  2. Filter by framework or control
  3. Upload evidence (PDFs, screenshots, policies)
  4. Set expiration date for periodic review
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Control: NIST 800-53 AT-2 (Security Awareness Training) β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Status: βœ… Attested β”‚
β”‚ Evidence: training-completion-report-2025.pdf β”‚
β”‚ Attested By: security-admin@company.com β”‚
β”‚ Date: 2025-01-15 β”‚
β”‚ Expires: 2026-01-15 β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Compliance Scores​

Calculation​

Overall Score = (Passing Automated + Passing Attested) / Total Applicable Γ— 100

By Category​

Controls are grouped into families/domains:

NIST FamilyControlsPassingScore
Access Control (AC)252288%
Audit (AU)161487%
Configuration (CM)141071%
Identification (IA)1212100%
System Protection (SC)221882%

Track improvement over time:

  • Weekly compliance snapshots
  • 30/60/90 day trends
  • Regression detection (score dropped)

Exemptions & Risk Acceptance​

Creating an Exemption​

When a control doesn't apply or risk is accepted:

  1. Navigate to the finding
  2. Click Accept Risk or Mark Exempt
  3. Provide justification
  4. Set review date

Exemption Workflow​

Finding Detected β†’ Review Required β†’ Approved β†’ Exempted
↓
Rejected β†’ Must Remediate

Auditor Visibility​

Exemptions are clearly marked in reports:

Control: CIS-AWS-5.2
Status: EXEMPTED
Justification: "Legacy system scheduled for decommission Q2 2026"
Approved By: ciso@company.com
Review Date: 2026-06-30

Reports​

Available Report Types​

ReportDescriptionAudience
Executive SummaryHigh-level posture, trends, top risksLeadership
Framework ReportDetailed control-by-control statusAuditors
Gap AnalysisWhat's failing and whySecurity team
Remediation PlanPrioritized fix listEngineering
POA&MPlan of Action & MilestonesFederal compliance
SSPSystem Security Plan (auto-generated)FedRAMP/FISMA
FAR 52.204-21 ReportBasic safeguarding attestation for federal contractorsContracting Officers, Federal Primes
DFARS 252.204-7012 ReportCDI safeguarding + SPRS score for DoD contractorsDoD Contracting, DCSA

Export Formats​

  • PDF β€” Formatted for printing/sharing
  • Excel β€” For analysis and manipulation
  • JSON β€” For API/automation
  • Word β€” For SSP editing

Scheduling​

Automate report delivery:

schedule:
frequency: weekly
day: monday
time: "08:00"
recipients:
- security-team@company.com
- compliance@company.com
reports:
- executive-summary
- framework-detail

Continuous Monitoring​

Real-Time Detection​

Findings appear within minutes of discovery:

  1. Discovery job runs (scheduled or triggered)
  2. New/changed nodes evaluated against rules
  3. Findings created/resolved
  4. Alerts sent (Slack, email, webhook)

ConMon for FedRAMP​

FedRAMP requires continuous monitoring. Infracast provides:

  • Automated monthly scans
  • Deviation tracking
  • POA&M generation
  • Significant change detection

See FedRAMP Guide for details.

API Access​

Query compliance data programmatically:

# Get compliance summary
curl -H "Authorization: Bearer $TOKEN" \
"$API_URL/api/v1/tenants/$TENANT/compliance/summary"

# Get findings for a framework
curl -H "Authorization: Bearer $TOKEN" \
"$API_URL/api/v1/tenants/$TENANT/findings?framework=nist-800-53"

# Export report
curl -H "Authorization: Bearer $TOKEN" \
"$API_URL/api/v1/tenants/$TENANT/reports/generate" \
-d '{"type":"framework","framework":"nist-800-53","format":"pdf"}'

# Hot-reload rule packs (no restart required)
curl -X POST -H "Authorization: Bearer $TOKEN" \
"$API_URL/api/v1/rules/reload"

Next Steps​