Prepared by NetAssist (M) Sdn Bhd
Security assessment guide
A vulnerability assessment finds known weaknesses across your systems and ranks them for fixing. A penetration test goes further: an authorised tester tries to exploit weaknesses the way an attacker would, to confirm they are real and see how much access an attacker could gain.
Published 20 October 2026 · Updated 27 October 2026
- NIST SP 800-115: vulnerability scanners check only for the possible existence of a vulnerability; a penetration test exploits it to confirm it exists.
- The UK NCSC sees penetration testing as a way of gaining assurance in vulnerability assessment and management, not as a primary method for finding vulnerabilities.
- Malaysia’s National Cyber Security Agency (NACSA) says penetration testing services must be licensed under the Cyber Security Act 2024 (Act 854, in operation since 26 August 2024), with some exceptions; NACSA’s FAQ gives 1 October 2024 as the start date for licence applications.
- NIST notes that several low-risk vulnerabilities can present a higher risk when combined, and calls penetration testing “a more reliable way” to identify that risk.
Penetration test or vulnerability assessment: which do you need? Choose a vulnerability assessment when you need a broad, repeatable view of known weaknesses across many systems and a ranked list to fix. Choose a penetration test when you need evidence of whether an attacker could actually exploit a particular system, application or path, and how far they could get.
On this page9
What is the difference between a vulnerability assessment and a penetration test?
A vulnerability assessment identifies and ranks possible weaknesses, mostly with automated scanning that a skilled person interprets. A penetration test, or pen test, tries to exploit chosen weaknesses under agreed rules to confirm they are real. NIST SP 800-115 groups vulnerability scanning with techniques that find possible weaknesses, and penetration testing with techniques that validate them.
“While vulnerability scanners check only for the possible existence of a vulnerability, the attack phase of a penetration test exploits the vulnerability to confirm its existence.”— NIST SP 800-115, section 5.2.1
VAPT stands for vulnerability assessment and penetration testing, the two done together.
| Aspect | Vulnerability assessment | Penetration test |
|---|---|---|
| What it answers | Which known weaknesses may exist, and which come first? | Can an agreed target be exploited, and how far could an attacker get? |
| Typical output (NIST) | Usually a list of possible weaknesses with risk levels and ways to fix them. | Usually a report of confirmed weaknesses, a risk rating and guidance on fixing them. |
| How often (NIST) | Regularly scheduled scanning. | Periodic; for networks and systems, an annual basis may be sufficient. |
| Main limits | Scanners give false positives and miss weaknesses that only appear in combination. | Covers only the agreed scope; can damage systems. |
Which one fits your situation?
As general guidance drawn from NIST SP 800-115, start with a vulnerability assessment when you need breadth, and use a penetration test when you need proof of what an attacker could do. The table maps common situations to NIST’s statements; your own risks and obligations decide.
| Your situation | Usually fits |
|---|---|
| Unsure what is exposed, or many systems to cover | Vulnerability assessment |
| Regular checks on patches and settings | Scheduled vulnerability scanning |
| Several low-risk findings that may combine | Penetration test |
| Proof that a weakness can be exploited | Penetration test |
| Checking whether your team notices an attack | Penetration test, possibly covert |
Swipe sideways to see every column
What does a vulnerability assessment show, and what can it miss?
A vulnerability assessment shows which known weaknesses may exist across your systems and how serious each is. NIST says scanning can help identify outdated software versions, missing patches and misconfigurations, but scanners “can have a high false positive error rate (i.e., reporting vulnerabilities when none exist)” and miss vulnerabilities revealed only through combinations of attack patterns.
NIST advises that “Assessors should determine the appropriate risk level for each vulnerability and not simply accept the risk levels assigned by vulnerability scanners.” Our article on what most penetration testers get wrong looks at the same over-reliance on automated tools.
When is a penetration test the better choice?
Choose a penetration test when you need to know whether a weakness can really be used against you, such as when a customer or auditor asks for evidence. NIST notes that several low-risk vulnerabilities can present a higher risk when combined, and calls penetration testing “a more reliable way” to identify that risk.
“Penetration testing should be viewed as a method for gaining assurance in your organisation’s vulnerability assessment and management processes, not as a primary method for identifying vulnerabilities.”— UK National Cyber Security Centre (NCSC), Penetration testing
NIST says penetration testing can also be useful for determining “Defenders’ ability to detect attacks and respond appropriately”, such as whether your managed security operations centre (SOC) notices. For covert or other unannounced testing, NIST says the assessment plan should define how test activity detected by your security staff should be handled.
For web applications, the OWASP Web Security Testing Guide says penetration testing “certainly has its place in a testing program”, but OWASP does not believe it should be “the primary or only testing technique”.
What kinds of penetration test are there?
NIST describes two choices. External testing works from outside the security perimeter, usually as seen from the internet; internal testing works from the internal network, as a trusted insider or an attacker past the perimeter. Overt testing has the knowledge and consent of IT staff; covert testing has upper management’s full permission but not IT staff’s knowledge, and tests how staff respond.
What should be agreed before either test begins?
Before a vulnerability assessment or penetration test starts, agree the scope, the authorisation and the rules in writing. In the planning phase NIST describes for a penetration test, “rules are identified, management approval is finalized and documented, and testing goals are set”, and no testing takes place. NIST notes scanning may also disrupt network operations.
The NIST glossary defines rules of engagement as “Detailed guidelines and constraints regarding the execution of information security testing.” NIST’s general guidance is that an assessment plan should answer five questions:
- What is the scope of the assessment?
- Who is authorized to conduct the assessment?
- What are the assessment’s logistics?
- How should sensitive data be handled?
- What should occur in the event of an incident?
NIST also says the owner of any third-party network housing your systems usually must consent in writing, and the plan should name the testers’ IP addresses, so administrators can tell a test from a real attack.
Does a penetration testing provider in Malaysia need a licence?
Penetration testing providers in Malaysia need a licence, with some exceptions. NACSA’s licensing FAQ names penetration testing and managed SOC monitoring as the services that must be licensed under the Cyber Security Act 2024 (Act 854), which came into operation on 26 August 2024 and, in NACSA’s words, “includes provisions to regulate cyber security service providers through licencing.”
NetAssist holds NACSA licences for penetration testing and managed SOC monitoring.
Question 7 of the NACSA licensing FAQ gives the definition under the Regulations [P.U. (A) 221/2024]: a penetration testing service is “a service for assessing, testing or evaluating the level of cyber security of a computer or computer system, by searching for vulnerabilities on, and compromising, the cyber security defences of the computer or computer system”, and it “includes any of the following activities”, among them (a) “determining the cyber security vulnerabilities of a computer or computer system, and demonstrating how such vulnerabilities may be exploited and taken advantage of” and (c) “identifying and measuring the cyber security vulnerabilities of a computer or computer system, indicating vulnerabilities and preparing appropriate mitigation procedures required to eliminate vulnerabilities or to reduce vulnerabilities to an acceptable level of risk”. Whether a particular vulnerability assessment falls within that definition is a question for your own advisers.
The exceptions include services provided by a Government Entity and services for computers located outside Malaysia. The FAQ also says applications “will commence on 1st October 2024” (question 4), a subcontractor or third party that provides the cyber security service on behalf of the main contractor “is required to be licenced” (question 11), and “A licence is valid for a period of one (1) Year.” (question 12)
Sector regulators add their own rules: Bank Negara Malaysia’s RMiT policy document (issued 25 September 2026, Appendix 5, Part D) requires the financial institutions it covers to establish “standard operating procedures (SOP) for VAPT activities”. On costs, see how to budget for Act 854 compliance and our Cyber Intelligence articles.
What do NetAssist’s penetration tests and vulnerability assessments cover?
At NetAssist, our penetration testing assesses networks, servers, cloud environments, critical IT infrastructure and applications to discover security weaknesses before attackers exploit them. We evaluate web, mobile, API, desktop and emerging technology applications, and simulate real-world cyberattacks to test the effectiveness of security controls and threat detection capabilities. Our vulnerability assessments cover networks, databases and Active Directory, and include secure code review.
We also review security configurations, architectures and processes to identify risks and compliance gaps. Our penetration tests are performed by experienced, industry-certified professionals, with the scope and methodology customised to your business environment and post-assessment support with expert guidance and remediation solutions. What you receive at the end depends on what we agree to test. See our penetration testing and vulnerability assessment services.
FAQ
Is VAPT one service or two?
Two different activities, often named together. The vulnerability assessment finds and ranks possible weaknesses; the penetration test tries to exploit selected ones to confirm they are real. NIST SP 800-115 treats them as different techniques, so check what each part of a VAPT proposal covers.
How often should each be done?
No single schedule fits all. NIST’s 2008 testing guide (section 6.2) says “Assessment frequency is often driven by an organization’s requirements to demonstrate compliance with specific regulations or policies.” It adds: “Since an assessment provides a snapshot of security at a given point in time, organizations may choose to require more frequent assessments.”
Does a penetration test prove that a system is secure?
No. NIST’s testing guide notes that an assessment provides “a snapshot of security at a given point in time”, so a penetration test covers what was tested, within its scope, at that time. NIST adds that assessments “are not meant to take the place of implementing security controls and maintaining system security.”
Sources
- NIST SP 800-115, Technical Guide to Information Security Testing and Assessment (PDF, 2008), NIST (opened 20 Oct 2026)
- Glossary: Rules of Engagement, NIST CSRC (opened 20 Oct 2026)
- Penetration testing (reviewed 10 January 2022), UK NCSC (opened 20 Oct 2026)
- Web Security Testing Guide v4.2: Introduction, OWASP (opened 20 Oct 2026)
- Cyber Security Act 2024 (Act 854), NACSA (opened 27 Oct 2026)
- Licensing of Cyber Security Service Provider FAQ (PDF), NACSA (opened 27 Oct 2026)
- Risk Management in Technology policy document (PDF, 2026), Bank Negara Malaysia (opened 27 Oct 2026)
Plan your next assessment
Tell us which systems, applications and environments you want assessed, and we will shape the scope and methodology around your business environment.

