Access Control: The process of regulating who can access and perform operations on data within a database. Access control mechanisms enforce security policies by granting or denying permissions to users based on their identities, roles, or other attributes.

ACID: An acronym that stands for Atomicity, Consistency, Isolation, and Durability, representing the key properties of a database transaction:

Atomicity: Ensures that all operations within a transaction are completed successfully or none at all. Transactions are treated as indivisible units, and if any operation fails, the entire transaction is rolled back.

Consistency: Ensures that the database remains in a consistent state before and after the execution of a transaction, preserving integrity constraints, business rules, and data dependencies.

Isolation: Ensures that the execution of concurrent transactions does not interfere with each other, providing each transaction with a consistent view of the database, regardless of other concurrent transactions.

Durability: Ensures that the effects of committed transactions are permanent and persistent, even in the event of system failures or crashes, through mechanisms such as transaction logging and write-ahead logging.

Advanced Persistent Threats (APTs): Coordinated and sophisticated attacks orchestrated by skilled adversaries, often targeting databases and other critical infrastructure over extended periods to steal data, disrupt operations, or achieve geopolitical objectives.

Audit and Compliance Testing: Ensuring that database operations, access controls, and data handling practices comply with regulatory requirements, industry standards, and organizational policies through audit trails, logging, and compliance checks.

Authentication: The process of verifying the identity of a user or entity attempting to access a database. Authentication mechanisms typically involve presenting credentials such as usernames, passwords, biometric data, or cryptographic tokens.

Authorization: The process of determining what actions or operations a user is allowed to perform within a database after authentication. Authorization mechanisms enforce access control policies by granting or denying permissions based on the user’s identity, role, or privileges.

Automated Monitoring and Alerting: The implementation of tools and processes to continuously monitor database health, performance, and availability, with automated alerts triggered in response to anomalies, errors, or potential issues.

Audit Trail: A chronological record of activities and events related to database access, modifications, and usage. Audit trails are used for security monitoring, compliance auditing, and forensic analysis to track and investigate suspicious or unauthorized activities.

Backdoor Exploitation: Unauthorized access to databases through hidden or undocumented entry points deliberately left by attackers or inadvertently introduced by developers, administrators, or third-party vendors.

Backup: A copy of database data and configuration settings stored separately from the primary database to facilitate recovery in case of data loss or corruption, often performed regularly to ensure up-to-date backups are available.

Backup and Recovery: Procedures and mechanisms for creating copies of database data and restoring them in case of data loss, corruption, or system failures, ensuring data integrity and availability.

Backup and Recovery Testing: Testing the procedures and mechanisms for backing up and restoring database data and configurations to ensure data availability, integrity, and recoverability in case of disasters or failures.

Boundary Testing: Testing database inputs, queries, or operations at the boundaries of permissible values or ranges to identify potential errors, vulnerabilities, or unexpected behavior.

Buffer Overflows: Buffer overflow vulnerabilities in database software can be exploited by attackers to execute arbitrary code or crash the database server, potentially leading to unauthorized access or denial of service.

Column: A vertical arrangement of data values within a table, representing a specific attribute or field of the entities stored in the table.

Column-Family Store: A type of NoSQL database optimized for storing and querying data organized by columns rather than rows, providing efficient storage and retrieval of wide tables with sparse data. Examples include Apache Cassandra, Apache HBase, and ScyllaDB.

Commit: The final step in a transaction where all changes made within the transaction are made permanent and visible to other transactions. Once a transaction is committed, its changes become durable and cannot be undone without executing a rollback.

Concurrency Control: Techniques and mechanisms used to manage and coordinate concurrent access to shared resources, such as database records, to prevent data inconsistencies and ensure transaction isolation and integrity.

Concurrency Control Testing: Assessing the effectiveness of concurrency control mechanisms, such as locking, isolation levels, and transaction management, in preventing data corruption, deadlocks, or inconsistent states in multi-user environments.

Concurrency Testing: Assessing the behavior of a database system when multiple users or transactions access and modify data concurrently to ensure data consistency, isolation, and transaction management.

Credential Theft and Brute Force Attacks: Unauthorized access to databases through the theft of user credentials or by systematically guessing passwords using automated tools, potentially leading to data theft or compromise.

Cross-Site Scripting (XSS): An attack where malicious scripts are injected into web pages viewed by other users, potentially leading to the execution of unauthorized actions or the theft of session cookies, which can compromise database access.

Data Breach: Unauthorized access to sensitive or confidential data stored in a database, often resulting from vulnerabilities, misconfigurations, or insider threats, and leading to data theft or exposure.

Data Consistency: Ensuring that database transactions are executed correctly and reliably, maintaining the integrity and consistency of data across multiple operations and concurrent users.

Data Encryption: The process of converting plaintext data into ciphertext using cryptographic algorithms to protect its confidentiality. Encrypted data can only be decrypted by authorized users with the appropriate decryption keys, reducing the risk of unauthorized access or data breaches.

Data Exfiltration: Unauthorized extraction or theft of sensitive data from a database, often conducted stealthily to avoid detection, potentially leading to financial losses, reputational damage, or regulatory sanctions.

Data Governance: The framework and processes for managing, protecting, and ensuring the quality, integrity, and security of data assets across an organization, including policies, standards, roles, and responsibilities.

Data Integrity Testing: Verifying the accuracy, consistency, and reliability of data stored in the database by checking for constraints, relationships, and validation rules.

Data Leakage: Inadvertent exposure of sensitive data through misconfigured permissions, weak encryption, or insecure data handling practices can result in data leakage and compromise of sensitive information.

Data Loss Prevention (DLP): Strategies and technologies used to prevent unauthorized disclosure or leakage of sensitive data from a database, including monitoring, encryption, access controls, and policy enforcement.

Data Masking: The technique of obscuring or anonymizing sensitive data in a database to protect privacy and confidentiality, while still allowing authorized users to perform certain operations on the data.

Data Migration Testing: Validating the accuracy and completeness of data transferred from one database system to another during migration, conversion, or integration projects to minimize data loss, corruption, or inconsistencies.

Data Mining: The process of discovering patterns, trends, correlations, and insights from large datasets stored in databases using techniques such as statistical analysis, machine learning, and artificial intelligence.

Data Replication: The process of copying and synchronizing database data across multiple storage locations or servers to ensure data availability, improve performance, and provide resilience against hardware failures or disasters.

Data Tampering: Attackers may attempt to modify or manipulate data stored in the database, either to conceal their activities, disrupt business operations, or cause financial harm.

Data Validation Testing: Checking the correctness and completeness of input data processed by the database system, including validation of data types, formats, ranges, and constraints.

Data Warehouse: A specialized database system designed for storing and analyzing large volumes of structured and unstructured data from multiple sources to support decision-making and business intelligence (BI) initiatives.

Database: A structured collection of data organized for efficient storage, retrieval, and management, typically stored and managed using a database management system (DBMS).

Database: A structured collection of data organized for efficient retrieval, storage, and manipulation using database management system (DBMS) software.

Database Administration (DBA): The role responsible for managing and maintaining database systems, including installation, configuration, optimization, security, backup, recovery, performance monitoring, and troubleshooting.

Database Auditing: The process of monitoring and recording database activities, such as user logins, data accesses, modifications, and administrative operations, for the purpose of security analysis, compliance, and forensic investigations.

Database Backup: A copy of database data and configuration settings stored separately from the primary database to facilitate recovery in case of data loss, corruption, or disaster, often performed regularly to ensure up-to-date backups are available.

Database Cluster: A group of interconnected database servers or instances working together to provide high availability, fault tolerance, and scalability, often implemented using technologies such as clustering, replication, or sharding.

Database Connection Pool: A cache of reusable database connections maintained by the application server or middleware, allowing multiple client applications to efficiently share and reuse connections to the database, reducing connection overhead and improving performance.

Database Firewall: A security mechanism that monitors and filters incoming and outgoing database traffic to prevent unauthorized access, SQL injection attacks, data exfiltration, and other malicious activities. Database firewalls enforce security policies based on predefined rules and signatures.

Database Hardening: The process of configuring and securing a database system to reduce its vulnerability to security threats and attacks. Database hardening measures may include disabling unnecessary features, applying security patches, configuring access controls, and implementing encryption.

Database Index: A data structure used to improve the speed and efficiency of data retrieval operations by providing quick access to specific data records based on indexed columns or keys, reducing the need for full table scans.

Database Instance: A single, independent installation of a database management system running on a server, representing a distinct environment with its own set of databases, configurations, and resources.

Database Management System (DBMS): Software that enables users to interact with databases by providing functions for creating, querying, updating, security, and administering database systems.

Database Monitoring: The continuous surveillance and analysis of database activities, performance metrics, and security events to detect and respond to potential security incidents, performance issues, or anomalies. Database monitoring tools provide real-time alerts, logs, and reports to administrators and security personnel.

Database Query: A request for data or information from a database, typically written in a query language such as SQL (Structured Query Language) and executed by the database management system to retrieve, manipulate, or analyze data.

Database Replication: The process of copying and synchronizing database data and changes between multiple servers or instances, typically used for redundancy, load balancing, disaster recovery, and distributed data access.

Database Resiliency: The ability of a database system to maintain its functionality, performance, and availability in the face of various disruptions, such as hardware failures, software bugs, network outages, or cyberattacks.

Database Restore: The process of recovering database data from a backup copy to restore the database to a previous state after data loss, corruption, or disaster, typically involving backup files, recovery procedures, and database management tools.

Database Schema: A logical structure or blueprint that defines the organization, structure, and relationships of data within a database, including tables, columns, keys, constraints, and other metadata.

Database Schema Testing: Verifying the structure, design, and relationships of database objects, including tables, indexes, views, and constraints, to ensure they meet design specifications and data modeling requirements.

Database Security: Measures and controls implemented to protect database systems, data assets, and infrastructure from unauthorized access, disclosure, modification, or destruction, including authentication, authorization, encryption, auditing, and monitoring mechanisms.

Database Server: A computer system or server dedicated to hosting and managing one or more databases, providing centralized access and processing capabilities to client applications.

Database Testing: The process of verifying the functionality, performance, and reliability of a database system to ensure it meets specified requirements and quality standards.

Denial of Service (DoS) and Distributed Denial of Service (DDoS): Attacks aimed at disrupting database services by overwhelming servers or network infrastructure with a high volume of traffic, rendering them unavailable to legitimate users.

Denormalization: The process of intentionally introducing redundancy into a database schema to improve performance by reducing the need for joins and optimizing query execution.

Disaster Recovery (DR): The process of restoring database operations and data access after a catastrophic event, such as natural disasters, fires, or cyberattacks, typically involving backup and recovery strategies, offsite data replication, and failover to secondary data centers.

Database Transaction: A logical unit of work performed within a database management system (DBMS) that consists of one or more operations, such as inserts, updates, or deletes, and is treated as a single, atomic entity.

Deadlock: A situation in which two or more transactions are unable to proceed because each is waiting for a resource held by the other, resulting in a circular dependency and a deadlock condition.

Dirty Read: A phenomenon that occurs when one transaction reads data that has been modified by another uncommitted transaction, potentially leading to inconsistent or incorrect results.

Document-Oriented Database: A database system that stores and retrieves data in the form of documents, typically encoded in formats like JSON or XML. Document databases are well-suited for handling semi-structured data and hierarchical structures. Examples include MongoDB, Couchbase, and Amazon DocumentDB.

Encryption: The process of encoding database data to prevent unauthorized access or disclosure, ensuring that sensitive information remains confidential even if intercepted by attackers.

Failover: The automatic or manual process of redirecting database operations from a failed or degraded primary server to a standby or secondary server to maintain continuous service availability and minimize downtime.

Fault Tolerance: The capability of a database system to continue operating without interruption in the event of hardware or software failures, often achieved through redundant hardware components, data replication, and error detection/correction mechanisms.

File Inclusion Vulnerabilities: Exploiting weaknesses in web application code to include arbitrary files, such as database configuration files or sensitive data, leading to unauthorized access or information disclosure.

Foreign Key: A column or set of columns in a table that establishes a relationship with the primary key of another table, enforcing referential integrity and enabling data consistency across related tables.

Graph Database: A type of database optimized for storing and querying graph-like data structures, consisting of nodes, edges, and properties. Graph databases excel at representing and traversing complex relationships between entities. Examples include Neo4j, Amazon Neptune, and JanusGraph.

High Availability (HA): A characteristic of a database system that ensures it remains operational and accessible to users with minimal downtime or interruption, typically achieved through redundancy, failover mechanisms, and automated recovery processes.

In-Memory Database: A database system that stores and manipulates data primarily in memory, offering high-speed data access and processing compared to disk-based storage. In-memory databases are commonly used for caching, real-time analytics, and high-performance computing. Examples include Redis, MemSQL, and SAP HANA.

Index: A data structure that enhances the performance of database queries by providing efficient access paths to rows based on the values of specified columns, reducing the need for full table scans.

Insecure Authentication and Authorization: Weak or inadequate authentication and authorization mechanisms can allow unauthorized users to gain access to sensitive data or perform unauthorized actions within the database.

Insecure Configuration: Misconfigured database settings or access controls can leave databases vulnerable to unauthorized access, data leakage, or other security breaches.

Insecure Data Transmission: Lack of encryption or use of weak encryption protocols during data transmission between clients and the database server can expose sensitive data to interception or eavesdropping attacks.

Insecure Direct Object References (IDOR): Insecure direct object references occur when attackers manipulate input parameters to gain unauthorized access to database objects or records they should not have access to.

Insider Threats: Malicious actions or negligence by individuals with legitimate access to databases, including employees, contractors, or partners, leading to data theft, sabotage, or unauthorized modifications.

Insufficient Logging and Monitoring: Inadequate logging and monitoring capabilities can make it difficult to detect and respond to security incidents or suspicious activities within the database environment.

Integration Testing: Testing the interaction and integration between different database components, modules, or systems to ensure they function together correctly and exchange data accurately.

Intrusion Detection and Prevention (IDP): Technologies and techniques used to detect and block unauthorized access attempts or malicious activities in real-time, helping to prevent security breaches and mitigate their impact.

Isolation Levels: Configurable settings in a database system that determine the degree to which concurrent transactions are isolated from each other, preventing interference and maintaining data integrity.

Key-Value Store: A database system that stores data as a collection of key-value pairs, allowing rapid retrieval of values based on their associated keys. Key-value stores are simple and efficient but offer limited query capabilities. Examples include Redis, Amazon DynamoDB, and Apache HBase.

Load Balancing: The distribution of database workload across multiple servers or nodes to optimize resource utilization, improve performance, and mitigate the risk of overload or service degradation.

Lost Update: A data inconsistency issue that occurs when two or more transactions attempt to update the same data simultaneously, resulting in one transaction’s changes being overwritten or lost.

Man-in-the-Middle (MitM): Interception and manipulation of data transmitted between users and databases by inserting a malicious intermediary, compromising confidentiality, integrity, and authenticity.

Missing Security Patches: Failure to apply security patches and updates to database software can leave systems vulnerable to known security vulnerabilities that have been addressed in newer versions of the software.

NewSQL Database: A class of relational database systems that aim to combine the scalability and flexibility of NoSQL databases with the consistency and transactional capabilities of traditional RDBMS. NewSQL databases are designed to handle large-scale distributed systems while maintaining ACID compliance. Examples include Google Spanner, CockroachDB, and NuoDB.

Normalization: The process of organizing database tables and reducing data redundancy by eliminating duplicate information and establishing relationships between tables to minimize data anomalies.

Non-Relational Database (NoSQL): A type of database that does not adhere to the relational model, often used for handling large volumes of unstructured or semi-structured data, providing flexibility, scalability, and performance advantages in certain use cases.

NoSQL Database: A database system designed for storing and retrieving unstructured or semi-structured data, often providing flexible schemas and horizontal scalability. NoSQL databases include document stores (e.g., MongoDB), key-value stores (e.g., Redis), column-family stores (e.g., Apache Cassandra), and graph databases (e.g., Neo4j).

Optimistic Concurrency Control: A concurrency control strategy that allows multiple transactions to proceed concurrently without locking resources, detecting conflicts only at the time of commit and rolling back conflicting transactions if necessary.

Partitioning: The division of a large database table into smaller, more manageable segments or partitions based on specified criteria (e.g., ranges of values, hash functions), improving performance, scalability, and manageability.

Patch Management: The practice of applying software updates, patches, and fixes to database systems in a timely manner to address known security vulnerabilities and protect against exploitation by attackers.

Performance Testing: Evaluating the responsiveness, scalability, and throughput of a database system under various load conditions to identify performance bottlenecks, optimize resource utilization, and ensure acceptable response times.

Pessimistic Concurrency Control: A concurrency control strategy that involves locking resources preemptively to prevent conflicts between concurrent transactions, ensuring serializability and consistency but potentially reducing concurrency and performance.

Phishing and Social Engineering: Deceptive techniques aimed at tricking individuals into divulging sensitive information, such as database credentials or access codes, through email, phone calls, or other communication channels.

Primary Key: A unique identifier for each row in a table, ensuring data integrity and providing a reference point for establishing relationships with other tables.

Privilege Escalation: Exploiting vulnerabilities or misconfigurations to gain elevated privileges within a database system, allowing attackers to access sensitive data, execute arbitrary commands, or compromise other systems.

Query: A request or command issued to a database management system (DBMS) to retrieve, manipulate, or modify data stored in a database. Queries are typically written in SQL and can perform operations such as SELECT, INSERT, UPDATE, and DELETE.

Ransomware: Malware that encrypts database files or entire systems, demanding payment (usually in cryptocurrency) for decryption keys, posing a significant threat to data integrity and availability.

Recovery Point Objective (RPO): The maximum tolerable amount of data loss that an organization is willing to accept in the event of a disaster or system failure, measured in terms of the time between the last backup and the occurrence of the event.

Recovery Time Objective (RTO): The maximum acceptable downtime for restoring database operations after a disruption, representing the targeted duration within which database services should be restored to normal functioning.

Redundancy: The duplication of critical components, such as servers, storage devices, or network connections, within a database system to eliminate single points of failure and enhance resilience against hardware failures or disruptions.

Relational Database: A type of database that organizes data into tables consisting of rows and columns, with relationships established between tables using keys, enabling efficient querying and data manipulation.

Relational Database Management System (RDBMS): A database management system that organizes data into tables consisting of rows and columns, with relationships defined between tables. Examples include MySQL, PostgreSQL, Oracle Database, and Microsoft SQL Server.

Replication: The process of copying and distributing database data across multiple servers or nodes to improve availability, fault tolerance, and performance, often used in distributed or high-availability environments.

Regression Testing: Repeatedly testing database functionality after making changes or updates to ensure that existing features continue to work as expected and that new changes have not introduced unintended side effects or errors.

Role-Based Access Control (RBAC): A method of access control where permissions are assigned to users based on their roles within an organization, simplifying administration and ensuring consistent enforcement of access policies.

Rollback: The process of reverting the changes made by a transaction that has not been committed or has encountered an error, ensuring that the database returns to its state prior to the start of the transaction.

Row (Tuple): A horizontal arrangement of data values within a table, representing a single record or instance of the entities stored in the table.

Savepoint: A point within a transaction where the current state of the database is saved, allowing for partial rollback or recovery to that specific point in case of errors or failures.

Schema: A formal description of the structure, constraints, and relationships of data stored in a database, defining the tables, columns, data types, keys, and integrity rules.

Security Information and Event Management (SIEM): A centralized system for collecting, correlating, and analyzing security event data from various sources, including databases, to identify and respond to security threats effectively.

Security Testing: Evaluating the effectiveness of security measures and controls implemented in the database system to protect against unauthorized access, data breaches, and other security threats.

Sharding: A horizontal partitioning technique that distributes database records across multiple servers or nodes (shards) based on predefined criteria, such as data ranges or hash functions, to improve scalability and performance.

Spatial Database: A database system designed for storing and querying spatial data, such as geographic information system (GIS) data, spatial relationships, and geometries. Spatial databases support spatial indexing and spatial query operations. Examples include PostGIS, Oracle Spatial, and MongoDB Geospatial Queries.

Stored Procedure: A precompiled and stored collection of SQL statements that performs a specific task or set of tasks within a database. Stored procedures can be invoked by applications or other database objects and offer advantages such as improved performance, security, and code reuse.

SQL (Structured Query Language): A standard programming language used for managing relational databases. SQL is used to perform tasks such as querying data, updating records, and defining database schemas.

SQL Injection (SQLi): A type of cyber attack where malicious SQL code is injected into input fields or query parameters of a web application to manipulate the underlying database or gain unauthorized access. SQL injection attacks can lead to data breaches, data loss, and unauthorized data modifications if not properly mitigated.

Table: A fundamental component of a relational database consisting of rows and columns, representing entities and their attributes, with each row representing a record or instance of the entity.

Third-Party Software Vulnerabilities: Vulnerabilities in third-party software components or libraries used by the database system can be exploited by attackers to compromise the security of the database.

Transaction: A logical unit of work performed within a database system, typically comprising one or more database operations (e.g., reads, writes) that must be executed atomically, consistently, isolated, and durably (ACID properties).

Time-Series Database: A database system optimized for storing and querying time-series data, such as sensor readings, stock prices, or log data, with support for efficient data ingestion, retention policies, and time-based queries. Examples include InfluxDB, Prometheus, and TimescaleDB.

Transaction Isolation Levels: Configurable settings that determine the degree of isolation between concurrent transactions, ranging from Read Uncommitted (lowest isolation level) to Serializable (highest isolation level), balancing between consistency and performance.

Transaction Log: A record of all changes made to a database during the execution of transactions, including committed and uncommitted transactions, used for recovery, rollback, and replication purposes.

Trigger: A database object that automatically executes a specified action or set of actions in response to certain database events, such as INSERT, UPDATE, or DELETE operations on a table. Triggers are often used to enforce data validation rules, maintain audit trails, or propagate changes to related tables.

Two-Factor Authentication (2FA): An authentication method that requires users to provide two forms of identification or credentials to access a database, typically combining something they know (e.g., password) with something they have (e.g., a security token or mobile device).

Two-Phase Commit (2PC): A distributed transaction protocol used to ensure atomicity and consistency across multiple databases or resources involved in a distributed transaction, involving a prepare phase and a commit phase.

Unit Testing: Testing individual database objects, such as stored procedures, functions, triggers, or queries, in isolation to validate their correctness and functionality.

View: A virtual table generated by a query that does not store data itself but instead presents data from one or more underlying tables. Views provide a way to simplify complex queries, enforce security restrictions, and present data in different perspectives without altering the underlying data structures.

Vulnerability Assessment: The process of identifying and assessing security vulnerabilities and weaknesses in a database system to prioritize remediation efforts and mitigate potential risks. Vulnerability assessments may involve scanning, testing, and analyzing the database infrastructure, configurations, and applications for known vulnerabilities and misconfigurations.

Weak Passwords: Use of weak, default, or easily guessable passwords for database accounts can make it easier for attackers to gain unauthorized access to the database.

Write-Ahead Logging (WAL): A technique used to ensure durability in database systems by writing transaction log records to stable storage before modifying database pages, guaranteeing that committed transactions are recoverable even in the event of a system crash or failure.

Zero-Day Exploits: Attacks that target previously unknown vulnerabilities in database software or underlying infrastructure, allowing attackers to gain unauthorized access, execute arbitrary code, or escalate privileges before patches or mitigations are available.

Zero-Day Vulnerability: A security vulnerability or software flaw that is exploited by attackers before it is known to the vendor or security community. Zero-day vulnerabilities pose significant risks to database security as they can be exploited to launch targeted attacks or data breaches without available patches or mitigation measures.