Use cases

What teams use AuditWard for

AuditWard runs one audit from one URL: AI agents QA-test the site in a real Chromium browser and security-scan it with real pentest tooling. Below are the jobs people reach for it most, with an honest line on what each one covers and where it fits in your workflow.

How a run works

One URL in, evidence out.

Every use case runs the same pipeline. A Planner reads your URL and instructions and builds a test checklist. An Explorer agent works through it in a real browser while security tools probe the target. An Analyst triages the evidence into confidence-scored findings, tagged to the frameworks you care about, with annotated screenshots and a PDF report.

QA and security in one pass

The browser session checks real user flows while curl, testssl.sh, Nuclei, Nmap, Gobuster, nslookup, and WhatWeb look for exposures. You get both halves from a single scan.

Findings you can act on

Each finding is triaged, given a confidence score, and tagged per item to PCI DSS 4.0, SOC 2, GDPR, OWASP Top 10, HIPAA, or ISO 27001. AuditWard does not replace a manual penetration test. It points you at what to fix first.

FAQ

Common questions.

Do I need to pick a use case to start a scan?

No. Every use case runs the same audit. You give AuditWard a URL you are authorized to test, plus optional instructions, and the same QA and security pipeline runs regardless of which page you came from.

Does AuditWard replace a penetration test?

No. It complements one. AuditWard finds and evidences issues fast and flags them with confidence scores and framework tags, but it is not a certified pentest or an Approved Scanning Vendor scan.

Can I scan an app that sits behind a login?

Yes, on Starter and above. When a scan reaches a login wall it pauses with structured questions. You answer in the dashboard or over MCP and the scan resumes. Your answers are KMS-encrypted before storage.