Product

From blank target to a report from saved work

Follow one engagement through AttackCompass — record what you find, see what deserves attention next, keep the route clear, and build the report from work you already saved.

You choose and run every action. AttackCompass keeps the engagement coherent.

Workflow cards

Workflow cards with detailed instructions — not thin checklists

Browse technique steps by phase. Each card is operator-controlled — you choose what to run, and AttackCompass keeps the method and context attached to the engagement.

Inside a card

One step: instructions, commands, success, failure

Open a card and work it like an operator. You get the method, copyable commands for the active target, what success looks like, and what to try if it fails.

Operator controlled. No autonomous exploitation. Commands stay in your terminal.

Active route

Keep From / Via / Target visible

Real engagements branch. AttackCompass records the active route so pivots stay readable while recommendations stay scoped to where you are.

Operator-controlled. No autonomous exploitation.

From

Operator position

Where you start

Via

Current pivot

How you got here

Target

Active focus

What you are working on

Recommendations

Recommendations you can understand

Steps are ranked from engagement evidence — not open-ended model improvisation. The important part: AttackCompass tells you why.

What it considers

  • What you discovered
  • Where you are in the engagement
  • What access you have
  • Technique requirements
  • What you already attempted
  • Likely value of the next action
RecommendedDeferredBlockedCompleted

Example

Suggested next step

Recommended

Recommended because what you already saved supports this action, and nothing it needs is still missing.

You can read the reason and decide whether the step fits.

Fit

Built for how pentesters already work

AttackCompass is not another tool you run. It is the system that keeps the engagement coherent from discovery to report.

Will this replace my tools?

No. Keep Nmap, Burp, BloodHound, NetExec, and the rest. AttackCompass sits above them and connects the engagement.

Can I run my own methodology?

Yes. You choose every action. Recommendations adapt to what you saved — they do not force a fixed checklist.

What about custom engagements?

Start from web, network, Active Directory, or custom. Record what you find and the next-step ranking follows that state.

Will this slow me down?

Capture has a cost. The payoff is not reconstructing the engagement when it is time to report — and not losing the why behind each next step.

Guided engagement

One path from scope to report

The same loop you run on a real authorized pentest — kept in one workspace.

  1. Create the engagement

    Start a workspace for the authorized test. Choose the engagement shape that matches the work — web, external, internal, Active Directory, or custom.

    Web ApplicationExternal NetworkInternal NetworkActive DirectoryCustom
  2. Record discoveries

    Add hosts, services, credentials, and findings as you test. Keep using Nmap, Burp, BloodHound, and the rest — in Lab mode you can also import Nmap or OpenVAS XML.

    HostsServicesCredentialsFindingsNmap / OpenVAS
  3. Run operator-controlled steps

    Open a workflow card for instructions, copyable commands, success checks, and failure fallbacks. You choose and run every action.

    InstructionsCommandsSuccessFailure
  4. Follow the route

    Keep From / Via / Target clear so pivots stay readable as the engagement branches.

    FromViaTarget
  5. Capture evidence

    Save notes, screenshots, and proof while you work so the report is not rebuilt from memory later.

    NotesScreenshotsProof
  6. Build and review the report

    Add saved findings and proof to the report. Edit and review — including diffs that mark sections that may need attention — then export: Lab mode can export the complete rendered PDF; Client mode uses browser print / Save as PDF. Lossy Markdown content export is available in both.

    FindingsReviewPDFMarkdown

Reporting

Build the report from work you already saved

When testing stops, saved findings and proof are ready in the report editor — edit and review, then export. Lab mode: complete rendered PDF. Client mode: browser print / Save as PDF.

  • Saved findings and proof pulled into the report
  • Edit text and layout; review diffs mark sections that may need review
  • Lab mode: export the complete rendered PDF; Client mode: browser print / Save as PDF
  • Lossy Markdown content export when you need the content elsewhere

7-Day Full Trial

Run the loop on an authorized engagement

Full access for seven days. No billing details required to start. Discover → prioritize → capture evidence → generate report.

Read the Security Model