Authorization & Business Logic Research

Stop finding endpoints.
Start finding authorization bugs.

TraceHound maps APIs, analyzes permissions, discovers authorization weaknesses and uncovers business logic vulnerabilities that traditional scanners miss.

Built for bug bounty hunters, penetration testers and application security teams.

↗Authorization paths
made visible
Cross-role test
in progress
BUILT FOR THE BUGS THAT HIDE BETWEEN REQUESTSExplore the gap

Designed for people who test what happens next

Bug hunters
AppSec teams
Pentesters
Red teams
API security engineers

The authorization gap

Today's security tools miss the bugs that matter most.

Endpoints are only the surface. The hardest flaws live in the relationships between identities, permissions, resources and the workflows that connect them.

B

Burp Suite

Manual testing
IN YOUR TOOLKIT

Excellent request interception

Business logic needs human-led workflows

N

Nuclei

Template scanning
IN YOUR TOOLKIT

Broad vulnerability coverage

Limited context across identities and state

Z

OWASP ZAP

DAST automation
IN YOUR TOOLKIT

Flexible automated testing

Authorization research is not its focus

THE UNMAPPED TERRITORY

Coverage ends where context begins.

Finding a route is easy. Knowing which identity can reach which resource, through which sequence, is the hard part.

Authorization testingBusiness logic discoveryMulti-role workflows
TTHE NEXT LAYERTraceHound

A different layer of API security

From isolated requests to the full attack path.

A research platform designed to model how real people, roles and workflows interact with your API.

01 / MAP
AAdmin
MMember
RResource
⌘Endpoint
!Permission
UNEXPECTED ACCESS
expected investigate

Authorization graph

See how users, roles, resources, endpoints and permissions connect. Spot the access paths that fall outside the expected model.

02 / COMPARE
IDENTITYREADUPDATEDELETE
Admin
Manager
Member
Guest
!Member can update another user's recordREVIEW

Multi-user attack matrix

Model admin, manager, member and guest sessions side by side. Test how each identity can interact with the same object.

03 / TRACE
CreatePOST /orders
ApprovePOST /orders/:id/approve
PayPOST /paymentsBYPASS?
DeployPOST /release
TransferPOST /transfer

Workflow intelligence

Connect create, approve, pay, deploy and transfer actions. Find missing steps, trust boundaries and sequence bypasses.

04 / CONNECT
ATTACK PATH CANDIDATEHIGH IMPACT
IDIDORRead another account
↑Privilege escalationAssume manager role
◎Account takeoverChange recovery email
4 requests correlatedConfidence 0.94

Attack path discovery

Link low-level authorization failures into a clear, evidence-backed chain with real impact and reproducible requests.

Built around authorization

The context traditional scanners don't model.

A focused toolkit for the places where endpoint discovery ends and security research begins.

Authorization mapping

Map IDOR and BOLA risk across identities, permissions, endpoints and owned resources.

Business logic engine

Reason about application rules, trust boundaries and actions that should not be possible.

Workflow discovery

Connect API calls into real user journeys and surface missing or reorderable steps.

Attack graphs

Turn scattered observations into traceable, evidence-backed attack paths.

Privilege escalation

Identify where a low-privilege identity can gain access or perform a restricted action.

API relationship analysis

Understand how operations, objects and state changes relate across an API.

Role-aware testing

Compare roles to uncover BFLA, vertical privilege escalation and cross-role access.

GraphQL security analysis

Explore object access, field permissions and resolver behavior across GraphQL operations.

Multi-user sessions

Keep identities distinct while testing the same resources and workflows side by side.

Evidence-based findings

Make every lead reviewable with the requests, responses and reasoning behind it.

A research workflow, end to end

Make the invisible testable.

TraceHound is being designed to fit into the way security teams already investigate APIs.

01

Capture traffic

Start with the API traffic and workflows you already know.

02

Map permissions

Identify users, roles, resources and the access boundaries between them.

03

Model workflows

Connect requests into sequences with meaningful state and business context.

04

Discover attack paths

Compare identities and actions to find unexpected access and bypasses.

05

Validate findings

Review evidence, confirm impact and keep the final decision in human hands.

i

Discovery should support the researcher, not replace their judgment. Findings are designed to be inspected and validated before they are reported.

The path ahead

Built with the community. Shipped with intent.

Milestones are directional while we validate the product and learn from early researchers.

IN RESEARCH

Q1

Concept validation

Learn from the researchers who face authorization testing every day.

Q2

Private alpha

Put the first authorization mapping workflows in expert hands.

Current focus

Q3

Research edition

Expand workflow modeling and attack path analysis with community feedback.

Q4

Public launch

Make a focused authorization research platform available to more teams.

FUTURE

Enterprise platform

Explore team workflows, governance and integrations as the product matures.

Sequence shown for product planning. Timing may change as research and community feedback shape development.

Pricing, shaped by the people who use it

Good security research tools should be accessible.

We are validating what a useful product looks like at each stage. No pricing is set yet.

Community

For curious researchers

Coming soon

  • Core authorization research
  • Community-led feedback
  • Early product updates
Help shape community

Enterprise

For product security teams

Coming soon

  • Team-oriented workflows
  • Scale and governance needs
  • Integration exploration
Help shape enterprise
↗

Pricing is not yet finalized. We are collecting feedback from the security community before making a decision.

Share what feels fair

Help shape TraceHound

Get in before the first release.

Tell us what you test, what you need, and what a tool like this would be worth to you. Your answers will shape what we build.

Early access updates, without the noise

A say in the features that matter

Optional invitation to a private alpha

We only collect what you share here. We never ask for API traffic, credentials or target details.

TRACEHOUND / EARLY ACCESS

Join the research list

What would you realistically pay per month?

A research signal, not a commitment to purchase.

Your details help us validate demand and contact you about TraceHound. No spam, and no API data collected.

Independent research, early support

Support early development.

TraceHound is being developed independently. If you believe authorization testing deserves better tools, you can become an early supporter.

Support options are being prepared. Join the waitlist to hear when they open.

Buy a coffeeOne-time encouragementSoonEarly supporterHelp fund the researchSoonFounding memberBack the first editionSoon

Secure checkout destinations will appear here when configured.

The useful details

Questions from the field.

Straight answers while the product is still taking shape.

01How is TraceHound different from Burp Suite?

Burp Suite is excellent for intercepting, inspecting and manually testing requests. TraceHound is being designed to focus on the relationships around those requests: identities, object ownership, permissions and multi-step business workflows. It is intended to complement hands-on testing, not replace a capable proxy.

02Is TraceHound a replacement for Nuclei?

No. Nuclei is built for fast, template-based checks across many targets. TraceHound is focused on authorization and business logic research that depends on context across users, resources and sequences of actions.

03Which APIs will it support?

The initial direction is HTTP APIs used by real applications. We are validating which capture and modeling workflows matter most before finalizing the support matrix.

04Will it support REST APIs?

REST-style APIs are a core use case for the product vision, including object-level authorization, role checks and workflow transitions.

05Will it support GraphQL?

GraphQL security analysis is part of the roadmap direction. We are exploring how to model resolver access, object relationships and field-level authorization clearly.

06When will TraceHound launch?

There is no confirmed public launch date yet. The current roadmap is directional: concept validation, private alpha, research edition and public launch. Join the waitlist for meaningful updates.

07How much will it cost?

Pricing is not finalized. We are collecting willingness-to-pay feedback across community, individual and team use cases before making a decision.

08What happens to my waitlist information?

We use the details in this form to understand demand and contact you about TraceHound updates or early access. We do not request API traffic, credentials or target details in the waitlist.

09Can I run tests locally?

Local testing is an important design consideration for sensitive application data. The deployment model and specific local or self-hosted options are still being evaluated.

10Is this designed for authorized testing only?

Yes. The product is intended for testing systems you own or have explicit permission to assess, such as an approved bug bounty scope or a client engagement.

11Will there be an enterprise edition?

An enterprise platform is a future roadmap direction. Team access, governance, deployment and support requirements will depend on feedback from AppSec and security engineering teams.

12Will TraceHound fit into CI/CD?

CI/CD integration is an area we want to understand with teams. Authorization and workflow tests often need realistic identities and state, so we are validating where automation helps without creating noisy or unsafe checks.

13How can bug hunters use it?

The intended workflow is to help researchers compare roles, explore ownership boundaries and connect request sequences while investigating an authorized target. Findings still need manual validation and must follow each program's scope and rules.

14Does TraceHound automatically exploit vulnerabilities?

The product vision centers on discovering, explaining and validating authorization weaknesses. Safe behavior, user control and evidence review are design priorities; final execution boundaries are still being defined.

15Can I influence what gets built?

Yes. The waitlist asks about your role, interest in a private alpha and pricing expectations so we can prioritize around real research needs. You can also share feedback when we contact you.