Definition
The proportion of automatically enforced compliance and security policies that have been reviewed and updated within the policy's defined review cycle, measured against the current regulatory and threat landscape.
The Measurement Gap
There is no metric that tells you whether automatically enforced compliance policies are current relative to the regulatory and threat landscape, which means the platform can enforce stale policies with full confidence.
Formula
Plain language: List every compliance and security policy the platform enforces automatically (FedRAMP controls, HIPAA requirements, PCI rules, organizational coding standards, vulnerability patterns). For each, check when it was last reviewed and updated. Compare to the policy's required review frequency (typically quarterly for security policies, annually for compliance policies, or whenever a regulatory change is published). Policies that are past due for review are "stale."
Notation:
PFS = (P_current / P_total) × 100
Variables:
- P_current = policies where last_review_date + review_interval ≥ today (count, DERIVED)
- P_total = total enforced policies (count, NATIVE from platform policy configuration)
- last_review_date = date the policy was last reviewed and confirmed or updated (date, MANUAL or NATIVE from policy management system)
- review_interval = required review frequency for this policy type (days, MANUAL: defined by security/compliance team)
Proposed formula, pending validation pilots.
At a Glance
Decision Supported
Are the compliance policies the platform is enforcing still current, or is the platform confidently enforcing stale rules while the regulatory and threat landscape has moved on?