Every IT modification, whether it’s about updating firewall configurations, launching new servers, or altering system settings, comes with inherent risks. Without adequate documentation or authorization, these changes can lead to significant vulnerabilities. IT personnel are required to adhere to formal Change Management Procedures, which include documenting who initiated the change, the reasons behind it, the testing conducted and ensuring that rollback strategies are in place should a failure occur. Neglecting approvals or acting under pressure can create perilous gaps, as demonstrated by an incident where an undocumented firewall adjustment left a database port exposed to the internet, which was swiftly taken advantage of by attackers. A structured approach to change management fosters accountability and helps avert such mistakes.
Why this matters:
“Quick” tweaks break things and hide risk.
Do this:
- Raise a change record (what/why/risk/rollback).
- Use maintenance windows and notify stakeholders.
- Verify post-change and capture lessons learned.
Mini-lab:
Draft a change: “Enforce TLS 1.2+ on web servers” with a simple rollback plan.
Do/Don’t:
- Do Pair risky changes with a rollback plan.
- Don’t edit firewall rules live without a ticket.