Skip to content

// Pentest

Sample pentest report

5 minUpdated November 9, 2026By Ler em português

The report, page by page

Four pages of the sample. The company is fictitious; the format is what the client receives. The sample is in Portuguese.

  • Page of the sample report. Cover: the result in one sentence and each finding on the risk scale
    Cover: the result in one sentence and each finding on the risk scale
  • Page of the sample report. Summary for whoever decides: what it means, what to do first and what is already right
    Summary for whoever decides: what it means, what to do first and what is already right
  • Page of the sample report. A finding: score, impact, steps, request and fix
    A finding: score, impact, steps, request and fix
  • Page of the sample report. Personal data: RET’s role and what falls to the client under the LGPD
    Personal data: RET’s role and what falls to the client under the LGPD
Download the sample report (PDF)

About this example

The company below, Loja Exemplo Ltda, is fictitious. No data here comes from a real customer. The format is the same as RET’s delivered reports, which follow the reporting structure of the OWASP Web Security Testing Guide.

RET runs this test: a 25-hour Sprint for R$9,500, within 7 business days. See price and timeline for my case

Findings summary

A 25-hour grey-box test of Loja Exemplo’s orders API, from 3 to 7 November.

IDTitleRiskCVSS 4.0Status
RET-001-01Another customer’s order readable by IDHigh7.1Fixed
RET-001-02Error message reveals whether an email has an accountMedium6.9Risk accepted
RET-001-03Coupon applied more than once with parallel requestsLow2.3Fixed

How a finding appears in the report

RET-001-01, another customer’s order readable by ID. High risk, CVSS 4.0 7.1 (CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N), CWE-639, OWASP API1:2023.

Description: GET /api/orders/{id} returns the order without checking that it belongs to the logged-in user. Impact: any logged-in customer reads names, addresses and items from other customers’ orders by changing the number in the URL.

How to reproduce: sign in with test account A, open your own order, replace the ID with an order from test account B. The response returns B’s order (data masked in the report).

Fix: check on the server that the order belongs to the session user before responding, and add an automated test that tries to read another account’s order.

What comes with it

Besides the technical report:

  • an executive report, free of jargon, for decision makers;
  • action plan and independence statement, when the customer falls under Brazil’s Central Bank Article 22-A;
  • findings as GitHub or Jira issues, if the customer wants them;
  • a second check of fixes for 90 days and an attestation letter with the result.

Frequently asked questions

Is this example from a real customer?

No. Loja Exemplo Ltda is fictitious. A customer report is confidential and only shared with their permission.

How much does a test like this cost?

The 25-hour Sprint costs R$9,500, delivered within 7 business days.

Does the attestation letter say the system is secure?

No. It states what was tested, when, how many findings there were and the status of fixes. It is not a certificate or a compliance opinion.

Keep reading