Sample scope — the one page you sign

The entire agreement. One target, non-destructive 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

Modenon-destructive · 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)

Data handlingTarget-derived content (surface data, findings, response excerpts) is transmitted over TLS to and processed by our model provider under its API terms — the current provider publishes that API content is not stored and is not used to improve its services without explicit agreement; we verify the terms per provider and model before any change and disclose the provider per engagement, before processing your data. We do not control provider-side compliance. On our side: your report and technical evidence are deleted 90 days after the retest completes — or, if no retest is requested, 90 days after the request window expires or the engagement closes, whichever comes first; the signed contract package is kept seven years for legal and financial proof. Early deletion on request is honored except for records we must keep under legal, contractual or tax obligations, or evidence under a documented dispute hold. Target-derived technical content is never sold, published, or used for any other purpose; administrative data (billing, signatures, email) is processed by the providers that perform those functions (payment, email, e-signature) under their terms.

AI boundaryconventional web/API routes of the target are in scope even if the app uses AI; testing model behavior (prompt injection, tools, agent actions) is the separate AI & MCP Red Team service

Test instance— (production, non-destructive)

02 · Non-destructive 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 the agreed start

The signature starts the clock: the run starts on the effective date written at signature (immediately, unless a later date is agreed — the effective date is the anchor). The full report — validated findings with PoCs, a verified-resistances certificate, and remediation guidance — is delivered within 48 hours of the effective date. 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 — one full retest pass is included in the price. Request the retest within 30 days of delivery (same scope, no new signature). A finding closes when it reads FIXED, still-vulnerable, or contested with evidence on the record; a contested finding is then re-tested until it closes. A retest requested after the 30-day window requires a new engagement.

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 — together with the Terms of Service version identified in the engagement packet at signing (dated copy attached; that signed version controls even if the public page is updated later). Nothing else is in scope.