Vulnerability assessment
Scan agreed systems for known weaknesses and remove false positives.
A prioritised findings list with fixes.
A vulnerability assessment finds known weaknesses across your systems. A penetration test then tries to exploit selected weaknesses, with your permission, to show what an attacker could actually reach. BPro scopes both against your systems and the reason you need the test, then reports each finding with evidence and a fix.

/ Fit check
Best for
Businesses answering client, insurer or regulator questions about testing, and teams that want proof their fixes worked
Not for
Organisations that must use a CERT-In empanelled auditor or another accredited tester for a specific contract or regulation; confirm that requirement first
Deliverables
Written scope and rules of engagement, a report with severity-rated findings and evidence, and a retest of fixed issues where agreed
/ Direct answer
VAPT combines automated vulnerability scanning with manual testing. The scope sets which networks, applications, APIs or cloud services are tested, from where, and during which hours. Findings are rated by severity, shown with evidence and paired with remediation steps. A retest confirms that the fixes worked.
/ Scope your engagement
A useful test starts with clear targets, test windows and the reason for testing: a client questionnaire, an insurer, a regulator or a recent change.
Scan agreed systems for known weaknesses and remove false positives.
A prioritised findings list with fixes.
Manually test selected systems and attack paths within written rules.
Evidence-based findings, impact and a management summary.
Fix findings with your team or ours, then retest them.
An updated report showing what was fixed.
This example illustrates the record format. It is not a client result or a service-level commitment. Your proposal lists the deliverables and responsible people.
| Item | What is agreed | Who approves |
|---|---|---|
| Targets | IP ranges, URLs, applications and cloud tenants in scope, plus exclusions | System owner |
| Timing | Test windows, blackout periods and the report date | Business owner and IT lead |
| Safety | Emergency stop contact and techniques that need prior approval | Named technical contact |
Systems to test, why you need the test, any required standard or tester credential, test windows and who can authorise it.
/ 01
A vulnerability assessment is broad: it scans for known weaknesses and lists them. A penetration test is deep: a tester tries to exploit chosen weaknesses to prove impact. Most businesses need both, which is why they are often sold together as VAPT.
| Vulnerability assessment | Penetration test | |
|---|---|---|
| Goal | Find and list known weaknesses | Show what an attacker could do with them |
| Method | Mostly automated scanning, then review to remove false positives | Manual testing that attempts exploitation within the agreed rules |
| Coverage | Wide: many systems in one pass | Focused: the systems and paths in scope |
| Output | List of vulnerabilities with severity | Proven attack paths, business impact and evidence |
/ 02
The scope is agreed per engagement. Common targets are internet-facing systems, the internal network, web applications and their APIs, and cloud configuration such as Microsoft 365 and Azure.
/ 03
Each engagement moves from scope and authorisation to discovery, testing, reporting and retest. Nothing is tested until the scope, timing and contacts are approved in writing.
Agree targets, exclusions, test windows, emergency contacts and written permission from the system owner.
Map hosts, services and application functions in scope, then run vulnerability scans.
Manually confirm findings and attempt exploitation within the agreed rules, stopping where testing could harm a live service.
Rate each finding by severity, show the evidence and give a specific fix, with a summary for management.
Check fixed findings and update the report so you can show the result to clients, insurers or auditors.
Testing follows recognised methods such as NIST SP 800-115 for technical security testing and the OWASP Web Security Testing Guide for web applications.
/ 04
A management summary, the scope and method, each finding with its severity, evidence, affected systems and remediation steps, and the retest status. Findings are written so your IT team or supplier can act on them without guessing.
/ 05
At least once a year and after significant changes, such as a new application, a network redesign or a cloud migration. Some standards set this out directly: PCI DSS, for example, expects regular vulnerability scans and annual penetration tests for card payment environments. Check what your contracts, insurer or regulator require.
VAPT stands for Vulnerability Assessment and Penetration Testing. It combines scanning for known weaknesses with manual testing that proves which ones can be exploited.
Tests are planned to avoid disruption. The scope sets test windows, excludes fragile systems where needed, and names contacts who can stop testing at any time. Higher-risk techniques are agreed before they are used.
Some government bodies, regulators and contracts require a tester with a specific empanelment or accreditation, such as CERT-In empanelment in India. Check that requirement before you engage any provider, and ask to see the credential.
It depends on scope. A small external network test may take a few days of testing; a larger internal network or complex application takes longer. The proposal states the testing days and the report date.
Yes. BPro can remediate findings through its managed IT, Microsoft 365 and cybersecurity services, or work alongside your own IT team or supplier, then retest the fixes.
/ Next step
Systems to test, why you need the test, any required standard or tester credential, test windows and who can authorise it.