(5) A protocol for confirming any vendor, client or customer account information change requests (including requests to change bank account numbers, contact information or mailing addresses) via direct call to that vendor, client or customer using only the telephone number provided by the vendor, client or customer before the change request was received?
This is application question 35 of 45 on the Tokio Marine HCC NGP-NBA. It is a control question and reaches 11 controls. The wording is the carrier's, quoted verbatim.
Held from the NetGuard Plus Cyber Liability Insurance Application (US) (read 2026-10-11), jurisdiction United States. All Tokio Marine HCC questions.
Facets: control: (5) A protocol for confirming any vendor, client or customer account information change requests (including requests to change bank account numbers, contact information or mailing addresses) via direct call to that vendor, client or customer using only the telephone number provided by the vendor, client or customer before the change request was received?; population: client
What this question reaches
- ISO 27001:2022 A.5.19: Information security in supplier relationships (direct)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - ISO 27001:2022 A.5.20: Addressing information security within supplier agreements (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - SOC 2 CC9.2: Assessing and managing vendor and business partner risk (direct)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - SOC 2 P6.4: Privacy commitments from vendors and third parties (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - NIST CSF 2.0 GV.SC-01: A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders (direct)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - APRA CPS 234 para 16: Assess the security capability of related and third parties (direct)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - APRA CPS 234 para 22: Evaluate the design of third-party controls (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - APRA CPS 234 para 28: Assess reliance on third-party control testing (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review
Subject: vendor_third_party. Owner a broker routes it to: Third-party risk owner.
The same control on other applications
Chubb Q22, Chubb Q24, CFC Underwriting Q2, CFC Underwriting Q3, Beazley Q20, Hiscox Q18, Hiscox Q20, Hiscox Q21, Hiscox Q41, Hiscox Q55, AmTrust Q1, Great American Insurance Group Q1.
Map your own answers in the tool. See the Tokio Marine HCC page, the controls index, the island and the answers.