Lifecycle of an Authorization Rule

This page describes the lifecycle of an authorization rule, detailing the statuses it can take and the transitions between them.

1. Draft

Description:

  • The rule is under development.

  • It is not published or active.

  • Only accessible to creators or administrators for review and refinement.

Use case:

  • Initial creation of a new rule.

  • Updates or modifications to an existing rule.

Next Status:

  • Moves to Proposed after the initial definition is complete.


2. Proposed

Description:

  • The rule has been finalized and is ready for review.

  • It is submitted to relevant stakeholders (e.g., security teams, business units, administrators) for approval.

  • The rule is not yet active in the system.

Use case:

  • Ensuring the rule meets security, compliance, and operational requirements before implementation.

Next Status:

  • Moves to Approved once validated.


3. Approved

Description:

  • The rule has been reviewed and approved by the designated authorities.

  • It is ready for enforcement in the system but not yet active.

Use case:

  • Staging the rule for implementation while ensuring that all dependencies or prerequisites are in place.

Next Status:

  • Moves to Enforced when it is ready to be applied.


4. Enforced

Description:

  • The rule is active and applied in the system.

  • It governs access or operations according to its defined parameters.

Use case:

  • Day-to-day operational use of the rule.

Next Status:

  • May be moved to Suspended or Deprecated if it needs to be paused or replaced.


5. Suspended

Description:

  • The rule is temporarily deactivated but remains accessible.

  • It is not actively governing access or operations.

Use case:

  • Testing or troubleshooting.

  • Temporary suspension for maintenance or system updates.

Next Status:

  • Can return to Enforced or move to Deprecated.


6. Deprecated

Description:

  • The rule is marked as obsolete.

  • It is no longer actively applied but remains in the system for reference or auditing purposes.

Use case:

  • Retiring rules that are no longer needed or have been replaced.

Next Status:

  • Moves to Archived when it is safe to delete from the system.


7. Archived

Description:

  • The rule is fully retired and removed from active use.

  • A record is maintained for compliance and audit purposes.

Use case:

  • Long-term storage of historical rule data.

Next Status:

  • Final state; no further transitions.


Lifecycle Transitions

Common Transitions:

  • Draft → Proposed → Approved → Enforced

  • Enforced → Draft (for modifications)

  • Enforced → Suspended (for temporary deactivation)

  • Enforced → Deprecated → Archived (for retirement)

Last updated