Black Friday Our software, PenTest Project: Slate Enterprise at €53 instead of €173 per user a month, and Flint free for 12 months. Until 30 November. See the offer →
PenTest Hub logo

Configuration · Privileges · Encryption

Database Security Testing

Your databases hold the data attackers want. We test their configuration, accounts, privileges, encryption and the paths that lead to them, so a single weakness does not expose everything.

  • Configuration and hardening
  • Accounts and privileges
  • Injection paths from applications
Sample findings · Database assessmentSample
CRITICALApplication account has full administrator rightsOne injection flaw would expose every database
HIGHDatabase reachable from the office networkNo segmentation from user workstations
HIGHBackups stored without encryptionOn a file share many staff can read
MEDIUMAuditing switched off for privileged actionsChanges by administrators leave no trace
Each finding with evidence, a risk rating and a fixSample findings

In one sentence

What is database security testing?

Database security testing assesses your databases and the systems around them for misconfigurations, excessive privileges, injection paths, encryption weaknesses and other routes to data compromise or unauthorised access.

Databases are rarely attacked directly from the internet. They are reached through applications, stolen credentials or flat networks, so we test the database and the paths that lead to it.

When it matters most

  • You hold personal, payment or health data
  • Many applications share one database server
  • You are preparing for an audit or a regulatory review
  • You have moved databases to the cloud

Scope

What we test

The database itself, who can reach it, and what they can do.

Configuration and hardening

Settings, enabled features and defaults compared with hardening guidance.

  • Hardening
  • Defaults
  • Features

Accounts and privileges

Application, administrator and service accounts: who has more access than they need.

  • Least privilege
  • Service accounts
  • Roles

Authentication

Password policies, default or shared credentials, and how applications authenticate.

  • Credentials
  • Defaults
  • Policies

Encryption

Encryption of data at rest, in transit and in backups, and how keys are managed.

  • At rest
  • In transit
  • Backups

Injection paths

How application flaws such as SQL injection could be used to reach and abuse the database.

  • SQL injection
  • Stored procedures
  • Applications

Network exposure and auditing

Which networks can reach the database, and whether privileged actions are logged.

  • Segmentation
  • Logging
  • Monitoring

Approach

Testing approaches based on access

Choose how much you share with us. More context means deeper coverage in the same time.

No prior knowledge

Black box

We test what an attacker on the network can reach and exploit without credentials.

Accounts and some context

Grey box

With a standard application or user account, we test privilege escalation and data access.

Full access

White box

With administrator read access, we review the full configuration against hardening guidance.

Engagement

How we work with you

  1. Scope online

    Describe what you need in Flint, our scoping platform. Answer only the questions that apply.

  2. Proposal, signed online

    Effort, price and the statement of work are built from your answers.

  3. Ready for day one

    Authorisation, test accounts and rules of engagement are agreed before testing starts.

  4. Senior-led testing

    Certified consultants lead the test. Our own AI framework, Striker AI, takes on the repetitive work.

  5. Report and retest

    Your report is ready in Slate, our client portal, within 48 hours of testing ending.

What you receive

Everything stays in one place, in your own client portal.

  • A report in Slate within 48 hours of testing ending
  • Every finding with evidence, a risk rating and a fix
  • An executive summary for leadership
  • Retests you can request finding by finding
  • Downloads as PDF or Excel
  • Evidence you can hand to your auditors

Standards

Standards we test against

Aligned with the benchmarks and requirements your auditors use.

  • CIS Benchmarks
  • OWASP Top 10
  • PCI DSS
  • ISO/IEC 27001
  • NIST SP 800-53

FAQ

Frequently asked questions

Can't find yours? Ask a senior tester and we'll reply directly.

Which databases do you test?
The relational and NoSQL databases your applications use, on premises or in the cloud. Tell us your platforms during scoping.
Will testing affect performance or data?
We agree testing windows and avoid techniques that change data or load the server heavily unless you ask for them.
Is a database test part of an application test?
An application test covers injection paths into the database. A database assessment goes further, reviewing configuration, accounts, encryption and network exposure.
Does it help with PCI DSS or ISO/IEC 27001?
Yes. It gives you independent evidence for the database controls those standards require.
When will we receive the report?
Within 48 hours of testing ending, in Slate, our client portal.

Contact

Tell us what you need to test

A senior tester reads every message and replies directly.