MA
Muhammad AldiansyahGRC Assurance Center
Governance with evidence

Policy Lifecycle & Exceptions

Govern policies from approval through communication, implementation, exception, review, and retirement.

On this page · 4 sections
01

Applicability & intent

Policies express mandatory direction. Supporting standards and procedures make that direction actionable, while exceptions record time-bound, risk-informed deviations.

  • Document why policy lifecycle & exceptions applies, what is in scope, and who is accountable.
  • Translate obligations into owned, testable outcomes with proportionate evidence.
  • Track exceptions, residual risk, changes, and corrective actions through governance review.
02

Governance lifecycle

  1. 01

    Confirm scope, context, interested parties, legal or contractual basis, and authoritative sources.

  2. 02

    Identify desired outcomes, owners, dependencies, existing controls, and evidence sources.

  3. 03

    Assess design and operating effectiveness using representative, time-bound evidence.

  4. 04

    Record gaps, risk, interim protections, target dates, and approval decisions.

  5. 05

    Verify remediation, report residual risk, and schedule reassessment when context changes.

03

Evidence & assurance

Evidence familyAssurance question
approved policy and version historyDoes governance establish accountable direction?
acknowledgement and implementation recordsDoes the process operate consistently?
exception rationale, compensating controls, and expiryCan the claimed outcome be independently verified?

Evidence should be attributable, current, protected, reproducible, and linked to an accountable owner. A document alone does not demonstrate that a control operates effectively.

04

Readiness decisions

  • Assign owner and approving authority.
  • Set event-driven and periodic review triggers.
  • Expire exceptions automatically into review.

Official references

NIST Cybersecurity Framework 2.0NIST Computer Security Resource Center