Domain 8Software Development SecurityCORE

Secure Software Development Lifecycle (SSDLC)

Integrating security into SDLC phases, DevSecOps pipelines, SAST vs DAST vs IAST/SCA testing, software assurance maturity models (SAMM, BSIMM), and API security.

Domain: Domain 8: Software Development Security•Updated: 2026-08-26
#SSDLC#DevSecOps#SAST#DAST#SCA#Threat Modeling#OWASP Top 10#Maturity Models

CISSP Domain 8: Secure Software Development Lifecycle (SSDLC) — Mindmap Review Study Guide

═══════════════════════════════════

PART 1: MERMAID MINDMAP

═══════════════════════════════════

mindmap
  root((Secure Software Development))
    ["Introduction and Basics"]
      ["Secure Software Development"]
      ["Non-Functional Requirements"]
      ["Bake In Security"]
    ["System and Software Life Cycles"]
      ["System Life Cycle SLC"]
      ["Software Development Life Cycle SDLC"]
      ["Plan and Management Approval"]
      ["Requirements Analysis"]
      ["Architecture and Design"]
      ["Development Phase"]
    ["Development Methodologies"]
      ["Waterfall"]
      ["Agile"]
      ["Sprints"]
      ["Scrum Master"]
      ["DevOps"]
      ["Continuous Integration and Delivery"]
      ["SecDevOps"]
      ["Segregation of Duties"]
    ["Testing and Evaluation"]
      ["Testing Phase"]
      ["Canary Deployments"]
      ["Evaluation Criteria"]
      ["Certification"]
      ["Penetration Testing"]
    ["Deployment and Operations"]
      ["Deployment Phase"]
      ["Accreditation"]
      ["Simplified SLC Model"]
      ["Operation Phase"]
      ["Disposal Phase"]
    ["Maturity Models"]
      ["Maturity Models"]
      ["Level 1 Initial or Ad-hoc"]
      ["Level 2 Repeatable"]
      ["Level 3 Defined"]
      ["Level 4 Managed"]
      ["Level 5 Optimized"]
      ["Software Development Maturity Model"]
      ["Generalized Common Model"]
    ["APIs and Obfuscation"]
      ["APIs"]
      ["REST"]
      ["SOAP"]
      ["Code Obfuscation"]
      ["Lexical Obfuscation"]
      ["Data Obfuscation"]
      ["Control Flow Obfuscation"]
    ["Acquiring Software"]
      ["Acquire Software"]
      ["Assess Vendors"]
      ["Contracts and SLAs"]
    ["Vulnerabilities and Weaknesses"]
      ["Buffer Overflows"]
      ["Parameter and Bounds Checking"]
      ["ASLR"]
      ["SQL Injection"]
      ["Cross-Site Scripting XSS"]
      ["Stored and Reflected XSS"]
      ["Cross-Site Request Forgery CSRF"]
      ["Covert Channels"]
      ["Storage and Timing Channels"]
      ["Backdoors and Trapdoors"]
      ["Memory and Object Reuse"]
      ["TOCTOU"]
      ["Citizen Developers"]
    ["Secure Programming Techniques"]
      ["Secure Programming"]
      ["Input Validation"]
      ["Syntactical Validation"]
      ["Semantic Validation"]
      ["Session Management"]
      ["Polyinstantation"]
    ["Maintaining Software"]
      ["Maintain Software"]
      ["SCM"]
      ["SOAR"]

═══════════════════════════════════

PART 2: TECHNICAL DEFINITIONS & CONCEPTS

═══════════════════════════════════

Introduction and Basics

Secure Software Development — Integrating security into the software development process right from the start and throughout the entire system life cycle to ensure applications provide confidentiality, integrity, and availability.

Non-Functional Requirements — Security requirements are typically labeled as non-functional requirements; when projects are over budget or behind schedule, management often cuts these first.

Bake In Security — The concept of involving security right from the start of a development project and throughout, as it is significantly more expensive to retrofit and add security later than to build it in from the beginning.

System and Software Life Cycles

System Life Cycle (SLC) — The overall life of a system from cradle to grave, encompassing the SDLC, and including planning, designing, development, testing, operations, maintenance, and eventual disposal.

Software Development Life Cycle (SDLC) — A subset of the SLC that focuses specifically on the development phases of a system.

Plan and Management Approval — The initial phase where project goals, objectives, and high-level cost estimates are defined, and management approval is obtained to proceed with requirements analysis.

Requirements Analysis — The phase where business requirements (user needs, data types to be collected/stored/processed, business uses) are gathered and validated to create a detailed set of requirements.

Architecture and Design — The phase where requirements are transformed into detailed system design documents, including architecture, security controls, and screen layouts.

Development Phase — The phase where coding begins and the system is written.

Development Methodologies

Waterfall — A development methodology where phases (plan, define requirements, build, test, release) are conducted sequentially; you cannot go backwards, and missed requirements must be included in the next cycle.

Agile — A development methodology created to address Waterfall’s rigidity, following the same phases but executing them in rapid, typically 2-week iterations to accommodate expected changes and fail fast.

Sprints — The short, typically 2-week iterations used in Agile to rapidly plan, define, build, test, and release.

Scrum Master — An Agile role acting as a facilitator and coach to the team; they have no real authority over the team and are not project managers, but facilitate communication to maximize productivity. ⚠️ EXAM TIP: Remember that a Scrum Master is a facilitator with no real authority, not a project manager.

DevOps — A methodology combining Development, Quality Assurance, and Operations to significantly shorten the development lifecycle (potentially to daily releases) using automated practices.

Continuous Integration and Continuous Delivery (CI/CD) — Automated practices included in DevOps to integrate and deliver code rapidly.

SecDevOps — Integrating security into DevOps by engaging developers and security strongly, using secure frameworks, automating security testing, and using traditional testing sparingly, since traditional Segregation of Duties between Dev and Ops is intentionally removed.

Segregation of Duties — A traditional security technique intentionally removed in DevOps to allow rapid iterations, requiring alternative security controls like automated testing.

Testing and Evaluation

Testing Phase — Testing throughout the system lifecycle to validate business requirements, review designs, and test units, interfaces, integration, and whole systems during development and operations.

Canary Deployments — A testing technique where new features are gradually released to a subset of users as an early warning system to see if anything breaks before a wider release.

Evaluation Criteria — Independent, objective evaluation and measurement of vendor products from a security perspective, involving two major steps: certification and accreditation.

Certification — The independent, comprehensive technical analysis of a solution or product. In the detailed SDLC, certification fits under the testing phase.

Penetration Testing — A traditional security testing technique that should be used sparingly in SecDevOps due to the rapid iterations of the lifecycle.

Deployment and Operations

Deployment Phase — The final stage of the SDLC where a system is moved into production.

Accreditation — The official management signoff of certification for a set period of time, allowing the product to be used in production. In the detailed SDLC, accreditation fits under the deployment phase. ⚠️ EXAM TIP: In the detailed SDLC, Certification fits under testing, while Accreditation fits under deployment.

Simplified SLC Model — A 5-step model (Initiation, Development/Acquisition, Implementation, Operation/Maintenance, Disposal). In this specific simplified model, both Certification and Accreditation fit into the Implementation step. ⚠️ EXAM TIP: Watch for slight variations in SDLC/SLC framework wording on the exam, but look for the general process of understanding requirements, designing controls, implementing, testing, deploying, operating, and retiring.

Operation Phase — The phase where the system is actively being used for business purposes.

Disposal Phase — The phase where a retired system is replaced; requires controls to migrate data/logic with integrity, retain old data as necessary, and defensibly destroy data if deleted (not just left on a hard drive).

Maturity Models

Maturity Models — Tools enabling the repeatable evaluation and benchmarking of processes using well-defined levels. Memorize the exact order of the levels:

  1. Initial or ad-hoc
  2. Repeatable
  3. Defined
  4. Managed
  5. Optimized

Level 1: Initial or Ad-hoc — The lowest maturity level, meaning there are no processes and it is barely controlled chaos.

Level 2: Repeatable — The second maturity level in the model.

Level 3: Defined — The third maturity level in the model.

Level 4: Managed — The fourth maturity level in the model.

Level 5: Optimized — The highest maturity level, representing an uneconomical and unobtainable goal for most organizations. ⚠️ EXAM TIP: Memorize the exact order of the 5 maturity levels as listed above.

Software Development Maturity Model — A maturity model specific to software development processes.

Generalized Common Model — A common maturity model used for various types of processes across an organization; highly likely to see exam questions about this specific model and its levels.

APIs and Obfuscation

APIs (Application Programming Interfaces) — A system of tools and resources allowing two applications (e.g., client and server) to talk across a network, enabling developers to make repetitive, complex processes highly reusable.

REST (Representational State Transfer) — The most commonly used API protocol; it is lightweight and fast.

SOAP (Simple Object Access Protocol) — An API protocol that is far more complex and heavyweight than REST, but provides a lot more capabilities.

Feature REST SOAP
Complexity Lightweight Heavyweight / Complex
Speed Fast Slower
Capabilities Standard Provides more capabilities
Usage Most commonly used Used when advanced features are needed

Code Obfuscation — The deliberate act of creating code that is difficult for humans to understand, used to make code more difficult to reverse engineer and conceal its purpose from unauthorized people.

Lexical Obfuscation — Modifies the look of the code (changing comments, removing debugging info, changing format); it is the easiest to do but the weakest form of obfuscation.

Data Obfuscation — Modifies the data structure (use of variables, arrays, etc.).

Control Flow Obfuscation — Modifies the flow of control through the code (reordering statements, methods, loops, and creating irrelevant conditional statements).

Acquiring Software

Acquire Software — When an organization contracts custom code or buys off-the-shelf products, they must conduct software assurance activities to ensure the code is free from vulnerabilities and functions as intended.

Assess Vendors — An important part of acquiring software to ensure the vendor uses secure software development techniques and sufficiently tests their code.

Contracts and SLAs — Tools used to define the controls a vendor must have in place and measure the effectiveness of these controls through metrics and reports.

Vulnerabilities and Weaknesses

Buffer Overflows — A condition where a program writes data to a buffer that is larger than the buffer, overrunning the boundary and overwriting adjacent memory locations; risk occurs when the overwritten data is read and executed.

Parameter and Bounds Checking — A secure coding technique to protect against buffer overflows by ensuring a chunk of data is never written to a buffer that is larger than the buffer.

ASLR (Address Space Layout Randomization) — Guards against buffer overflow attacks by randomizing the location where system executables are loaded into memory.

SQL Injection — An attack where malicious SQL code is sent to a web application and passed to the database, allowing the attacker to directly control the database.

Cross-Site Scripting (XSS) — An attack allowing an attacker to inject client-side scripts (typically JavaScript) into web pages viewed by other users, causing the malicious code to be executed by the victim’s browser.

Stored and Reflected XSS — The two major flavors of XSS; Stored is persistent, while Reflected is more common. All flavors target the victim’s browser.

Cross-Site Request Forgery (CSRF) — An attack targeting a web application by tricking a valid, authenticated user into sending commands to a web application that trusts the user. ⚠️ EXAM TIP: XSS targets the victim’s browser, while CSRF targets the web application.

Covert Channels — An unintentional communications path that has the opportunity to disclose confidential information.

Storage and Timing Channels — The two major types of covert channels; Storage is by far the most common.

Backdoors and Trapdoors — An intentional covert method of gaining access to a system and bypassing normal authentication and encryption controls, installed by an attacker or hidden in code.

Memory and Object Reuse — A vulnerability where memory deallocated from one application is reallocated to another, and the old data is still accessible; prevented by the OS zeroing out memory before reallocation.

TOCTOU (Time of Check Time of Use) — Also known as race conditions; occurs when a resource’s state changes between the time it is checked and the time it is used, invalidating the check and allowing an attacker to race in and change the resource.

Citizen Developers — Business operations employees empowered to create applications using accessible tools; the risk is that they are not properly trained developers and inevitably create insecure code.

Secure Programming Techniques

Secure Programming — Techniques used to address software vulnerabilities during development and operations.

Input Validation — Ensures only properly formed data is accepted and malformed or malicious input is rejected; a major defense against XSS and SQL injection. ⚠️ EXAM TIP: Input validation is the primary method for preventing XSS and SQL injection attacks.

Syntactical Validation — A type of input validation where the syntax or structure of the input is enforced.

Semantic Validation — A type of input validation where the correctness of values is enforced (e.g., ensuring a start date is before an end date).

Session Management — Carefully managing user sessions by ensuring only one session is allowed per username and terminating unused sessions via timeouts and screensavers to prevent session hijacking.

Polyinstantation — Allows different versions of the same information to exist at different classification levels; used to prevent unauthorized inference by creating different objects of the same name simultaneously.

Maintaining Software

Maintain Software — The phase and tools used to maintain software that is actively in operation.

SCM (Software Configuration Management) — Tools used to track and control changes to software.

SOAR (Security Orchestration, Automation, and Response) — Software used to automate security operations, including threat and vulnerability management and incident response.