Knowledge library

Clear answers for buying a pentest.

Start with the request in front of you. These guides explain the decisions that matter, the details that can wait, and how to evaluate the final evidence without unnecessary alarm.

Interpreting the request

Interpret the request

What does the customer mean by “pentest”?

Use this when the word is clear but the expected testing, system, timing, or evidence is not.

Clarify the request
Make first contact

What should we send a testing company first?

Use this to send enough for a useful first conversation without building the scope or sharing sensitive material.

Build the first handoff
Clarify the activity

Vulnerability scan or penetration test?

Use this when the requesting party’s language is vague or your team is comparing two different activities.

Compare the two

Planning the test

Prepare for your next deal

Could a missing pentest stall your next deal?

Find out what buyers will need and leave time for testing and fixes before a sale depends on the report.

Prepare before the ask
Plan the timeline

How long does a penetration test take?

Separate the testing window from scope, access, report delivery, remediation, and retesting.

Plan the schedule
Understand the cost

What determines the cost of a penetration test?

See how scope, roles, complexity, access, constraints, reporting, and retesting change the amount of work.

Understand the cost
Define the work

What belongs in a penetration-test scope?

Use this if you are unsure what should be included, excluded, prepared, authorized, and delivered.

Build the scope
Prepare the team

What should we prepare?

See what is helpful for the first conversation, what is needed during scoping, and what must be ready before testing.

Prepare for testing
Evaluate providers

How should we compare penetration-testing companies?

Use this to assess requirement interpretation, authorization, scope, testing approach, evidence handling, reporting, and retesting.

Compare providers

Reviewing evidence

Understand evidence

What should the report contain?

Use this when planning remediation, customer sharing, confidentiality, or follow-up questions.

Review report contents
Choose the evidence

Executive summary or full technical report?

Match the document to the reader, decision, confidentiality boundary, and required level of technical detail.

Choose the document

If the request is unclear

Start with who asked and the exact words they used.

The request may combine a testing requirement, a report request, a deadline, and questions about your systems.

Use the customer report-request guide, review the other buyer situations, or send us the request directly.

Next step

Prefer to start with the request itself?

Send a brief non-sensitive summary. You do not need to read every guide or finish the scope before contacting Trespass.