Compliance Posture
The Compliance Posture module is where an organization defines how posture should be interpreted for a governed subject. It keeps posture models, signal snapshots, projections, and recalculation history in one place.
Compliance posture is intentionally framework-agnostic. A workspace can model posture for a legal register, SoA, control family, source set, risk program, or another governed subject without Novantra hardcoding ADHICS, ISO, sector, role, or scoring behavior.
When to use it
Use Compliance Posture when you need to:
- Define what “compliant”, “partial”, “unknown”, “blocked”, or another tenant-owned state means for a context.
- Review signals contributed by enabled modules, such as source lifecycle status or regulatory register projection status.
- Keep posture projections separate from the records that produced the signals.
- Recalculate posture after source, framework, evidence, review, or register records change.
What you see in the product
Compliance Posture lives under Governance -> Compliance Posture.
The console has tabs for models, model versions, available signals, signal snapshots, projections, and recalculation runs. Administrators manage the models; contributors from other modules provide safe signal descriptors and signal snapshots.
Compliance Posture publishes safe export-field descriptors for models, signal snapshots, projections, and recalculation runs so Audit Packages can include posture context in tenant-owned templates. It can also publish recalculation-review work to Work Management when a run needs follow-up.
How it fits with other modules
Compliance Posture does not own source records, controls, obligations, or register rows. It consumes signals from those modules and produces posture projections. For example:
- Sources can contribute source version lifecycle signals.
- Regulatory Register can contribute register projection and review signals.
- Enabled modules can contribute their own posture signals through the same foundation.