Audit360 by ScopedAudit

Authorized security audits, from scope to report.

Audit360 orchestrates proven open-source security tools inside a signed, traceable framework. Black box, grey box, white box and red team — on your own servers.

Request a demo See how it works

For authorized, contracted audits only.

Web portal — grey box live STOP 
[guard] authorization ROE-014 · valid ✓
[guard] app.example.org · in scope ✓
[task]  port scan · isolated container started
[scan]  22/tcp   open  ssh
[scan]  443/tcp  open  https
[guard] re-check every second · ok
[task]  vulnerability scan · 3 findings normalized
[guard] 10.0.9.4 · out of scope — task refused
Illustration of the Audit360 live console.

Why ScopedAudit

What separates an audit from an attack is the framework around it.

01

Authorized

No task starts on a target outside a validated scope backed by an active, unexpired authorization. The check is built into the engine, not left to discipline.

02

Traceable

Who ran what, when, on which target, with which tool and what result: every action lands in an append-only audit log.

03

Sovereign

Audit360 runs on your own infrastructure. Evidence is encrypted at rest, and no cloud service is required to operate it.

How it works

Four steps, one platform.

  1. Frame

    Create the engagement, declare its scope and assets, attach the signed rules of engagement with their validity dates.

  2. Explore

    Launch reconnaissance and vulnerability tools from one console. Each runs in an isolated, short-lived container; output streams live.

  3. Prove

    Confirm exploitability with non-destructive proofs of concept. Each attempt must be approved by a second person, a lead auditor.

  4. Report

    Findings are normalized, deduplicated and scored (CWE, CVSS), then exported as Markdown, HTML, SARIF or JSON.

Black box

No prior knowledge of the target.

Grey box

Partial knowledge: test accounts, partial documentation.

White box

Full access: source code, architecture, credentials.

Red team

Objective-driven campaigns over time, with a timeline and an aggregated report.

Safeguards

Built so that the wrong thing cannot happen by accident.

A professional audit tool is defined by what it refuses to do. These controls are part of the engine and cannot be switched off from the interface.

  • Scope guard on every task. Targets outside the validated scope are refused before anything runs.
  • Continuous re-check. While a tool runs, the authorization is verified again every second; a revoked or expired one stops the task.
  • Emergency stop. One button ends every running task of an audit.
  • Two-person rule. Exploitation attempts need the approval of a lead auditor who is not the requester.
  • Hardened execution. Tools run in read-only, short-lived containers with all privileges dropped and bounded memory and CPU.
  • No mass targeting, no denial of service. These are not features, and never will be.

Built for Africa

Designed for the conditions audit teams actually work in.

On-premise first

Deploy inside your own walls. Client data never has to leave the country.

French and English

The whole interface is bilingual from day one, on a translation layer ready for more languages.

Light on bandwidth

Fonts and assets ship with the application: the interface makes no third-party request.

A tool that teaches

Each tool comes with a plain-language sheet: what it does, when to use it, its impact on the target, what to expect.

Open source

Nothing hidden in the tool that audits you.

Audit360 is built entirely on open-source components and does not invent attack techniques: it orchestrates tools the profession already trusts, and keeps their results in one place.

Deployment
On your own servers, no cloud required
Languages
French · English
Execution
One short-lived, isolated container per task
Reports
Markdown · HTML · SARIF · JSON

See Audit360 run an audit end to end.

A 30-minute walkthrough on a test environment: scope, live console, findings, report.

Request a demo