A cybersecurity risk assessment is one of those services where the cheapest quote can be the most expensive decision. A one-day checklist may produce a PDF, but it does not tell you which systems matter, which threats are realistic and which remediation will actually reduce risk. A useful assessment is scoped around the business, not around a template.
This guide explains what a proper assessment includes, the four scope levels we see in the market, and a cost model you can use to compare quotes. It does not publish a fixed price, because a price without scope is a guess.
What the assessment should answer
A risk assessment should give the owner four things:
- An asset and dependency map: what systems, data, suppliers and people the business depends on.
- A threat and vulnerability view: which threats are realistic for this business, and where the current controls are weak.
- A risk ranking: likelihood, impact and the owner for each material risk.
- A remediation sequence: what to fix first, what it costs, and what can wait.
If the report does not name an owner and a next action, it is not an operating document. It is a souvenir.
Four scope levels
1. Self-assessment
The team completes a structured questionnaire, reviews it with a facilitator and produces an action list. This is useful for a small business with a simple stack and an internal owner. The cost is mostly internal time plus a short review. The limitation is that the business may not see its own blind spots.
2. Light-touch review
An external reviewer interviews two or three owners, reviews the key systems and samples evidence: MFA coverage, backup restore, patching, access reviews and incident contacts. The output is a short report and a 90-day plan. This is often the right first step for an SME.
3. Full assessment
The reviewer covers the business processes, applications, cloud accounts, suppliers, data flows and recovery capability. It includes technical sampling, evidence review and a workshop. The output is a risk register, a remediation roadmap and a board summary. This is appropriate when the business handles payments, personal data or a critical service.
4. Regulated or enterprise assessment
The work maps to a framework such as NIST CSF 2.0 or ISO/IEC 27001, includes control testing and may support an audit or customer due-diligence process. It needs more evidence, more interviews and a longer review cycle.
The cost model
Build the budget from five lines:
- Discovery and interviews: number of owners, processes and sites.
- Evidence review: policies, access lists, backup tests, patching, supplier contracts and incident records.
- Technical sampling: identity, endpoints, cloud configuration, network exposure and logging.
- Reporting and workshop: risk register, prioritisation and a session with the people who will act.
- Internal time: the hours your team spends gathering evidence and attending interviews.
Then add a contingency for follow-up questions. The provider's invoice is only one part of the cost. The internal time is often the larger hidden number.
Why quotes vary
- Number of systems: a single ecommerce stack is different from five branches, a warehouse and a legacy ERP.
- Data sensitivity: payment data, student data and health data raise the evidence and privacy requirements.
- Regulatory context: Bangladesh Bank guidance for financial institutions, the Personal Data Protection Act, 2026 and customer contracts can add scope.
- Technical depth: interviews and policy review are cheaper than configuration testing and log analysis.
- Reporting quality: a templated PDF is different from a risk register with owners and a board summary.
- Remediation: assessment and implementation are separate. A quote that bundles them without a scope is difficult to compare.
The Bangladesh context in 2026
Regulators are tightening expectations. Bangladesh Bank has issued cybersecurity directives for the financial sector, including mandatory MFA for critical systems and stronger encryption requirements. The Personal Data Protection Act, 2026 adds privacy obligations for personal data. Even if an SME is not directly regulated, customers and partners increasingly ask for evidence of basic controls.
The threat picture is also changing. The World Economic Forum's Global Cybersecurity Outlook 2026 reports that 87 percent of leaders see AI-related vulnerabilities as the fastest-growing cyber risk. IBM's 2026 breach report puts the global average breach cost at $4.99 million and the average time to identify and contain at 247 days. An SME will not face that exact number, but the direction is clear: slow detection and unclear ownership are expensive.
Questions to ask a provider
- Which framework or method will you use, and why?
- Who will be interviewed, and how many hours are included?
- What evidence will you review? Will you test configuration or only ask questions?
- What does the report contain: a risk register, owners, remediation steps and a board summary?
- What is excluded, and what triggers a change order?
- Who owns the findings and can we reuse them with another provider?
- What happens after the report: a workshop, a remediation quote or nothing?
What not to buy
- A one-day "hacking test" that is not a risk assessment.
- A generic checklist with no interviews or evidence review.
- A report with no asset map, no owners and no priorities.
- A quote that bundles remediation without defining the scope.
- A promise of "100 percent security" or a guarantee that no incident will occur.
A 90-day plan
- Week 1: list the systems, data, suppliers and people that matter.
- Week 2-3: gather evidence: access lists, MFA coverage, backup test, patching and incident contacts.
- Week 4-5: interviews and technical sampling.
- Week 6: risk ranking and remediation workshop.
- Week 7-8: fix the top two or three risks and assign owners.
- Day 90: review the plan and set the next assessment date.
Where this fits in our work
If you need an assessment scoped to your business, start with Managed Technology & Cybersecurity. The pricing page explains how we scope work. For the implementation side, read what malware actually costs a small business and the SME incident response plan.
Sources
- NIST Cybersecurity Framework 2.0, accessed 17 November 2026.
- NIST SP 800-30 Rev. 1, Guide for Conducting Risk Assessments, accessed 17 November 2026.
- The Daily Star, "BB issues 17-point cybersecurity directive", accessed 17 November 2026.
- World Economic Forum, "Global Cybersecurity Outlook 2026", January 2026.
- IBM, "Cost of a Data Breach Report 2026", July 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 *.