CyberSib
Field notesFN-001Nov 20, 20267 min read
Entry FN-001

How We Run a Penetration Test, From Scope to Retest

A walkthrough of a CyberSib penetration test: how we set scope, how we move from reconnaissance to privilege escalation, and what a finding has to contain before it reaches your report.

A penetration test shows how an attacker gets past your security controls and how far they get once inside. This post walks through how we run one and what you receive at the end.

A penetration test shows an attacker getting past the security controls on your network, and how far that goes, including privileged access on critical systems. The useful part is the demonstration. Scanner output lists what might be wrong. A penetration test shows what an attacker can do with it, step by step, with the evidence.

§ 1The engagement at a glance

Every engagement follows the same five phases. The testing itself sits in the middle. The phases around it decide whether the results are useful to you.

Diagram

findings shared as they are confirmed

01 Project kickoff

02 Scoping and planning

03 Security assessment

04 Progress tracking

05 Final delivery

  1. Project kickoff. We gather your security requirements, define scope and boundaries, allocate the team, and agree on a timeline.
  2. Scoping and planning. We analyze the technical environment, select the testing methodology, set up the risk rating framework, and prepare tooling.
  3. Security assessment. We combine vulnerability scanning with manual testing and evaluate each security control in scope.
  4. Progress tracking. You get weekly progress reports, documented vulnerabilities as we confirm them, updated risk ratings, and remediation recommendations.
  5. Final delivery. We hand over a detailed vulnerability report, an executive summary, a remediation strategy, and recommendations for future work.

§ 2Scope is a security control

A weak penetration test usually fails in the scope, not in the testing. If the scope lists hostnames but leaves out the roles a user can hold, the tester never learns that a “viewer” can become an “admin.” If the scope excludes the export service because it is “internal,” the tester never tries to reach it from the outside.

At kickoff we write two documents with you:

  • A scope document that lists systems, environments, user roles, and test accounts for each role. For web and API targets, we ask for at least two accounts per role so we can test whether one user can reach another user’s data.
  • Rules of engagement that cover testing windows, rate limits, systems that must not be disrupted, how to reach your on-call contact, and what we do if we find evidence of a prior compromise.

§ 3Testing methodology: five steps

Inside the security assessment phase, we work through five steps. Each step is documented, so the report shows exactly how we reached each finding.

  1. Initial scoping and planning. We confirm what is reachable and build a test plan for each component.
  2. Reconnaissance and information gathering. We map the attack surface: hosts, services, API routes, client-side code, roles, and the trust relationships between components.
  3. Vulnerability identification. We test each component for known weakness classes and for flaws specific to how your application works.
  4. Exploitation and privilege escalation. We confirm a weakness by exploiting it within the agreed rules, then try to chain it toward higher privileges or more sensitive data.
  5. Post-exploitation and reporting. We record what an attacker could reach from each foothold and write the finding with the evidence that proves it.

§ 4A worked example: privilege escalation through a role parameter

The following example is illustrative. It is not client data. It shows the type of finding that automated scanners rarely report and that a manual tester checks on every engagement.

A web portal lets users update their display name. The browser sends a PATCH request to the user API. The tester adds one field that the UI never sends:

http
1PATCH /api/v2/users/4182 HTTP/1.12Host: portal.internal.example3Cookie: sid=9f2c…; role=viewer4Content-Type: application/json56{"display_name": "j.doe", "role": "admin"}

The server responds:

http
1HTTP/1.1 200 OK23{"id": 4182, "role": "admin", "updated": true}

The API binds every field in the request body to the user record, including role. The tester now holds an admin session and requests the bulk export endpoint:

http
1GET /admin/export?all=true HTTP/1.12Host: portal.internal.example3Cookie: sid=9f2c…

The response is an 18 MB CSV file of customer records.

Diagram
Admin exportUser APITester (viewer account)Admin exportUser APITester (viewer account)PATCH /users/4182 {"role":"admin"}200 OK, role=adminGET /admin/export?all=true200 OK, full customer CSV

A scanner sees two 200 OK responses and moves on. A tester sees a viewer account that now owns the customer database. The report finding states the root cause (the update handler accepts fields the client should never control), the impact (any authenticated user can become an administrator), and the fix (an explicit allowlist of writable fields, plus a server-side authorization check on role changes).

§ 5Why we spend most of our time on access control

Access control flaws are common in public bug bounty data. The HexBrain index of 15,244 publicly disclosed HackerOne reports lists 1,494 reports in its Access Control class, 464 of them tagged as privilege escalation. The same index lists 373 more reports as insecure direct object references (IDOR).

These bugs are hard for tools because the request is valid. Only someone who knows that user A must not see user B’s invoice can tell that the response is wrong. That is why we ask for multiple accounts per role during scoping.

§ 6Retesting matters as much as testing

A fix can close the exact request in a report and leave the underlying flaw open. A public example: in HackerOne report #791775, a researcher bypassed Shopify’s email verification, which allowed takeover of store accounts through Shopify’s SSO. According to the program’s public summary, Shopify deployed a permanent fix three hours after disabling the affected feature. The researcher then bypassed email verification again, and Shopify found “another bug with a separate root cause,” which it asked him to file as a separate report.

HexBrain’s bypass library groups 256 disclosed reports under “earlier fixes,” meaning reports that got past the fix for an earlier report. That pattern is why every finding in our report includes the root cause, not only the reproduction steps, and why we recommend a retest once fixes ship.

§ 7What a finding must contain

Before a finding reaches your report, it has to answer five questions:

Question What the report includes
What is wrong? A one-line title and a plain-language summary
How did we reach it? Numbered reproduction steps with the exact requests and responses
What can an attacker do? Impact written for both engineers and the business owner
How severe is it? A severity rating with the scoring rationale
How do you close it? A specific fix for the root cause, plus defense in depth where it applies

If we can’t prove a finding with evidence, it goes in the report as an observation, not as a vulnerability. That keeps your engineers working on real issues.

§ 8Questions to ask any penetration testing vendor

Whether or not you work with us, ask these before you sign:

  • How many accounts per role will you test with?
  • Will you attempt privilege escalation, or stop at identification?
  • How do you report a critical finding during the engagement, not only at the end?
  • Does every finding include the evidence and the root cause?
  • Is a retest included?

§ 9Next step

If you want a penetration test scoped to your environment, request a scoping call. We confirm scope, boundaries, and timeline at kickoff, before any testing starts.

§ 10References

Further reading.

Related service

Penetration Testing

We show how an attacker could get past the controls on your network and reach privileged access on critical systems.

Request a scoping call
Next up
§ 02 — Next step

Who should we prepare your report for?

Type your company name to see it on the report cover and the scoping worksheet underneath. Hover over the cover to lift it.Tap the cover to lift it.

CyberSibSample
Security Assessment Report
Prepared for
Your company
ScopeDefined at kickoffFindings—Date2026
Light box · auditor view · press X to exit