← All checklists

Checklist 07 of 10 · October 2026

Edge AI security checklist

Five checks before your model ships to hardware you do not physically guard

On 17 Sep 2026 a group reported unbolting one licence-plate-reader camera and finding the encryption key next to the recorded media: about 1.6 million images and 27,321 clips from roughly 21 days, from a device whose vendor had said footage is only briefly stored. A device that scores frames locally must decrypt them locally, so "encrypted at rest" protects a dead disk, not a working device.

The checks

Everything starts ticked. Untick what you will not do; the choice is saved on this device only, and Print keeps only what you kept.

What happened. The claim was "briefly stored"; the device held about 21 days of media, and nobody knew because nobody had taken a unit down and counted. Retention on the edge is a claim until someone counts, and the count is what a thief gets.

The check.

  • Once a quarter, image one deployed device per hardware revision and list every file with its age.
  • Put the counted retention in the questionnaire; set the on-device window in minutes and alert past it.

Source: News report with the extracted counts, 17 Sep 2026

What happened. The stolen camera's media partition carried the key that unlocked the media, so on-device encryption changed nothing for whoever held it. The consumer IoT baseline standard says sensitive security parameters shall be stored securely and a per-device identity shall resist physical, electrical and software tampering.

The check.

  • Per-device keys in a secure element or TEE, generated on the device, never on flash; no shared fleet key.
  • The cloud accepts a device only after attestation; "encrypted at rest" is true only when the device is off.

Source: ETSI EN 303 645 V2.1.1, provisions 5.4-1 and 5.4-2, June 2020; News report with the partition layout, 17 Sep 2026

What happened. The model needed each frame for milliseconds; the device kept it for weeks. About 50,200 vehicles and 11 people were in the extracted media because raw frames stayed after the inference that used them. The NIST core baseline makes data protection a capability of the device itself.

The check.

  • Write the inference output (class, count, score) and at most a thumbnail; drop the frame after scoring.
  • Anything waiting for upload is encrypted with a key the device does not hold; delete on acknowledgement.

Source: NISTIR 8259A, IoT Device Cybersecurity Capability Core Baseline, May 2020

What happened. A device nobody guards can be opened, re-flashed and put back, so the model and the firmware must prove where they came from. The baseline standard asks for secure boot and updatable software; UK law for consumer connectable products (in force 29 April 2024) requires a published minimum security-update period.

The check.

  • Secure boot with anti-rollback; the model is signed with a key that never lives on the device, and an unsigned model does not load.
  • Signed over-the-air updates with a tested rollback; publish the support period per hardware revision.

Source: ETSI EN 303 645 V2.1.1, provisions 5.3 and 5.7-1, June 2020; UK product security regime for connectable products, in force 29 April 2024

What happened. One unit gave up 21 days of media; with a shared key it would have been the fleet. The NIST baseline asks that each device be uniquely identifiable and report its own state, which helps only if revoking one has been rehearsed.

The check.

  • Per-device identity and certificate, and a "reported stolen" runbook that revokes it within minutes.
  • Remote wipe on next contact; rehearse the runbook on a real unit twice a year.

Source: NISTIR 8259A, Device Identification and Cybersecurity State Awareness, May 2020; UK product security regime for connectable products, in force 29 April 2024

The incident figures are the reporting group's counts as carried by the news report; the standards quoted are the consumer IoT baseline and the NIST core baseline, which industrial and commercial devices usually exceed, not replace.

Take this list with youThe PDF is the handout: this list on one or two pages. The Markdown is for your own docs, your wiki, or an assistant you want to hand the list to. Print gives you this list only, without the navigation.

Something in your production AI broke in a way that is not on this list? Tell me what broke.

New checklists, as they are published

One list at a time, each built the same way: a dated failure, the control that stops it, and the primary source so you can check it. Nothing else goes to this address, no digest and no newsletter.