PDF Version Demo
Benefit in Obtaining the Exam Certification
- Company decision makers see value in certification
- Certified Secure Software Lifecycle Professional (CSSLP) report high job satisfaction
Our CSSLP exam dumps will include those topics:
- Secure Software Testing: 14%
- Supply Chain and Software Acquisition: 8%
- Secure Software Requirements: 14%
- Secure Software Implementation/Programming: 16%
- Secure Lifecycle Management: 10%
- Secure Software Concepts: 13%
- Secure Software Design: 16%
- Software Deployment, Operations, and Maintenance: 9%
For more info visit: CSSLP Exam Reference
ISC2 CSSLP Exam Syllabus Topics:
| Topic | Details |
|---|---|
Secure Software Concepts - 10% | |
| Core Concepts | - Confidentiality (e.g., covert, overt, encryption) - Integrity (e.g., hashing, digital signatures, code signing, reliability, modifications, authenticity) - Availability (e.g., redundancy, replication, clustering, scalability, resiliency) - Authentication (e.g., multifactor authentication (MFA), identity & access management (IAM), single sign-on (SSO), federated identity) - Authorization (e.g., access controls, permissions, entitlements) - Accountability (e.g., auditing, logging) - Nonrepudiation (e.g., digital signatures, block chain) |
| Security Design Principles | - Least privilege (e.g., access control, need-to-know, run-time privileges) - Separation of duties (e.g., multi-party control, secret sharing and split knowledge) - Defense in depth (e.g., layered controls, input validation, security zones) - Resiliency (e.g., fail safe, fail secure, no Single Point of Failure (SPOF)) - Economy of mechanism (e.g., Single Sign-On (SSO), password vaults, resource) - Complete mediation (e.g., cookie management, session management, caching of credentials) - Open design (e.g., Kerckhoffs's principle) - Least common mechanism (e.g., compartmentalization/isolation, white-listing) - Psychological acceptability (e.g., password complexity, screen layouts, Completely Automated Public Turing test to tell Computers and Humans Apart (CAPTCHA), biometrics) - Component reuse (e.g., common controls, libraries) - Diversity of defense (e.g., geographical diversity, technical diversity, distributed systems) |
Secure Software Requirements - 14% | |
| Define Software Security Requirements | - Functional (e.g., business requirements, use cases, stories) - Non-functional (e.g., operational, deployment, systemic qualities) |
| Identify and Analyze Compliance Requirements | |
| Identify and Analyze Data Classification Requirements | - Data ownership (e.g., data owner, data custodian) - Labeling (e.g., sensitivity, impact) - Types of data (e.g., structured, unstructured data) - Data life-cycle (e.g., generation, retention, disposal) |
| Identify and Analyze Privacy Requirements | - Data anonymization - User consent - Disposition (e.g., right to be forgotten) - Data retention - Cross borders (e.g., data residency, jurisdiction, multi-national data processing boundaries) |
| Develop Misuse and Abuse Cases | |
| Develop Security Requirement Traceability Matrix (STRM) | |
| Ensure Security Requirements Flow Down to Suppliers/Providers | |
Secure Software Architecture and Design - 14% | |
| Perform Threat Modeling | - Understand common threats (e.g., Advance Persistent Threat (APT), insider threat, common malware, third-party/supplier) - Attack surface evaluation - Threat intelligence (e.g., Identify credible relevant threats) |
| Define the Security Architecture | - Security control identification and prioritization - Distributed computing (e.g., client server, peer-to-peer (P2P), message queuing) - Service-oriented architecture (SOA) (e.g., Enterprise Service Bus (ESB), web services) - Rich internet applications (e.g., client-side exploits or threats, remote code execution, constant connectivity) - Pervasive/ubiquitous computing (e.g., Internet of Things (IoT), wireless, location-based, Radio-Frequency Identification (RFID), near field communication, sensor networks) - Embedded (e.g., secure update, Field-Programmable Gate Array (FPGA) security features, microcontroller security) - Cloud architectures (e.g., Software as a Service (SaaS), Platform as a Service (PaaS), Infrastructure as a Service (IaaS)) - Mobile applications (e.g., implicit data collection privacy) - Hardware platform concerns (e.g., side-channel mitigation, speculative execution mitigation, embedded Hardware Security Modules (HSM)) - Cognitive computing (e.g., Machine Learning (ML), Artificial Intelligence (AI)) - Control systems (e.g., industrial, medical, facility-related, automotive) |
| Performing Secure Interface Design | - Security management interfaces, Out-of-Band (OOB) management, log interfaces - Upstream/downstream dependencies (e.g., key and data sharing between apps) - Protocol design choices (e.g., Application Programming Interface (APIs), weaknesses, state, models) |
| Performing Architectural Risk Assessment | |
| Model (Non-Functional) Security Properties and Constraints | |
| Model and Classify Data | |
| Evaluate and Select Reusable Secure Design | - Credential management (e.g., X.509 and Single Sign-On (SSO)) - Flow control (e.g., proxies, firewalls, protocols, queuing) - Data loss prevention (DLP) - Virtualization (e.g., software defined infrastructure, hypervisor, containers) - Trusted computing (e.g., Trusted Platform Module (TPM), Trusted Computing Base (TCB)) - Database security (e.g., encryption, triggers, views, privilege management) - Programming language environment (e.g., Common Language Runtime (CLR), Java Virtual Machine (JVM)) - Operating System (OS) controls and services - Secure backup and restoration planning - Secure data retention, retrieval, and destruction |
| 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 | |
Secure Software Implementation - 14% | |
| Adhere to Relevant Secure Coding Practices (e.g., standards, guidelines and regulations) | - Declarative versus imperative (programmatic) security - Concurrency (e.g., thread safety, database concurrency controls) - Output sanitization (e.g., encoding, obfuscation) - Error and exception handling - Input validation - Secure logging & auditing - Session management - Trusted/Untrusted Application Programming Interface (APIs), and libraries - Type safety - Resource management (e.g., compute, storage, network, memory management) - Secure configuration management (e.g., parameter, default options, credentials) - Tokenizing - Isolation (e.g., sandboxing, virtualization, containers, Separation Kernel Protection Profiles (SKPP)) - Cryptography (e.g., payload, field level, transport, storage, agility, encryption, algorithm selection) - Access control (e.g., trust zones, function permissions, Role Based Access Control (RBAC)) - Processor microarchitecture security extensions (e.g., Software Guard Extensions (SGX), Advanced Micro Devices (AMD) Secure Memory Encryption(SME)/Secure Encrypted Virtualization(SEV), ARM TrustZone) |
| Analyze Code for Security Risks | - Secure code reuse - Vulnerability databases/lists (e.g., Open Web Application Security Project (OWASP) Top 10, Common Weakness Enumeration (CWE)) - Static Application Security Testing (SAST) (e.g., automated code coverage, linting) - Dynamic Application Security Testing (DAST) - Manual code review (e.g., individual, peer) - Look for malicious code (e.g., backdoors, logic bombs, high entropy) - Interactive Application Security Testing (IAST) |
| 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 | - Systems-of-systems integration (e.g., trust contracts, security testing and analysis) |
| Apply Security During the Build Process | - Anti-tampering techniques (e.g., code signing, obfuscation) - Compiler switches - Address compiler warnings |
Secure Software Testing - 14% | |
| Develop Security Test Cases | - Attack surface validation - Penetration tests - Fuzzing (e.g., generated, mutated) - Scanning (e.g., vulnerability, content, privacy) - Simulation (e.g., simulating production environment and production data, synthetic workloads) - Failure (e.g., fault injection, stress testing, break testing) - Cryptographic validation (e.g., Pseudo-Random Number Generator (PRNG), entropy) - Regression tests - Integration tests - Continuous (e.g., synthetic transactions) |
| Develop Security Testing Strategy and Plan | - Functional security testing (e.g., logic) - Nonfunctional security testing (e.g., reliability, performance, scalability) - Testing techniques (e.g., white box and black box) - Environment (e.g., interoperability, test harness) - Standards (e.g., International Organization for Standardization (ISO), Open Source Security Testing Methodology Manual (OSSTMM), Software Engineering Institute (SEI)) - Crowd sourcing (e.g., bug bounty) |
| 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 | - Bug tracking (e.g., defects, errors and vulnerabilities) - Risk Scoring (e.g., Common Vulnerability Scoring System (CVSS)) |
| Secure Test Data | - Generate test data (e.g., referential integrity, statistical quality, production representative) - Reuse of production data (e.g., obfuscation, sanitization, anonymization, tokenization, data aggregation mitigation) |
| Perform Verification and Validation Testing | |
Secure Software Lifecycle Management - 11% | |
| Secure Configuration and Version Control (e.g., hardware, software, documentation, interfaces, patching) | |
| Define Strategy and Roadmap | |
| Manage Security Within a Software Development Methodology | - Security in adaptive methodologies (e.g., Agile methodologies) - Security in predictive methodologies (e.g., Waterfall) |
| 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 | - End of life policies (e.g., credential removal, configuration removal, license cancellation, archiving) - Data disposition (e.g., retention, destruction, dependencies) |
| Report Security Status (e.g., reports, dashboards, feedback loops) | |
| Incorporate Integrated Risk Management (IRM) | - Regulations and compliance - Legal (e.g., intellectual property, breach notification) - Standards and guidelines (e.g., International Organization for Standardization (ISO), Payment Card Industry (PCI), National Institute of Standards and Technology (NIST), OWASP, Software Assurance Forum for Excellence in Code (SAFECode), Software Assurance Maturity Model (SAMM), Building Security In Maturity Model (BSIMM)) - Risk management (e.g., mitigate, accept, transfer, avoid) - Terminology (e.g., threats, vulnerability, residual risk, controls, probability, impact) - Technical risk vs. business risk |
| Promote Security Culture in Software Development | - Security champions - Security education and guidance |
| Implement Continuous Improvement (e.g., retrospective, lessons learned) | |
Secure Software Deployment, Operations, Maintenance - 12% | |
| Perform Operational Risk Analysis | - Deployment environment - Personnel training (e.g., administrators vs. users) - Safety criticality - System integration |
| Release Software Securely | - Secure Continuous Integration and Continuous Delivery (CI/CD) pipeline - Secure software tool chain - Build artifact verification (e.g., code signing, checksums, hashes) |
| Securely Store and Manage Security Data | - Credentials - Secrets - Keys/certificates - Configurations |
| Ensure Secure Installation | - Bootstrapping (e.g., key generation, access, management) - Least privilege - Environment hardening - Secure activation (e.g., credentials, white listing, device configuration, network configuration, licensing) - Security policy implementation - Secrets injection (e.g., certificate, Open Authorization (OAUTH) tokens, Secure Shell (SSH) keys) |
| 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) | - Collect and analyze security observable data (e.g., logs, events, telemetry, and trace data) - Threat intel - Intrusion detection/response - Secure configuration - Regulation changes |
| Support Incident Response | - Root cause analysis - Incident triage - Forensics |
| 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 | - Backup, archiving, retention - Disaster recovery (DR) - Resiliency (e.g., operational redundancy, erasure code, survivability) |
| Integrate Service Level Objectives (SLO) and Service Level Agreements (SLA) (e.g., maintenance, performance, availability, qualified personnel) | |
Secure Software Supply Chain - 11% | |
| Implement Software Supply Chain Risk Management | - Identify - Assess - Respond - Monitor |
| Analyze Security of Third-Party Software | |
| Verify Pedigree and Provenance | - Secure transfer (e.g., interdiction mitigation) - System sharing/interconnections - Code repository security - Build environment security - Cryptographically-hashed, digitally-signed components - Right to audit |
| Ensure Supplier Security Requirements in the Acquisition Process | - Audit of security policy compliance (e.g., secure software development practices) - Vulnerability/incident notification, response, coordination, and reporting - Maintenance and support structure (e.g., community versus commercial, licensing) - Security track record |
| Support contractual requirements (e.g., Intellectual Property (IP) ownership, code escrow, liability, warranty, End-User License Agreement (EULA), Service Level Agreements (SLA)) | |
How much CSSLP Exam Cost
The price of the exam is 549 USD.
Easy to understand and operate
Once you buy our CSSLP training materials, you will be surprised by the perfection of our products. First of all, the CSSLP exam dumps have been summarized by our professional experts. The structure of knowledge is integrated and clear. All the key points have been marked clearly and the difficult knowledge has detailed explanations. You will find the ISC CSSLP study guide materials are easy for you to understand. What's more, the PC test engine of CSSLP best questions has a clear layout. All the settings are easy to handle. You will enjoy the whole process of doing exercises. After you finish set of CSSLP certification training, you can check the right answers and the system will grade automatically. This can help you to have a clear cognition of your learning outcomes.
A year free updating for our CSSLP training materials
Do you want to enjoy the best service in the world? Our CSSLP exam dumps materials completely satisfy your demands. Our company has never stand still and refuse to make progress. Our engineers are working hard to perfect the CSSLP study guide materials. Once the latest version has been developed successfully, our online workers will quickly send you an email including the newest version of ISC CSSLP training materials. So you can check your email boxes regularly in case you ignore our emails. The best learning materials are waiting for you to experience. Many customers have become our regular guests for our specialty. In addition, we only offer you one year free updating for our CSSLP exam dumps materials. If you are content with our CSSLP study guide, welcome to our online shop.
After purchase, Instant Download: Upon successful payment, Our systems will automatically send the product you have purchased to your mailbox by email. (If not received within 12 hours, please contact us. Note: don't forget to check your spam.)
In modern society, there are many ways to become a successful person. Usually, it will take us a lot of time to find the right direction of life. As old saying goes, knowledge will change your life. Our CSSLP training materials will help you experience the joys of learning. At the same time, you will be full of energy and strong wills after you buy our CSSLP exam dumps. You can fully realize your potential and find out what you really love. When you pass the ISC CSSLP exam and enter an enormous company, you can completely display your talent and become social elites.
Free trials before buying our CSSLP study guide materials
If you are the first time to know about our CSSLP training materials, so you are unsure the quality about our products. That is just a piece of cake. Our company offers free demo of CSSLP exam dumps for you to have a try. If you are willing to trust us and know more about our products, you can enter our company's website and find out which product you want to try. The webpage will display the place where you can download the free demo of CSSLP study guide. The free trials just include the sectional contents about the exam. If you find the free demo is wonderful and helpful for you to pass the ISC CSSLP exam. You can buy our products at once. We are waiting for your coming.
Heather 
Christine 
Zebulon 
Beryl 
Wright 
Candice 
Jacqueline 
Lucien 
Basil 
Barret 
Beacher 
Arno 
Horace 
Pamela 
Lillian 
Mabel 
Nelly 
