Home / Cybersecurity / Track 1A: Secure SDLC
Next batch January 2027. 15 seats.
Track 1A: Secure SDLC
For developers, tech leads and DevOps engineers who want security built into how their team ships software. You threat-model an app before it is built, design its login and permissions safely, stop secrets reaching Git and add security gates to a CI pipeline, using free and open-source tools throughout.
- Level
- 2, for working developers
- Hours
- 20 hours, 7 modules
- Format
- Live online
- Schedule
- 5-day intensive or 5 weekends
- Fee
- On enquiry, team rates available
What you’ll learn
- Map each stage of your team’s development process to the security activity that belongs there.
- Turn requirements into security requirements using the OWASP ASVS, and build a STRIDE threat model as code with Threagile.
- Design login, sessions and permissions safely with OAuth 2.0, OpenID Connect, JWTs and role-based access.
- Stop secrets reaching Git with pre-commit hooks and Gitleaks, and catch insecure code in the IDE.
- Add SAST and dependency scanning to CI as gates, write custom Semgrep rules, and generate an SBOM.
- Set up a triage process so findings reach the right developer with a fix, and start a security champions group.
- Use a local LLM to draft fixes, and check them before they merge.
Seven modules, one secure pipeline.
Each module ends in a hands-on project. In the capstone, you build a secure pipeline for a sample application.
| Module | Focus | Hands-on project | Hours |
|---|---|---|---|
| 0. Context | Where security fits in the development process | Map each SDLC phase to its pipeline stage | 1 |
| 1. Requirements and threats | ASVS requirements and threat modelling as code | Threat model with Threagile | 4 |
| 2. Secure design | Authentication, sessions and authorisation | Configure OIDC login and roles in Keycloak | 3 |
| 3. Secure coding | IDE checks and secrets prevention | Pre-commit hooks with Gitleaks | 3 |
| 4. Pipeline gates | SAST, SCA and SBOMs in CI | Custom Semgrep rules and a failing build | 5 |
| 5. Triage and champions | Routing findings to owners, runtime feedback | Findings workflow in DefectDojo | 2 |
| 6. AI-assisted fixes | Drafting and checking fixes with a local LLM | Fix a finding with Ollama, then rescan | 2 |
All tools are free or open source, so you can set up the same pipeline at work. Want to test applications and review code for flaws? See Track 1B: Application Security.
From the Module 3 and 4 labs
Real commands and real output from a practice repository and a deliberately vulnerable app.
-
Stop the secret
A pre-commit hook runs Gitleaks on every commit. A developer tries to commit a hard-coded token, and the commit is blocked before it ever reaches the repository.
$ git commit -m "Add API config" Finding: GITHUB_TOKEN = "REDACTED Secret: REDACTED RuleID: github-pat Entropy: 4.553056 File: config.py Line: 2 Fingerprint: config.py:github-pat:2 8:55AM INF 1 commits scanned. 8:55AM INF scan completed in 21.7ms 8:55AM WRN leaks found: 1 -
Fix it at the source
The token moves to an environment variable. The same hook runs again, finds nothing, and the commit goes through.
$ git commit -m "Read token from environment" 8:55AM INF 1 commits scanned. 8:55AM INF scan completed in 4.86ms 8:55AM INF no leaks found [master (root-commit) 1700e48] Read token from environment 1 file changed, 4 insertions(+) create mode 100644 config.py -
Write a rule for your code
Off-the-shelf rules miss patterns specific to your codebase. Learners write their own Semgrep rule for SQL built from f-strings, then run it.
rules: - id: sql-built-from-fstring languages: [python] severity: ERROR message: >- SQL query built with an f-string from user input. An attacker can change the query. Use a parameterised query: db.execute(sql, (value,)). metadata: cwe: "CWE-89: SQL Injection" owasp: "A03:2021 Injection" patterns: - pattern-either: - pattern: | $Q = f"..." ... $DB.execute($Q, ...) - pattern: $DB.execute(f"...", ...)$ semgrep scan --config sqli.yml login.py ┌────────────────┐ │ 1 Code Finding │ └────────────────┘ login.py ❯❯❱ sql-built-from-fstring ❰❰ Blocking ❱❱ SQL query built with an f-string from user input. An attacker can change the query. Use a parameterised query: db.execute(sql, (value,)). 2┆ query = f"SELECT email, role FROM users WHERE email = '{email}' AND password = '{password}'" 3┆ return db.execute(query).fetchone() -
Gate the build
The same scan runs in CI. A finding fails the build; the fixed code passes. Nothing insecure merges without someone deciding it should.
$ semgrep scan --config sqli.yml --error login.py; echo "exit $?" exit 1 # build fails $ semgrep scan --config sqli.yml --error login_fixed.py; echo "exit $?" exit 0 # build passes
Private batches for teams
We run Track 1A privately for engineering teams, scoped to your languages, your Git platform and your CI tool. Online or at your office.
How is this different from Track 1B?
Track 1A is about building security into how software is made: design, coding habits and pipeline gates. Track 1B is about finding flaws in software that already exists, by testing the running app and reviewing its code. Developers usually start with 1A; testers and aspiring AppSec engineers with 1B.
Do I need security experience?
No. We teach the security from the start. You do need to be a working developer. If you don’t write code yet, start with the Cybersecurity Foundation.
Will I get a certificate?
Yes, a Sophorion certificate of completion with an ID your employer can check on our verification page, plus your project write-ups.
Reserve a seat in the January batch.
Tell us your stack and we’ll confirm the schedule that suits you.
