ScanQube | AppSec Operations

End-to-end path

Scope the work, run it live, read the saved story, then act.

This is the simplest durable model for the platform: Settings defines the guardrails, War Room creates fresh work, Reports explains the result, and Ops carries the next step.

Settings first when scope mattersWar Room launches live workReports explains the saved resultOps tracks the next step

Lifecycle Stages

From scope confirmation through retest.

Run Modes

Light, full, and deep execution depth.

Exit Checks

Signals that tell you the next page is now the right page.

Shortest full loop

Settings → War Room → Reports → Ops

Use this full chain when the target is new, the run is fresh, and follow-up work is likely.

Most common shortcut

Reports → Ops

When the saved scan already exists, skip the live run and move straight into detailed review.

Lifecycle Stages

Follow this order when you want to stay oriented across the whole product.

1. Confirm scope and operating rules

Check Settings when the target, protected paths, delivery defaults, or approval posture might affect the mission.

2. Launch the live mission

Use War Room to enter the target, optional credentials, optional repository, and the scan depth that matches the job.

3. Monitor the run while it is live

Use Tactical Theatre and mission telemetry to watch progress, understand what the platform is doing, and abort only if the mission is clearly wrong.

4. Reopen the saved result in Reports

Once the run saves cleanly, move into Reports so the result becomes a stable story instead of a live stream.

5. Review policy, proof, and evidence

Start with the decision summary, then open Proof and Evidence only when you need supporting detail or replay context.

6. Move action into Ops only when needed

Use Ops for follow-up ownership, routing, waiver decisions, replay health, or tracked external work.

7. Retest from the saved story

Use the saved scan, attached proof, and prior evidence as the starting point for any future revalidation.

Choosing A Scan Mode

Pick the depth that matches the job instead of always reaching for the longest run.

Light

Use this for the fastest validation pass, a quick smoke check, or a targeted re-check when you do not need the deepest exploration.

Best for speed and frequent verification.

Full

Use this as the balanced default when you want a strong live pass without committing to the longest possible run.

Best for most normal live missions.

Deep

Use this when you want the broadest and longest validation pass because the target, risk, or change deserves deeper coverage.

Best when time is less important than depth.

How To Know The Next Handoff Is Safe

These checks keep you from moving too early and losing context.

A live run is ready to leave War Room

The mission is complete, a saved scan exists, and you can reopen it in Reports without relying on the live stream.

A report is ready to leave Reports

The decision, proof, and evidence are clear enough that someone can take action without re-reading the whole scan story.

A follow-up item is ready to leave Ops

The owner, destination, approval, or replay outcome is clear and the next action is now tracked.

Rules That Keep The Lifecycle Clean

These habits reduce rework and make the product much easier to teach.

Dashboard gives context. Reports gives detail.

If you are unsure where to start, open Dashboard. If you already know the scan, open Reports.

War Room is for new work.

Use War Room only when you need a fresh run or live execution view.

Review before routing.

Confirm the scan, proof, and evidence in Reports before you push follow-up into Ops or an issue tracker.

Settings comes before automation, not after confusion.

If scope, delivery, or approval rules matter, confirm them before you launch broad work.

Ops is for action after the story is clear.

Open Ops when the work needs an owner, waiver, replay, or tracked follow-up, not when you are still interpreting findings.

Open Settings Open War Room Open Reports Open Ops

End-to-end path

Scope the work, run it live, read the saved story, then act.

This is the simplest durable model for the platform: Settings defines the guardrails, War Room creates fresh work, Reports explains the result, and Ops carries the next step.

Settings first when scope mattersWar Room launches live workReports explains the saved resultOps tracks the next step

Lifecycle Stages

From scope confirmation through retest.

Run Modes

Light, full, and deep execution depth.

Exit Checks

Signals that tell you the next page is now the right page.

Shortest full loop

Settings → War Room → Reports → Ops

Use this full chain when the target is new, the run is fresh, and follow-up work is likely.

Most common shortcut

Reports → Ops

When the saved scan already exists, skip the live run and move straight into detailed review.

Lifecycle Stages

Follow this order when you want to stay oriented across the whole product.

1. Confirm scope and operating rules

Check Settings when the target, protected paths, delivery defaults, or approval posture might affect the mission.

2. Launch the live mission

Use War Room to enter the target, optional credentials, optional repository, and the scan depth that matches the job.

3. Monitor the run while it is live

Use Tactical Theatre and mission telemetry to watch progress, understand what the platform is doing, and abort only if the mission is clearly wrong.

4. Reopen the saved result in Reports

Once the run saves cleanly, move into Reports so the result becomes a stable story instead of a live stream.

5. Review policy, proof, and evidence

Start with the decision summary, then open Proof and Evidence only when you need supporting detail or replay context.

6. Move action into Ops only when needed

Use Ops for follow-up ownership, routing, waiver decisions, replay health, or tracked external work.

7. Retest from the saved story

Use the saved scan, attached proof, and prior evidence as the starting point for any future revalidation.

Choosing A Scan Mode

Pick the depth that matches the job instead of always reaching for the longest run.

Light

Use this for the fastest validation pass, a quick smoke check, or a targeted re-check when you do not need the deepest exploration.

Best for speed and frequent verification.

Full

Use this as the balanced default when you want a strong live pass without committing to the longest possible run.

Best for most normal live missions.

Deep

Use this when you want the broadest and longest validation pass because the target, risk, or change deserves deeper coverage.

Best when time is less important than depth.

How To Know The Next Handoff Is Safe

These checks keep you from moving too early and losing context.

A live run is ready to leave War Room

The mission is complete, a saved scan exists, and you can reopen it in Reports without relying on the live stream.

A report is ready to leave Reports

The decision, proof, and evidence are clear enough that someone can take action without re-reading the whole scan story.

A follow-up item is ready to leave Ops

The owner, destination, approval, or replay outcome is clear and the next action is now tracked.

Rules That Keep The Lifecycle Clean

These habits reduce rework and make the product much easier to teach.

Dashboard gives context. Reports gives detail.

If you are unsure where to start, open Dashboard. If you already know the scan, open Reports.

War Room is for new work.

Use War Room only when you need a fresh run or live execution view.

Review before routing.

Confirm the scan, proof, and evidence in Reports before you push follow-up into Ops or an issue tracker.

Settings comes before automation, not after confusion.

If scope, delivery, or approval rules matter, confirm them before you launch broad work.

Ops is for action after the story is clear.

Open Ops when the work needs an owner, waiver, replay, or tracked follow-up, not when you are still interpreting findings.

Open Settings Open War Room Open Reports Open Ops

Scan Lifecycle

Scope the work, run it live, read the saved story, then act.

Lifecycle Stages

Choosing A Scan Mode

How To Know The Next Handoff Is Safe

Rules That Keep The Lifecycle Clean

Platform Documentation

Loading documentation

Scan Lifecycle

Scope the work, run it live, read the saved story, then act.

Lifecycle Stages

Choosing A Scan Mode

How To Know The Next Handoff Is Safe

Rules That Keep The Lifecycle Clean