Skip to content
Made for:Platform & security teams

From breach to rotation

Offline blast-radius analysis for non-human identity in CI. NHI-Blast reads your GitHub Actions, Terraform and IAM policy, then shows what a compromised entrypoint can reach, which credentials survive its revocation and the order to rotate them.

Want to see it trace a real incident?

Play the sample scan and watch NHI-Blast turn the synthetic fx07-incident fixture into a survival report and a rotation plan.

Read the quickstart

Every thread NHI-Blast follows

  • GitHub Actions workflows
  • Reusable workflows
  • Local composite actions
  • OIDC trust policies
  • Terraform plan and state
  • IAM policy documents
  • Mutable third-party actions
  • Secrets Manager entries
  • SSM parameters
  • STS sessions

The incident math,quietly worked out

NHI-Blast answers three questions from the files you already have: what was reachable, what survives the revocation, and in what order to rotate it.

From the compromised entrypoint through jobs, OIDC trust, assumed roles and IAM grants, down to every credential store at the end.

  • Workflows, Terraform and IAM read together
  • Remote reusable workflows use the caller grant

Each reachable credential ends with the job, expires on its own, or survives until someone rotates it.

  • Unknown authority never counts as survival
  • Each line names its evidence and source

Survivors are rotated after containment and in dependency order, so nothing left open can re-read a fresh credential.

  • Step by step, with the reason for each
  • Model containment first with whatif

A single HTML file with the summary, survival, rotation plan, findings and evidence. It works from a folder with no network at all.

  • Every input family labelled, no silent gaps
  • JSON and SARIF for your own tooling
Painting of a sunlit table by an open window, with a ring of brass keys on a folded document, a mug of coffee and a pot of rosemary

Ready before the incident,steady during it

Run it on every pull request, rank your mutable actions ahead of time, and have an answer the moment an entrypoint is revoked.

One scan, the whole picture

A single command parses the files, audits OIDC trust, runs each compromise scenario and writes the findings.

Every finding explains itself

Ask for any finding, node or edge and NHI-Blast prints the evidence chain behind it, down to the file and line.

A gate in CI, not another dashboard

Add --fail-on high to a workflow job and the scan exits 1 when a finding meets the threshold, so the change stops there.

Reads everything,runs nothing

NHI-Blast is built to read files it cannot trust. It reconstructs authority from what the files describe, and never executes, fetches or calls out while it does.

Nothing runs, nothing calls out

No Terraform, Git or shell commands, no downloads and no evaluation of workflow expressions. Every read stays inside the scan root, and escaping symlinks are refused.

No execution, no network

Painting of one hand passing a ring of keys to another over a porch railing, in front of a white cottage with a blue door

Secret values stay in the files

Credential values are never stored, printed, logged or embedded in a report. When a workflow holds a literal secret, only its kind and length are reported.

Only kinds and lengths, never values

About the project

A calmer wayto answer an incident.

NHI-Blast is an open-source command line tool under the MIT License, now in public beta. It rebuilds the authority your CI files describe, offline, so you know which machine credentials outlive a revoked entrypoint even when live cloud access is out of reach.

Painting of a quiet office corner at golden hour, with papers, a fountain pen and a ring of keys on a wooden table beneath an arched window onto olive trees

Field note

Unknown edges stay potential.

Three promises kept in every report

  1. i.

    Evidence before verdicts

    Every edge is declared, derived, assumed or unknown, and says so. Unknown authority is kept as potential and never counted as a credential that survives.

  2. ii.

    No silent gaps

    Analysis completeness labels every input family as analysed, partial, not provided or not supported. A missing file reads as missing, never as clean, and there is no score to hide behind.

  3. iii.

    Honest about its limits

    Version 0.3.0 is a public beta, not a production security control, and no independent audit is claimed. What it does not model is written down for anyone to read.

The NHI-Blast maintainers

Read the known limitations

Hand off the guesswork.Keep the evidence.

Whether you run one repository or a whole platform, NHI-Blast tells you what a compromised entrypoint could reach, which credentials it leaves behind and how to close them in order. It needs Python 3.12 or the Windows executable, and no cloud credentials at all.