{
  "canonicalUrl": "https://xn--mwe.com/comparisons/cut-set-vs-attack-path/",
  "claimStatus": "PROJECT DOCTRINE",
  "correctionStatus": "CURRENT K05 RELEASE",
  "decisionUse": "Use this distinction to prevent a representation, queue, diff, merge, cut set, plan, score, signature, result, or redaction record from being represented as authority, deployment, operation, or truth.",
  "distinction": "Abstract cut set and Protected attack path answer different evidentiary or operational questions and must remain separate.",
  "failure": "Conflation can manufacture readiness, erase uncertainty, bypass accountable review, or expose protected information.",
  "id": "K01-COMP-073",
  "lastReviewed": "2026-08-16",
  "left": "Abstract cut set",
  "leftMeaning": "Shows a bounded set of shared assurance dependencies.",
  "name": "Abstract cut set vs Protected attack path",
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "right": "Protected attack path",
  "rightMeaning": "May reveal sensitive topology, sequence, access, or exact configuration and is excluded from public output.",
  "slug": "cut-set-vs-attack-path",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "topic": "cyber-physical-mission-assurance",
  "type": "Comparison"
}