Need-to-know
What is Need-to-know?
Need-to-know is the principle that access to information should be limited to people who require that specific information to perform their duties, even if they hold a general level of trust or clearance.
Examples
- A manager may hold senior status in the organization but still should not access a sensitive investigation file unless their role requires it.
- Two engineers may both work in the same department, but only one may need access to a restricted design repository tied to a confidential project.
Discover 🔎
Trust alone is not enough to justify access. An organization may believe a person is reliable, experienced, and cleared for sensitive work, yet still decide that certain information should remain outside that person’s view. That is the logic behind need-to-know.
The principle matters because information exposure grows quickly when access is granted based only on rank, convenience, or broad trust. Need-to-know narrows the question. It does not ask only whether this person is generally trusted. It asks whether this person genuinely requires this particular information for this particular task.
Summary 📝
Need-to-know is the principle that information should be accessible only to those who require it for their work, mission, or assigned responsibility. It adds a narrower layer of control beyond general trust, clearance, or role membership. By reducing unnecessary visibility, it helps protect confidentiality and supports more disciplined handling of sensitive information.
Tip: The interactive version includes progress tracking, decks, and premium deep dives.