{
  "schemaVersion": "artifactExample.v2",
  "artifactId": "IMP",
  "title": "Incident Management Policy",
  "definitionRef": {
    "artifactId": "IMP",
    "definitionSchemaVersion": "artifactDefinition.v2",
    "definitionId": "IMP.artifactDefinition.v2",
    "title": "Incident Management Policy"
  },
  "organization": "Arcfield",
  "sections": [
    {
      "id": "title_page",
      "title": "Title Page",
      "values": {
        "Document Title": "Incident Management Policy",
        "Document ID": "INC-MGT-POL-001",
        "Version": "1.1",
        "Status": "Approved",
        "Organization": "Arcfield",
        "Owner": "Security Lead",
        "Approver": "ISMS Manager",
        "Classification": "Internal",
        "Effective Date": "2026-09-11",
        "Next Review Date": "2027-09-11"
      },
      "items": [
        "Document Title: Incident Management Policy",
        "Document ID: INC-MGT-POL-001",
        "Version: 1.1",
        "Status: Approved",
        "Organization: Arcfield",
        "Owner: Security Lead",
        "Approver: ISMS Manager",
        "Classification: Internal",
        "Effective Date: 2026-09-11",
        "Next Review Date: 2027-09-11"
      ],
      "contentType": "metadata"
    },
    {
      "id": "abstract",
      "title": "Abstract",
      "text": "This is a fictional Arcfield worked example of INC-MGT-POL-001. It states operating rules for Incident Management Policy. The cover status is not a real management-team approval and not a certification statement. New numerical and method choices are EXAMPLE_DECISION and pending review. They are not ISO/IEC 27001:2022 obligations and not a recovered Artifact Candidate page.",
      "contentType": "narrative"
    },
    {
      "id": "document_control",
      "title": "Document Control",
      "contentType": "control_table"
    },
    {
      "id": "change_log",
      "title": "Revision history",
      "groups": [
        {
          "text": "A published change is a new row. Do not edit an approved version in place."
        },
        {
          "rows": [
            {
              "Version": "1.0",
              "Date": "2026-08-29",
              "Change": "Initial Arcfield Platform publication.",
              "Approved by": "ISMS Manager"
            },
            {
              "Version": "1.1",
              "Date": "2026-09-11",
              "Change": "Approved Arcfield worked example after the 11 September 2026 internal audit.",
              "Approved by": "ISMS Manager"
            }
          ]
        }
      ],
      "contentType": "revision_table"
    },
    {
      "id": "instructions",
      "title": "Instructions",
      "groups": [
        {
          "text": "This file is a fictional Arcfield example, not your organization's approved policy. Copy this file as the controlled Word master for your ISMS only after you replace Arcfield decisions with your own."
        },
        {
          "items": [
            "Treat INC-MGT-POL-001 and the rule IDs as the example identity. Cover status Approved is the Arcfield scenario freeze, not a real management-team sign-off of these new rule sentences.",
            "Replace Arcfield names, methods and owners before you adopt the file.",
            "Cite the Document Control version from related records. Do not copy this body into those records."
          ]
        }
      ],
      "contentType": "ordered_list"
    },
    {
      "id": "policy_content",
      "title": "Policy",
      "groups": [
        {
          "id": "introduction",
          "heading": "What this policy is",
          "level": 1,
          "text": "This document is Arcfield's Incident Management Policy, document ID INC-MGT-POL-001. It binds how Arcfield reports, classifies, owns, preserves evidence for, and learns from information-security incidents. Response playbooks live in IRP and IRPROC. It is not the ISMS Scope Statement, the Risk Assessment Methodology or the Statement of Applicability. It applies to Arcfield Platform production, customer data, CI/CD, privileged access and critical suppliers. Neighbouring records cite this Document Control version. Do not copy these paragraphs into those records."
        },
        {
          "id": "scope",
          "heading": "Scope",
          "level": 1,
          "text": "Use this table before you copy a rule into another record or exclude a duty from this file.",
          "rows": [
            {
              "In this policy": "The classified rules IMP-RPT-001, IMP-SEV-001, IMP-OWN-001 through IMP-EV-001, roles, the worked Arcfield example and the records this file owns.",
              "Not in this policy": "The ISMS boundary (ISS), Annex A selection (SoA), or live neighbouring registers. Those files keep their own versions."
            },
            {
              "In this policy": "Interfaces that must cite this Document Control version, including CI/CD, identity and suppliers where they affect confidentiality, integrity or availability.",
              "Not in this policy": "Live ISS or SoA decisions. Neighbouring live registers keep their own versions. Those files are named, not copied here."
            }
          ]
        },
        {
          "id": "terms",
          "heading": "Terms used here",
          "level": 1,
          "text": "These terms are local to this file. Expand every acronym on first use in the body. Artefact ID ISO is Information Security Objectives, not the International Organization for Standardization.",
          "rows": [
            {
              "Term": "Owner",
              "Meaning": "The named role that can be called in an audit for an outcome. A team name is not an owner."
            },
            {
              "Term": "Exception",
              "Meaning": "A time-bound, approved departure with expiry and a compensating control. An expired row does not authorise continued deviation."
            },
            {
              "Term": "Document Control version",
              "Meaning": "The version cited from neighbouring records. Do not copy this body into those records."
            },
            {
              "Term": "Enforcement",
              "Meaning": "The named system rejects the unauthorised attempt for the named population. Registration or capability is not enforcement."
            }
          ]
        },
        {
          "id": "named_registers",
          "heading": "Systems, integrations and data",
          "level": 1,
          "text": "Related inventories live in the companion documents named below. Cite the approved version. Do not copy their content. Availability follows the book pack, not this sentence.",
          "items": [
            "[Asset Inventory](AI_Asset_Inventory.xlsx) — In-scope assets with owner, classification, hosting, personal-data flag and related risk.",
            "[Supplier Inventory](SINV_Supplier_Inventory.xlsx) — Security-relevant suppliers with tier, due diligence, contract controls, subprocessors and exit planning.",
            "[Users and Access Inventory](UAI_Users_and_Access_Inventory.xlsx) — Users and accounts with access rights, privileged access, MFA status, reviews and revocations."
          ],
          "ordered": true,
          "relationView": "inventory"
        },
        {
          "id": "reporting_rule",
          "heading": "Reporting",
          "level": 1,
          "text": "Read IMP-RPT-001 as the classified Arcfield rule for this topic. Capability or presence is not enforcement.",
          "rows": [
            {
              "Rule ID": "IMP-RPT-001",
              "Statement": "Suspected incidents, weaknesses, data exposure or lost devices are reported without delay through the approved channel. A chat mention to a colleague is not a report.",
              "Scope": "All in-scope personnel and suppliers who handle Arcfield Platform information.",
              "Owner": "Security Lead",
              "Evidence expectation": "Expected: incident record with reporter and timestamp. No observation is supplied."
            }
          ]
        },
        {
          "id": "classification_and_severity",
          "heading": "Classification and severity",
          "level": 1,
          "text": "Read IMP-SEV-001 as the classified Arcfield rule for this topic. Capability or presence is not enforcement.",
          "rows": [
            {
              "Rule ID": "IMP-SEV-001",
              "Statement": "Severity is assigned using the approved scale before containment decisions that affect customers. Informal 'it looks bad' is not a severity.",
              "Scope": "Opened security incidents.",
              "Owner": "Security Lead",
              "Evidence expectation": "Expected: severity field on the incident record. No observation is supplied."
            }
          ]
        },
        {
          "id": "response_ownership",
          "heading": "Response ownership",
          "level": 1,
          "text": "Read IMP-OWN-001 as the classified Arcfield rule for this topic. Capability or presence is not enforcement.",
          "rows": [
            {
              "Rule ID": "IMP-OWN-001",
              "Statement": "Every open incident has one named Incident Manager. A shared inbox is not the owner.",
              "Scope": "Open Arcfield Platform security incidents.",
              "Owner": "Security Lead",
              "Evidence expectation": "Expected: named owner on the incident record. No observation is supplied."
            }
          ]
        },
        {
          "id": "evidence_preservation",
          "heading": "Evidence preservation",
          "level": 1,
          "text": "Read IMP-EVD-001 as the classified Arcfield rule for this topic. Capability or presence is not enforcement.",
          "rows": [
            {
              "Rule ID": "IMP-EVD-001",
              "Statement": "Volatile evidence needed for the incident is preserved before rebuild. Wiping a host to restore service requires a recorded decision.",
              "Scope": "Incidents that touch production hosts or customer-data stores.",
              "Owner": "Security Lead",
              "Evidence expectation": "Expected: preservation note or recorded wipe decision. No observation is supplied."
            }
          ]
        },
        {
          "id": "lessons_learned_and_improvement",
          "heading": "Lessons learned and improvement",
          "level": 1,
          "text": "Read IMP-LL-001 as the classified Arcfield rule for this topic. Capability or presence is not enforcement.",
          "rows": [
            {
              "Rule ID": "IMP-LL-001",
              "Statement": "Incidents at Medium or above produce a lessons-learned record and, where a control failed, a corrective action. Closing the incident is not closing the improvement.",
              "Scope": "Medium, High and Critical incidents.",
              "Owner": "Security Lead",
              "Evidence expectation": "Expected: lessons-learned record plus CAR when a control failed. No observation is supplied."
            }
          ]
        },
        {
          "id": "evidence",
          "heading": "Evidence expectations",
          "level": 1,
          "text": "Use this table to see what a named evidence ID can prove. It is not a log of collected observations.",
          "rows": [
            {
              "Rule ID": "IMP-EV-001",
              "Statement": "Each rule above states an evidence expectation. An identifier without a bound dataset is not collected evidence.",
              "Scope": "All IMP rules in this file.",
              "Owner": "Security Lead",
              "Evidence expectation": "Expected evidence reference; no evidence supplied. Do not render this row as an observation."
            }
          ]
        }
      ],
      "contentType": "policy_sections"
    },
    {
      "id": "evidence_and_records",
      "title": "Evidence and records",
      "groups": [
        {
          "text": "These companions hold live records. This policy states what evidence it needs; it does not ship observations. An evidence ID without a dataset is an expectation. The Owner on the cover is accountable for those live records when you adopt the file."
        },
        {
          "items": [
            "[Mandatory Documents and Records Register](MDR_Mandatory_Documents_and_Records_Register.xlsx) — The 27 mandatory ISO 27001 documents and records, with owner, required status, approval, review cadence, location and evidence readiness.",
            "[Document Register](DR_Document_Register.xlsx) — Controlled documented information: origin, owner, approver, version, review cycle, retention and location.",
            "[Records Retention Schedule](RRS_Records_Retention_Schedule_Register.xlsx) — Retention rules for ISMS, security, privacy, audit and operational records, with owner, period, disposal method and evidence."
          ],
          "ordered": true,
          "relationView": "evidence"
        }
      ],
      "contentType": "evidence_table"
    },
    {
      "id": "external_references",
      "title": "References",
      "groups": [
        {
          "id": "linked_documents",
          "heading": "Linked documents",
          "level": 1,
          "text": "Availability is by book pack. In-pack files may sit next to this document after unpack. Other-book files are named, not shipped in this Office pack.",
          "rows": [
            {
              "Kind": "Artifact",
              "Reference": "AI Asset Inventory",
              "How this document uses it": "In-scope assets with owner, classification, hosting, personal-data flag and related risk In this book's pack when present.",
              "href": "AI_Asset_Inventory.xlsx",
              "availability": "in-pack"
            },
            {
              "Kind": "Artifact",
              "Reference": "SINV Supplier Inventory",
              "How this document uses it": "Security-relevant suppliers with tier, due diligence, contract controls, subprocessors and exit planning Another book's pack, not this Office pack.",
              "href": "SINV_Supplier_Inventory.xlsx",
              "availability": "other_volume"
            },
            {
              "Kind": "Artifact",
              "Reference": "UAI Users and Access Inventory",
              "How this document uses it": "Users and accounts with access rights, privileged access, MFA status, reviews and revocations In this book's pack when present.",
              "href": "UAI_Users_and_Access_Inventory.xlsx",
              "availability": "in-pack"
            },
            {
              "Kind": "Artifact",
              "Reference": "MDR Mandatory Documents and Records Register",
              "How this document uses it": "The 27 mandatory ISO 27001 documents and records, with owner, required status, approval, review cadence, location and evidence readiness In this book's pack when present.",
              "href": "MDR_Mandatory_Documents_and_Records_Register.xlsx",
              "availability": "in-pack"
            },
            {
              "Kind": "Artifact",
              "Reference": "DR Document Register",
              "How this document uses it": "Controlled documented information: origin, owner, approver, version, review cycle, retention and location In this book's pack when present.",
              "href": "DR_Document_Register.xlsx",
              "availability": "in-pack"
            },
            {
              "Kind": "Artifact",
              "Reference": "RRS Records Retention Schedule",
              "How this document uses it": "Retention rules for ISMS, security, privacy, audit and operational records, with owner, period, disposal method and evidence In this book's pack when present.",
              "href": "RRS_Records_Retention_Schedule_Register.xlsx",
              "availability": "in-pack"
            },
            {
              "Kind": "Artifact",
              "Reference": "SIR Security Incident Register (Secure Engineering, Incident Response & Security Monitoring)",
              "href": "SIR_Security_Incident_Register.xlsx",
              "How this document uses it": "Interface record. Cite this Document Control version; do not copy this file into that record In this book's pack when present.",
              "availability": "in-pack"
            },
            {
              "Kind": "Artifact",
              "Reference": "CAR Corrective Actions Register (Building the ISMS, Context of the Organization (Clause 4))",
              "href": "CAR_Corrective_Actions_Register.xlsx",
              "How this document uses it": "Interface record. Cite this Document Control version; do not copy this file into that record In this book's pack when present.",
              "availability": "in-pack"
            },
            {
              "Kind": "Artifact",
              "Reference": "CIL Continual Improvement Log (Building the ISMS, Continual Improvement (Clause 10))",
              "href": "CIL_Continual_Improvement_Log.xlsx",
              "How this document uses it": "Interface record. Cite this Document Control version; do not copy this file into that record In this book's pack when present.",
              "availability": "in-pack"
            }
          ]
        },
        {
          "id": "external_sources",
          "heading": "External references",
          "level": 1,
          "text": "Cite these ISO clauses and book chapters from workshops and audits.",
          "rows": [
            {
              "Kind": "ISO",
              "Reference": "ISO/IEC 27001:2022",
              "How this document uses it": "Normative ISMS requirements this companion artifact supports.",
              "href": "https://www.iso.org/standard/82875.html"
            },
            {
              "Kind": "Book",
              "Reference": "Secure Engineering, Secrets Management",
              "How this document uses it": "Primary operating chapter for this companion artifact.",
              "href": "https://www.amazon.com/dp/9789908983455"
            },
            {
              "Kind": "Book",
              "Reference": "Implementation & Certification, Asset Management & Information Classification",
              "How this document uses it": "Primary operating chapter for this companion artifact.",
              "href": "https://www.amazon.com/s?k=ISO+27001+for+Software+Companies+Implementation+and+Certification"
            }
          ]
        }
      ],
      "contentType": "reference_table"
    }
  ],
  "enrichment": {
    "source": "Example.json",
    "method": "curated-json",
    "note": "Completes Example JSON with renderer-native sections and generalized groups; no mdSource helper fields."
  },
  "snapshotRef": {
    "snapshotId": "arcfield.platform.surv.2026-09-11",
    "schemaVersion": "evidenceSnapshot.v1"
  },
  "scenarioRef": {
    "crId": "CR-POL-EN-002",
    "dependsOn": [
      106,
      107
    ],
    "family": "Policy",
    "role": "Fictional Arcfield worked example. Not a real management-team approval and not a certification statement.",
    "reviewState": "pending",
    "provenance": "EXAMPLE_DECISION"
  }
}
