# How to View Blast Radius Before Clicking Remediate: Step by Step

> How to View Blast Radius Before Clicking Remediate. A practical walkthrough with ZopNight: read-only setup, production excluded by default, reversible at every step.

Source: https://zop.dev/learn/how-to/view-blast-radius-before-remediation
Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, how-to, learn

---

Use the ZopNight blast radius pre-flight check on every cloud action. Read the 1-hop adjacency graph, interpret affected, warning, and safe classes, and gate one-click remediation on risk score.

This is the practical version, the one you can follow in a single sitting. It starts read-only, touches no production resource by default, and every step is reversible, so there is no point at which you are committed to something you cannot undo. Budget about 15 minutes. Before you start you will want: A ZopNight account with blast radius enabled at the org level; Cloud accounts connected so the adjacency graph is populated; Remediation rights for the target resource type.

## The steps

1. Open the action wizard.
2. Read the impact classes.
3. Inspect each affected neighbor.
4. Check the risk score against the threshold.
5. Capture the snapshot on approval.
6. Re-check after a failed validation.

## Why this is safe to do today

The reason this is a low-stakes change is that nothing here is destructive. Scheduling stops and starts resources; it never deletes them, and your data persists across a stop exactly as it does across a normal reboot. Production is excluded by default, actions run in dependency order, and every state change is logged with what triggered it.

If you want the fuller context behind this task, the [FinOps](https://zop.dev/learn/finops) guide covers where it fits, and the [AWS EC2 scheduling](https://zop.dev/zopnight/aws/ec2) page shows the same loop applied to a specific resource.

## Getting started

Getting started is intentionally low-stakes:

- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
- Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
- Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.

Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.

## Frequently asked questions

### What if the blast radius panel is empty?

An empty panel means the resource has no 1-hop neighbors in the indexed graph. Confirm the cloud account is fully discovered and that the resource was created after the last nightly graph rebuild. Resources created in the last hour may not be reflected until the next incremental update.

### Can I lower the risk threshold per team?

Yes. The default 60 threshold can be overridden per team or per resource type from Settings, Auto-Remediation. Lower thresholds force more actions into the approver workflow; higher thresholds let more actions run one-click.