ACID Principles Explained for CISSP: Databases Must Be Reliable
- Luke Ahmed
- 3 hours ago
- 2 min read

ACID!
Just a cool word to begin with, and the CISSP definition of it is even cooler.
Whenever I start studying anything in the Domain 8 pages of CISSP books, I just can’t wait to get to the easy topics, one of which is ACID.
It just focuses on the reliability of database transactions.
ACID represents the core design principles that ensure databases process transactions safely and predictably.
ACID stands for:
Atomicity
The word atomic comes from the idea of an atom in physics. An atom is considered the smallest indivisible unit of matter in classical chemistry.
You can’t take half an atom and expect it to behave like the whole thing.
Database designers borrowed this idea.
A database transaction must complete entirely or not at all. If part of a transaction fails, the database rolls back the entire operation. Partial updates are never allowed. There is no such thing as half a transaction.
For example, imagine a banking system transferring money between accounts. If the
system withdraws money from one account but fails to deposit it into the other, the transaction must be rolled back.
Consistency
The database must remain in a valid state before and after a transaction. All defined rules, constraints, and relationships must remain intact.
This ensures that transactions never violate database rules.
Isolation
Multiple transactions can occur simultaneously without interfering with one another. Each transaction behaves as if it were operating alone. This prevents data corruption when many users access a database at the same time.
Durability
Once a transaction is committed, it remains permanent—even if the system crashes
immediately afterward. This property ensures that completed transactions are never lost.
For the CISSP exam, ACID questions often test whether you understand the concept behind these properties, not just the definitions.
Think like a manager: ACID exists to ensure that data remains trustworthy and predictable, even when systems fail.
Think like a person: you want ALL the money you want to withdraw from a bank, not just some of it!




















