Secure Software Architecture and Design

Secure Software Architecture and Design is Domain 3 of the CSSLP Common Body of Knowledge. It addresses how security requirements, identified earlier in the lifecycle, are translated into a structural blueprint that resists attack and limits damage when failures occur. The central idea is that security must be designed in, not bolted on, because architectural flaws are far more costly to fix after implementation than coding bugs. Key activities begin with threat modeling. Using methods such as STRIDE, PASTA, or attack trees, architects decompose the system into components, data flows, and trust boundaries, then enumerate threats and rank them with frameworks like DREAD or CVSS. This drives decisions about which controls are needed and where. The domain emphasizes core secure design principles: least privilege, separation of duties, defense in depth, fail secure, economy of mechanism, complete mediation, open design, least common mechanism, psychological acceptability, and leveraging existing trusted components. Architects also apply attack surface reduction, minimizing exposed interfaces, services, and privileges. Security architecture decisions cover authentication, authorization, session management, cryptography selection and key management, input validation strategies, logging and auditing, and secure error handling. The CSSLP also expects knowledge of architectures such as service-oriented, cloud, mobile, embedded, and distributed systems, each carrying distinct risks like multi-tenancy, API exposure, or physical tampering. Design review is another pillar. Security architects evaluate proposed designs against requirements, standards, and regulatory obligations, and perform architectural risk assessments to identify weaknesses before coding starts. Reusable, vetted components and secure design patterns are encouraged, while known anti-patterns are avoided. Finally, the domain includes documenting security decisions, selecting trustworthy technologies, and establishing non-functional security properties such as availability and resilience. The outcome is an architecture that enforces confidentiality, integrity, and availability, aligns with business risk tolerance, and provides a verifiable foundation for secure implementation and testing in later lifecycle phases. Secure Software Architecture and Design is Domain 3 of the CSSLP Common Body of Knowledge. It addresses how security requirements, identified earlier in the lifecycle, are translated into a structural blueprint that resists attack and limits damage when failures occur. The central idea is that secu…