Free Surface Recon
$0
A lightweight reconnaissance pass that identifies obvious public exposure and helps scope deeper testing.
Start Free Surface Recon- Surface summary
- Notable exposure list
- Suggested audit scope
WardenBot.ai starts with authorized scope, validates real exploitability, and turns confirmed findings into agent-ready remediation your team can review and apply.
This page explains the audit paths. The pricing page explains payment flow and manual scope review before checkout.
$0
A lightweight reconnaissance pass that identifies obvious public exposure and helps scope deeper testing.
Start Free Surface Recon$1,500
A focused dynamic application security test for authorized web apps and APIs, combining automation with human validation.
Request Scope Review$5,000
A combined assessment for AI-enabled applications, deployment configuration, and internet-facing infrastructure.
Request Scope ReviewBeta
Continuous security checks designed to turn approved test coverage into repeatable pipeline feedback.
Join Beta WaitlistActive testing starts only after target ownership, scope, safety limits, blackout windows, and emergency contact details are reviewed.
Submit domains, apps, APIs, credentials, test windows, and off-limits actions for manual review.
Run approved dynamic checks with rate limits, non-destructive payloads, and human oversight for sensitive cases.
Confirm impact with evidence summaries, affected components, exploit paths, and severity rationale.
Use agent-ready markdown to guide fixes, then validate against explicit retest criteria.
# agent-fix.md
## Finding
Cross-tenant report reads are possible through /api/workspaces/:id/reports when a valid session from another account supplies a guessed workspace id.
## Objective
Block access unless the authenticated account owns the workspace. Preserve existing owner access and audit logging.
## Suggested files
- src/api/workspaces/[id]/reports.ts
- src/lib/authz/workspaces.ts
- tests/api/workspace-reports.test.ts
## Implementation notes
1. Load the workspace by id before reading reports.
2. Compare workspace.accountId with session.accountId.
3. Return 403 with no report metadata when ownership fails.
4. Keep the existing audit event for allowed reads.
## Acceptance tests
- Owner can read reports for their own workspace.
- Non-owner receives 403.
- 404 and 403 responses do not leak report counts or names.
- Red-team replay command now fails with 403. Start with Free Surface Recon, then request scope review if deeper web/API or AI + Infra testing is warranted.