When a vendor or supplier requests any change to its account details (including routing numbers and account numbers), do you confirm requested changes via an out-of-band authentication (a method other than the original means of request?
This is application question 20 of 21 on the Beazley F00863. It is a control question and reaches 7 controls. The wording is the carrier's, quoted verbatim.
Held from the Cyber Insurance Application (revenues lower than $250M) (read 2026-10-11), jurisdiction United States. All Beazley questions.
Facets: control: When a vendor or supplier requests any change to its account details (including routing numbers and account numbers), do you confirm requested changes via an out-of-band authentication (a method other than the original means of request?; population: account; exception: the original means of request
What this question reaches
- ISO 27001:2022 A.5.3: Segregation of duties (direct)
Establishes the verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change - ISO 27001:2022 A.5.19: Information security in supplier relationships (supporting)
Establishes the verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change - ISO 27001:2022 A.6.3: Information security awareness, education and training (supporting)
Establishes the funds-transfer or dual-control practice the question names; it does not establish the bank's own configuration or that no fraudulent payment was made.
Evidence to have on file: the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold; the payment approval log, with a dated example above the threshold - SOC 2 CC6.3: Role-based access, least privilege and segregation of duties (direct)
Establishes the verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change - SOC 2 CC3.3: Considering fraud risk (COSO principle 8) (supporting)
Establishes the verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change - NIST CSF 2.0 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties (direct)
Establishes the verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change - 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 verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change
Subject: payment_verification. Owner a broker routes it to: Finance and treasury owner.
The same control on other applications
Coalition Q6, Chubb Q21, Chubb Q22, Chubb Q23, Chubb Q24, Hiscox Q41, Hiscox Q67, Tokio Marine HCC Q30, Tokio Marine HCC Q31, Tokio Marine HCC Q32, AXIS Insurance Q58, AXIS Insurance Q59.
Map your own answers in the tool. See the Beazley page, the controls index, the island and the answers.