CompTIA PenTest+ guideStudy & preparation
CompTIA PenTest+ Reporting: Turn Evidence Into a Useful Finding
Short answer
Build a PenTest+ report finding from what the evidence actually shows, then explain its significance and limits for the intended reader. CompTIA's PT0-003 objective 1.4 names executive summary, methodology, detailed findings, attack narrative, recommendations, limitations and assumptions. Use the fictional exercise below to practice those components; its structure is an editorial teaching aid, not a mandatory CompTIA template.
Which report components does PT0-003 name?
Build the finding from supported observations, then adapt the explanation to its audience. CompTIA's PT0-003 objective 1.4 names executive summary, methodology, detailed findings, attack narrative, recommendations, limitations and assumptions; the objectives document, version 5.0, was checked November 11, 2026.
This exercise follows the V3/PT0-003 exam identified on CompTIA's certification page, also checked November 11, 2026. Use each component to answer a different question:
| Component | Question to answer in your draft |
|---|---|
| Methodology | What authorized activity produced the evidence? |
| Detailed finding | What happened, where, and which evidence supports it? |
| Attack narrative | How did the observed events connect? |
| Executive summary | What does the result mean for the client's decision? |
| Recommendations | What action follows from the finding? |
| Limitations and assumptions | What was not tested, and what information was accepted as given? |
These are writing prompts, not a prescribed report order or grading rubric. The flashcards planned for full CompTIA PenTest+ prep can help you recall the component names. For the surrounding exam topics, use the PenTest+ exam outline. Here, practice one narrower task: preserving the meaning of evidence as you turn it into a report.
What belongs in a finding before you state the impact?
Start with this fictional evidence packet. Every system, account, result and client decision below is invented for the exercise. The packet is not an official or recalled exam question.
The client authorized a check of export permissions in a staging portal containing synthetic records. Its supplied access policy says a Viewer may read the dashboard but may not export records. The tester used the assigned Viewer account, selected the portal's visible export control and received a file containing three synthetic records.
| Evidence reference | Supplied information |
|---|---|
| E1: client policy and account record | The assigned account has the Viewer role; the stated policy prohibits that role from exporting records. |
| E2: test log | The assigned account used the export control during the authorized staging test. |
| E3: captured result | A returned file contains three synthetic records from the test dataset. |
| L1: scope limit | No production system, other account or other role was tested. |
| A1: client decision | The application team will review the export authorization rule, prepare an approved correction and arrange a retest. |
A flawed note might read: “Critical breach: anyone can download all customer data. Fix permissions immediately.” It adds an unsupported severity, expands one account to everyone, turns synthetic records into customer data and implies unlimited access.
Rewrite it as a finding grounded in the packet:
Viewer account exported records contrary to the supplied policy. In the authorized staging test, the assigned Viewer account used the export control and received three synthetic records (E2–E3). The client's policy prohibits exports for this role (E1). The result demonstrates a mismatch between the stated export restriction and the behavior observed for this account in staging. Production behavior and access by other accounts or roles were not tested (L1). The application team has agreed to review the export authorization rule, prepare an approved correction and arrange a retest (A1).
The revision identifies the affected setting, the expected behavior, the actual behavior and the evidence. It does not guess the implementation defect. If the underlying observation still needs validation, work through the PenTest+ vulnerability-validation guide before turning it into a confident report claim.
How does an attack narrative connect observations?
Use the narrative to explain the relationship between events. For this packet, the meaningful sequence is the assigned role, the authorized test action, the returned result and the comparison with the client's rule.
An appropriate short narrative is:
The tester began with the client-assigned Viewer account in the staging portal. During the approved permissions check, the tester selected the export control and received a file containing three synthetic records. Comparing that result with the supplied Viewer policy identified the export-permission mismatch.
Each sentence can be traced to the packet. There is no supplied evidence of privilege escalation, lateral movement, persistence or access to another system, so none belongs in this narrative. To recognize lateral movement and persistence when evidence does show them, see the Post-exploitation and Lateral Movement practice planned for CompTIA PenTest+ prep.
Do not make a short chain sound more dramatic to justify the heading. Instead, check whether a reader can follow how the conclusion arose. If a step depends on an assumption, identify it rather than filling the gap with a plausible technical story.
How do you write the executive version of the same evidence?
Keep the same finding, but focus on the decision and the boundary. An executive summary should not become more certain merely because it contains fewer details.
For this exercise, use these two sentences:
In a staging test, a Viewer account exported synthetic records despite the client's stated restriction, showing that the tested access rule was not enforced for that account. The application team has agreed to review and correct the rule and arrange a retest; production systems and other roles were not tested, so this result does not establish their exposure.
The technical version supplies evidence references and the observed sequence. The executive version preserves the significance, agreed action and limit. Neither asserts a real data breach or predicts a financial loss.
Compare the two versions side by side. If one says “staging” while the other implies production, or one says “one account” while the other says “all users,” repair that change in meaning before polishing the wording.
Where do assumptions, limits and recommendations belong?
For this example, the supplied client policy defines the expected behavior. That is different from an observation produced by the test. Write the source of the expectation explicitly so a reviewer can distinguish what the client stated from what the tester demonstrated.
The scope limit also belongs beside the conclusion it limits. Listing “production excluded” only in a distant section would leave an unqualified claim of production exposure misleading.
CompTIA's PT0-003 objective 1.5 addresses remediation. In this exercise, the next action comes from the fictional client's decision, not from an unsupported claim that a particular code change will fix every case. Do not prescribe a patch, configuration setting or implementation technique that the packet never establishes. The questions planned for CompTIA PenTest+ prep at launch cover the Engagement Management domain, where objectives 1.4 and 1.5 sit.
Before handover, turn the agreed action into a request for the missing details: who owns the review, what correction is approved, and what authorized retest will compare actual behavior with the intended policy. Keep those details pending until supplied. A recommendation is not evidence that remediation has occurred.
What should you check before handing over the report?
Read the revised finding against the packet one sentence at a time:
- Trace the claim. Identify the observation, client statement or clearly labeled inference supporting it.
- Keep the scope visible. Preserve the tested environment, account and result without generalizing beyond them.
- Separate result from cause. Do not claim a particular implementation failure unless the evidence establishes it.
- Reconcile the audiences. Check that the executive summary and technical finding describe the same event and uncertainty.
- Leave an actionable handoff. State the agreed next step and any ownership or retest details still needed.
Now cover the worked finding and rewrite the packet in your own words. Produce one technical finding and a two-sentence executive summary, then underline any claim you cannot trace back to the supplied information.
Use the 20 free PenTest+ practice questions for additional concept checks, and place another report-writing exercise in the free PenTest+ study plan. Keep the writing exercise separate from your multiple-choice result: the useful output here is a report another reader can assess without guessing what was observed.
Trust the source
Official sources
Exam policies can change. Use these primary sources for the most current details.