NAXXAN ← naxxan.ai Request Verify External
NAXXAN SECURITY — ENGAGEMENT SCOPE
Sample · no engagement exists until this page is signed

Sample scope — the one page you sign

The entire agreement. One target, read-only rules, one signature, one report, one retest. Everything in [brackets] is a placeholder — your engagement signs this same page, filled in.

Ref[engagement ref]
Date of signature[date]
Target domainyourdomain.com
Moderead-only · black-box
01 · Engagement target

One public app or API, by domain

The scope is exactly one public application or API together with its domain. Everything at or below the declared origin is in scope; everything else is out. Black-box: we never need your code, your repository, or your credentials.

Domain / URLhttps://yourdomain.com [placeholder]
Repository— (black-box)
Test instance— (production, read-only)
02 · Read-only rules

What the attack will never do

The run simulates an external attacker against the declared origin: passive reconnaissance, endpoint probing, proof-of-concept execution. Every payload is non-destructive by design.

  • no destructive payloads
  • no real data exfiltrated
  • no denial of service
  • no data modified or deleted
  • no real payments
  • no social engineering of staff
  • nothing outside the declared origin

What we may create while testing: test accounts and synthetic requests to reach authenticated flows. Every account, request, and record we create is declared here in advance and itemized in the final report — contamination is a line item, never a surprise.

03 · Authorization

The signature is the authorization

This page must be signed by someone with authority over the target domain — an owner or an authorized technical lead. Payment does not authorize the run; this signature does. By signing, the client declares ownership of the declared domain and authorizes exactly this page.

04 · Timeline and deliverables

Report within 48 hours of signature

The run starts on the date agreed at signature. The full report — validated findings with PoCs, a verified-resistances certificate, and remediation guidance — is delivered within 48 hours of signature. Your code and data stay yours: black-box means we handle none of your source; the report is confidential by default.

05 · Price

Quoted before, fixed at signature

One price for the whole engagement. Quoted before signature and fixed on this page when you sign it — nothing metered, nothing surprises you later.

[price at engagement date]
06 · Retest and abort channel

Either side can stop the run

Retest included: after you remediate, we re-attack every finding once — included in the price, until each one reads fixed or formally contested.

Abort channel: a direct channel (email and phone) to the operator is declared at signature. Either side can stop the run at any moment with a single message — no justification required. Work performed up to that point is delivered as-is.

Client — yourdomain.com [name · title]
Signature · date
Naxxan Security — operator [name]
Signature · date
Signing authorizes exactly this page — the target, the rules, and the timeline above. Nothing else is in scope.
Sample document — [bracketed] fields are placeholders, yourdomain.com is an example domain. Questions before signing: engagements@naxxan.ai · the companion artifacts: sample report · sample attestation (PDF)