Encryption methods and what they protect
Understand encryption at rest, in transit and end to end, then check key ownership, device coverage and recovery for your business information.

An application can advertise encryption while leaving important questions unanswered. Which copies are covered? Who can decrypt them? Can your business recover the keys after a device fails or a staff member leaves?
Encryption transforms readable information into ciphertext using an algorithm and a key. It helps protect confidentiality. Your review should connect that protection to a specific device, transfer or stored copy.
Understand the methods without choosing an algorithm yourself
Symmetric encryption uses the same secret key to encrypt and decrypt. AES is a common example. Asymmetric cryptography uses a related public and private key pair; RSA and elliptic-curve techniques appear in systems for encryption, signatures or establishing keys, depending on the scheme.
These methods have different jobs. Secure protocols can combine them. The Cloudflare explanation of encryption describes the distinction. Asymmetric encryption isn’t a straight upgrade on symmetric encryption.
Use maintained products and established protocols, with IT reviewing their configuration. DES is a historical algorithm whose NIST standard was withdrawn. It shouldn’t appear as a suitable option in a new business deployment.
Check data at rest
At-rest encryption protects stored information. Examples include device drives, databases, backup media and cloud storage. The Cyber Centre’s encryption guidance covers both stored data and transfer paths.
Ask IT to show the encryption status of each device or service. Check portable drives and exported files separately. A policy saying laptops must be encrypted doesn’t mean every laptop is.
Disk encryption helps protect a lost device when its keys aren’t available to the finder. An unlocked computer can still expose files through the signed-in user or malware. Access control and endpoint protection remain necessary.
Check data in transit
In-transit encryption protects information travelling between specified endpoints. HTTPS protects a connection to a website. It says nothing about whether the business running the site is trustworthy, or whether it should receive your records.
Map the complete route: browser to application, application to another service, and any later export or email. Ask whether each connection is protected. Don’t bypass a certificate warning to complete a transfer.
A business VPN may protect a particular network path, but it doesn’t set file permissions or protect copies made later. The file-handoff guide covers recipient checks and delivery procedures.
Ask what end-to-end protection includes
End-to-end encryption is intended to keep content readable only at the communicating endpoints, including keeping it unreadable to the service carrying it. Ordinary transport encryption and provider-managed storage encryption have different boundaries.
Review the exact feature, participants and client versions. Ask about backups, attachments, recordings, exports and recovery arrangements. Those copies may have different protection. The people you send it to can still copy or disclose what they read.
Make key custody and recovery explicit
Record who controls decryption keys and who can authorize recovery. If the provider holds keys, ask which support or administrative processes can make data readable. If you hold them, confirm how they’re protected and recovered.
Test a representative restore using the documented key process. Don’t keep the only recovery key on the encrypted device. Plan for a person’s absence, a device loss and an unavailable identity service.
Before accepting a product, request evidence of the protection for your own workflow. Include the copies it creates and the recovery route, then record any gaps with an owner and a date for review.


