extracted_sl5_overlay.json

{
  "CP-04(04)": {
    "name": "Contingency Plan Testing | Full Recovery and Reconstitution",
    "attributes": {
      "Justification to Select": "Full recovery and reconstitution capabilities should be tested so they will work reliably when needed. ​ ​",
      "Test Method": "Examine, Interview, Test"
    },
    "selected": true
  },
  "CP-09(03)": {
    "name": "System Backup | Separate Storage for Critical Information",
    "attributes": {
      "Justification to Select": "Already selected in IL6, adding additional instruction for SL5",
      "Parameter Value(s)": "Organization-defined critical system software and other security-related information, including model weights and training data ​ ​",
      "Test Method": "Examine, Interview, Test"
    },
    "selected": true
  },
  "CP-10(02)": {
    "name": "System Recovery and Reconstitution | Offline Storage",
    "attributes": {
      "Justification to Select": "SL5 requires offline storage of certain data as well as offline data transfer devices. ​ ​",
      "Test Method": "Examine, Interview",
      "Open Questions": "Do we need supplemental guidance about offline storage facilities, should other controls be involved here?"
    },
    "selected": true
  },
  "CP-11": {
    "name": "ALTERNATE COMMUNICATIONS PROTOCOLS",
    "attributes": {
      "Justification to Select": "Already selected in IL6, but adding more content.",
      "Parameter Value(s)": "Alternate communications protocols as defined in the contingency plan.",
      "Test Method": "Examine, Interview, Test",
      "Supplemental Guidance": "An attacker who compromises the system may be able to eavesdrop on communications occurring over the network. If these communications are used to plan or implement a response, the attacker may be able to preempt it. Instead responders should coordinate their efforts over a separate communication system that is not visible to the attacker. This should include even the initial report of the attack.",
      "Open Questions": "Maybe CP-8 is also relevant to this? IA - IDENTIFICATION AND AUTHENTICATION"
    },
    "selected": true
  },
  "IA-03": {
    "name": "DEVICE IDENTIFICATION AND AUTHENTICATION",
    "attributes": {
      "Justification to Select": "Already selected in IL6, but adding more content in the context of zero trust.",
      "Parameter Value(s)": "All devices; local, remote, or network",
      "Test Method": "Examine, Test",
      "Supplemental Guidance": "Consistent with zero trust architecture, all devices should be uniquely identified and authenticated before a network connection is made."
    },
    "selected": true
  },
  "IA-03(04)": {
    "name": "Device Identification and Authentication | Device Attestation",
    "attributes": {
      "Justification to Select": "Zero trust requires devices to attest their identity and security posture with a TPM.",
      "Parameter Value(s)": "A trusted platform module (TPM) ​ ​",
      "Test Method": "Examine, Test",
      "Supplemental Guidance": "Consistent with zero trust architecture, devices should attest their identity and security posture in a non-spoofable manner via a TPM."
    },
    "selected": true
  },
  "IR-04(05)": {
    "name": "Incident Handling | Automatic Disabling of System",
    "attributes": {
      "Justification to Select": "Models engaging in potentially dangerous behavior should be disabled automatically, especially in a context where there are far too many instances for manual supervision. ​ ​",
      "Test Method": "Examine, Interview, Test",
      "Supplemental Guidance": "TODO something about making sure models can be stopped automatically by some hypervisor, putting hypervisor in its own sandbox.",
      "Open Questions": "Do we need supplemental guidance about offline storage facilities, should other controls be involved here? SC - SYSTEM COMMUNICATION PROTECTION"
    },
    "selected": true
  },
  "SC-03": {
    "name": "SECURITY FUNCTION ISOLATION",
    "attributes": {
      "Open Questions": "Unsure what enhancements to select"
    },
    "selected": false
  },
  "SC-03(01)": {
    "name": "Security Function Isolation | Hardware Separation",
    "attributes": {
      "Open Questions": "Unsure of test methods"
    },
    "selected": false
  },
  "SC-06": {
    "name": "RESOURCE AVAILABILITY",
    "attributes": {
      "Open Questions": "Unsure if should select"
    },
    "selected": false
  },
  "SC-07": {
    "name": "BOUNDARY PROTECTION",
    "attributes": {
      "Justification to Select": "Already selected by IL6.",
      "Open Questions": "Unsure what enhancements to select"
    },
    "selected": true
  },
  "SC-11": {
    "name": "TRUSTED PATH",
    "attributes": {
      "Open Questions": "Unsure if should select"
    },
    "selected": false
  },
  "SC-12(01)": {
    "name": "Cryptographic Key Establishment and Management | Availability",
    "attributes": {
      "Justification to Select": "Already selected in IL6.​ ​ ​",
      "Test Method": "Examine, Interview",
      "Supplemental Guidance": "Consider where escrow of keys may conflict with cryptographic erasure of data."
    },
    "selected": true
  },
  "SC-12(02)": {
    "name": "Cryptographic Key Establishment and Management | Symmetric Keys",
    "attributes": {
      "Justification to Select": "Already selected by IL6.",
      "Parameter Value(s)": "NIST FIPS-validated​ ​ ​",
      "Test Method": "Examine, Interview",
      "Open Questions": "Unsure of test methods"
    },
    "selected": true
  },
  "SC-12(03)": {
    "name": "Cryptographic Key Establishment and Management | Asymmetric Keys",
    "attributes": {
      "Justification to Select": "Already selected by IL6.",
      "Parameter Value(s)": "Certificates issued in accordance with organization-defined requirements ​ ​",
      "Test Method": "Examine, Interview",
      "Open Questions": "Unsure what parameters to select, Unsure of test methods"
    },
    "selected": true
  },
  "SC-16": {
    "name": "TRANSMISSION OF SECURITY AND PRIVACY ATTRIBUTES",
    "attributes": {
      "Open Questions": "Unsure if should select, and if so what enhancements"
    },
    "selected": false
  },
  "SC-25": {
    "name": "THIN NODES",
    "attributes": {
      "Justification to Select": "Critical actions can be performed by components that are hardened through simplicity by having minimal functionality.",
      "Test Method": "Examine, Interview",
      "Open Questions": "Unsure if should select"
    },
    "selected": true
  },
  "SC-26": {
    "name": "DECOYS",
    "attributes": {
      "Justification to Select": "Decoys or honeypots can be useful for alerting when attackers have breached a layer of defense. RAND SL5 report calls for honeypots.",
      "Test Method": "Examine, Interview",
      "Open Questions": "Unsure if should select"
    },
    "selected": true
  },
  "SC-28(02)": {
    "name": "Protection of Information at Rest | Offline Storage",
    "attributes": {
      "Justification to Select": "SL5 requires offline storage of certain data as well as offline data transfer devices. ​ ​",
      "Test Method": "Examine, Interview",
      "Open Questions": "Do we need supplemental guidance about offline storage facilities, should other controls be involved here?"
    },
    "selected": true
  },
  "SC-28(03)": {
    "name": "Protection of Information at Rest | Cryptographic Keys",
    "attributes": {
      "Justification to Select": "Keys should be stored in TPMs.",
      "Parameter Value(s)": "Hardware-protected key store ​ ​",
      "Test Method": "Examine, Interview",
      "Open Questions": "Should we say more here, should other controls be involved?"
    },
    "selected": true
  },
  "SC-29": {
    "name": "HETEROGENEITY",
    "attributes": {
      "Justification to Select": "Useful in certain contexts like defense in depth.",
      "Test Method": "Examine, Interview",
      "Supplemental Guidance": "Heterogeneity should be used in contexts where security is determined by the strongest link rather than the weakest link. For example, if multiple firewalls are used, using different types of firewalls means a vulnerability in one will not compromise the system.",
      "Open Questions": "Unsure if this is a good selection/supplementation."
    },
    "selected": true
  },
  "SC-30": {
    "name": "CONCEALMENT AND MISDIRECTION",
    "attributes": {
      "Open Questions": "Unsure if to select, very open-ended"
    },
    "selected": false
  },
  "SC-31": {
    "name": "COVERT CHANNEL ANALYSIS",
    "attributes": {
      "Justification to Select": "Not selected by IL6, however necessary to prevent exfiltration including of model weights.",
      "Parameter Value(s)": "Storage and timing",
      "Test Method": "Examine, Interview, Test",
      "Open Questions": "Unsure if should select enhancement SC-31(01)"
    },
    "selected": true
  },
  "SC-31(02)": {
    "name": "Covert Channel Analysis | Maximum Bandwidth",
    "attributes": {
      "Justification to Select": "To enforce SC-31(02), detect any suspicious movement of large amounts of data.",
      "Parameter Value(s)": "Any channel providing access to weight storage​ ​ ​",
      "Supplemental Guidance": "Total egress out of systems containing frontier model weights should be limited to some fraction of the size of the model to prevent exfiltration. ​ ​",
      "Test Method": "Examine, Interview, Test",
      "Open Questions": "Unsure of parameter value SI - SYSTEM AND INFORMATION INTEGRITY"
    },
    "selected": true
  },
  "SI-12(03)": {
    "name": "Information Management and Retention | Information Disposal",
    "attributes": {
      "Justification to Select": "Not selected in IL6, but cryptographic erasure is described in IL6.",
      "Parameter Value(s)": "Cryptographic erasure",
      "Supplemental Guidance": "Cryptographic erasure is used to reliably erase data that is stored by a cloud provider without relying on that cloud provider to erase it. It works by having sole custody of the keys used to encrypt the data, and destroying those keys, thereby effectively erasing the encrypted data. ​",
      "Test Method": "Examine, Interview"
    },
    "selected": true
  },
  "SI-15": {
    "name": "INFORMATION OUTPUT FILTERING",
    "attributes": {
      "Justification to Select": "Not selected in IL6, but output filtering is needed to prevent misuse of APIs.",
      "Parameter Value(s)": "CSP-defined software programs and/or applications",
      "Supplemental Guidance": "API responses, especially those including the output from models, are checked for content that could reveal sensitive information, especially pertaining to weights. If detected, the response is blocked and flagged. ​",
      "Test Method": "Examine, Interview, Test"
    },
    "selected": true
  }
}