Change Management Policy
Veridian Corp — IT Change Control Standards
Document ID: CM-001
Version: 2.0
Effective Date: January 15, 2026
Owner: IT Operations Team
Approved By: Chief Technology Officer
Change Classification & Approval
All changes to production systems, infrastructure, or applications must go through the Change Advisory Board (CAB) approval process before implementation.
Standard changes (pre-approved, low risk) must be logged in the Change Management system within 24 hours of implementation.
Non-standard changes require a completed Change Request form submitted at least 5 business days before the planned implementation date.
Emergency changes must receive approval from the CISO or CTO within 2 hours; the change request must be retroactively completed within 24 hours.
Change Planning & Testing
All changes must include a documented rollback plan that has been reviewed and approved before the change is executed.
All production changes must be tested in a staging environment that mirrors production before CAB submission.
Change success metrics must be defined in the Change Request and verified within 24 hours of implementation.
Change Windows & Freeze Periods
Change windows for production systems are restricted to Tuesday–Thursday, 10 PM–4 AM local time unless emergency approval is obtained.
Change freeze periods apply during the last 5 business days of each calendar quarter; no non-emergency changes are permitted during freeze periods.
Post-Implementation Review
Post-implementation reviews are required for all Severity 1 and Severity 2 changes and must be completed within 48 hours of implementation.
Changes to FDA-validated systems (MasterControl QMS, device firmware deployment pipeline) require Quality Assurance sign-off in addition to CAB approval.
Software changes to FDA-cleared device firmware must follow SOP-SW-002 and may require regulatory assessment per FDA-COMP-001.
Change Classification Matrix
| Type | Definition | CAB Required | Lead Time | Rollback Required | Examples |
|---|---|---|---|---|---|
| Standard | Pre-approved, low risk, documented procedure | No — log only | 24h post-implementation | No | Password policy update, cert renewal |
| Normal | Medium risk, planned maintenance | Yes | 5 business days | Yes | Database upgrade, OS patch batch |
| Major | High risk, cross-system impact | Yes + CTO review | 10 business days | Yes + tested | Network segmentation change, ERP upgrade |
| Emergency | Active incident mitigation | CISO/CTO within 2h | Immediate | Yes | Ransomware containment, critical CVE patch |
| FDA Validated | Changes to Part 11 / QMS systems | Yes + QA sign-off | 10 business days | Yes + revalidation plan | MasterControl upgrade, firmware OTA |
Change Advisory Board (CAB) Members
| Role | Name | Department | Voting Member |
|---|---|---|---|
| CAB Chair | James Okonkwo | IT Operations | Yes |
| CISO | Marcus Webb | IT Security | Yes |
| CTO | Elena Vasquez | Engineering | Yes |
| QA Representative | Dr. Sarah Kim | Quality Assurance | Yes |
| DPO | Lisa Kim | Legal / Compliance | Advisory |
| Regulatory Affairs | Dr. Elena Vasquez | Regulatory | Advisory |
Recent Production Changes (2026 Q1 Log)
| Change ID | Description | Type | Date | Systems | Outcome | PIR |
|---|---|---|---|---|---|---|
| CHG-2026-0847 | Azure AD conditional access policy update | Normal | Jan 14 | Identity / SSO | Success | Complete |
| CHG-2026-0901 | MasterControl QMS patch v2026.1 | FDA Validated | Feb 4 | QMS | Success | Complete |
| CHG-2026-0956 | VPM-4000 firmware OTA v4.2.2 | FDA Validated | Feb 18 | Device fleet | Success | Complete |
| CHG-2026-1023 | Critical OpenSSL CVE patch — prod API | Emergency | Mar 2 | API Gateway | Success | Complete |
| CHG-2026-1089 | CloudHealth data pipeline migration | Major | Mar 15 | PHI platform | Scheduled | — |