CISSP Domain 3: Secure Design Principles & Security Models — Mindmap Review Study Guide
═══════════════════════════════════
PART 1: MERMAID MINDMAP
═══════════════════════════════════
mindmap
root((Domain 3 Models<br/>and Frameworks))
["Asset and Data Classification"]
["Asset Classification"]
["Data Classification"]
["Models Definition"]
["Enterprise Security Architecture"]
["Zachman Framework"]
["SABSA"]
["TOGAF"]
["Lattice Based Models"]
["Bell-LaPadula Model"]
["Simple Security Property"]
["Star Property"]
["Strong Star Property"]
["Biba Model"]
["Simple Integrity Property"]
["Star Integrity Property"]
["Invocation Property"]
["Lipner Implementation"]
["Rule Based Models"]
["Clark-Wilson Model"]
["Brewer-Nash Model"]
["Chinese Wall"]
["Graham-Denning Model"]
["Harrison-Ruzzo-Ullman Model"]
["Generic Rights"]
["Secure Design Principles"]
["Threat Modeling"]
["Least Privilege"]
["Defense in Depth"]
["Secure Defaults"]
["Fail Securely"]
["Separation of Duties"]
["Keep it Simple"]
["KISS"]
["Economy of Mechanism"]
["Zero Trust"]
["Trust But Verify"]
["Privacy by Design"]
["Shared Responsibility"]
["Security Frameworks"]
["ISO 27001"]
["ISMS"]
["Annex A"]
["ISO 27002"]
["NIST 800-53"]
["COBIT"]
["ITIL"]
["HIPAA"]
["SOX"]
["FedRAMP"]
["FISMA"]
["Cyber Kill Chain"]
["Cyber Attack Chain"]
═══════════════════════════════════
PART 2: TECHNICAL DEFINITIONS & CONCEPTS
═══════════════════════════════════
Asset and Data Classification
Asset Classification — Encompasses data classification and implies that all organizational assets must be classified and protected appropriately, not just data.
Data Classification — A subset of asset classification focused specifically on categorizing data based on its sensitivity and value.
Models — Conceptual representations of things that shrink and simplify complex systems into components, allowing security to be baked into every aspect of a system.
Enterprise Security Architecture
Architecture — Simply a bunch of components that work together.
Security Architecture — How we protect and secure each of the components in the architecture.
Enterprise Security Architecture — How we protect all the components of the enterprise, including people, processes, systems, networks, etc.
Zachman Framework — An enterprise security architecture that defines a 2-dimensional table (how, where, who, when, and why as columns) to structure and break down an enterprise into components.
SABSA — Sherwood Applied Business Security Architecture; a risk-driven enterprise security architecture model derived from an analysis of business requirements for security.
TOGAF — The Open Group Architecture Framework; helps break an organization down into components so you can build security into each component.
⚠️ EXAM TIP: You do not need to memorize the specific tables/structures for Zachman or SABSA. Just know that Zachman, SABSA, and TOGAF are the three major Enterprise Security Architecture frameworks.
Lattice Based Models
Lattice Based Models — Models that essentially mean layers; they define different layers of confidentiality or integrity and then define rules about what can be read or written between the layers.
Bell-LaPadula Model — A confidentiality-only lattice model that defines layers of secrecy and rules for controlling what a subject (person or process) can do between these layers.
Biba Model — An integrity-only lattice model that defines layers of integrity (low, medium, high) and rules controlling what a subject can do between layers to maintain integrity.
Lipner Implementation — Not a model itself, but an implementation that combines both Bell-LaPadula and Biba to maintain both confidentiality and integrity simultaneously.
Comparison: Bell-LaPadula vs. Biba
| Feature | Bell-LaPadula Model | Biba Model |
|---|---|---|
| Primary Focus | Confidentiality | Integrity |
| Mnemonic | None specified | The “I” in Biba stands for Integrity |
| Read Rule | Simple Security Property: Can only read at your own level and below (read down). | Simple Integrity Property: Can only read at your own layer or above (read up). |
| Write Rule | Star Property: Can only write data at your own level and above (write up). | Star Integrity Property: Can only write down. |
| Read/Write Rule | Strong Star Property: If both reading and writing, can only do so at your own level. | Invocation Property: Third rule (speaker notes you do not need to know about it). |
⚠️ EXAM TIP: Biba is essentially a mirror or the exact inverse of Bell-LaPadula. Remember the “I” in Biba stands for Integrity.
Rule Based Models
Clark-Wilson Model — A rule-based model focused entirely on integrity that goes much deeper than Biba to ensure system consistency and prevent unauthorized or bad changes.
Brewer-Nash Model — Also known as the Chinese Wall model; has one single goal: preventing conflicts of interest.
Graham-Denning Model — A rule-based model that specifies rules allowing subjects to access objects.
Harrison-Ruzzo-Ullman Model — An enhancement of the Graham-Denning model that adds Generic Rights.
Clark-Wilson Model Specifics
3 Goals of Integrity:
- Preventing unauthorized subjects from making any changes
- Preventing authorized subjects from making bad changes
- Maintaining the Consistency of the System
3 Clark-Wilson Rules:
- You must have well-formed transactions
- You must have Separation of duties
- You must have the access triple – subject & program & Object
Secure Design Principles
Threat Modeling — A systematic process for the identification, enumeration, and prioritization of threats in a given system.
Least Privilege — The principle of restricting a user’s ACTIONS to only those actions required for them to perform their role.
Defense in Depth — Having multiple layers of security controls (ideally a complete control combining preventive, detective, and corrective controls) so that if one layer fails, additional layers protect the asset.
Secure Defaults — The principle that the default configuration settings for a system should be the most secure settings possible (e.g., a new firewall defaulting to block all traffic).
Fail Securely — The principle that when a system fails, it fails to a higher security state (e.g., a firewall failing securely blocks all traffic).
Failing Open — The opposite of failing securely; a system failure results in a less secure state (e.g., a firewall failing open lets all traffic through).
Comparison: Fail Securely vs. Failing Open
| Failure State | Definition | Firewall Example |
|---|---|---|
| Fail Securely | System fails to a higher security state. | Blocks all traffic. |
| Failing Open | System fails to a less secure state. | Lets all traffic through. |
Separation of Duties (SoD) — Also known as Segregation of Duties; the principle of having more than one person required to complete a task to prevent errors and fraud. If SoD is implemented, collusion is required to perpetrate fraud.
Keep it Simple — The KISS (Keep it simple stupid) principle, also called Economy of Mechanism; the universal truth that vulnerabilities inevitably increase as complexity increases, so smaller and simpler systems have fewer vulnerabilities and are easier to test.
Zero Trust — The principle that organizations should not automatically trust anything inside or outside its perimeters; trust nothing and verify everything trying to connect to or access organizational assets.
Trust But Verify — The principle that organizations cannot prevent all attacks, so they must focus on complete controls (a combination of prevention, detection, and correction), assuming preventative controls will fail.
Comparison: Zero Trust vs. Trust But Verify
| Principle | Core Focus | Key Concept |
|---|---|---|
| Zero Trust | Access & Perimeter | Do not automatically trust anything inside or outside perimeters; verify everything. |
| Trust But Verify | Control Completeness | Assume prevention will fail; ensure complete controls (prevention, detection, correction) are in place. |
Privacy by Design — The concept of “baking privacy in” from the very start rather than adding it later. It is a framework of 7 foundational principles:
- Proactive not reactive – don’t wait for a privacy breach to happen before you think about privacy controls
- Privacy as the default setting
- Etc.
Shared Responsibility — Recognizing that organizations rely heavily on service providers (like cloud providers) and must have clearly defined accountabilities and responsibilities, because an organization cannot be secure if its service providers do not have good security controls.
Security Frameworks
ISO 27001 — The most widely used security framework in the world, providing best practice recommendations for an ISMS (Information Security Management System). It defines 114 controls across 14 categories in Annex A (covering security governance, policies, onboarding, asset management, access control, cryptography, physical/network security, and compliance). Organizations can be ISO 27001 certified.
ISO 27002 — Provides the Code of Practice (implementation guidance) for the controls defined in ISO 27001. It is a guidance document only; organizations cannot be certified against ISO 27002.
Comparison: ISO 27001 vs. ISO 27002
| Feature | ISO 27001 | ISO 27002 |
|---|---|---|
| Purpose | Best practice recommendations for an ISMS. | Code of practice / implementation guidance for 27001 controls. |
| Content | Defines 114 controls across 14 categories (Annex A). | Provides detailed guidance on implementing those controls. |
| Certification | Organizations can be ISO 27001 certified. | Cannot be certified against ISO 27002. |
⚠️ EXAM TIP: ISO 27001 defines the controls and you can be certified. ISO 27002 is just guidance and you cannot be certified against it.
NIST 800-53 — Provides a set of security and privacy controls specifically for US federal agencies.
COBIT — Control Objectives for Information and Related Technologies; created by IT Auditors at ISACA, making it particularly useful for audit and assurance work.
ITIL — Information Technology Infrastructure Library; defines a framework of best practices for delivering IT services aligned with business goals (e.g., change, configuration, access, event, and availability management).
HIPAA — Health Insurance Portability and Accountability Act; a framework focused on safeguarding medical information.
SOX — Sarbanes-Oxley Act; a US federal law (prompted by Enron and WorldCom) requiring top management to individually certify the accuracy of financial information with severe penalties for fraud. The security aspect requires financial records to have integrity and be available.
FedRAMP — Provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. Any US Federal Government entity wanting to use cloud services must use FedRAMP-approved services.
FISMA — Defines security requirements for US Federal Government agencies and contractors, requiring each agency to develop, document, and implement an agency-wide information security program.
Cyber Kill Chain — Also referred to as the Cyber Attack Chain; defines 7 stages of common cyberattacks where security teams can prevent, detect, or intercept attackers. Breaking a link in the chain stops the attack.
⚠️ EXAM TIP: You must memorize the exact order of the 7 stages of the Cyber Kill Chain and high-level what is happening at each stage:
- Reconnaissance
- Weaponization
- Delivery
- Exploit
- Installation
- Command & Control
- Actions