impact analysis
An assessment of what a proposed change or a disruption would affect, including systems, users, dependencies and business operations.
In more detail
For a change, it asks questions such as whether a service must restart, whether a stricter setting will lock out an old tool, and which other services depend on this one. For resilience planning, a business impact analysis measures how an outage of each business process would hurt over time and sets recovery targets. Skipping it is how a small, approved change causes a large outage.
Related terms
- BIA — A study of which business processes matter most and how the harm from an outage grows over time, used to set recovery targets.
- change request — A formal record asking to make a specific change, stating what will change, why, who owns it, and how it will be tested and undone.
- dependency — Anything a program needs in order to work, such as a library, a tool or another service.
- impact — How much harm an event would cause, such as money lost, data exposed, services stopped or people affected.
Taught in
- Security Baselines, Policies & Hardening Standards — Cybersecurity Fundamentals, GRC & Cryptography
- Risk Assessment: Qualitative vs Quantitative — Cybersecurity Fundamentals, GRC & Cryptography
- Business Impact Analysis, RTO & RPO Modeling — Cybersecurity Fundamentals, GRC & Cryptography
- Disaster Recovery Sites: Hot, Warm & Cold — Cybersecurity Fundamentals, GRC & Cryptography
- Security Capstone Review & Certification — Cybersecurity Fundamentals, GRC & Cryptography
- Test Activities, Testware And Traceability — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep
- Confirmation, Regression And Maintenance Testing — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep
References
- NIST glossary: security impact analysis
- NIST glossary: business impact analysis
- ISTQB Glossary: impact analysis
- ISTQB CTFL Syllabus v4.0.1, section 2.3