Encryption: at rest, in transit, and the keys

Encryption scrambles data so only someone with the key can read it. Who holds the key matters as much as the encryption.

// TECH FOR GRC

Two places data needs protecting

  • At rest: data sitting in a database, a storage bucket, a backup or on a laptop disk. Protected by turning on encryption for that storage, and by tools such as BitLocker or FileVault on laptops.
  • In transit: data moving between a browser and a website, or between two servers. Protected by TLS, the technology behind HTTPS and the padlock in the browser.

Keys are the real control

Encrypted data is only as safe as its key. Companies keep keys in a key management service:

  • AWS KMS
  • Azure Key Vault
  • Google Cloud KMS

Auditors ask:

  • Who can use or change the keys?
  • Are they rotated?
  • Is key access logged?

Hashing is different

Passwords should not be encrypted (which can be reversed) but hashed: turned one-way into a value that cannot be turned back. If a company says it "encrypts passwords", ask what it means.

What this means for evidence

  • At rest: the storage setting showing encryption on, with the key used.
  • In transit: a TLS scan or load balancer settings showing HTTPS only, with old protocols off.
  • Laptops: an MDM report showing every device encrypted.
  • Keys: who has access to them, and the rotation setting.
// WHAT IT LOOKS LIKE AS EVIDENCE
S3 public access blocked at account levelAmazon S3 · proves CC6.1, CC6.7, A.8.3
Amazon S3SAMPLE
S3 › Block Public Access settings for this account

Block Public Access (account settings)

complyoo-prod (4821 0093 1176)Viewed 2026-10-01 09:30 UTC1
  • Block all public accessOn2
  • Block public access via new ACLsOn
  • Block public access via any ACLsOn
  • Block public access via new bucket policiesOn
  • Block public and cross-account access via any policiesOn
  • Default encryption (all buckets)SSE-KMS, key complyoo-data3
  1. 1Date and the account. Account-level settings cover every bucket, which is stronger than bucket by bucket.
  2. 2Block all public access is on for the whole account.
  3. 3Default encryption with a managed KMS key. This is the encryption-at-rest evidence.

Weak version: Only one bucket's settings, not the account. The auditor cannot conclude anything about the other buckets.

// FROM A REAL ACCOUNTAWS console, S3 bucket · identifiers blurred
Block all public access is On for this bucket, and the bucket policy panel confirms that no policy can open it while the setting stays on.
StrongBlock all public access is On for this bucket, and the bucket policy panel confirms that no policy can open it while the setting stays on.
Default encryption is SSE-S3. AWS has encrypted new S3 objects by default since January 2023, so a reviewer looks for buckets where someone changed it, not for buckets where it is on.
Worth knowingDefault encryption is SSE-S3. AWS has encrypted new S3 objects by default since January 2023, so a reviewer looks for buckets where someone changed it, not for buckets where it is on.
Encryption in transit on the public APITLS scanner · proves CC6.7, A.8.24, A.8.21
TLS scan reportSAMPLE
Scans › api.complyoo.com

TLS configuration: api.complyoo.com

External scanScanned 2026-10-031
CheckResult2
CertificateValid until 2027-02-11, trusted issuer
TLS 1.2 and 1.3Enabled
TLS 1.0 and 1.1Disabled3
HTTP to HTTPS redirectEnforced
  1. 1Scan date and the exact host scanned.
  2. 2Each check with its result, from the scanning tool rather than a claim.
  3. 3Old TLS versions disabled. Leaving them on is a common finding.

Weak version: A browser padlock screenshot shows a certificate exists. It says nothing about which TLS versions are allowed.

Laptop disk encryption reportIntune, Jamf or Kandji · proves CC6.7, A.8.1, A.7.9
Microsoft IntuneSAMPLE
Devices › Monitor › Encryption report

Encryption report

Tenant: complyoo.onmicrosoft.comExported 2026-10-021
DeviceUserOSEncryption2Compliant
CMP-LT-031arjun.mWindows 11BitLocker: encryptedYes
CMP-MB-012priya.rmacOS 15FileVault: encryptedYes
CMP-LT-044sana.kWindows 11BitLocker: encryptedYes
  1. 1Export date. Compare the device count with the asset inventory to show nothing is missing.
  2. 2Encryption status per device.

Weak version: Shows the encryption policy exists, not which devices are actually encrypted.

// REMEMBER THIS

Encrypted at rest, encrypted in transit, and someone accountable for the keys.

// CHECK YOURSELF

1. HTTPS protects data...

2. What makes encrypted data unsafe even when encryption is on?

3. How should passwords be stored?