Outrider Local Portal

Loading engagements…

Run dashboard

Guided onboarding and guarded run creation.

Start a New Engagement

Engagement
Scope
Review

Engagement Engagement platform Target domain Operator nameYour name or handle. This is attribution, not authenticated identity. Authorization referenceProgram name, program URL, ticket number, rules-of-engagement reference, or other opaque authorization record. Optional traffic-identification header nameOptional header supplied by a bug-bounty or client program, such as X-Bug-Bounty. Optional traffic-identification header valueOutrider stores it as engagement metadata but does not automatically attach it to current fixed enrichment providers.

Scope Primary target In-scope rulesOne rule per line: domains (example.com), wildcards (*.example.com), IPs/CIDRs, or URL paths (www.example.com/book/, api.example.com:8443/v1, www.example.com/api/*/admin). Out-of-scope rules Include all subdomains

*.example.com does not include example.com. Never assume all subdomains are authorized.

Review

I confirm that I am authorized to assess the listed scope and understand that returned observations do not expand that scope. Authorize unattended active enumeration of any in-scope asset after setup. Recorded as a revocable, time-bounded scope-wide approval; findings still require human review, and intrusive/prohibited actions remain handoff-only.

Import a Legacy Target

Create a governed run from an existing target workspace folder. Its files are registered as evidence (hash and size); no findings are created. You supply the scope and authorization.

Source Target workspace folderSubfolders of the targets base only.

Governed metadata Target domain Engagement platformPrefilled from the folder's memory.md when present; you can change it. Operator nameAttribution, not authenticated identity. Authorization referenceProgram name/URL, ticket number, or rules-of-engagement reference. In-scope rulesOne rule per line: domains, wildcards (*.example.com), IPs/CIDRs, or URL paths (www.example.com/book/, api.example.com:8443/v1, www.example.com/api/*/admin). URL assets from memory.md keep their path scope. Out-of-scope rules

Confirm I am authorized to assess the listed scope and understand the folder's files will be registered as evidence.

Run dashboard

Start a New Engagement

Import a Legacy Target

Engagement summary

Advanced Workspace