Designing Secure Communication Protocols for Internet of Things Devices

A structured, applied course in IoT communication security — designed to be used the week you return.

📍 Tunis🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points

Course Overview

Technical debt in IoT communication security is borrowed against future delivery capacity, at compound interest. Most outages involving this strand of technology and systems delivery are triggered by a change somebody considered routine. The programme works equally well for those formalising the technology and systems delivery capability for the first time and those improving an existing approach. Comparative studies of IoT communication security across sectors find the same handful of failure points recurring. Exercises escalate in difficulty, ending with the ambiguous situations that make this area of technology and systems delivery hard in practice. The course gives participants a defensible structure for the technology and systems delivery discipline and the judgement to adapt it. Progress on IoT communication security is usually lost in the gap between approval and execution. Participants gain a clear basis for measuring what this aspect of technology and systems delivery has actually achieved. The final session converts the week's work on the technology and systems delivery discipline into commitments with owners and dates.

Expected Learning Outcomes

01

Test IoT communication security under realistic load before it meets real load.

02

Prepare a short, evidence-based briefing on IoT communication security for senior management.

03

Plan capacity for IoT communication security against measured growth rather than optimism.

04

Document IoT communication security to the level a new engineer could operate it.

05

Design the architecture of IoT communication security around its failure modes, not only its happy path.

06

Review contracts and agreements for the obligations they create around IoT communication security.

07

Apply a repeatable review cycle to IoT communication security and act on what it produces.

Who Should Attend

01

IT governance and audit staff reviewing IoT communication security.

02

Information security specialists protecting IoT communication security.

03

Operations staff who encounter the consequences of IoT communication security directly.

04

Infrastructure and platform engineers operating IoT communication security.

05

Software engineers and technical leads building IoT communication security.

06

Managers with direct responsibility for IoT communication security within the technical platform.

Course Modules

01

IoT communication security: change control and rollback

2 sessions · 8 points

Session 1Making releases of IoT communication security routine instead of risky

  • Define incident severity levels for IoT communication security and the response each triggers.
  • Build the internal briefing that explains IoT communication security to those affected.
  • Set out the decisions in IoT communication security that require sign-off and by whom.
  • Decide what will be stopped to create capacity for IoT communication security.

Session 2The hard cases in IoT communication security and how to reason about them

  • Assign responsibility for keeping documentation of IoT communication security current.
  • Record what was learned when IoT communication security did not go as planned.
  • Establish who is informed, consulted and accountable in IoT communication security.
  • Inventory third-party dependencies inside IoT communication security and their update status.
02

IoT communication security: architecture and designing for failure

2 sessions · 8 points

Session 1The paperwork for IoT communication security that is actually needed

  • Record the technical debt in IoT communication security and schedule repayment.
  • Draft the minimum viable technical standard for IoT communication security.
  • Identify the single points of failure in IoT communication security.
  • Confirm data retention and deletion rules applied within IoT communication security.

Session 2Who answers for IoT communication security, and to whom

  • Review access rights on IoT communication security and remove what is no longer needed.
  • Restore a backup of IoT communication security in a test environment and time it.
  • Test the failover for IoT communication security rather than assuming it works.
  • Confirm every release of IoT communication security can be rolled back within a defined time.
03

IoT communication security: capacity, performance and load

2 sessions · 8 points

Session 1Running an incident on IoT communication security calmly

  • Collect evidence on the present handling of IoT communication security before proposing changes.
  • Define the trigger that would require IoT communication security to be redesigned.
  • Assess the exit route from any cloud or vendor dependency in IoT communication security.
  • Confirm the support model and escalation path for IoT communication security.

Session 2Designing IoT communication security around how it will fail

  • Verify six months later that changes to IoT communication security have held.
  • Apply change control to IoT communication security including emergency changes.
  • Run a load test on IoT communication security at expected peak plus a margin.
  • Configure alerting on IoT communication security that reflects what users experience.
04

IoT communication security: build, pipeline and release discipline

2 sessions · 8 points

Session 1Sizing capacity for IoT communication security on measured growth

  • Compare the cost of IoT communication security with the cost of its absence.
  • Document the runbook for IoT communication security to the level a new engineer could use.
  • Write down the assumptions underpinning the approach to IoT communication security.
  • Review whether IoT communication security is aligned with the objectives of the technical platform.

Session 2Proving the backup of IoT communication security by restoring it

  • Measure current load on IoT communication security and project it forward twelve months.
  • Confirm that reporting on IoT communication security reaches the people who can act.
  • Establish what evidence demonstrates IoT communication security is under control.
  • Anticipate the objections IoT communication security will raise and prepare the answers.

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.