Do all third-party requests for changes to payment details (e.g. payee bank account details) go through a two-factor verification process?
This is application question 38 of 43 on the Ocean Underwriting Ocean Underwriting Cyber Insurance Proposal Form. It is a control question and reaches 12 controls. The wording is the carrier's, quoted verbatim.
Held from the Cyber Insurance Proposal Form (Ocean Underwriting Pty Limited, agent for Tokio Marine & Nichido Fire Insurance Co., Ltd, 2024) (read 2026-10-17), jurisdiction Australia. All Ocean Underwriting questions.
Priority underwriting question: a "no" here is a subject a cyber underwriter weighs most. A carrier may still accept a compensating-controls explanation, so it is not a binary decline.
Facets: control: Do all third-party requests for changes to payment details (e.g. payee bank account details) go through a two-factor verification process?; population: account
What this question reaches
- ISO 27001:2022 A.8.5: Secure authentication (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login - ISO 27001:2022 A.5.17: Authentication information (supporting)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login - ISO 27001:2022 A.5.3: Segregation of duties (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 - SOC 2 CC6.1: Logical access security over protected information assets (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login - SOC 2 CC6.3: Role-based access, least privilege and segregation of duties (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-03: Users, services, and hardware are authenticated (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login - 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 (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 - ACSC Essential Eight MFA: Multi-factor authentication (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login - CIS Controls v8 6.4: Require MFA for Remote Network Access (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login - CIS Controls v8 6.5: Require MFA for Administrative Access (supporting)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login - CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications (supporting)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login - PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login
Subject: mfa. Owner a broker routes it to: IT identity and access owner.
The same control on other applications
Coalition Q6, Chubb Q21, Chubb Q23, Beazley Q3, Beazley Q4, Hiscox Q25, Hiscox Q28, Hiscox Q29, Hiscox Q40, Hiscox Q67, Great American Insurance Group Q9, Great American Insurance Group Q18.
Map your own answers in the tool. See the Ocean Underwriting page, the controls index, the island and the answers.