✳ The reference desk / In practice

CIA triad

A shorthand for naming whether a loss is disclosure, unauthorized change, or downtime.

Confidentiality, Integrity, Availability

What it means

The CIA triad provides three useful questions about an asset: who should be able to see it, who may change it, and when must authorized users be able to use it? These correspond to confidentiality, integrity, and availability. The triad helps beginners describe a security outcome before discussing a product or control.

One event can affect several properties at once. Ransomware may interrupt access, alter records, and accompany data theft. The triad is also a starting point rather than a complete model of every concern. Safety, privacy, accountability, and business context may require additional analysis even when the three properties have been considered.

The idea at a glance / Foundations

One vector. Three different losses.

Use one burn vector to distinguish disclosure, an improper change, and lost access.

Fictional Chronos Hub record MV-17 has an approved burn vector for chronos-gs-17. Each row is a separate controlled loss example; these are not stages or one combined incident.

CIA triad: Use one burn vector to distinguish disclosure, an improper change, and lost access. The explanation below describes the relationships.MV-17 · Chronos Hub burn vectorApproved value: signed burn vectorConfidentiality lossA copy reaches an unapproved reader.Integrity lossSaved: EMPTY ≠ burn vector.Availability lossAuthorized reader: no record by 06:00.ONE ASSET · THREE QUESTIONS

READ THE PICTURE

Compare three losses

A copy reaches an unapproved reader: confidentiality loss. An improper edit stores EMPTY: integrity loss. Flight dynamics cannot get MV-17 by 06:00: availability loss. The examples distinguish three properties of the same asset; a real incident can combine them.

Keep in mindA real incident can affect several properties. Protecting or checking one property does not establish the others, and CIA is not a complete model of every security concern.

Read the complete example
  1. Compare three losses. A copy reaches an unapproved reader: confidentiality loss. An improper edit stores EMPTY: integrity loss. Flight dynamics cannot get MV-17 by 06:00: availability loss. The examples distinguish three properties of the same asset; a real incident can combine them. MV-17 is a fictional Chronos Hub burn-vector record whose approved value is the signed vector for chronos-gs-17. In the confidentiality example, an unapproved recipient receives a readable copy; the original can remain unchanged and available. In the integrity example, a direct, unapproved edit changes a separate test copy to EMPTY, contradicting the approved vector; a responding service does not make that value correct. In the availability example, an authorized reader cannot retrieve MV-17 by the 06:00 pass. These are separate controlled examples, not consecutive protection stages or claims that the other properties automatically hold. Real incidents may affect multiple properties: an attacker could disclose, alter, and disrupt the same data. Integrity also includes validation of legitimate changes; permission alone does not guarantee a correct result. Availability concerns timely, reliable use by authorized users. The CIA questions are a useful starting point; safety, privacy, and accountability may need additional analysis.

A real incident can affect several properties. Protecting or checking one property does not establish the others, and CIA is not a complete model of every security concern.

Diagram references: NIST SP 800-12 Rev. 1 - Confidentiality, Integrity, and Availability

AN ILLUSTRATIVE SCENARIO

A clinic medication record

A clinic reviews how it protects a medication record. Confidentiality concerns who may read it. Integrity concerns whether its contents match the authorized clinical record and whether changes are traceable. Availability concerns whether clinicians can obtain it when needed. Restricting access so tightly that authorized care staff cannot retrieve it may damage availability. The team works with clinical owners to define normal access, controlled emergency access, and review of exceptional use, rather than maximizing one property in isolation.

Put it to work

  1. Choose a specific asset and write one concrete loss scenario for each property, avoiding broad labels such as “data security.”
  2. Ask the owner which consequences matter most in the actual workflow and identify tradeoffs, dependencies, and exceptional operating conditions.
  3. Select and test protections for each relevant property, then check whether improving one has introduced an unacceptable problem for another.

How to check your work

A reviewer should be able to connect each chosen safeguard to a named property and a meaningful consequence. Test cases should include both protection against misuse and successful legitimate use.

Connect the ideas

  • Confidentiality

    The property that information is available only to people or systems authorized to see it.

  • Integrity

    The property that data and processes remain complete and unaltered except by authorized action.

  • Availability

    The property that authorized people can use a system or record when they need it.

  • Asset

    Anything whose disclosure, alteration, destruction, or downtime would harm a person or organization.

Explore a field lesson

Find your next idea.

Tip: press / to open search. Escape closes this window.