Provifact™ Mission Control¶
Mission Control
Validating evidence identity and freshness…
What requires attention now
Every state below comes from deterministic comparison. Open an item for its evidence chain.
Read-only signal flow
Baseline posture
All 98 approved rules stay visible. Only reviewed exact provider mappings enter the deterministic denominator.
| Control objective | Desired | Observed | Deterministic state | Evidence | Action |
|---|
Current findings
Filters operate only on the validated package; they do not trigger collection.
| Setting | State | Severity | Observed → target | Assignment |
|---|
Change watch
Resolved findings
New drift
Comparison provenance
Baseline implementation backlog
These are planning gaps, not failed controls. Each rule needs an approved Intune, custom-profile, script/agent, or alternate-evidence path before deterministic evaluation.
Collection coverage and blind spots
Inventory-only records are visible but do not change alignment. Parser or exact-mapping gaps require engineering review.
Assessment support
| Framework | Evaluated | References | Aligned | Drifting | Boundary |
|---|
Evidence health and privacy
Approved baseline
Collection health
Private → public gate
Managed Apple aggregate
Authority boundary and methodology
Git revert changes reviewed desired-state history; it does not revert Intune. Provifact has no Intune write capability. Technical configuration may support an assessment objective but cannot establish organizational compliance. Human assessors retain final judgment.
Deterministic audit methodology · Data handling · Complete baseline inventory