Do you require customer sign-off on mid-project changes?
This is application question 85 of 101 on the Arch Insurance 00 NPL0154 00 07 16 and 00 NPL0151 00 07 16. It is a control question and reaches 5 controls. The wording is the carrier's, quoted verbatim.
Held from the Short Form Application for Arch NetSafe 2.0 Network Security & Privacy & Media Insurance (form 00 NPL0154 00 07 16) and Application for Arch NetSafe 2.0 Network Security & Privacy, Technology, E&O & Media Insurance (form 00 NPL0151 00 07 16) (read 2026-10-12), jurisdiction United States. All Arch Insurance questions.
Facets: control: Do you require customer sign-off on mid-project changes?; population: customer
What this question reaches
- ISO 27001:2022 A.8.32: Change management (direct)
Establishes the change control the question names; it does not establish that every change followed it.
Evidence to have on file: the change record for a recent release, with its approvals; the rule on which changes need sign-off, and by whom - ISO 27001:2022 6.3: Planning of changes (supporting)
Establishes the change control the question names; it does not establish that every change followed it.
Evidence to have on file: the change record for a recent release, with its approvals; the rule on which changes need sign-off, and by whom - SOC 2 CC8.1: Managing changes to procedures, software, data and infrastructure (direct)
Establishes the change control the question names; it does not establish that every change followed it.
Evidence to have on file: the change record for a recent release, with its approvals; the rule on which changes need sign-off, and by whom - NIST CSF 2.0 ID.RA-07: Changes and exceptions are managed, assessed for risk impact, recorded, and tracked (direct)
Establishes the change control the question names; it does not establish that every change followed it.
Evidence to have on file: the change record for a recent release, with its approvals; the rule on which changes need sign-off, and by whom - PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software (supporting)
Establishes the change control the question names; it does not establish that every change followed it.
Evidence to have on file: the change record for a recent release, with its approvals; the rule on which changes need sign-off, and by whom
Subject: change_management. Owner a broker routes it to: Engineering change owner.
The same control on other applications
Hiscox Q54, Aspen American Insurance Company Q37.
Map your own answers in the tool. See the Arch Insurance page, the controls index, the island and the answers.