Training programme · Outcomes first
Build and review APIs with explicit trust boundaries.
Designed for developers, architects, testers and platform engineers.
| Programme detail | What to expect |
|---|---|
| Audience | Developers, architects, testers and platform engineers |
| Prerequisites | Working knowledge of HTTP, APIs and authentication |
| Learning outcomes | Threat-model a representative API; test access-control and workflow abuse; translate findings into engineering tests |
| Delivery format | Instructor-led workshop, guided labs and team action plan |
| Typical duration | 2–3 days; final schedule and fees quoted after needs assessment |
| Assessment | Scenario decisions, lab evidence or practical action plan as appropriate |
| Certificate | HAPSA participation/completion record; not represented as an accredited professional certification |
Included in final programme brief
Every delivery is confirmed in writing before scheduling.
- Named learning outcomes and module sequence.
- Lab/environment requirements and acceptable-use rules.
- Trainer and participant responsibilities.
- Accessibility and language requirements.
- Schedule, fees, cancellation terms and data handling.
Scope the right training programme.
Share the audience, current skill level, desired outcome, preferred dates and delivery location. We will return a clear programme brief.