Guide
Guide (Manual pentest checklist) is a workflow tool for a manual penetration test, not an automated scan. Your tester works through a structured checklist based on the OWASP Testing Guide, PTES and NIST SP 800-115, records the result of each check with notes and evidence, and ends with a session report.
What the checklist covers
8 checks, including MFA bypass, account lockout, password reset tokens and OAuth handling.
5 checks, including IDOR, horizontal and vertical privilege escalation and CSRF.
6 checks, including session fixation, cookie flags, logout invalidation and idle timeout.
8 checks, including SQL injection, XSS, XXE, command injection, SSTI and path traversal.
5 checks, including price manipulation, race conditions, workflow step skipping and mass assignment.
A check on the TLS version and cipher suites the application accepts.
A manual test with a paper trail
- 1
Start a session
Create a pentest session for a project. Your progress is saved, so you can stop and come back to it.
- 2
Work through the checks
Mark each of the 33 checks as pass, fail or not applicable, and add notes on what you tested.
- 3
Attach evidence
Attach files such as screenshots to a check. A failed check can be linked to a finding so that it is tracked to closure.
- 4
End the session
Finish the session to get a score and a pentest report, and keep earlier sessions in the session history.
## Finding: Broken Object Level Authorisation
**Severity:** Critical
**Endpoint:** GET /api/v2/invoices/{id}
### Proof of Concept
Using Account A credentials, access Account B invoice:
curl -H "Authorization: Bearer <account_a_token>" \
https://app.example.com/api/v2/invoices/INV-00842
### Impact
Full access to any customer's invoices and financial data.Spoorder Guide vs a spreadsheet checklist
| Criterion | Spoorder | a spreadsheet checklist |
|---|---|---|
| Structure | 33 checks in six categories | A list each tester keeps their own way |
| Evidence | Notes and files attached to each check | Scattered screenshots |
| Follow-up | Failed checks linked to tracked findings | Copied into a ticket by hand |
| Reporting | Session report and history | Written from scratch each time |
Does Spoorder perform the penetration test for me?
No. Guide does not supply testers. It gives your own tester, or the firm you hire, a structured checklist, a place to record results and evidence, and a report at the end.
What is the checklist based on?
The OWASP Testing Guide, PTES (Penetration Testing Execution Standard) and NIST SP 800-115. It has 33 checks across authentication, authorisation, session management, injection, business logic and transport security.
Is a pentest required for SOC 2, ISO 27001 or PCI DSS?
It depends on the framework and your auditor. PCI DSS requires penetration testing at least once every 12 months and after significant changes. For other frameworks, check what your auditor expects. Guide records the test as evidence; it does not decide whether the requirement is met.
What happens to a failed check?
You can link a failed check to a finding, so it is prioritised, assigned and re-tested like the findings from the scan engines.
Which plan includes Guide?
The full workflow is included from the Scale plan ($449/mo), or on Pro with the Scale engine pack add-on. Pro has a read-only preview.
Start scanning
Start with a free health check. Guide is included from Scale ($449/mo).