IT, production and development
Secure development
Working securely where systems are run, machines are controlled and software is built. With diagrams, examples, a final test and a certificate of participation.
What you learn
- You know why security is planned at the start of development and not just before the release.
- You know the basics of the manufacturer obligations under the Cyber Resilience Act and which standards describe the practice.
- You can formulate security requirements so that they can be verified.
- You carry out a simple threat model for a feature: what are we building, what can go wrong, what do we do about it?
- You apply the four threat modeling questions to a feature of your own product.
- You choose third-party components deliberately and keep them up to date.
- You know what an SBOM is, how it is created and what it is needed for.
- You assess a reported vulnerability in a component by whether you are affected, not just by its CVSS score.
Show all 25 learning goals
- You know the minimum content the CRA requires for handling components and vulnerabilities.
- For the most recently shipped release of your product, you check how quickly you can find a specific component in it.
- You keep passwords, keys and tokens out of source code, the repository and logs.
- You know what to do if a secret does end up in a repository.
- You ship products with secure defaults: no default passwords, only necessary services open.
- You apply the principle of least privilege to services, accounts and pipelines.
- You check in your own repository whether a secret scanner runs and what it finds.
- You know the most common classes of flaws in applications and how to avoid them in code.
- In code review, you look specifically at security-relevant places.
- You know which automated checks belong in a pipeline and what each of them finds.
- You write tests that prove security requirements, including for the misuse case.
- You write misuse-case tests for a security requirement and check one of your own pull requests with the review questions.
- You protect the build and release from tampering and sign what you ship.
- You know how security updates reach customers securely and quickly.
- You know the role of a PSIRT and the process of coordinated vulnerability disclosure (CVD).
- You know the CRA reporting deadlines for actively exploited vulnerabilities and severe incidents.
- You check for your product how vulnerabilities can be reported from outside and who in the team receives them.
Course content
5 chapters with 15 lessons. One step per page, on your phone too, with review questions for practice.
-
Security requirements and threat modeling about 30 minutes
- Why security starts at the beginning
- Security requirements that can be verified
- Threat modeling in four questions
-
Dependencies, SBOM and vulnerabilities about 25 minutes
- Third-party code is your code
- The SBOM: the software bill of materials
- Assessing vulnerabilities in components
Exercise: Add a component to the SBOM
-
Secrets, configuration and secure defaults about 15 minutes
- Secrets do not belong in code
- Secure by default
- Least privilege and hardened configuration
-
Code review and security testing about 30 minutes
- The usual suspects
- Code review with an eye on security
- Automated checks and tests
-
Releases, updates and vulnerability disclosure about 30 minutes
- Securing build and release
- Delivering security updates
- PSIRT, coordinated disclosure and reporting obligations
Exercise: Reporting deadlines under the CRA
You do the exercises in a practice company of your own with sample data. This needs a portal account; employees with a learner login complete the course without the exercises.
Completion and proof
- Final testPass mark 80%, no time limit. The questions are drawn from a pool again on every attempt. You can retake the test.
- Certificate of participationPDF per person with number, verification code, chapters, legal bases, learning time and test date.
- Training recordWho has finished and who is overdue, for everyone on one page, as PDF or Excel.
- Access12 months from the course start; start within 12 months of activation. For the refresher you book the course again.
Sources
The laws and standards this course is based on.
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Art. 13(2), (3) and (8), Art. 32, Art. 71, Annex I Part I points 1 and 2
- IEC 62443-4-1:2018, Secure product development lifecycle requirements, Practices 1 to 3 (SM, SR, SD)
- NIST SP 800-218, Secure Software Development Framework (SSDF) 1.1, groups PO and PW
- OWASP Application Security Verification Standard (ASVS) 5.0.0
- Threat Modeling Manifesto
- OWASP Password Storage Cheat Sheet
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Art. 13(5) and (6), Annex I Part II points 1 to 3
- IEC 62443-4-1:2018, Secure product development lifecycle requirements, Practice 6 (DM) and SM-9 to SM-11
- NIST SP 800-218, Secure Software Development Framework (SSDF) 1.1, PW.4 and RV.1
- BSI TR-03183-2, Cyber resilience requirements for manufacturers and products, part 2: Software Bill of Materials (SBOM), version 2.1.0
Show all 26 sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Annex I Part I point 2(b), (c), (d), (e) and (j)
- IEC 62443-4-1:2018, Secure product development lifecycle requirements, Practice 3 (SD) and Practice 8 (SG)
- NIST SP 800-218, Secure Software Development Framework (SSDF) 1.1, PO.5, PS.1 and PW.9
- OWASP Application Security Verification Standard (ASVS) 5.0.0, V13 Configuration
- ETSI EN 303 645 V3.1.3, Cyber Security for Consumer Internet of Things: Baseline Requirements, Provision 5.1
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Annex I Part I point 2(a), (d) and (f), Annex I Part II point 3
- IEC 62443-4-1:2018, Secure product development lifecycle requirements, Practice 4 (SI) and Practice 5 (SVV)
- NIST SP 800-218, Secure Software Development Framework (SSDF) 1.1, PW.5, PW.7 and PW.8
- OWASP Top 10:2025
- OpenSSF Compiler Options Hardening Guide for C and C++
- CISA et al., The Case for Memory Safe Roadmaps (December 2023)
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Art. 13(8) and (9), Art. 14, Annex I Part I point 2(c), Annex I Part II points 2 and 4 to 8
- IEC 62443-4-1:2018, Secure product development lifecycle requirements, Practice 6 (DM), Practice 7 (SUM) and SM-6 to SM-8
- NIST SP 800-218, Secure Software Development Framework (SSDF) 1.1, PS.2, PS.3 and RV.1 to RV.3
- ISO/IEC 29147:2018, Vulnerability disclosure; ISO/IEC 30111:2019, Vulnerability handling processes
- FIRST, PSIRT Services Framework, Version 1.1