Prepared by NetAssist (M) Sdn Bhd
Security assessment guide
A penetration test is only as useful as its report. This guide sets out what a complete report should contain and how to check one, drawing on the US National Institute of Standards and Technology (NIST), the OWASP Web Security Testing Guide and the UK National Cyber Security Centre (NCSC). At NetAssist, a Malaysian managed security service provider, penetration testing is one of our security assessment services.
Published 29 October 2026
- The UK NCSC says a test report should include the security issues found, the test team’s view of each one’s risk, a way to resolve each issue, an opinion on the accuracy of your own vulnerability assessment and advice on improving it.
- NIST SP 800-115 says mitigation recommendations, including the outcome of the root cause analysis, should be developed for each finding.
- The CVSS v4.0 specification says a CVSS score’s vector string should be displayed with the score.
- The NCSC says any deviation from a vulnerability’s standard rating should be documented and justified by the penetration testing team.
A complete report has an executive summary in business terms, the agreed scope, method and limitations, and a findings section in which every issue carries a reference, an explained risk rating, enough detail to reproduce it and a way to fix it. NIST and the NCSC add a plan for closing each finding and advice on improving your own vulnerability assessment.
On this page9
What is a penetration test report for?
A report turns the test into decisions. NIST SP 800-115 says a report should identify system, network and organisational vulnerabilities and their recommended mitigation actions. The UK NCSC adds that the aim should always be to use a report’s findings to improve your own vulnerability assessment and management processes, so a good report improves your processes as well as listing issues.
NIST’s technical guide to security testing notes that because a report may have multiple audiences, multiple report formats may be required. The OWASP Web Security Testing Guide puts it plainly:
“The quality of the technical testing is completely irrelevant if the client can’t understand your findings.”– OWASP Web Security Testing Guide v4.2, 5. Reporting
What should the executive summary say?
The executive summary should let a manager understand the result without the technical detail. The OWASP Web Security Testing Guide suggests it covers the objective of the test, the key findings in a business context, such as possible compliance issues or reputation damage, and strategic recommendations on how the business can stop the issues from happening again.
OWASP says the report should appeal to both executive management and technical staff. As general guidance, if the person who approves the budget for fixes cannot follow the summary, ask for it to be rewritten.
What should each finding include?
Each finding should give an engineer enough to understand the issue, reproduce it and fix it. OWASP lists a reference ID, a title, the likelihood and impact, a risk level, a detailed description including how it can be exploited, and detailed remediation steps. NIST SP 800-115 adds that recommendations, including the outcome of the root cause analysis, should be developed for each finding.
| Element | What to look for | Source |
|---|---|---|
| Reference ID | An identifier used to discuss the finding and cross-reference it across the report | OWASP WSTG |
| Title and description | What the vulnerability is, how it can be exploited and the damage that may result | OWASP WSTG |
| Likelihood | How easy it is to exploit, whether working exploit code exists, the level of access required and attacker motivation | OWASP WSTG |
| Risk rating | The test team’s assessment of the level of risk the vulnerability exposes you to | UK NCSC |
| Remediation | Detailed steps to fix it, with technical and nontechnical recommendations | OWASP WSTG, NIST SP 800-115 |
| Root cause | The outcome of the root cause analysis behind the recommendation | NIST SP 800-115 |
NIST’s examples: a technical recommendation such as applying a particular patch, and a nontechnical one such as updating the patch management process. In NIST’s words, a root cause “can often be traced to program-level weaknesses”. OWASP adds that possibly sensitive data, such as passwords or personal information, should be masked.
How should severity ratings be explained?
Every issue should carry a severity rating, and the report should explain the scale it uses. The NCSC says there should be a severity rating for any issues found. OWASP suggests the values Informational, Low, Medium, High and Critical, and says the values used should be detailed in an appendix, so a reader can see how each rating was set.
Many reports also use the Common Vulnerability Scoring System (CVSS), which is owned and managed by FIRST, a US-based non-profit. FIRST says CVSS produces a numerical score reflecting a vulnerability’s severity, which can be translated into ratings such as low, medium, high and critical. The CVSS v4.0 specification says the vector string should be displayed with the score, and that users should enrich the Base metrics with Threat and Environmental values specific to their use of the vulnerable system.
The NCSC notes that other mitigating controls, or additional vulnerabilities, can justify rating an issue away from its standard level, and says any such deviation should be documented and justified.
What should the report say about scope, method and limits?
It should say what was and was not tested, how, and what got in the way. OWASP’s suggested introduction covers the agreed scope, the limitations, such as out-of-bounds areas, broken functionality, lack of time or lack of access or credentials, the timeline, and the team’s expertise and qualifications. NIST says internal reports should include test methodology, test results, analysis and a plan of action and milestones (POA&M).
Limitations matter because a report cannot speak for what was not tested: the NCSC notes testers may recommend that an out-of-scope exclusion be recorded as a limitation on testing. OWASP’s suggested appendices include the methodology, rating explanations, relevant tool output (cleaned, “not just dump it”) and a checklist of the tests conducted.
Raw tool output is not analysis: NIST says automated findings often need to be validated to isolate false positives. Our guide to penetration testing or vulnerability assessment explains the difference, and our article on what most penetration testers get wrong covers over-reliance on automated tools. NIST also says that if testing gains administrator rights on a critical system, assessors should immediately notify the person named in the assessment plan or rules of engagement.
What should happen after the report arrives?
Your team should review the report, decide on the fixes and track them to closure. The NCSC says the report should be assessed by your vulnerability management group like an internal vulnerability assessment, and that risk assessment and decisions on fixes are your responsibility. NIST recommends a POA&M so that each vulnerability is addressed with specific, measurable, attainable, realistic and tangible actions.
“Vulnerability risk assessment and mitigation is a business process and should not be wholly outsourced to the test team.”– UK National Cyber Security Centre, Penetration testing
As general guidance drawn from the NCSC, NIST and OWASP:
- Hold a debrief. The NCSC says a debriefing, where the testers run through their findings, can be useful.
- Rate in your own context. The NCSC notes testers may lack details of a system or its business impact, so may rate issues lower or higher than you.
- Choose the fix. The NCSC says the solutions your testers propose may not be the only ones possible.
- Plan and track. Record the tasks, resources, milestones and completion dates in a POA&M.
- Retest. NIST says a retest can verify a fix only if a mirror copy of the original test is performed. OWASP suggests a retest report give the updated status of earlier findings.
What does this mean for a penetration test in Malaysia?
Malaysia’s licensing definition of a penetration testing service lists “preparing appropriate mitigation procedures”, as well as finding weaknesses, among the activities it can include. NACSA’s licensing FAQ, citing the Cyber Security (Licensing of Cyber Security Service Provider) Regulations 2024 [P.U. (A) 221/2024], says a penetration testing service includes any of a list of activities, among them demonstrating how vulnerabilities may be exploited and preparing appropriate mitigation procedures.
The NACSA licensing FAQ words that activity as “indicating vulnerabilities and preparing appropriate mitigation procedures required to eliminate vulnerabilities or to reduce vulnerabilities to an acceptable level of risk”. Agree the report’s contents before testing: NIST suggests the rules of engagement set the minimum information each report will provide.
At NetAssist, we hold NACSA licences for penetration testing and managed SOC monitoring. Our penetration testing assesses networks, servers, cloud environments, critical IT infrastructure and applications, and simulates real-world attacks. We customise the scope and methodology to your business environment and provide post-assessment guidance and remediation support. What the report contains depends on what we agree to test; see our security assessment and consultancy services.
FAQ
Should a penetration test report include a CVSS score?
If you need one, ask for it with its vector string. OWASP notes that some engagements require a CVSS score, and the NCSC suggests stating reporting requirements such as CVSS scores in the scoping document. The CVSS v4.0 specification says the vector string should be displayed with the score.
Is a list of scanner results a penetration test report?
Not on its own. NIST says automated tools can produce many findings that often need to be validated to isolate false positives, and describes a penetration test report as one that describes identified vulnerabilities, presents a risk rating and gives guidance on how to mitigate them.
How should we store a penetration test report?
As sensitive information. NIST warns that details of network architecture, system configuration, security controls and specific vulnerabilities would give an adversary “a blueprint and roadmap” for exploiting your systems, and says assessment reports should be stored securely. OWASP advises securing and encrypting the report.
Does a report with no high-risk findings mean we are secure?
No. The NCSC says a penetration test can only validate that systems are not vulnerable to known issues on the day of the test. OWASP’s example disclaimer calls a test a “point in time” assessment: the environment could have changed since the test was run.
Can NetAssist carry out a penetration test?
Yes. At NetAssist, we hold NACSA licences for penetration testing and managed SOC monitoring. Our testing covers web, mobile, API, cloud, internal, external, wireless and network assessments, with the scope and methodology customised to your business environment.
Sources
- NIST SP 800-115: Technical Guide to Information Security Testing and Assessment, US National Institute of Standards and Technology, September 2008 (opened 30 Oct 2026)
- Penetration testing, UK National Cyber Security Centre, reviewed 10 January 2022 (opened 30 Oct 2026)
- Licensing of Cyber Security Service Provider FAQ, National Cyber Security Agency (NACSA) Malaysia (opened 30 Oct 2026)
- Web Security Testing Guide v4.2: 5. Reporting, OWASP (opened 30 Oct 2026)
- Common Vulnerability Scoring System SIG, FIRST (opened 30 Oct 2026)
- CVSS v4.0 Specification Document, FIRST (opened 30 Oct 2026)
Planning a penetration test?
Tell us which systems and applications you want tested and what the report needs to show. We will shape the scope and methodology around your business environment.

