The documentation for authentication and authorisation systems is accurate only until the next release. Availability targets for authorisation systems are commercial commitments, whatever the engineering team calls them. The programme uses small-group work so that each participant's treatment of this aspect of technology and systems delivery is examined, not just described. Participants develop a defensible line of reasoning for the choices they make about authentication and authorisation systems. Teams frequently over-invest in documenting the technology and systems delivery discipline and under-invest in testing it. Mature organisations treat authorisation systems as a standing capability rather than a project that finishes. The programme converts authentication and authorisation systems from an area of general awareness into a set of repeatable practices. The material serves both public bodies and commercial organisations dealing with authorisation systems. Participants leave with a plan for this aspect of technology and systems delivery sized to what their organisation can realistically absorb.
Expected Learning Outcomes
✓
Document authentication and authorisation systems to the level a new engineer could operate it.
✓
Secure the software supply chain and dependencies within authorisation systems.
✓
Control technical debt in authentication and authorisation systems deliberately rather than by neglect.
✓
Diagnose whether a problem in authorisation systems is one of design, resourcing or discipline.
✓
Design a training and briefing approach that sustains competence in authentication and authorisation systems.
✓
Document decisions about authorisation systems in a form that remains useful after the people change.
✓
Build incident response for authentication and authorisation systems with defined severity and escalation.
Who Should Attend
✓
Team leaders and supervisors who put authentication and authorisation systems into practice day to day.