Course Overview
The Official(ISC)Ā²Ā® Certified Secure Software Lifecycle Professional (CSSLP Ā®)training provides a comprehensive review of the knowledge required to incorporate security practices āauthentication, authorization and auditing ā into each phase of the Software Development Lifecycle (SDLC), from software design and implementation to testing and deployment.
Read More
This training course will help students review and refresh their knowledge and identify areas they need to study for the CSSLP exam Content aligns with and comprehensively covers the eight domains of the (ISC)Ā² CSSLP Common Body of Knowledge (CBKĀ®).Ā
We use courseware developed by (ISC)Ā² ācreator of the CSSLPCBK āto ensure your training is relevant and up-to-date.Ā TheĀ instructors are verified security experts who hold the CSSLPĀ and have completed intensive training to teach (ISC)Ā² content.Ā
Who is it for?
This training course is intended for professionals who have at least four years of cumulative, paid work experience as a software development lifecycle professional in one or more of the eight domains of the (ISC)2 CSSLP CBK. The course builds on and brings together the holistic view of the topics covered in the everyday environment of an information assurance professional.Ā
Read Less
Entry Requirements
This training course is intended for professionalsĀ whoĀ Have at least four years of cumulative, paid work experience as a software development lifecycle professional in one or more of the eight domainsĀ of the (ISC)2 CSSLP CBKĀ
The Exam
Recommended as preparation for the following exam:Ā
- (ISC)2 Certified Secure Software Lifecycle ProfessionalĀ
A candidate is required to have a minimum of four years cumulative paid full-time Software Development Lifecycle (SDLC) professional work experience in one or more of the eight domains of the (ISC)2 CSSLP CBK, or three years of cumulative paid full-time SDLC professional work experience in one or more of the eight domains of the CSSLP CBK with a four –Ā year degree leading to a Baccalaureate, or regional equivalent in Computer Science, Information Technology (IT) or related fields.Ā
A candidate that doesnāt have the required experience to become a CSSLP may become an Associate of (ISC)Ā² by successfully passing the CSSLP examination. The Associate of (ISC )Ā² will then have 5 years to earn the 4 years required experience.Ā
The CSSLP exam takes four hours to complete and consists of 175 multiple choice questions. CandidatesĀ need to achieve a minimum of 700 out of 1000 points to pass the exam and gain the certification.Ā
Please note an exam voucher is included as part of this courseāÆĀ
Course Objectives
After completing thisĀ course,Ā you should be able to:Ā
- Understand the core concepts of software security and the foundational principles that drive construction of resilient software.Ā
- Recognize the importance of security requirements and understand the techniques for elicitation and specification of software security requirements.Ā
- Recognize privacy requirements and their impact on the selection of safeguards and countermeasures.Ā
- Understand threatĀ modelling, attack surface evaluation, and architectural risk assessment.Ā
- Recognize secure design principles and patterns.Ā
- Understand secure coding practices, common application vulnerabilities and their mitigation strategies.Ā
- Understand various code analysis techniques using automated and manual techniques.Ā
- Recognize risks of third-partyĀ software componentsĀ and libraries, malicious code and mitigation strategies.Ā
- Describe security testing strategy and techniques and identify functional and non-functional testing methods.Ā
- Describe defect tracking and risk scoring methods.Ā
- Identify secure software methodologies, standards and frameworks.Ā
- Understand Governance, Risk, and Compliance and recognize regulations and compliance requirements.Ā
- Describe risks during deployment and understand security relevant issues during the operations and maintenance phase of the lifecycle.Ā
- Understand vulnerability management, security monitoring, incident response, and root cause analysis.Ā
- Recognize software supply chain risks and attacks.Ā
Syllabus – Key points
Domain 1: Secure Software ConceptsĀ
- Core ConceptsĀ
- Security Design PrinciplesĀ
Domain 2: Secure Software RequirementsĀ
- Define Software Security RequirementsĀ
- Identity and Analyze Compliance RequirementsĀ
- Identify and Analyze Data Classification RequirementsĀ
- Identify and Analyze Privacy RequirementsĀ
- Develop Misuse and Abuse CasesĀ
- Develop Security Requirement Traceability Matrix (STRM)Ā
- Ensure Security Requirements Flow Down to Suppliers/ProvidersĀ
Domain 3: Secure Software Architecture and DesignĀ
- Define the Security ArchitectureĀ
- Performing Secure Interface DesignĀ
- Performing Architectural Risk AssessmentĀ
- Model (Non-Functional) Security Properties and ConstraintsĀ
- Model and Classify DataĀ
- Evaluate and Select Reusable Secure DesignĀ
- Perform Security Architecture and Design ReviewĀ
- Define Secure Operational Architecture (e.g., deployment topology, operational interfaces)Ā
- Use Secure Architecture and Design Principles, Patterns, and ToolsĀ
Domain 4: Secure Software ImplementationĀ
- Adhere to Relevant Secure Coding Practices (e.g., standards, guidelines and regulations)Ā
- Analyze Code for Security RisksĀ
- Implement Security Controls (e.g., watchdogs, File Integrity Monitoring (FIM), anti-malware)Ā
- Address Security Risks (e.g.,Ā remediation, mitigation, transfer, accept)Ā
- Securely Reuse Third-Party Code or Libraries (e.g., Software Composition Analysis (SCA))Ā
- Securely Integrate ComponentsĀ
- Apply Security During the Build ProcessĀ
Domain 5: Secure Software TestingĀ
- Develop Security Test CasesĀ
- Develop Security Testing Strategy and PlanĀ
- Verify and Validate Documentation (e.g., installation and setup instructions, error messages, user guides, release notes)Ā
- Identify Undocumented FunctionalityĀ
- Analyze Security Implications of Test Results (e.g., impact on product management, prioritization, break build criteria)Ā
- Classify and Track Security ErrorsĀ
- Secure Test DataĀ
- Perform Verification and Validation TestingĀ
Domain 6: Secure Lifecycle ManagementĀ
- Secure Configuration and Version Control (e.g., hardware, software, documentation, interfaces, patching)Ā
- Define Strategy and RoadmapĀ
- Manage Security Within a Software Development MethodologyĀ
- Identify Security Standards and FrameworksĀ
- Define and Develop Security DocumentationĀ
- Develop Security Metrics (e.g., defects per line of code, criticality level, average remediation time, complexityĀ
- Decommission SoftwareĀ
- Report Security Status (e.g., reports, dashboards, feedback loops)Ā
- Incorporate Integrated Risk Management (IRM)Ā
- Promote Security Culture in Software DevelopmentĀ
- Implement Continuous Improvement (e.g., retrospective, lessons learned)Ā
Domain 7: Software Deployment, Operations and MaintenanceĀ
- Perform Operational Risk AnalysisĀ
- Release Software SecurelyĀ
- Securely Store and Manage Security DataĀ
- Ensure Secure InstallationĀ
- Perform Post-Deployment Security TestingĀ
- Obtain Security Approval to Operate (e.g., risk acceptance, sign-off at appropriate level)Ā
- Perform Information Security Continuous Monitoring (ISCM)Ā
- Support Incident ResponseĀ
- Perform Patch Management (e.g.,Ā secure release, testing)Ā
- Perform Vulnerability Management (e.g., scanning, tracking, triaging)Ā
- Runtime Protection (e.g., Runtime Application Self-Protection (RASP), Web Application Firewall (WAF), Address Space Layout Randomization (ASLR))Ā
- Support Continuity of OperationsĀ
- Integrate Service Level Objectives (SLO) and Service Level Agreements (SLA) (e.g., maintenance, performance, availability, qualified personnel)Ā
Domain 8: Supply ChainĀ
- Implement Software Supply Chain Risk ManagementĀ
- Analyze Security of Third-Party SoftwareĀ
- Verify Pedigree and ProvenanceĀ
- Ensure Supplier Security Requirements in the Acquisition ProcessĀ
- Support contractual requirements (e.g., Intellectual Property (IP) ownership, code escrow, liability, warranty, End-User License Agreement (EULA), Service Level Agreements (SLA))Ā
Reviews
There are no reviews yet.