{
  "canonicalClaimUrl": "https://xn--mwe.com/knowledge/critical-datacenter-protection/#clm-k04-top-017-c",
  "claimStatus": "PROJECT DOCTRINE",
  "correctionStatus": "CURRENT K04 STRATEGIC RECORD",
  "id": "CLM-K04-TOP-017-C",
  "lastReviewed": "2026-08-15",
  "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-017-c.json",
  "name": "Critical Datacenter Protection — Project doctrine",
  "ownerAnchor": "clm-k04-top-017-c",
  "ownerId": "K04-TOPIC-017",
  "ownerRoute": "/knowledge/critical-datacenter-protection/",
  "ownerType": "topic",
  "proposition": "Project doctrine treats the campus as one cyber-physical system and designs protection from unacceptable consequences backward, while keeping defensive automation, use-of-force authority, and external cyber effects under separate controls.",
  "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.",
  "releaseId": "K12-2026-08-16",
  "releaseVersion": "2.1.0",
  "researchCutoff": "2026-08-15",
  "scope": "Normative K04 position for Critical Datacenter Protection.",
  "slug": "clm-k04-top-017-c",
  "sourceIds": [
    "SRC-INL-CCE",
    "SRC-NIST-800-82R3",
    "SRC-NIST-800-207",
    "SRC-NRC-10CFR-73-54"
  ],
  "sourceSections": [
    {
      "section": "CCE methodology",
      "sourceId": "SRC-INL-CCE",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
      "url": "https://inl.gov/national-security/cce/"
    },
    {
      "section": "Critical function focus",
      "sourceId": "SRC-INL-CCE",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.",
      "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/"
    },
    {
      "section": "Abstract",
      "sourceId": "SRC-NIST-800-82R3",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
      "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
    },
    {
      "section": "Abstract",
      "sourceId": "SRC-NIST-800-207",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.",
      "url": "https://csrc.nist.gov/pubs/sp/800/207/final"
    },
    {
      "section": "73.54(a)",
      "sourceId": "SRC-NRC-10CFR-73-54",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
      "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
    },
    {
      "section": "73.54(b)",
      "sourceId": "SRC-NRC-10CFR-73-54",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.",
      "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
    }
  ],
  "type": "ClaimRecord"
}