# What Is a Database? Why Is Database Security Critical for Organisations?

**URL:** https://securesys.com.tr/en/learning/database-security/what-is-a-database-and-why-security-matters

![What Is a Database? Why Is Database Security Critical for Organisations?](/images/bilgi-merkezi/covers/cover-veritabani-01.webp)

Almost all the digital operations of modern organizations run on databases.

Customer records,

financial transactions,

personnel information,

ERP systems,

CRM applications,

e-commerce platforms,

mobile applications,

web services,

production systems,

log records,

API services

and the greater part of corporate applications are directly related to databases.

While the front end of a web application forms the part visible to the user, the truly critical information is most often held in the database systems behind it.

For this reason databases are not merely a part of the technical infrastructure.

They are at the same time the organization's;

operational memory,

commercial data,

customer information,

financial records

and most often the centre holding its most valuable digital assets.

For this reason, in the modern cyber security approach, database security must be treated as a separate area of expertise.

The core question is this:

**“If an attacker reaches the database, which of the organization's data can they access and how much damage can they cause?”**

The answer to this question is quite critical for many organizations.

### What Is a Database?

A database is the system that enables data to be stored in an organized, accessible and manageable form.

A simple Excel table can hold data too.

However, at corporate scale;

millions of records,

thousands of concurrent users,

high transaction volume,

complex queries,

authorization,

backup,

replication,

audit

and transaction management

needs such as these arise.

At this point a Database Management System, that is a DBMS, is used.

### What Is a DBMS?

DBMS means:

#### Database Management System

that is:

#### the system that manages the database

in full.

A DBMS enables data to be;

created,

stored,

read,

updated,

deleted,

authorized

and managed.

Among the examples widely used in the corporate world;

PostgreSQL,

Microsoft SQL Server,

Oracle Database,

MySQL,

MariaDB

may be found.

### Are “Database” and “DBMS” the Same Thing?

In daily use they are most often used with the same meaning.

Technically, the database expresses the structure in which the data resides, while the DBMS is the software managing that structure.

However, in corporate conversation;

“database server”,

“database system”,

“database infrastructure”

these expressions are most often used in a broader sense.

### Why Are Databases Critical for Organizations?

Many of an organization's critical business processes cannot run without a database.

For example, let us consider an e-commerce system.

In the database;

product information,

stock status,

customer accounts,

orders,

payment information,

addresses

may be found.

If the database becomes unreachable, the user may be unable to place an order even though the website appears to be up.

For this reason the database is:

**one of the fundamental parts of business continuity.**

### What Is Database Security?

Database security is the protection of database systems and the data inside them against;

unauthorized access,

data leakage,

data modification,

deletion,

ransomware,

insider threat,

misconfiguration

risks such as these.

This does not mean merely setting a database password.

Real database security;

authentication,

authorization,

network security,

encryption,

audit,

patch management,

backup,

monitoring

and hardening

consists of many layers such as these.

### Why Is Database Security a Separate Security Area?

Using a firewall does not automatically make the database secure.

Using EDR does not fully control database access either.

Database systems have their own;

user,

role,

permission,

schema,

stored procedure,

trigger,

audit

mechanisms.

For this reason database security requires separate expertise.

### The CIA Triad in Database Security

Database security can be explained with the classic information security principles.

#### Confidentiality

Only authorized people must reach the data.

For example, not everyone must be able to see the salary information in the human resources database.

#### Integrity

Data must not be modifiable without authorization.

For example, the balance in a bank account must not be changeable without permission.

#### Availability

Data must be usable when needed.

If the database goes down, critical applications may not run.

### What Kinds of Data Can Be in a Database?

Depending on the organization, inside a database;

personal data,

financial information,

customer records,

identity information,

addresses,

telephone numbers,

e-mail addresses,

payment records,

trade secrets,

production data,

logs,

password hashes

may be found.

For this reason a database compromise can turn into a serious data breach.

### What Is a Database Breach?

A Database Breach is an unauthorized person reaching the data inside a database or taking it out.

This event;

a weak password,

SQL Injection,

wrong authorization,

a stolen administrator account,

an open database port,

an application vulnerability

can occur because of these.

### What Is the Database Attack Surface?

The Attack Surface expresses all the points an attacker can reach or abuse.

For a database the attack surface can include these components:

- Database ports
- The administrator console
- Web applications
- APIs
- Service accounts
- Backup files
- Replication connections
- Database management tools
- Cloud management accounts
- The operating system

For this reason a database is not protected through its own software alone.

### Should Database Ports Be Exposed to the Internet?

In general, critical corporate database systems must not be directly exposed to the internet.

For example;

PostgreSQL,

MSSQL,

MySQL

having their ports open to everyone over the internet enlarges the attack surface.

Access to the database must be provided only from the necessary application server or management networks.

### Why Is Database Network Segmentation Important?

The database server must not sit on the same flat network as user computers.

A sample architecture:

User VLAN

↓

Application VLAN

↓

Database VLAN

can be separated along these lines.

The firewall permits only the necessary traffic flows.

### Should Users Connect Directly to the Database?

In most applications, no.

The user;

a web application

or

a business application

must obtain data access through one of these.

Direct user connections to the database must be kept to a minimum.

### Who Is the Database Administrator – DBA?

The DBA is the:

#### Database Administrator

the specialist role responsible for database systems';

installation,

configuration,

performance,

backup,

restore,

authorization

and operation.

The DBA can hold high privileges.

For this reason DBA accounts must be treated as privileged accounts.

### Why Is the DBA Account Critical?

The DBA can most often reach all the data inside the database.

For example, the DBA;

can read tables,

can change data,

can create users,

can drop the database.

For this reason a DBA account compromise is a critical security event.

### Should the Database Administrator Account Be Used for Daily Work?

No.

The administrator account must be used only for management operations.

For daily;

mail,

internet,

document

work it must not be used.

### What Is Least Privilege in Database Security?

Least Privilege:

#### the minimum privilege principle

expresses granting the user only the permissions they need.

For example, a reporting user may need only:

SELECT

as their privilege.

To this user;

UPDATE,

DELETE,

DROP

privileges must not be granted.

### Database Role-Based Access Control – RBAC

RBAC enables user privileges to be managed through roles.

For example;

DB_ReadOnly

DB_Developer

DB_Operator

DB_Admin

roles can be created.

This approach makes access management easier.

### Should Each Application Use a Separate Database User?

As far as possible, yes.

More than one application using the same database account;

audit,

privilege management,

incident investigation

can create a problem in these areas.

It is healthier for each application to use a separate service account.

### Why Is a Shared Database Account Risky?

For example, if 20 people use the:

dbadmin

account, who performed which operation cannot be known.

This situation leads to an accountability problem.

### What Should a Database Password Be Like?

On database accounts;

strong,

unique,

long

passwords must be used.

Default passwords absolutely must be changed.

### Should Default Database Accounts Be Checked?

Yes.

The;

default users,

sample users,

test databases

that arrive during installation must be removed or made secure.

### What Is Database Hardening?

Database Hardening is the process of reducing the attack surface by turning off unnecessary features and strengthening security settings.

For example;

turning off unnecessary services,

removing default accounts,

providing minimum network access,

using secure authentication

fall within the scope of database hardening.

### Why Is Database Hardening Important?

Database software can contain a great many features.

However, unused features can enlarge the attack surface.

The core principle:

**An unused feature must be turned off.**

### What Is Database Patch Management?

Database software, like other software, can have security vulnerabilities.

Security patches published by the vendor need to be applied in a controlled way.

### Why Are Database Patches Delayed?

Organizations can be wary of database patching.

Because critical applications can be affected.

However, a database left unpatched for years can create serious attack risk.

For this reason;

testing,

staging,

change management,

a rollback plan

must be used.

### Should Vulnerability Management Cover Database Systems?

Yes.

The database server;

the operating system,

the DBMS version,

network services,

configuration

must be assessed in these respects.

### What Is a Database Security Assessment?

A Database Security Assessment is the systematic examination of the database's security configuration.

For example;

weak accounts,

unnecessary privileges,

open ports,

missing patches,

audit settings

can be checked.

### Can a Database Hardening Benchmark Be Used?

Yes.

Secure configuration guides such as the CIS Benchmark can be used.

The vendor's security hardening documents can also be followed.

### What Is SQL Injection?

SQL Injection is the situation where, because the application cannot process user input safely, the attacker can manipulate the database query.

This vulnerability generally arises at the application layer.

However, the result appears on the database.

### Why Is SQL Injection Dangerous?

As a result of a successful SQL Injection attack the attacker;

can read data,

can change data,

can bypass authentication

and can create a serious impact in proportion to the database privileges the application holds.

### Is SQL Injection a Database Problem?

It relates to both application and database security.

The real fault is most often that the application does not build safe queries.

However, if the database account has been given excessive privileges, the impact of the attack grows.

### What Is a Parameterized Query?

A Parameterized Query is the safe query method that separates user input from the SQL command.

It is one of the fundamental methods for reducing SQL Injection risk.

### Does a Stored Procedure Fully Prevent SQL Injection?

No.

A stored procedure is useful if it is designed safely.

However, if dynamic and unsafe SQL is being built inside it, SQL Injection can still occur.

### What Is a Database Firewall?

A Database Firewall can help block abnormal or unauthorized behaviour by analysing database queries and connections.

This differs from a traditional network firewall.

### Does a Web Application Firewall Protect the Database?

A WAF can help detect or block web-based SQL Injection attacks in particular.

However, it does not take the place of database security.

Defense in Depth must be applied.

### What Is Defense in Depth?

Defense in Depth expresses the use of more than one security layer together.

An example for a database:

WAF

↓

Secure Application

↓

Firewall

↓

Database Authentication

↓

RBAC

↓

Audit

↓

DAM

Even if one of these layers fails, the others can limit the attack.

### What Is Database Encryption?

Database Encryption is the protection of data by encrypting it.

There are two fundamental areas:

#### Encryption at Rest

and

#### Encryption in Transit

### What Is Encryption at Rest?

It is the encryption of the database files residing on disk.

It makes reading the data harder even if the storage is stolen or the disk files are seized.

### What Is TDE?

TDE is expressed as:

#### Transparent Data Encryption

that is:

#### encryption that is transparent to the application

in plain terms.

It enables the encryption of database files and, in some cases, transaction logs.

The application can generally run without being affected by this process.

### Does TDE Hide the Data from the Database User?

No.

This is a very important distinction.

An authorized database user can read the data with a normal query.

TDE provides protection more against data theft at the disk or database file level.

### What Is Column-Level Encryption?

It is the additional encryption of specific sensitive columns.

For example;

a national ID number,

credit card information,

health data

fields such as these can be encrypted separately.

### What Is Database Encryption in Transit?

It is the encryption of the traffic between the client and the database with secure protocols such as TLS.

This way database queries and responses are not carried over the network in the clear.

### Why Is Database TLS Important?

In database network traffic;

usernames,

queries,

responses,

sensitive data

may be present.

If TLS is not used, a network sniffing risk can arise.

### Where Should the Database Encryption Key Be Kept?

The encryption key;

must not be protected inside the same open file system as the database.

A KMS,

an HSM,

a secure vault

can be used.

### Should Database Backups Be Encrypted?

Yes.

The production database being encrypted while the backup file is kept unencrypted is an important security gap.

All of the production data may be inside the backup.

### Why Is Database Backup Critical?

Database corruption,

a wrong SQL operation,

ransomware,

hardware failure,

an administrator error

a backup can be used in these situations.

### Are Database Backup and File Backup the Same?

No.

A database is a transaction-based system.

Taking a simple copy of the file may not be sufficient for database consistency.

### What Is a Consistent Database Backup?

It ensures the database is backed up in a transactionally consistent state.

When restored, the database must open properly.

### What Is a Full Database Backup?

It is a backup of the entire database.

It can form the foundation of the recovery chain.

### What Is a Differential Database Backup?

It is a backup of the data changed since the last full backup.

It is supported on some database platforms.

### What Is a Transaction Log Backup?

It is a backup of the database transaction records.

This structure can provide a lower RPO.

### What Is Point-in-Time Recovery?

PITR is:

#### Point-in-Time Recovery

the ability to bring the database back to a specific moment in time.

For example, if a faulty DELETE was carried out at 14:37:

14:36:59

a return to this point can be targeted.

### Why Is the Database RPO Critical?

On a database with heavy transaction traffic, a 24-hour backup may not be sufficient.

For example, in a banking or e-commerce database even minutes can matter.

For this reason the RPO must be determined according to business need.

### Why Is the Database RTO Critical?

The database is a dependency of many applications.

If the database takes 8 hours to restore, all the applications may be unable to run for 8 hours.

For this reason restore performance must be tested.

### Should a Database Restore Test Be Performed?

Absolutely.

Seeing that a backup was taken is not enough.

It must be verified that the backup can genuinely be restored.

### What Is a Database Integrity Check?

They are the checks aiming to detect corruption in pages, indexes or data structures inside the database.

Different integrity check mechanisms may exist depending on the platform.

### What Is Database Corruption?

It is the corruption of the database files or of the data structure.

Its causes;

a storage problem,

hardware failure,

a software bug,

an improper shutdown

can be any of these.

### Can Corruption Be Carried into the Backup?

Yes.

If a backup is taken of a corrupted database, the corruption can be inside the backup too.

For this reason integrity monitoring is important.

### What Is Database Maintenance?

Database Maintenance comprises the regular maintenance operations performed so that the database runs healthily, performantly and securely.

For example;

index maintenance,

statistics update,

integrity check,

backup,

patching,

log checks,

capacity management

can be performed.

### Is Database Maintenance Done Only for Performance?

No.

Database maintenance;

performance,

availability,

security,

data integrity

is important for these.

### What Is an Index?

An index is the data structure that enables database queries to run faster.

It can be thought of like the index at the back of a book.

### Can Too Many Indexes Be Harmful?

Yes.

An index can increase query performance.

However, it can slow down INSERT, UPDATE and DELETE operations.

For this reason index management must be done in a balanced way.

### What Is Fragmentation?

On some database systems, index structures becoming scattered over time can affect performance.

Depending on the platform, reorganize or rebuild operations can be evaluated.

### What Are Statistics?

They express the data distribution information the database optimizer uses when building a query plan.

If the statistics are stale, a poor execution plan can arise.

### Is Query Performance Related to Security?

Indirectly yes.

Bad queries can consume CPU and memory resources and create a denial-of-service-like effect.

For this reason performance monitoring also supports availability security.

### What Is a Database Connection Pool?

It is the mechanism that lets applications reuse existing database connections instead of opening a new connection for every query.

If configured wrongly, database connection exhaustion can occur.

### Why Is the Maximum Connection Setting Important?

Uncontrolled connections can consume database resources.

For this reason connection limit and pool settings are important.

### What Is Database Monitoring?

Database Monitoring is the continuous monitoring of the database's;

availability,

performance,

security,

capacity

state.

### Which Database Metrics Should Be Monitored?

For example;

CPU,

memory,

disk usage,

IO latency,

connection count,

slow queries,

deadlocks,

failed logins

can be monitored.

### Why Is a Failed Login a Security Event?

A large number of failed database logins;

brute force,

credential stuffing,

a wrongly configured application

can be an indicator of these.

### What Is a Database Audit?

A Database Audit is the recording of the operations performed on the database.

For example;

who connected,

which table they read,

which data they changed,

which user was created

can be tracked.

### Are a Database Log and an Audit the Same Thing?

Not always.

An operational log shows the technical operation of the system.

An audit log, meanwhile, can focus on recording user activity and operations that matter from a security perspective.

### Why Is the Audit Log Critical?

After a data breach this question has to be answered:

**“Which user reached which data?”**

Without an audit, answering this question can be very difficult.

### What Is Database Activity Monitoring – DAM?

DAM is:

#### Database Activity Monitoring

which enables database activity to be monitored centrally and with a security focus.

Database queries,

logins,

privileged activity,

sensitive data access

events such as these can be analysed.

### Why Is DAM Used?

It is useful particularly in organizations with;

high-volume databases,

critical data,

compliance requirements,

privileged user monitoring

as their profile.

### Should DBA Activity Be Monitored?

Yes.

The DBA holds high privileges.

However, the “the administrator is trustworthy anyway” approach is not sufficient.

Privileged account activity must be audited.

### Why Is Insider Threat Critical for Databases?

An employee with legitimate access to the database can behave maliciously.

For example, they can take the customer list outside.

For this reason the focus must not be on external attackers alone.

### What Is Data Exfiltration?

Data Exfiltration is data being taken outside the organization without authorization.

For a database it;

a bulk query,

an export,

a dump,

a backup copy

can occur through these.

### Should Large SELECT Queries Be Monitored?

On critical and sensitive databases, queries pulling far more data than normal behaviour can be examined from a security perspective.

For example, if a user who normally views 50 customer records suddenly pulls 5 million records, an alarm can be generated.

### What Is Database Anomaly Detection?

It is the detection of deviations from a user's normal database behaviour.

For example;

night-time access,

a different IP,

access to a large number of tables,

a high volume of data export

can be assessed as anomalies.

### Should Database Logs Be Sent to SIEM?

On critical database systems, yes.

Through SIEM;

failed logins,

privileged activity,

account creation,

permission changes,

audit events

can be monitored centrally.

### Database and SOC Integration

SOC teams can assess database security events together with network and endpoint events.

For example;

EDR → credential theft

Firewall → database connection

DAM → bulk customer query

SIEM → data exfiltration alarm

can be correlated within the same incident.

### The Relationship Between Database Security and DLP

DLP focuses on controlling sensitive data leaving the organization.

The database, meanwhile, is one of the main sources of that data.

When DAM and DLP are used together, the movement of data leaving the database can be tracked better.

### What Is Sensitive Data Discovery?

It is determining which tables inside the database contain sensitive data.

For example;

national ID numbers,

IBANs,

telephone numbers,

addresses,

e-mail addresses

the columns containing these can be discovered.

### Why Is Data Classification Important for Databases?

Not all database tables carry the same importance.

Data;

Public,

Internal,

Confidential,

Restricted

can be divided into classes such as these.

Stronger controls can be applied to more sensitive data.

### What Is Database Masking?

Data Masking is showing a different value in place of the real value of sensitive data.

For example:

12345678901

instead of this:

123******01

can be shown.

### Where Is Data Masking Used?

It is useful particularly in;

test,

development,

support

environments.

It reduces the presence of real customer data in the developer environment.

### Should the Production Database Be Copied to the Test Environment?

It must not be copied directly and without control.

If the production database contains personal and sensitive data, a serious risk can arise in the test environment.

### Are Data Masking and Anonymization the Same?

No.

Masking generally hides the data in terms of visibility.

Anonymization, meanwhile, aims at removing the link to the data in such a way that the person can no longer be identified.

### Where Should Database Secrets Be Stored?

Inside the application connection string;

a username,

a password,

an API secret

may be present.

This information must not be hard-coded inside the source code.

### What Is a Connection String?

It is the configuration determining how the application will connect to the database.

For example;

server,

port,

database name,

username

it can contain these.

### Why Is a Hard-Coded Password Risky?

If a database password is written into the source code repository;

a developer,

the CI/CD system,

a repository compromise

the credential can be obtained as a result of these.

### Should Secret Management Be Used?

Yes.

Credentials can be obtained dynamically from systems such as a vault or a cloud secret manager.

### Is Password Rotation Necessary for Databases?

Depending on risk and architecture, regular credential rotation can be applied.

It is important particularly for privileged and service accounts.

### Can Certificate-Based Authentication Be Used?

In some database environments, certificates or strong central identity mechanisms can be used.

This can reduce the use of static passwords.

### Can MFA Be Used for Database Login?

It depends on the direct support of the database platform or on the identity layer in use.

MFA must be strongly evaluated particularly for DBA management access.

### Should PAM Be Used for Database Administrators?

In critical environments it is useful.

PAM;

a password vault,

session recording,

approval,

JIT access

can provide these.

### What Is JIT Database Access?

It is database administrator privileges not being permanently open but granted temporarily at the moment of need.

For example, DBA production access can be active only for the duration of a change.

### How Should Production Database Access Be Managed?

For example:

request

↓

manager approval

↓

PAM

↓

temporary access

↓

session recording

↓

access revoke

a process along these lines can be established.

### Should Developers Reach the Production Database?

At the minimum level possible.

If developer access is required, it;

read-only,

temporary,

audited

can be provided in this form.

### What Is Separation of Duties for Databases?

For example, the DBA both managing the database and being able to delete the audit logs can create risk.

The separation of duties principle can be applied.

### Should the Database Audit Log Be Immutable?

In critical environments it matters that audit records cannot easily be deleted by the database administrator.

The logs can be sent to a central SIEM or to immutable log storage.

### What Is Database High Availability?

HA is:

#### High Availability

which aims for the database to keep serving during an interruption.

A cluster or replication can be used.

### Does HA Replace Backup?

No.

If the primary database is deleted by mistake, that change can be carried to the replica as well.

Replication is not a backup.

### What Is Database Replication?

It is the copying of data from one database system to another.

The purpose;

availability,

read scaling,

DR

can be any of these.

### What Is Synchronous Replication?

Before the transaction completes, the replica may be expected to have received the data too.

It provides a lower RPO but can affect latency.

### What Is Asynchronous Replication?

The primary completes the operation and the data is sent to the replica later.

There is a performance advantage but a certain amount of data loss can occur.

### Why Must Database DR Be Planned Separately?

The database is the central dependency of most applications.

During DR;

replica activation,

DNS,

the connection string,

data consistency

must be checked.

### What Is Database Failover?

It is the secondary database becoming active when the primary database goes out of service.

It can be automatic or manual.

### What Is Failback?

It is the service being moved back to the main system when the primary environment returns.

Data synchronization must be done correctly.

### What Is the Database Split-Brain Risk?

Two database nodes both believing they are primary can create data inconsistency.

In cluster architectures, quorum and fencing mechanisms are important.

### What Is Database Capacity Management?

It is planning storage, memory, CPU and connection capacity according to future need.

If the database disk fills up, the system can stop.

### Is a Full Database Disk a Security Event?

From an availability perspective, yes.

For example, if the transaction log disk fills completely, application operations can stop.

### Why Must the Transaction Log Be Monitored?

The transaction log can grow rapidly.

Because of a backup or maintenance error the disk can fill completely.

### What Should Database Alerting Cover?

For example;

high CPU,

disk full,

replication lag,

backup failed,

failed login,

deadlock,

slow query,

privilege change

must generate an alarm.

### What Is a Database Baseline?

The database's normal behaviour profile is established.

For example the normal;

CPU,

query rate,

login count,

data volume

is known.

Deviations are detected more easily.

### What Is a Database Security Baseline?

It is the secure configuration standard.

For example;

which ports are open,

which authentication will be used,

which accounts will exist,

which audit policy will be active

is defined.

### Should Dev, Test and Production Databases Be Separated?

Yes.

The production database and the test systems may not be at the same security level.

For this reason environment separation must be performed.

### Should the Test Database Use Production Credentials?

No.

Every environment must have its own credentials and secrets.

### What Is Database Change Management?

It is the controlled application of schema or configuration changes.

For example;

ALTER TABLE,

an index change,

a version upgrade

can be subject to the change process.

### Why Is a Database Schema Change Risky?

A wrong schema change;

an application outage,

data loss,

performance degradation

can create these.

### Should There Be a Database Rollback Plan?

Yes.

If the change fails, the method of return must be determined in advance.

### Should a Pre-Change Backup Be Taken?

Creating a backup or a restore point before critical database changes can be useful.

### What Should Be Done Before a Database Upgrade?

Generally;

a compatibility test,

a backup,

a rollback plan,

an application test

must be performed.

### What Is an End-of-Life Database?

It is a database version whose vendor support has ended.

Because it receives no security patches it can create high risk.

### Why Is a Legacy Database Dangerous?

Old applications can depend on an old database version.

However, security vulnerability and compatibility risks increase over time.

### What Is a Database Asset Inventory?

It is the inventory of all the database systems the organization owns.

For example;

server,

database name,

version,

owner,

criticality,

data classification

this information can be held.

### Is an Unknown Database a Security Risk?

Yes.

A database IT does not know about;

unpatched,

unbacked-up,

exposed to the internet

can be any of these.

For this reason asset discovery is important.

### What Is a Shadow Database?

It is a database or data store created by business units without IT's knowledge.

It is risky from a security and compliance perspective.

### Cloud Database Security

In cloud database services, certain parts of infrastructure management can be handled by the provider.

However, the customer is still responsible for areas such as;

IAM,

network,

data,

backup,

configuration

as their share.

### Is a Managed Database Secure?

Being managed does not automatically mean it is entirely secure.

Wrong IAM or public network exposure can create serious risk.

### Why Is a Public Cloud Database Risky?

If the database is reachable from the public internet, risks such as brute force and vulnerability scanning increase.

A private endpoint and network restriction can be evaluated.

### Cloud Database Shared Responsibility

The provider can manage certain infrastructure components of the database platform.

The customer, meanwhile, manages areas such as;

users,

roles,

data,

network access,

the backup policy

as their share.

### Database Security and KVKK

A significant part of personal data resides in database systems.

For this reason, from a KVKK perspective;

access control,

logging,

encryption,

data minimization,

retention

controls such as these are important.

### Why Is a Database Audit Important from a KVKK Perspective?

In a data breach, being able to determine which user reached which data can be important.

Audit records support the incident examination.

### What Is Database Retention?

It is the policy determining how long data will be kept.

Not every piece of data must be kept for an unlimited period.

### What Is Database Data Minimization?

It is not keeping data that is not necessary for the business purpose.

Unnecessary data enlarges both the impact of an attack and the compliance risk.

### Database Security and ISO/IEC 27001

From an ISO/IEC 27001 perspective, the information assets inside the database must have their;

confidentiality,

integrity,

availability

risks assessed.

Processes such as access control, backup, logging, vulnerability management and cryptography are directly related to database security.

### Database Security and PCI DSS

Database systems holding card data can fall within PCI DSS scope.

In that case;

access control,

logging,

encryption,

vulnerability management

additional requirements such as these can arise.

### Corporate Database Security Checklist

An organization must be able to answer these questions:

Do we have a database inventory?

Which database holds which data?

Is the database exposed to the internet?

Is there network segmentation?

Are default accounts disabled?

Are DBA accounts separate?

Is Least Privilege applied?

Is audit active?

Do database logs go to SIEM?

Is the data encrypted?

Is TLS in use?

Is the backup encrypted?

Is the restore tested?

Are the patches up to date?

Is a database vulnerability assessment performed?

These questions form a strong starting point for database security maturity.

### The Most Common Mistakes in Database Security

The mistakes frequently encountered in organizations are as follows:

- exposing database ports to the internet,
- leaving default users in place,
- using a shared DBA account,
- granting unnecessary privileges to application accounts,
- not using encryption,
- not monitoring database logs,
- not enabling audit,
- deferring patches for years,
- using production data in the test environment,
- storing the backup unencrypted,
- not performing restore tests,
- giving developers permanent production access,
- using hard-coded database passwords,
- not classifying sensitive data.

### The Defense in Depth Approach in Database Security

A secure database architecture does not rest on a single control.

Example:

#### WAF

↓

#### Secure Application

↓

#### Network Firewall

↓

#### Database Segmentation

↓

#### Strong Authentication

↓

#### RBAC / Least Privilege

↓

#### Encryption

↓

#### Audit & DAM

↓

#### SIEM Monitoring

↓

#### Encrypted & Immutable Backup

These layers complement each other.

### Questions Management Should Ask About Database Security

Senior management or IT leaders must be able to get answers to these questions:

In which databases is our critical data?

Who can reach that data?

Is DBA activity monitored?

Are the databases exposed to the internet?

When was the last security assessment performed?

When was the last patch applied?

Have the database backups been restored?

If an administrator exports the customer database, would we notice it?

These questions show the organization's real risk position far more than technical detail does.

### Conclusion: Database Security Is at the Centre of Corporate Cyber Security

In modern organizations the value of applications comes largely from the data they process.

A significant part of that data, meanwhile, resides in database systems.

For this reason assessing a database's security only through the question:

**“Is the password strong?”**

is not correct.

Real database security;

**network segmentation,**

**strong authentication,**

**least privilege,**

**RBAC,**

**encryption,**

**hardening,**

**patch management,**

**audit logging,**

**Database Activity Monitoring,**

**backup**

and **restore testing**

requires controls such as these to be applied together.

At the same time, database security is not done against external attackers alone.

Administrator errors,

insider threat,

wrong configuration,

application vulnerabilities,

data corruption

and hardware failure

risks such as these must be assessed as well.

Organizations' goal must not be merely to keep the database running.

The real goal is:

**that the data is accessible to the right people, with the right privileges, at the right time, and that its integrity is preserved.**

For this reason a strong database security approach must be able to answer three fundamental questions:

#### Who is accessing?

#### What are they accessing?

#### What did they do?

A fourth question must be added to these:

#### When something goes wrong, can we bring the data back safely?

Organizations able to answer these questions reliably stand on far firmer ground in terms of database security.