Which risk encryption addresses
Full-volume encryption reduces the risk of data exposure if a drive is stolen, lost, sent for repair or decommissioned without being wiped. For a local AI system, that may include source documents, OCR output, a vector index, logs and backups. Microsoft describes BitLocker as a way to protect data on lost or stolen devices; a TPM can help verify boot integrity.
Disk encryption is not user access management. When the server is on and the volume is unlocked, services and people with the relevant permissions can read data. Encryption does not control who calls the model’s HTTP API, who views chat history or which network segments can reach storage.
Separate threats and controls
For a small local environment, a control map may include:
- encryption for all volumes, including temporary files and backups;
- separate accounts for the application, administrators and users;
- a restricted network route to the model API and identity checks at the gateway;
- least-privilege access to documents and indexes by role;
- retention limits and removal of source copies after processing;
- controlled access to recovery keys and regular recovery tests.
Check where OCR output and temporary files are written. Often the main directory is encrypted while an index, export or log is stored on another drive. Backups should be treated as complete copies of sensitive data.
Checks before a pilot
Record who owns the recovery key and where its protected copy is stored. Test recovery on a spare device rather than on the day a production server fails. Recheck encryption after a drive replacement or configuration change. If you use a TPM and PIN, rehearse startup after an update or failure.
Use standard internal-service controls for the API: authentication, network segmentation, auditing and account revocation. Verify that a disabled user loses access and that temporary files, indexes and logs are not left on unencrypted storage.
A manager’s checklist
Ask for a data map for one node: which media are encrypted, where keys are stored, who can call the API and which copies remain after processing. Encryption closes one risk—the compromise of an offline drive. Other risks require separate controls.
