Change Approvals
Patch jobs often require formal approval, especially in production environments. Cloudaware Patch Management integrates with Change Management so you can tie deployments to change records and Change Advisory Board (CAB) decisions.
Use this guide to understand how approvals are incorporated into the patching workflow to control execution and support auditability.
Approvals in the Workflow
Typical patterns include:
- Creating a change request for each scheduled patch release.
- Linking one or more patch jobs to that change.
- Requiring approval from designated approvers or a CAB before execution in production.
You can use different approval requirements for environments such as Dev, QA, and Prod.
Guardrails
To keep patching safe and auditable:
- Restrict who can create or approve patch jobs via RBAC.
- Require approvals for emergency releases except in well‑defined break‑glass situations.
- Use change templates to standardize information (scope, risk, test plans, rollback plans).
Change and Patch Management audit trails together provide a clear record of who approved and executed each patch release.