REQUEST A

PENTEST.

Start with four qualification details: work email, company, target type, and desired outcome. If the request is a fit, we follow up to confirm authorization, detailed scope, access needs, safety constraints, and timing before any testing begins. The agreed engagement concludes with the reporting deliverables defined during scoping.

Timing depends on the authorized scope, target complexity, access, testing constraints, and reporting needs. We confirm an expected schedule after qualification and detailed scoping rather than promising a fixed turnaround from the initial request.

The initial request intentionally excludes credentials, target URLs, IP addresses, repositories, and other sensitive scope details. If the request proceeds, the team agrees an appropriate method for collecting authorization, target information, access material, and engagement-specific data-handling requirements.

Not in the qualification form. Some authorized assessments may benefit from scoped test accounts, while others can be performed without credentials. Any access requirements and a suitable transfer method are agreed during detailed scoping.

You can request qualification for a web application, API, mobile application, source code, network or infrastructure, or a combination of surfaces. Final coverage depends on authorization, technical fit, safety constraints, and the scope agreed for the engagement.

Deliverables are confirmed during scoping. A typical report can include an executive summary, in-scope findings, evidence collected within the authorized boundaries, risk rationale, remediation guidance, and stated limitations. A report may support an assurance program, but it does not by itself establish compliance or guarantee that every vulnerability was found.