Compliance Posture¶
Compliance Posture shows which controls in a framework AI SIEM can monitor, and whether that monitoring is switched on. It is a monitoring-coverage signal to inform your own audit — not audit evidence, a certification, or a substitute for a qualified assessor. Controls AI SIEM can't observe are left out rather than shown as passing.
Frameworks¶
| Framework | Controls mapped |
|---|---|
| CIS AWS Foundations Benchmark v5.0.0 (section 4, monitoring) | 4.3, 4.8, 4.9 |
| HIPAA Security Rule | 5 |
| NIST SP 800-53 Rev 5 (controls in the FedRAMP baseline) | AU-2, AU-6, AU-9, AU-12, AC-2, AC-6(9), SI-4 |
| PCI DSS v4.0 | 5 |
| SOC 2 (Trust Services Criteria) | 5 |
"5 of 5" means five mapped controls, not the whole framework. Listing NIST controls from the FedRAMP baseline does not mean AI SIEM, or your deployment, is FedRAMP authorized.
Choose which frameworks appear under Settings → Compliance Frameworks. A framework you turn off is left out of the view and of the daily posture snapshot, not shown as passing. Individual controls can't be turned off; use detection-rule exclusions for known-good activity instead.
How a control is assessed¶
- Covered — the data sources and detection rules that monitor the control are on.
- Not monitored — a source or rule the control needs is off. The control shows which one.
A framework's score is the share of its controls that are covered. Open threats don't lower it: catching something shows the monitoring works.
Each control also shows how many open (untriaged) threats count against it, as N to review. Each threat is counted once per control, under its threat type or the detection rule that raised it. Click the count to open Threats filtered to exactly those threats, and use Back to Compliance Posture to return. Resolving, marking false positive, or dismissing a threat removes it from the count, and the audit trail records who reviewed it and why — the evidence an auditor looks for.
Partial coverage¶
Some controls are only partly monitored, for example CIS 4.8 detects bucket-policy changes that make a bucket public, not every bucket-policy change. These are labeled Partial coverage with a note on what isn't watched. They are shown, never hidden.
History¶
A daily snapshot of this view is kept in the tamper-evident audit store, so posture can be trended over time. See the audit trail.
Retention and compliance fit¶
Retention is set by tier and maps onto the hot-vs-total split that compliance frameworks are written around. See the retention table in getting started for the per-tier values. In summary:
- Essential and above keep at least 90 days immediately searchable, meeting PCI DSS's three-month hot requirement.
- Advanced and above provide a full 12 months searchable, covering PCI DSS's 12-month total and typical SOC 2 audit periods.
- For HIPAA (6 years) or SOX (7 years) audit-log obligations, raise the
AuditRetentionDaysstack parameter at deploy (up to 36500 days) and chooseCOMPLIANCEObject-Lock mode if records must be immutable until retention elapses. The audit trail can be extended independently of the tier.