Use case · Change approval

Approve the exact script version.

Approve the script, not a description of it. Every report ties findings to line numbers, rule IDs and engine versions.

No card required. Your script is never executed.

Three patterns we flag

  • The change ticket says one server; the script says all

    Get-ADComputer -Filter * | Restart-Computer -Force
  • The ticket says purge old rows; the query has no WHERE

    Invoke-Sqlcmd -Query "DELETE FROM dbo.Events"
  • The backout plan assumes a snapshot the script deletes

    Get-VM | Get-Snapshot | Remove-Snapshot

Sample: purge-audit.ps1

Real pattern, synthetic script. SQL changes every row in a table.

Try this sample in the free checker

What every report contains

  • Verdict
  • Blast radius
  • Permissions
  • Reversibility
  • Rule IDs
  • Engine versions

Exports

  • PDF, Markdown and JSON: available today
  • ServiceNow and Jira attachment: coming next

What we check

  • Verdict and blast radius
  • Permissions needed
  • Reversibility and rollback steps
  • Rule IDs and engine versions

What we can't know

  • · How many objects match in your environment when it runs
  • · The current state of your environment
  • · Which permissions the account running it actually holds

The script is never run and we never connect to your environment, so every report states what it could not determine.

Check the next script before it runs.