Integrity And Confidentiality

Why Integrity and Confidentiality Matter

Integrity and confidentiality are usually treated together because they protect two different failure modes in the same data flow: unauthorised change and unauthorised disclosure. For personal data, that means organisations must keep records trustworthy while also limiting who can see them, move them, or copy them.

The two properties are often interdependent in practice. Strong access control helps preserve confidentiality, while change control, validation, and traceability help preserve integrity. If either weakens, personal data can become unreliable, exposed, or both.

How the Principle Shapes Control Design

This GDPR principle pushes organisations toward layered safeguards rather than a single control. Encryption, access restriction, privileged administration controls, logging, segregation of duties, and protected change pathways all support the same outcome: data should not be altered except by authorised processes, and should not be disclosed to unauthorised parties.

That matters because personal data is often handled across many systems, including production, analytics, support, and backup environments. Each transition creates an opportunity for accidental corruption, overexposure, or silent drift from the authoritative record.

Typical Failure Modes

Integrity failures commonly appear as unauthorised edits, incomplete updates, version mismatches, truncation, or processing errors that make records misleading. Confidentiality failures commonly appear as excessive access, weak sharing controls, insecure exports, or data being surfaced in logs, reports, or test environments.

Both failures can occur without a headline incident. A small permissions mistake can expose more records than intended, while a poor change process can create bad data that persists into downstream decisions, customer communications, or compliance reporting.

Why It Is a Governance Principle, Not Just a Technical Control

Integrity and confidentiality is a design principle because it requires organisations to assign ownership for data handling, classify sensitivity, define authorised processing, and maintain evidence that controls are working. It is not satisfied by one technology choice alone.

In practice, it helps teams decide which records need tighter handling, which systems must be trusted as sources of truth, and where compensating controls are needed when business speed, integrations, or legacy platforms make ideal protection difficult.

Risk and Threat Considerations

Weak integrity and confidentiality controls can expose personal data to both silent corruption and unauthorised disclosure. The risk is especially important where the same dataset is reused across operational, analytics, and support workflows, because one control failure can spread quickly across multiple systems.

Failure mechanism: Excessive access, weak change controls, or insecure data handling can let an attacker, insider, or misconfigured process alter records or read them without authorisation, while leaving limited immediate visibility.

Impact: Organisations can lose trust in the data, make incorrect decisions, breach privacy obligations, and create downstream exposure through inaccurate records, unauthorised sharing, or compromised derivative datasets.

Practitioner Guidance

Why practitioners should care: Treat integrity and confidentiality as a paired control objective when designing data flows, because protecting only one often leaves the other weakened. A system that is private but unreliable, or accurate but overexposed, still fails the principle.

Governance implication: Assign clear ownership for who may change data, who may view it, and which processes are authorised to move it between environments. The key question is whether the control design can prove both restricted access and controlled modification, not just one of them.

Related resources from NHI Mgmt Group

• Why do access controls and logging matter so much for data integrity and confidentiality?
• What is the difference between data integrity and data confidentiality in API security?
• Why do hard-coded or shared cryptographic keys create outsized risk for confidentiality and integrity?
• Why does PKI matter for data integrity and confidentiality in 5G communications?