Sites and APIs
TLS for sessions and forms.
Encryption transforms readable data into ciphertext using algorithms and keys so only holders of the right key can read it again. Encrypt in transit (TLS) and at rest (disks, databases, backups). It is a cybersecurity pillar and part of personal-information duties (Law 25, PIPEDA).
In one sentence
Encryption makes data unreadable without the right key—in transit and at rest.
Key points
Term at a glance
Without encryption, a network intercept or stolen disk exposes plaintext. NIST standards guide recommended algorithms (AES, etc.).
Application-level (field) encryption is sometimes added for highly sensitive data.
For an SME, TLS everywhere, encrypted disks, and encrypted backups cover the essentials.
Personal info, secrets, payments.
Up-to-date HTTPS/TLS, HSTS, managed certs.
Volumes, DB, backups; keys in a KMS.
Rotation, least privilege, access logging.
A digital clinic in Quebec enforces HTTPS, encrypts the patient DB at rest via cloud KMS, and stores encrypted offsite backups. A stolen laptop does not yield plaintext records.
TLS for sessions and forms.
Encrypted buckets and disks.
End-to-end or at-rest protection.
Meet Law 25 / PIPEDA expectations.
| Encryption | Hashing | |
|---|---|---|
| Reversible | Yes with the key | No (one-way) |
| Typical use | Data confidentiality | Passwords, integrity |
| Key | Needed to decrypt | No decryption |
| Example | AES, TLS | bcrypt, SHA-256 (by use) |
A breach without encryption can trigger individual notice, reputational harm, and fines. Well-managed encryption reduces residual impact—and reassures insurers and clients.
Necessary but not sufficient: also cover rest and backups.
Follow NIST/OWASP; avoid home-grown crypto.
Often negligible on modern hardware; measure.
Out of code: KMS/HSM, secrets managers.
Want a quick check of TLS, at-rest encryption, and key management? We can audit.
Talk about encryption