📘Study Focus | Domain 8: Software Development Security

 Last domain — let’s finish strong with Domain 8: Software Development Security. This one is all about secure coding practices, SDLC phases, application security models, and the infamous software vulnerabilities that show up in CISSP trick questions.

📘 Domain 8: Software Development Security

🔑 Flashcard Topics (AppSec, DevOps, Vulnerabilities, and SDLC Memory Traps)

🏗️ System Development Life Cycle (SDLC)

🔁 SDLC Phases

  • 1. Initiation → 2. Acquisition/Development → 3. Implementation → 4. Operation → 5. Disposal

📄 Security in SDLC

  • Security must be integrated at every phase, starting at requirements.

📦 Secure Coding Guidelines

  • Follow standards like OWASP, CERT, and NIST 800-64.

🧱 Development Models

  • Waterfall = Sequential, rigid

  • Agile = Iterative, flexible

  • DevOps = Combines development + operations

  • DevSecOps = Builds security into DevOps pipeline

🧪 Software Testing Types

  • Static Testing (SAST) = Code reviewed without execution

  • Dynamic Testing (DAST) = Code tested during runtime

  • Regression Testing = Ensure new code doesn’t break old features

  • Fuzz Testing = Inputs malformed/random data to crash the app

🛡️ Application Security Controls

  • Input Validation = Prevents injection attacks

  • Output Encoding = Escapes data for safe rendering

  • Parameterization = Stops SQL injection by separating code from data

  • Error Handling = Should not reveal internal details to users

🛠️ Software Architecture Concepts

  • Trusted Computing Base (TCB) = Components enforcing security policy

  • Reference Monitor = Always-enforcing access checker between subject and object

  • Security Kernel = Implements the reference monitor

⚠️ Common Software Vulnerabilities

  • Buffer Overflow = Input overflows memory buffer

  • SQL Injection = Unvalidated input manipulates SQL queries

  • XSS (Cross-Site Scripting) = Inject JS into browser

  • CSRF (Cross-Site Request Forgery) = Tricks user into submitting requests

  • Race Condition = Two operations conflict in timing

  • TOCTOU (Time-of-Check to Time-of-Use) = Change between check and use causes exploit

🔐 Access Control in Software

  • Access Control Matrix = Subjects × Objects grid of permissions

  • Bell-LaPadula / Biba = Can also apply at software architecture level

🏷️ Code Reuse Risks

  • Third-Party Libraries = May include vulnerabilities

  • Open Source Components = Must be vetted for updates and known CVEs

📜 Change Management in Dev

  • Any code changes must be reviewed, approved, tested, and documented before deployment.

🧩 Database and Storage Security

  • Normalization = Reduces redundancy and anomalies

  • Stored Procedures = Safer than raw SQL queries

  • Encryption at Rest/In Transit = Encrypt sensitive data in DB and in transport

🧬 Threat Modeling

  • STRIDE Model
    Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege

  • DREAD Model (Deprecated)
    Damage, Reproducibility, Exploitability, Affected Users, Discoverability

That’s Domain 8 complete, and with it, your CISSP flashcard outline is done! 🎉

Would you like:

  1. A printable flashcard deck (PDF/Anki format)?

  2. A study tracker to review high-priority topics daily?

  3. A “last 72-hour” cram plan to lock in high-yield concepts?

Let me know what’s next, and we’ll finish this prep the smart way.

Comments

Post a Comment

Popular posts from this blog

🧭 CISSP Study Note: Guidelines

🧭 CISSP Study Note: Guidelines 🔍 Definition Guidelines are suggested practices, recommendations, or expectations that help individuals or teams perform tasks effectively and consistently to achieve organizational goals, standards, and strategic objectives . Unlike policies or standards, guidelines are not mandatory —they offer flexibility while still encouraging best practices. 🧠 Why It Matters in Cybersecurity In a security framework, not every situation can be addressed with a rigid rule . Guidelines fill that gap by offering direction without strict enforcement , helping professionals: Make informed decisions Handle exceptions responsibly Align behavior with organizational goals Maintain consistency across teams They also support user education, secure configurations, and best practices adoption without limiting operational flexibility. 📋 Guidelines vs. Policies vs. Standards Term Binding? Purpose Policy ✅ Mandatory Defines what must be...
Read more

💸 CISSP Study Note: Risk Transference

 💸 CISSP Study Note: Risk Transference 🔍 Definition Risk Transference is the process of shifting the financial or operational impact of a risk to a third party , typically through contracts, insurance, or outsourcing agreements . While the risk itself doesn’t disappear, its burden is transferred , meaning someone else becomes responsible for managing or absorbing the consequences . 🧠 Why It Matters in Cybersecurity Not all risks are feasible to mitigate or avoid directly—especially high-cost, low-probability events . Risk transference allows organizations to: Focus on their core competencies Offload specialized or high-risk tasks Limit financial exposure Improve recovery options without investing heavily in in-house controls 📌 Transference does NOT eliminate the risk—it shifts the responsibility or financial impact. 🧾 Common Methods of Risk Transference Method Description Cybersecurity Insurance Transfers financial losses from cyberattack...
Read more

📏 CISSP Study Note: Standards

📏 CISSP Study Note: Standards 🔍 Definition Standards are specific, mandatory rules or technical specifications that define how policies must be implemented and how performance or behavior must conform to meet organizational or regulatory expectations. They are non-negotiable , measurable, and enforceable, often serving as the baseline for procedures and audits . While policies tell you what to do, standards tell you exactly how it must be done. 🧠 Why It Matters in Cybersecurity Standards are critical for ensuring consistency , reliability , and compliance across systems, teams, and departments. They help: Reduce ambiguity in control implementation Align practices with compliance frameworks Support repeatable, auditable processes Simplify training, onboarding, and cross-team coordination 🧩 Standards in the Policy Hierarchy Level Purpose Policy High-level directive—“What must be done” Standard ✅ Mandatory specification—“How it must ...
Read more