Domain 1. Systems Security Engineering Foundations |
25% |
Candidates will utilize the fundamentals of systems security engineering, grasping concepts such as trust hierarchies and the interplay between systems and security processes. They'll execute these processes, pinpointing organizational security authority and incorporating design principles. Furthermore, they'll integrate security tasks into system development methodologies, validating security requirements and integrating software assurance methods. Technical management responsibilities encompass project planning, assessment, control, decision-making, risk and configuration management, and quality assurance. Candidates will also engage in the acquisition process, drafting security requirements, participating in selection, and contributing to Supply Chain Risk Management. Finally, they'll craft Trusted Systems and Networks (TSN) to ensure thorough security integration. |
Domain 3: Security Planning and Design |
30% |
Candidates will evaluate the organizational and operational landscape by gathering stakeholder requirements, recognizing limitations and assumptions, evaluating potential threats, and identifying the necessary safeguards for systems. They'll then devise Security Test Plans (STP) accordingly. Additionally, they'll implement system security principles by integrating resilience techniques, defense-in-depth strategies, fail-safe defaults, and principles like least privilege, all while understanding concepts like the economy of mechanism and Separation of Duties (SoD). They'll outline system requirements, establish the context of system security, document a baseline of security requirements, and analyze system security needs. Lastly, they'll craft system security architecture and design through functional analysis, maintaining a clear traceability, developing key design components, conducting trade-off evaluations, and assessing the effectiveness of protection measures.
|
Domain 5: Secure Operations, Change Management and Disposal |
17% |
Developing a secure operations strategy means being involved in safe day-to-day operations, handling changes, and getting rid of things safely. This includes making clear rules for people doing the work, talking to others about security regularly, and keeping an eye on things all the time. It's also about helping out if there's a security problem and planning how to keep things working smoothly. Being part of checking changes, understanding their effects, and making sure they're safe is important too. Updating documents that talk about risks, figuring out how to throw things away safely, and having a plan for getting rid of stuff securely are big parts of this. Lastly, making sure the steps for shutting down and throwing things away are followed, and checking that everything was done correctly, finish off the tasks in this area. |
Domain 2: Risk Management |
14% |
Applying security risk management principles encompasses mitigating risks to the system and efficiently handling operational risks. This involves setting up the risk context, recognizing system security weaknesses, thoroughly analyzing and assessing risks, and suggesting appropriate risk mitigation strategies while aligning with Enterprise Risk Management (ERM) practices. It also involves integrating risk management across the system's lifecycle, documenting risk assessments and decisions, understanding stakeholders' risk tolerance, identifying required fixes and system adjustments, and recommending suitable risk treatment approaches. |
Domain 4: Systems Implementation, Verification and Validation |
14% |
Implementing, integrating, and deploying security solutions involves performing activities related to system security implementation and integration, as well as system security deployment. Verifying and validating security solutions includes conducting system security verification and security validation to ensure that security controls meet stakeholder security requirements. |
Official Information |
|
https://www.isc2.org/Certifications/CISSP-Concentrations#tab-2-1 |