Course Bulletin No. 41, winter term 2026Security training and awarenessEnrolment +1-555-0187

Programme AC-26-063 · Labs · Software company
Public copy, names removed

Secure code for a payments team

Instructor leaning in beside a learner at a laptop with a dark terminal in a training lab
Headline result
9
Issues fixed in the next sprint
Programme sheet AC-26-063
Sample

Sector

Software company, name withheld

Scope

18 developers

Programme

WL-320 Secure code

Duration

2 days

Result

9 issues fixed in the next sprint

§2 Summary

Break the sample app. Then read your own.

Written for the client's leadership. The client's name and staff names are removed from this copy.

§2.1 What they asked

A software company's payments team shipped fast and reviewed fast. Security review meant a checklist at the end, and the checklist was always green.

§2.2 What we ran

Lena Sorensen ran WL-320 Secure code at their office for two days, with Owen Hartley and Nadia Brennan on the other two benches: eight seats or fewer to each instructor. Day one, the team broke a sample app. Day two, they fixed it in review.

§2.3 What changed

In the sprint after the course the team found nine issues in their own code with the same review habits, and fixed them before release.

§3 Schedule
AC-26-063, sample programme

Two days and a sprint, step by step.

From the programme record. 18 developers on three benches.

When

Step

By

Outcome

Week 1

Stack and review process read

Lena Sorensen

Done

Day 1

Break the sample app: inputs, sessions, secrets

Lena Sorensen

18 seats

Day 2

Fix it in review, pairs swap fixes

Lena Sorensen

18 of 18

Sprint 1

Same review habits on the team's own code

Client

9 found

After the programme

Sprint 1

All nine fixed before release

Client

Closed

Sprint 2

Review checklist rewritten by the team

Client

Done

§4 What we measured

Nine issues. Three shown in full.

Issue

Priority

Status

Card token written to a debug log

High

Fixed

Session kept after password change

High

Fixed

API key in a test config

Medium

Fixed

Six more are kept in the client's copy. All nine were fixed in the next sprint.
Two analysts working through an attack graph on dark monitors with a test laptop on the desk
In numbers
Sample

Developers

18

Instructors

3

Issues fixed

9

§5 Client note
AC-26-063, sample programme

The checklist was always green. Two days later the team could tell me why it should not have been.

Engineering manager, software company (fictional client)
What changed

A second reader on every payments change

No secrets in test configs

WL-320 for every new developer

§6 More programmes
End of AC-26-063