Estimate what decentralised digital identity costs to run properly, and what is lost when it is not.
Building Secure Decentralised Digital Identity Platforms
Learn to design, measure and defend your organisation's approach to decentralised digital identity.
📍 Tunis🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Technical debt in decentralised digital identity is borrowed against future delivery capacity, at compound interest. Most outages involving this aspect of technology and systems delivery are triggered by a change somebody considered routine. Content is organised around the decisions practitioners actually face in the technology and systems delivery capability, not around theory headings. The programme suits teams tackling decentralised digital identity together as readily as individuals attending alone. The outcome is a practitioner who can hold a position on this aspect of technology and systems delivery and revise it on evidence. Improvement in the practice within technology and systems delivery stalls when it depends on one capable individual rather than a defined method. Practitioner evidence points the same way: decentralised digital identity improves fastest where responsibility for it is named and owned. Each session closes with a decision the participant must justify about the technology and systems delivery discipline in their own setting. The final session converts the week's work on the practice within technology and systems delivery into commitments with owners and dates.
Expected Learning Outcomes
Secure the software supply chain and dependencies within decentralised digital identity.
Reduce avoidable variation in how decentralised digital identity is carried out across teams.
Identify the failure points in decentralised digital identity most likely to cause loss, and control them first.
Test decentralised digital identity under realistic load before it meets real load.
Assess and manage third-party and cloud dependencies in decentralised digital identity.
Build incident response for decentralised digital identity with defined severity and escalation.
Who Should Attend
Technical staff being prepared for supervisory responsibility over decentralised digital identity.
Software engineers and technical leads building decentralised digital identity.
Quality and test engineers verifying decentralised digital identity.
Public sector officials applying decentralised digital identity within a regulated framework.
Infrastructure and platform engineers operating decentralised digital identity.
Solution architects designing decentralised digital identity.
Course Modules
Decentralised digital identity: requirements, targets and service levels
2 sessions · 8 pointsSession 1Least privilege in decentralised digital identity without blocking the work
- Test the failover for decentralised digital identity rather than assuming it works.
- Inventory third-party dependencies inside decentralised digital identity and their update status.
- Run a load test on decentralised digital identity at expected peak plus a margin.
- Review access rights on decentralised digital identity and remove what is no longer needed.
Session 2Retiring the legacy part of decentralised digital identity
- Agree what will be standardised in decentralised digital identity and what will not.
- Measure current load on decentralised digital identity and project it forward twelve months.
- Set delivery and reliability indicators for decentralised digital identity the team trusts.
- Identify the single points of failure in decentralised digital identity.
Decentralised digital identity: architecture and designing for failure
2 sessions · 8 pointsSession 1Who answers for decentralised digital identity, and to whom
- Configure alerting on decentralised digital identity that reflects what users experience.
- Identify the data already collected that bears on decentralised digital identity.
- Confirm data retention and deletion rules applied within decentralised digital identity.
- Define the trigger that would require decentralised digital identity to be redesigned.
Session 2Comparing decentralised digital identity with recognised practice
- Identify where judgement in decentralised digital identity is legitimate and where it is not.
- Identify single points of dependency in decentralised digital identity and reduce them.
- State the availability and recovery objectives for decentralised digital identity as numbers.
- Record the technical debt in decentralised digital identity and schedule repayment.
Decentralised digital identity: documentation, support and handover
2 sessions · 8 pointsSession 1Sizing capacity for decentralised digital identity on measured growth
- Remove steps in decentralised digital identity that add effort without adding assurance.
- Estimate the resource decentralised digital identity requires to run as designed.
- Assess the exit route from any cloud or vendor dependency in decentralised digital identity.
- Agree the indicators that will show whether decentralised digital identity is improving.
Session 2Documenting decentralised digital identity so someone else can operate it
- Set out how exceptions to decentralised digital identity are requested and approved.
- Agree the smallest change to decentralised digital identity that would be visibly useful.
- Define incident severity levels for decentralised digital identity and the response each triggers.
- Confirm every release of decentralised digital identity can be rolled back within a defined time.
Decentralised digital identity: change control and rollback
2 sessions · 8 pointsSession 1Running an incident on decentralised digital identity calmly
- Rehearse the briefing on decentralised digital identity that would follow an incident.
- Prepare the summary of decentralised digital identity that senior management will read.
- Arrange the handover of decentralised digital identity so capability survives staff changes.
- Document the runbook for decentralised digital identity to the level a new engineer could use.
Session 2What to measure in decentralised digital identity and what to ignore
- Check that records of decentralised digital identity answer the questions likely to be asked.
- Confirm that contractual obligations around decentralised digital identity are understood.
- Restore a backup of decentralised digital identity in a test environment and time it.
- Confirm that reporting on decentralised digital identity reaches the people who can act.
Choose the package that suits you
Silver Package
At least 3 people
USD1,250
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Gold Package
At least 3 people
USD1,850
- 5-night stay in a 5-star hotel
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Complete your registration
We will contact you within one business day to confirm.