The target list grows
One target can lead to many systems and paths.
Keep recon, creds, pivots, findings, and evidence connected in one workspace. AttackCompass helps you see what to test next, where expected inventory still has gaps from incomplete enumeration, and what belongs in the final report. You stay in control.
See AttackCompass on a real engagement before you decide.
As you scan and look around, save each host, service, and login you find.
See what to try for a first foothold and why. Save proof as you work.
When you get in, see what higher access to try next. Keep the path clear.
Use your saved loot and findings to write the final report.
Pentesting gets messy fast
A pentest may start with one target. Soon, your notes, proof, and test results are spread across many tools.
One target can lead to many systems and paths.
A new service, login, or finding can open a better path.
It may sit in notes, screenshots, or terminal logs.
You may have to search old notes to rebuild the report.
Done, blocked, and still open can live in different places.
One place for your pentest work
Each step uses what you already saved. Your findings and proof are ready when you write the report.
Add what you find as you test. In Lab mode, you can also import Nmap or OpenVAS XML files.
See what to test next. Each step says why it is recommended or what it needs first.
Save notes, proof, findings, logins, and access paths as you work.
Add saved findings and proof to the report. Edit and review. Lab mode: export the complete rendered PDF. Client mode: browser print / Save as PDF.
Works with your tools
Keep using your current tools with AttackCompass. In Lab mode, add hosts and services by importing Nmap or OpenVAS XML. For other tools, save the key findings, notes, proof, and results in one place.
Import XML files in Lab mode to add hosts and services.
Use Burp as you do now. Save the key finding and proof in AttackCompass.
Record useful findings and route details from the work you run outside AttackCompass.
Copy commands out, run them yourself, and save the result.
Run them outside AttackCompass. You choose every action.
Keep both. AttackCompass records what you found and what may be useful next.
Reporting
Save notes, proof, and findings while you test. When it is time to write, the work is ready to use and review.
Report
Show what was approved for the pentest.
Explain how the pentest was run.
Show how the work moved from one step to the next.
Add each issue and the systems it affects.
Add the proof that supports each finding.
Add clear steps to lower the risk.
State what was not tested or could not be checked.
Check changes and old sections before delivery.
A Letter
Real pentests do not follow a straight line. One host leads to a new service. A login opens a new path.
AttackCompass was built around one simple idea: work saved during a pentest should make the next step and the final report easier to understand.
Know what to test next. Save proof as you go. Build a report you can stand behind.
Security
Pentest engagements can contain credentials, hashes, API keys, vulnerabilities, screenshots, internal hostnames, network details, and exploit evidence. Client mode is commercial client-side encryption for sensitive fields against a hosted-storage adversary — sealed before upload, with structural metadata left readable on purpose.
Commercial client-side encryption for sensitive fields against a hosted-storage adversary: credentials, findings, notes, report content, and more are sealed in the browser or local proxy before they reach AttackCompass. Supported IPv4 addresses and ranges become keyed projections.
In Client mode, screenshots and engagement media are encrypted on your device before upload. The hosted app stores opaque ciphertext.
AttackCompass ranks next steps from what you recorded. You choose and run every attack action. The web product does not autonomously execute attack tools.
Deleting a workspace hard-deletes its database records. After a trial expires or a paid subscription ends without renewal, inactive accounts and engagement data are retained for 30 days, then permanently deleted.
Commercial client-side encryption for sensitive fields against a hosted-storage adversary. Operator controlled. No autonomous exploitation.
7-Day Full Trial
Get full access for seven days. Start with the sample engagement or use AttackCompass on your own approved pentest.
Discover → prioritize → capture evidence → generate report
No billing details required to start. If you do not choose a paid plan and agree to its terms, the trial ends after seven days without a charge.
Full Founding Operator access for seven days. No demo-only limits.
A trial converts only after you choose a plan, enter billing details, and agree to renewal. Paid plans renew on their own. Cancel any time. Tax calculated at checkout.
Ask for a full refund within 30 days of your first payment.
Email [email protected] within 30 calendar days of the first payment (UTC). Renewals and chargebacks do not qualify. See the Refunds page for full terms.
No. AttackCompass gives guidance. You choose and run every action.
Yes. Keep using your current tools with AttackCompass.
Client mode is commercial client-side encryption for sensitive fields against a hosted-storage adversary. Read the security page before adding client data — it explains what is sealed before upload, what structural metadata remains server-readable, and what happens when you export or delete data.
A trial without billing consent expires without a charge. Paid users can cancel anytime through the Stripe customer portal. If you need the portal link or help canceling, email [email protected]. For refund rules, see the Refunds page.