Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Cybersecurity & Risk 6 min read

Database access security cost in Bangladesh: a scope-based budget

What database access security actually includes, the seven cost drivers, a scoping calculator and the questions to ask a vendor.

E
EncryptTechBD · 0 comments
Laptop on a desk
Photo: Startup Stock Photos / StockSnap

Database access security is usually quoted as a day rate against an unclear scope. One vendor proposes a one-week review, another proposes a three-month programme, and both describe the same outcome: "secure database access". The difference is which parts of the problem they include.

This guide explains what the work actually covers, the drivers that change the price, a scoping calculator you can run before you request quotes, and the questions that make vendor proposals comparable.

What the work covers

A complete programme has nine parts. Most quotes include three or four.

  1. Inventory and classification. Every database, engine, version, environment, owner and data class.
  2. Identity. Named accounts for people, separate service identities for applications, and integration with your identity provider where the engine supports it.
  3. Role and privilege design. Roles built around job function, not around the person who needed something in 2019. Least privilege for read, write, schema change and administration.
  4. Secrets management. Credentials removed from source code and configuration files, stored in a secret manager, rotated on a schedule.
  5. Access path. A controlled route to production databases: bastion host, session manager or privileged access platform, with session recording where required.
  6. Audit logging. Query and login logs, shipped to a central store the database administrator cannot edit, with a retention period that matches your obligation.
  7. Data protection. Encryption in transit and at rest, plus masking or tokenisation for sensitive columns used in non-production and analytics.
  8. Break-glass and recovery. A documented emergency path, tested, with the credentials sealed and access reviewed afterwards.
  9. Operating routine. Quarterly access reviews, joiners and leavers, failed-login monitoring and an annual restore test that includes access recovery.

The seven cost drivers

  • Number of database engines. MySQL, PostgreSQL, SQL Server and Oracle have different identity and auditing capabilities. Each engine adds design and testing work.
  • Environment count. Production, staging, development and reporting copies multiply the access paths and the masking work.
  • Users and applications. Twenty named analysts is a different problem from two hundred, and shared application credentials are harder to remove than they look.
  • Privilege complexity. A handful of roles is straightforward. Hundreds of ad-hoc grants require archaeology before design.
  • Hosting model. Managed cloud databases have native IAM and audit services. On-premises or colocated databases need agents, network changes and more testing.
  • Legacy constraints. An application that cannot use short-lived credentials will need a compensating control, which costs engineering time.
  • Evidence requirements. A regulator or enterprise customer asking for quarterly evidence changes the logging, retention and reporting scope.

The cost model, line by line

Ask for a proposal with these lines separated, so you can compare and phase the work.

  • Discovery: inventory, data flow, privilege export and interviews.
  • Identity integration: SSO or IAM, service accounts, credential rotation.
  • Role redesign: role matrix, migration plan and application changes.
  • Access path: bastion or session manager setup, network rules, session recording.
  • Audit pipeline: log shipping, parsing, retention, alert rules.
  • Masking: sensitive column discovery and masking for non-production.
  • Migration windows: after-hours cutovers and rollback plans.
  • Run cost: secret manager, log storage, bastion or PAM licence, monitoring.
  • Internal time: application-team hours to change connection strings and test.

The last line is consistently underestimated. A role redesign that breaks a reporting job at month end costs more in business disruption than the consulting invoice.

A scoping calculator

Score the environment before you talk to vendors. The points are for effort estimation, not pricing.

  • Production database engines × 2 points each.
  • Non-production environments × 1 point each.
  • Applications using a shared or embedded credential × 3 points each.
  • Privileged roles that need redesign × 1 point each.
  • On-premises or colocated databases × 4 points each.
  • Audit sources to onboard × 2 points each.
  • Report or BI queries needing masked data × 2 points each.

Then read the total as a band rather than a price: under 20 points is a focused review and remediation, 20 to 40 is a project with application changes, 40 to 70 is a multi-team programme, and above 70 needs a phased roadmap with a platform owner. Bands help you sanity-check a quote; they do not replace a scoped assessment.

What to ask a vendor

  • Will you show us the privilege export and the role matrix before we approve the design?
  • How do you handle applications that cannot use short-lived credentials?
  • Which audit logs are captured, where are they stored, and who can delete them?
  • What happens to open sessions when an employee leaves?
  • How is the break-glass account stored, and when was it last tested?
  • What is the rollback plan if a role change breaks a month-end report?
  • Which parts are fixed fee, and which are time and materials?

Be cautious with any proposal that promises least privilege without listing the application changes it requires. The database side is often the easy half.

A 90-day plan

  1. Week 1-2: inventory databases and export every grant. Identify shared credentials and dormant accounts.
  2. Week 3-5: remove unused accounts, enforce named logins, enable audit logging.
  3. Week 6-8: move credentials into a secret manager and rotate them. Pilot the new access path with one team.
  4. Week 9-11: redesign the highest-risk roles and migrate one application per week with a rollback plan.
  5. Week 12: review evidence, test break-glass access, and schedule the quarterly access review.

Metrics

  • Number of shared or embedded credentials remaining.
  • Percentage of human access through a named identity with MFA.
  • Privileged accounts reviewed in the last quarter.
  • Time from leaver notification to access removal.
  • Percentage of production databases with query audit logging.
  • Number of break-glass uses per quarter, with reasons.

The Bangladesh context

Bangladesh Bank has issued cybersecurity directives for banks and financial institutions, and the Personal Data Protection Act, 2026 adds obligations around personal data handling. Even where a directive does not apply to your company directly, enterprise customers increasingly ask for evidence of named access, audit logging and periodic review. Treat those requests as a scoping input, because they change the evidence line in the budget more than the technical work.

Where this fits in our work

If you need the inventory, role design and audit pipeline delivered together, start with Managed Technology & Cybersecurity; the pricing page explains how assessment and remediation are scoped separately. For the application layer, read what API authentication and authorisation costs.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes