Interactive walkthrough

See a full red-team run, stage by stage.

Click through the five stages an Audn agent executes on every pull request across your client portfolio.

Stage 01

Install the GitHub Action

One workflow file turns any client repository into a continuously red-teamed target. No agents to deploy, no runners to maintain.

  • Works on GitHub, GitLab CI, and Azure Pipelines
  • Partner API key stored as a repo or org secret
  • Zero changes to application code
.github/workflows/audn.yml
name: Audn Red Team Gate
on: [pull_request]

jobs:
  redteam:
    runs-on: ubuntu-latest
    steps:
      - uses: audn/redteam-action@v1
        with:
          api-key: ${{ secrets.AUDN_PARTNER_KEY }}
          tenant: acme-corp
          target: https://staging.acme.example
          fail-on: critical
          output: sarif

Sample output

The report your client receives — under your brand.

Run #4821 · acme-corp/checkout-api · PR #337

Blackbox red-team report

Gate failed
1
Critical
1
High
1
Medium
11m 42s
Run time
  • CriticalAUDN-1042

    IDOR on /api/v2/invoices/{id} exposes cross-tenant records

    Agent authenticated as tenant B and enumerated 3,118 invoice IDs belonging to tenant A. Chain: weak sequential IDs → missing ownership check → full PII disclosure.

  • HighAUDN-1043

    Stored XSS in workspace display name

    Payload persisted through the settings API and executed in the admin console for every member of the workspace.

  • MediumAUDN-1044

    Session cookie missing SameSite attribute

    Allows cross-site request forgery against state-changing billing endpoints.

Want this run against your own staging environment?

We'll scope an authorized target with you and walk the results live.

Client portfolio, target environments, timeline — optional.