← Back to Insights
November 18, 2026 · 6 min read · Data Security
PII and Business Data Security: Beyond Encryption
"We encrypt all our data." That's what most companies say when asked about data security. Encryption is important. It's also the bare minimum. Here's what actually protects personal data and business data — and why encryption alone doesn't.
Two types of data, two types of risk
PII (personally identifiable information) — data that identifies a person. Names, email addresses, national insurance numbers, health records, location data. Protected under GDPR. A breach of PII is a regulatory matter — fines, notification obligations, personal liability.
Business data — trade secrets, financial data, intellectual property, customer lists, internal processes. Not all of it is regulated, but all of it is valuable. A breach of business data is a competitive matter — lost contracts, lost advantage, lost trust.
Both need protection. The protection they need is different.
Why encryption alone isn't enough
Encryption protects data at rest — when it's sitting on disk. But data doesn't sit still. It moves:
- In use — when an application reads decrypted data to process it, the data is in plaintext in memory. Anyone with access to the application sees it.
- In transit — when data moves between services, it may be encrypted in transit but decrypted at the destination. If the destination is insecure, encryption in transit didn't help.
- In logs — applications log data. If PII ends up in log files, it's in plaintext. Encrypted databases with plaintext logs is a common gap.
- In backups — if production is encrypted but backups aren't, the backup is the breach.
- In analytics — if PII is copied to a data warehouse for analysis, the warehouse may not have the same protections.
Encryption at rest is a starting point, not the endpoint. If the application, the logs, the backups, or the analytics pipeline expose plaintext data, the encrypted database didn't help.
What architecture actually protects data
- Access controls that work — not "we have IAM" but least privilege enforced, over-permissioned roles flagged automatically, access reviews logged and checked
- Data classification — know which data is PII, where it lives, who can access it. You can't protect what you haven't identified.
- Encryption with proper key management — not just "encrypted" but keys separated from data, key rotation tested, KMS configured correctly. If the provider holds the keys, they can decrypt.
- Log protection — scan logs for PII leakage, mask or redact sensitive fields before they're written. Plaintext PII in logs is a breach waiting to happen.
- Backup encryption — backups must have the same encryption as production. A backup is a copy of the data, not a lesser version of it.
- Data minimisation — don't collect PII you don't need. The cheapest way to protect data you don't have. If you store it, protect it. If you don't need it, don't store it.
- DLP (data loss prevention) — detect when sensitive data is being sent where it shouldn't — external services, personal email, unencrypted shares.
What regulators want to see
Under GDPR, a breach of PII requires notification to the supervisory authority within 72h and to affected individuals "without undue delay." Under NIS2, a data breach is an incident — reportable within 24h/72h.
The evidence regulators want isn't "we encrypted the data." It's: "here's our data classification showing what's PII, here's our access controls proving who can reach it, here's our encryption with keys we control, here's our log scanning confirming no PII leakage, here's our DLP detecting unauthorised transfers."
That's data security. Not "we encrypt." Architecture.
Questions about PII and data security?
Get in touch. 15-minute call, no obligation.
Get in touch
Aethel Guard is a Netherlands-based security architecture firm serving EU companies of all sizes. Your architect, not your vendor.