Trust and confidentiality

Client evidence is part of the security scope

Penetration tests and incident reviews can create sensitive evidence. Data handling must be agreed before credentials, reports or customer records are exchanged. The public contact path is for scope only, not secrets.

  • Manual validation
  • Secure evidence
  • Practical remediation

Coverage

Before evidence is shared

The engagement owner should confirm these controls in writing.

Client and target ownership

NDA or confidentiality terms

Named recipients

Approved transfer method

Least-privilege access

Permitted evidence types

Retention and deletion expectations

Incident escalation path

At a glance

Data by stage

Minimize data at every point in the engagement.

StagePreferred practice
Initial inquiryShare asset types, counts and deadlines, not credentials or private reports
ScopingUse redacted diagrams and inventories where possible
TestingUse dedicated test accounts and synthetic data
EvidenceCapture only what proves the finding and redact unrelated records
ReportingLimit distribution and classify the document
ClosureFollow the contracted retention or deletion process

Coverage

Credential controls

Access design affects both assessment quality and client risk.

Dedicated time-bound accounts

Representative roles rather than shared production users

MFA and secure secret exchange

No credentials in email body

Revocation after testing

Audit logs retained

Access reviewed before retest

What this means

Contract details to confirm

Exact retention periods, data location and any subprocessors should be confirmed in the proposal or service agreement. This page explains the working principles and is not a substitute for engagement-specific contractual terms.

Coverage

Security Hub privacy boundaries

The public hub keeps assessment inputs separate from website measurement.

The scope builder runs locally and does not submit its field values

Browser tools state when processing is local

Dedicated scanners open on a separate VAPT Experts property with their own notice

Google Analytics measures page and approved navigation activity with first-party analytics cookies

Advertising storage, Google Signals and advertising personalization are disabled

Public forms and email are not approved channels for credentials or protected evidence

Commercial details

Read the main website privacy policy

The main privacy page governs the primary website and contact form. Engagement-specific handling remains controlled by the signed agreement.

View Privacy Policy

Common questions

Common questions before you decide

Can we sign an NDA before scoping?

Yes. Ask for the NDA process before sharing sensitive architecture, reports or credentials.

Can we email a scanner report?

Use the initial email only to describe the report. Agree a secure transfer method before sending unredacted output.

Do you need production data?

Usually no. Synthetic or minimized data is preferred. Any real sensitive data requires explicit approval and handling controls.

Next step

Turn the requirement into a clear, testable scope

Share the asset type, important roles or environments, testing deadline and the decision the report needs to support. You can begin without sending credentials or sensitive evidence.

  1. 01Describe the need
  2. 02Confirm scope and safety
  3. 03Receive clear commercial terms
Build a Scope