Written authority before a request is sent.

The schedule must identify

Permitted testing

Only the named cases may be run, using the named identity, endpoint, client, window and limits. State-changing tools are disabled or require a separately approved fixture and consequence boundary. Load testing, vulnerability exploitation, persistence, privilege escalation, credential guessing, bypassing access controls and access to excluded data are prohibited unless a separate qualified agreement expressly authorizes them.

Stop rules

Stop immediately for disputed ownership or authority, unexpected personal or confidential data, an unlisted endpoint, material production impact, access beyond the agreed identity, an uncontrolled state change, suspected compromise or a request inconsistent with law or platform rules. Record what happened without expanding the test.

Evidence and publication

The report distinguishes requirement sources, executed observations and unknowns. Evidence is limited to what supports the agreed result. Customer identity, findings or evidence remain private unless the customer separately authorizes exact publication wording. An engagement does not create certification, security assurance, marketplace endorsement or permission to use a third party’s logo.

Confidentiality route

The service terms include mutual confidentiality. A customer may request a separate mutual NDA before sharing non-public architecture. An NDA does not replace testing authorization, privacy/operator terms, access controls or the engagement schedule.

Acceptance

Email discussion alone does not authorize testing. The final schedule and incorporated terms must be accepted in a recorded electronic form by authorized representatives. The supplier acknowledges acceptance before issuing the first invoice.