Make edge-storage encryption recoverable before enabling it

Bottom line: storage encryption can reduce disclosure from removed media, but a lost passphrase or misunderstood format/decrypt action can make authorized recovery impossible or erase the recording. Design recovery before changing the card.

Source fact: encryption and decryption workflows can format storage

The AXIS OS Web Interface Help for LTS 2026 documents encrypted SD-card controls. It states that encrypting a card formats and erases it and that decrypting it also formats and erases it. The interface documentation distinguishes changing the encryption password from those destructive operations. Related Axis guidance states that the original passphrase is required for supported reuse or decryption scenarios.

The safe sequence is therefore evidence first, configuration second. A technician should never discover the destructive effect while handling the only copy of relevant video.

Source boundary and applicability

The help applies to supported Axis products and software. Exact controls, recovery tools, passphrase behavior, and compatibility can differ by release and card state. Encryption does not by itself secure camera credentials, live streams, recorder copies, exports, backups, or authorized misuse. Organizational key-management and evidence rules remain necessary.

Applicability questions

What threat is encryption addressing: theft, removed media, service handling, or disposal?

Is the card the only copy, failover copy, or a synchronized recording?

Who creates, stores, retrieves, rotates, and audits the passphrase?

Can recovery occur if the camera fails and the card must be handled elsewhere?

Which actions format or erase the media on the deployed AXIS OS version?

DSE recommendation: use a two-person encryption runbook

The following steps are DSE recommendations based on the cited source.

Inventory the exact camera, firmware, card, purpose, and existing footage. Place any required recording under the appropriate hold or export workflow before initialization. Generate and escrow the passphrase in an approved secrets system with role separation, recovery access, and audit logging. Do not place it in a ticket, camera name, drawing, or unsecured installer note.

Rehearse enablement, authorized access, password change, camera replacement, and recovery using disposable test media and the supported tools. Mark every destructive step explicitly and require confirmation of card identity and evidence status. Define what occurs if the secret is unavailable or a device fails.

Set a recurring escrow-recovery check that proves an authorized alternate can retrieve the correct secret without displaying it to the tester or altering production media.

Verification and evidence

Retain the approved threat decision, device/card inventory, non-evidence test record, screenshots or exports that avoid secret disclosure, escrow-access test, role review, before-and-after recording check, and change ticket. Never attach the passphrase to the evidence package or verification artifact.

Official references

AXIS OS Web Interface Help – LTS 2026 – Axis Communications