Join our Newsletter — 33% off our NHI Course
Home› FAQ› Governance, Ownership & Risk› How do organisations decide whether data should be…
Governance, Ownership & Risk

How do organisations decide whether data should be treated as confidential or restricted?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 30, 2026 Domain: Governance, Ownership & Risk

Use sensitivity, business impact, and regulatory exposure as the main decision factors. Confidential data usually needs strong access control and encryption, while restricted data demands the highest protection because disclosure can cause severe legal, financial, or personal harm. Organisations should document these thresholds so teams classify similar data the same way.

What “confidential” and “restricted” should mean in practice

These labels should represent different levels of business and harm tolerance, not just a semantic preference. Confidential data is usually sensitive enough to justify tighter access and handling, while restricted data is reserved for the smallest audience because exposure would create severe legal, financial, operational, or personal harm. A useful policy works only if teams can apply it consistently.

That consistency depends on clear classification criteria, a documented handling matrix, and a shared understanding of who can approve exceptions. NHIMG’s Data Classification Guide is a useful reference point when organisations need a practical scheme that translates labels into handling rules, labelling behaviour, and default treatment.

How organisations set the threshold between the two labels

The decision usually rests on three questions: how sensitive the data is, what harm would follow if it leaked, and whether any law, contract, or policy creates a higher duty of care. If the answer is “material harm but bounded impact,” confidential is often appropriate. If the answer is “material harm with severe, broad, or hard-to-repair consequences,” restricted is the better fit.

That threshold should be written in business terms, not only security terms. For example, a customer record set may be confidential because it needs strong access control and encryption, while a merger document, incident report, or regulated identifier set may be restricted because disclosure would immediately change legal exposure, market position, or personal safety. A policy template that defines levels and handling rules helps prevent local teams from inventing their own interpretations, and NHIMG’s Data Classification Policy Template is built around that exact need.

What the classification decision should change downstream

The label is only useful if it changes control decisions. Confidential data should usually trigger stronger access control, limited sharing, and encryption at rest and in transit. Restricted data should go further: tighter approval, narrower distribution, more restrictive storage locations, stronger monitoring, and explicit rules for copying, exporting, or placing it into downstream systems.

Teams often miss that the real risk is not the label itself but inconsistent treatment across tools, repositories, and workflows. If the same dataset is called confidential in one system and unrestricted in another, the organisation loses the ability to enforce a consistent control baseline. That is why handling rules need to cover storage, transmission, backups, exports, and approved business use, not just the source repository.

Risk and Threat Considerations

Misclassification creates two distinct failure modes: under-classification leaves high-value data too easy to access, while over-classification can push people toward workarounds and shadow copies. The result is either avoidable exposure or unmanaged sprawl, both of which weaken governance.

Failure mechanism: When the threshold is vague, staff classify by convenience instead of impact, so sensitive records drift into broader sharing channels, weaker permissions, and uncontrolled exports.

Impact: The organisation may lose control of regulated, commercially sensitive, or personally harmful data, and may also create audit gaps because teams cannot show why one dataset received stricter handling than another.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
ISO/IEC 27001:2022A.5.12 — Classification of informationDirectly governs deciding information classification levels and criteria.
A.5.13 — Labelling of informationSupports making confidential and restricted labels operational and visible.
A.5.15 — Access controlConfidential and restricted labels should drive who can access the data.
Recommendation — Define classification criteria and apply them consistently to sensitive information. Label information so handling requirements are clear wherever data is stored or used. Restrict access based on the assigned information classification.
NIST CSF 2.0PR.DS-01 — Data-at-rest is protectedConfidential and restricted data both require stronger protection at rest.
PR.AA-05 — Identity management, authentication, and access control are managedThe distinction changes how tightly access should be granted and enforced.
Recommendation — Protect classified data at rest with appropriate safeguards. Enforce access controls that match the data's sensitivity level.

Practitioner Guidance

What to verify: Check that the classification rule is anchored to business impact and regulatory exposure, not just data type. If two similar datasets receive different labels, there should be a recorded reason tied to harm threshold, retention, or legal obligation.

Common mistake: Treating “restricted” as a prestige label rather than a genuinely narrower access class. If the label does not change who may access it, how it may be moved, or where it may be stored, the classification scheme is not doing useful work.

Practitioner takeaway: Good classification is less about perfect taxonomy and more about repeatable decisions, if teams can explain why a dataset crosses from “sensitive” into “severe-harm” territory, the label is far more likely to drive real protection.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org