Database Threat Landscape & Physical/Environmental Safety

Why Database Security Begins Before You Write a Single Query

A database is only as secure as the environment surrounding it. That environment has two layers: the physical world of servers, cables, and rooms, and the digital world of network traffic, credentials, and application code. A breach at either layer can expose every record you manage. As a database administrator, you are responsible for understanding both.

The Database Threat Landscape

Attackers pursue databases because that is where valuable data lives. Knowing how they approach the problem helps you defend against it. The STRIDE model, developed as a structured way to think about software threats, gives you a practical vocabulary:

• Spoofing – An attacker pretends to be a legitimate user or service. Example: logging into PostgreSQL with stolen credentials.
• Tampering – Data or code is modified without authorization. Example: an insider changes salary records directly in a table without going through the application.
• Repudiation – A user performs an action and later denies doing it, especially when audit logging is absent. Example: a DBA drops a table and there is no log to prove who did it.
• Information Disclosure – Sensitive data is exposed to unauthorized parties. Example: a misconfigured view lets a regular employee query another employee's Social Security Number.
• Denial of Service (DoS) – Legitimate users are prevented from accessing the database. Example: a runaway query or deliberate flood of connections exhausts server resources.
• Elevation of Privilege – A low-privilege account gains higher rights. Example: a developer account is exploited to execute commands with DBA-level permissions.

For each STRIDE category, a control exists. Spoofing is countered by strong authentication. Tampering is countered by referential integrity and role-based access controls. Repudiation is countered by audit logging. Information disclosure is countered by encryption and least-privilege grants. DoS is countered by connection limits, query timeouts, and redundancy. Elevation of privilege is countered by strict separation of roles and regular privilege reviews.

Common attack vectors you will encounter on the job include SQL injection (malicious SQL code embedded in application input), credential theft (passwords captured through phishing or weak storage), excessive privilege abuse (accounts with more rights than they need), unpatched vulnerabilities (database engine bugs that have published exploits), and insecure backups (backup files stored without encryption or access controls).

Data Classification

Not all data carries the same risk if exposed. The DAMA DMBOK2 framework describes data security as a discipline that includes classifying data so that the right controls are applied proportionally. A simple three-tier model is widely used:

| Tier | Label | Examples |

|------|-------|----------|

| 1 | Restricted / Confidential | Social Security Numbers, credit card numbers, health records, passwords |

| 2 | Internal / Sensitive | Salaries, employee performance data, business financials |

| 3 | Public / Non-sensitive | Product names, public pricing, first names used alone |

Regulatory frameworks such as HIPAA, PCI-DSS, and various state privacy laws influence how Tier 1 data must be handled. When in doubt, classify data at the higher tier until you can confirm otherwise.

Physical and Environmental Safety in the Data Center

Server rooms and data centers present real physical hazards. OSHA's general industry electrical safety standards apply to anyone working in these spaces. You are required to recognize hazards before you enter.

Five physical hazards common to server rooms:

1. Live electrical cables – Power distribution units, patch cables, and uninterruptible power supplies (UPS) carry live current. Never open energized equipment without following lockout/tagout (LOTO) procedures. LOTO requires that energy sources be isolated and physically locked before service work begins.

2. Rack instability – Server racks that are not bolted to the floor or properly loaded (heavier equipment at the bottom) can tip. Never pull multiple slides out of the same rack at the same time.

3. Airflow and cooling hazards – Raised-floor tiles can shift unexpectedly, and high-velocity air from precision cooling units can cause eye injury or dislodge equipment. Wear safety glasses when removing floor tiles. Keep hot-aisle and cold-aisle pathways clear.

4. Emergency Power-Off (EPO) locations – Every data center has EPO buttons or switches that cut all power instantly. Know exactly where they are before you start work. An accidental EPO activation can cause data loss across every system in the room.

5. Slip and trip risks – Cable management failures, wet floors from condensation, and raised floor edges are common causes of falls. Wear slip-resistant, closed-toe footwear and follow housekeeping rules.

Personal Protective Equipment (PPE): At minimum, wear safety glasses and closed-toe footwear in active data center spaces. When working near energized electrical panels, arc-flash rated PPE is required per NFPA 70E guidance. Follow whatever PPE requirements your employer's safety plan specifies.

Before any hands-on work in the data center: review the site's emergency procedures, locate fire suppression equipment (most data centers use clean-agent suppression, not water), and confirm you know the evacuation route. Never work alone in a data center if it can be avoided.

CIS Benchmarks as a Security Baseline

The Center for Internet Security (CIS) publishes configuration benchmarks for major database platforms including PostgreSQL. A CIS Benchmark is a consensus-based, documented set of configuration settings that reduce the attack surface of a system. DBAs use benchmarks to audit whether a database has been set up securely—checking items like default account removal, password policy enforcement, audit logging status, and file permission settings. Benchmarks are available free of charge for registered users at cisecurity.org and are referenced by many compliance frameworks.

Connecting the Layers

Physical safety and logical security are not separate topics that live in different departments. An attacker with physical access to a server can bypass nearly every software control you have implemented. A DBA who does not understand physical hazards can unintentionally cause an outage that is indistinguishable from a DoS attack. Your professional responsibility covers both layers.