Change Management with Blast Radius

Last Updated: January 7, 2026 Estimated Reading Time: 7 minutes

Overview

The Blast Radius feature helps you visualize the cascading impact of CI failures before implementing changes. This guide shows you how to integrate blast radius analysis into your change management process to reduce outages and make better-informed decisions.

What is Blast Radius?

Blast radius simulates what happens when a Configuration Item (CI) fails or becomes unavailable. It shows:

• Direct Impact: CIs immediately affected (e.g., applications running on a server)
• Cascading Impact: Downstream CIs affected through dependencies
• Business Impact: Services and users impacted by the change
• Risk Assessment: Severity level based on criticality and scope

When to Use Blast Radius

Change Management Scenarios

1. Server Maintenance: Assess impact before patching or rebooting
2. Infrastructure Upgrades: Understand dependencies before hardware changes
3. Application Deployments: Identify affected services and users
4. Network Changes: Visualize connectivity impacts
5. Decommissioning: Verify no critical dependencies before retiring CIs

Risk Assessment Questions

Answer these questions with blast radius:

• What services will be unavailable during maintenance?
• Which users/teams will be affected?
• Are there alternative CIs that can take over?
• What's the worst-case scenario if the change fails?
• Should this change require a CAB (Change Advisory Board) review?

Using Blast Radius Analysis

Step 1: Access Blast Radius

From CI Health Workspace:

1. Navigate to CI Health Workspace
2. Find the CI you want to analyze
3. Click on the CI card
4. Select "Blast Radius" tab in the details panel

From Dependency Map:

1. Navigate to Dependency Map
2. Locate the target CI on the graph
3. Right-click the CI node
4. Select "Show Blast Radius"

Direct Access:

1. Navigate to Features → Blast Radius
2. Search for the CI by name or ID
3. Click "Analyze"

Step 2: Configure Simulation Parameters

Impact Depth:

• 1 Level: Direct dependencies only (immediate impact)
• 2 Levels: Direct + one degree of separation (recommended)
• 3 Levels: Full cascading impact (comprehensive view)
• Unlimited: All connected CIs (useful for critical systems)

Failure Scenario:

• Planned Outage: Graceful shutdown (allows failover)
• Unplanned Failure: Sudden loss (worst-case scenario)
• Degraded Performance: Partial availability (50% capacity)

Time Window:

• Immediate: Impact at time of change
• Scheduled: Impact during maintenance window
• Extended: Impact if recovery takes longer than expected

Step 3: Interpret Results

Visual Indicators:

• Red nodes: Critically impacted CIs
• Orange nodes: High impact CIs
• Yellow nodes: Moderate impact CIs
• Gray nodes: Low impact or redundant CIs

Impact Summary Panel:

Total CIs Affected: 47
├── Critical: 5 (production services)
├── High: 12 (applications)
├── Medium: 18 (supporting infrastructure)
└── Low: 12 (dev/test systems)

Business Services Impacted: 3
├── Online Banking (Critical)
├── Mobile App (High)
└── Internal Portal (Medium)

Estimated Users Affected: 15,000
Risk Level: HIGH

Dependency Chain View:

• Shows path from target CI to affected services
• Identifies single points of failure
• Highlights redundancy gaps

Step 4: Assess Risk Level

Risk Matrix:

| Affected CIs | Critical Services | Risk Level | Recommendation | |--------------|-------------------|------------|----------------| | 0-10 | 0 | LOW | Standard change process | | 11-50 | 0-1 | MEDIUM | Manager approval required | | 51-100 | 2-5 | HIGH | CAB review required | | 100+ | 5+ | CRITICAL | Executive approval + rollback plan |

Additional Risk Factors:

• Timing: Changes during business hours increase risk
• Redundancy: No failover = higher risk
• Testing: Untested changes = higher risk
• Rollback: No rollback plan = higher risk

Step 5: Document Findings

Include in Change Request:

1. Blast Radius Screenshot: Visual representation of impact
2. Impact Summary: Number of CIs and services affected
3. Business Impact: Services unavailable and estimated users
4. Risk Assessment: Risk level with justification
5. Mitigation Plan: How you'll reduce impact
6. Rollback Plan: How to revert if issues arise

Example Documentation:

Change Request: Patch DB Server PROD-SQL-01
Blast Radius Analysis (2 levels, planned outage):
- Total Impact: 23 CIs
- Critical Services: 2 (Online Banking, Payment Processing)
- Estimated Users: 8,500
- Risk Level: HIGH

Mitigation:
- Schedule during maintenance window (Sat 2-6 AM)
- Enable database replication failover
- Pre-stage rollback scripts
- Notify affected teams 48 hours in advance

Rollback Plan:
- Revert to previous server snapshot (15 min)
- Restore database from backup if needed (2 hours)

Integration with Change Management Process

Pre-Change Assessment

Step 1: Initial Screening

• Run blast radius analysis for proposed change
• Determine risk level
• Route to appropriate approval chain

Step 2: CAB Review (for high/critical risk)

• Present blast radius visualization to CAB
• Discuss mitigation strategies
• Approve, defer, or reject based on risk

Step 3: Stakeholder Notification

• Identify affected teams from blast radius
• Send impact notifications with:
  • Affected services
  • Maintenance window
  • Expected outage duration
  • Contact for questions

During Change Implementation

Step 1: Pre-Implementation Validation

• Re-run blast radius to catch any CMDB updates
• Verify mitigation measures are in place
• Confirm rollback plan is ready

Step 2: Monitoring

• Watch for unexpected impacts beyond blast radius
• Monitor health scores of affected CIs
• Be prepared to execute rollback

Step 3: Post-Change Verification

• Verify all CIs in blast radius are operational
• Check for cascading issues not predicted
• Update CMDB if new dependencies discovered

Post-Change Review

Accuracy Assessment:

• Compare actual impact vs. predicted blast radius
• Identify false positives (CIs not actually affected)
• Identify false negatives (CIs affected but not predicted)

CMDB Improvement:

• Add missing relationships discovered during change
• Update CI criticality if impact was underestimated
• Document lessons learned

Advanced Blast Radius Techniques

Scenario Planning

Test Multiple Scenarios:

1. Best Case: Planned outage with successful failover
2. Expected Case: Planned outage with partial failover
3. Worst Case: Unplanned failure during peak hours

Compare results to understand risk range.

Comparative Analysis

Before Infrastructure Changes:

1. Run blast radius on current infrastructure
2. Model proposed new infrastructure in CSDM Workbench
3. Run blast radius on new design
4. Compare impact reduction

Example:

Current: Single web server
- Blast Radius: 12 critical services affected
- Risk: CRITICAL

Proposed: Load-balanced web server cluster
- Blast Radius: 0 critical services (automatic failover)
- Risk: LOW

Dependency Mapping

Identify Single Points of Failure:

1. Run blast radius on all critical CIs
2. Sort by "Total Impact" descending
3. CIs with highest impact are single points of failure
4. Prioritize redundancy investments

Incident Response Planning

Pre-Build Blast Radius Reports:

1. Generate blast radius for all critical infrastructure
2. Save reports for offline access
3. Include in incident runbooks
4. Update quarterly

During Major Incidents:

• Quickly reference pre-built blast radius
• Understand full scope of outage
• Prioritize restoration order (critical services first)

Best Practices

Do's

1. Run Blast Radius Before Every Change: Make it a required step
2. Document Risk Level: Include in change request
3. Update CMDB First: Accurate data = accurate predictions
4. Compare Predicted vs. Actual: Improve CMDB accuracy over time
5. Share with Stakeholders: Use visuals to communicate risk

Don'ts

1. Don't Skip for "Small" Changes: Unexpected impacts happen
2. Don't Ignore Warning Signs: High impact = high planning needed
3. Don't Proceed Without Mitigation: Reduce risk before changing
4. Don't Forget Rollback Plans: Always have an exit strategy
5. Don't Trust Outdated Data: Sync CMDB before analysis

Measuring Blast Radius Effectiveness

Key Metrics

1. Change Success Rate: % of changes without unplanned outages
2. Prediction Accuracy: Actual vs. predicted impact correlation
3. MTTR Improvement: Faster recovery with better planning
4. CAB Efficiency: Faster reviews with clear risk data
5. Incident Reduction: Fewer outages from better planning

Success Indicators

• Change success rate > 95%
• Blast radius prediction accuracy > 80%
• High-risk changes always have mitigation plans
• CAB approval time reduced by 30%+
• Unplanned outages reduced by 50%+

Related Articles

• Dependency Map - Visualizing dependencies
• Health Dashboard - Monitoring CI health
• CSDM Workbench - Modeling infrastructure
• Best Practices - CMDB hygiene

Need Help?

Contact [email protected] or use the AI Assistant to analyze blast radius for your specific changes.