A vulnerability assessment quote can look expensive until you compare it with what the cheap quote actually covers. In Bangladesh, many buyers receive one proposal priced per IP address and another priced per application, then assume the difference is vendor margin. Most of the time, the difference is scope: authenticated checks, manual validation, API testing, cloud configuration review, retesting and the quality of the report.
This guide explains vulnerability assessment scope and cost in Bangladesh, and how to compare proposals on the same scope.
Scan, assessment or penetration test?
The three terms are not the same purchase.
- Vulnerability scan: automated tooling checks known weaknesses, missing patches and common misconfigurations. It is broad, fast and noisy.
- Vulnerability assessment: a scan plus human validation, prioritisation and business context. The output is a decision-ready list, not a raw export.
- Penetration test: a goal-based attempt to exploit weaknesses, usually against a narrower scope. It answers whether an attacker can reach a specific asset or data set.
If you need a baseline before an audit, an assessment is usually right. If you need evidence that a critical system cannot be broken into, you need a penetration test. A scan without validation produces a long list and no plan.
What the scope should define
A scope document is not a list of IP addresses. It should state the assets, the environment, the depth of testing, the constraints and the deliverables.
- Assets: public IP ranges, internal subnets, web applications, APIs, mobile apps, cloud accounts, network devices and wireless networks.
- Environment: production, staging, disaster recovery or a copy. Testing production requires a change window and a rollback plan.
- Authentication: unauthenticated testing only, or authenticated testing with user roles. Authenticated testing finds more, but requires test accounts and careful handling of personal data.
- Depth: automated scanning, manual validation, configuration review, source code review or exploitation.
- Constraints: rate limits, fragile legacy systems, peak business hours, third-party hosting and notification requirements.
- Deliverables: technical report, executive summary, remediation guidance, raw tool output and a retest letter.
Every item changes effort. A scope that omits them returns later as a change request.
The scope drivers that move the price
Asset count and grouping. Ten public IP addresses with similar services take less time than ten addresses running different applications. Vendors price blocks of work, not just counts.
Exposure and criticality. An internet-facing payment portal needs more care than an internal print server. Critical systems justify manual validation, out-of-hours testing and a second reviewer.
Authentication and roles. Each role can expose a different permission boundary. Testing a customer, an agent and an administrator account is more work than testing one anonymous session.
Application depth. A brochure site is not the same as a portal with file uploads, payments, refunds, reporting and multi-step approvals. Login flows, session handling and business logic take time to test properly.
APIs and mobile apps. APIs need endpoint discovery, authentication testing and authorisation checks. Mobile apps add build review, transport security and backend API testing. Both are commonly under-scoped.
Cloud configuration. A review of identity, storage, network rules and logging in AWS, Azure or a local cloud account is a separate workstream from host scanning.
Network devices and segmentation. Routers, switches, firewalls and virtual infrastructure need specialist checks. So does the question of whether a compromised laptop can reach the finance server.
Timing and disruption. Night or weekend work, travel and coordination with a hosting provider add cost.
Reporting and retesting. A raw scanner export is cheap to produce. A prioritised report with reproduction steps, business impact and a remediation plan is not. A retest is a second piece of work and should be priced explicitly.
A cost model you can price internally
Ask every vendor to build the fee from the same lines. Then compare the lines, not just the total.
Assessment fee = discovery + scanning + manual validation + application review + reporting + retest + project management
Each line should be effort days multiplied by a blended day rate, plus tool or licence pass-through. Discovery covers inventory and rules of engagement. Scanning covers tool configuration. Manual validation separates real findings from false positives. Application review covers authenticated business logic. Reporting covers technical writing and an executive briefing. Retest verifies fixes.
Day rates vary by seniority, location and specialist skills, which is why a credible vendor prices scope before quoting. A per-IP price is a starting point, not a proposal.
Build a rough estimate before you call vendors
You do not need a price list to prepare a useful brief. Count the work and ask vendors to price each unit.
- Count external IP addresses and group them by the services they expose.
- Count internal subnets and note whether authenticated scanning is possible.
- List web applications, APIs and mobile apps, with the user roles that matter.
- Mark which systems are internet-facing, payment-related or hold personal data.
- Decide whether you need a retest, a remediation workshop or an executive briefing.
- Ask each vendor to show effort days, day rate and assumptions for every line.
A vendor that cannot show the build-up is guessing. One that shows it gives you a scope you can defend.
What to ask a vendor
- Which methodology do you follow, and how does it map to NIST SP 800-115 or OWASP ASVS?
- Who performs the work, and how much of it is automated?
- How do you validate findings and handle false positives?
- How do you protect credentials, test accounts and any personal data you encounter?
- What happens if testing disrupts a production system?
- Can we see a redacted sample report before we sign?
- Is retesting included, and how long after remediation?
A 90-day plan
- Days 1-15: inventory assets, classify by criticality and confirm the compliance driver.
- Days 16-30: write the scope and rules of engagement; get three quotes on the same document.
- Days 31-50: run the assessment, with a named contact on both sides.
- Days 51-70: triage findings, fix the critical items and assign owners for the rest.
- Days 71-90: retest, brief management and add the remaining findings to the next budget cycle.
The output of the project is not the report. It is a shorter list of open risks with dates and owners.
How to measure whether it was worth it
- Coverage: the share of known internet-facing assets that were in scope.
- Remediation: critical findings closed within the agreed window.
- Repeat findings: issues that survived the previous cycle.
- Time to fix: median days from report to verified fix.
Where this fits in our work
If you need help defining the scope or running the assessment, start with Managed Technology & Cybersecurity. The pricing page explains how we scope engagements. For the wider risk picture, read the SME cybersecurity risk assessment cost guide.
Sources
- NIST SP 800-115, Technical Guide to Information Security Testing and Assessment, accessed 17 November 2026.
- OWASP Application Security Verification Standard, accessed 17 November 2026.
- IBM, Cost of a Data Breach Report 2026, accessed 17 November 2026.
- The Daily Star, "BB issues 17-point cybersecurity directive amid rising threats", accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.