We’re at bspeka often get requests for a Penetration Testing, but it’s not always means Penetration Testing. Thats why we’ve decided to write this article.
Vulnerability Assessment and Penetration testing both are options of Security Testing. Let’s dive into this topic and try to cover main aspects of these processes from the Application Security point of view.
Vulnerability Assessment is the process of identifying threats and vulnerabilities on a target application. The goal of vulnerability assessment is to find as many vulnerabilities as possible in limited time-frame and within the testing scope.
Penetration Testing is a controlled attack simulation that helps to identify susceptibility to application breaches. The goal is to gain unauthorized access through exploitation which can be used to emulate the intent of a malicious hacker.
From time perspective Penetration Testing and Vulnerability Assessment both are usually limited by 2 weeks timeframe and really depends on application complexity and a number of features.
The Vulnerability Assessment report includes all security issues discovered in an examined application. While Penetration Testing report describes only the way (chain of features, security flaws, misconfigurations) of getting higher privileges in the tested application.
So Vulnerability Assessment report will be the list of issues:
The Penetration Testing report is written like a story:
I’ve opened the application and found the login form. I’ve tried to enter the credentials admin/admin and …
For example you’ve developed yet another CMS for news site. And its’ features look like:
Vulnerability Assessment Report will include issues discovered in these features:
While the Penetration Testing report most likely will include next issues:
Important note: Penetration Testing envisages exploiting discovered weaknesses to go deeper and deeper. And the report includes step-by-step exploiting description.
We’re at bspeka sure that the customer must get proofs of security test coverage during the Vulnerability Assessment. We use OWASP Testing Guides and Checklists based on these documents.
For example for Mobile Application Vulnerability Assessment (iOS and Android) we use checklist from this github repository or this for Web Application Vulnerability Assessment.
You’re free to choose any type of security testing for your application, but our recommendation is to start from Vulnerability Assessment to cover all Attack Surface and leave an attacker without low-hanging fruits.
Next table can be used as a small crib:
We’re open to answer any of your left questions in our contact form.