Capitol Indemnity Corporation (CapSpecialty) cyber policy application, held
8 questions, 23 controls reached, 0 flagged as priority underwriting questions and 0 flagged warranty (answers the carrier relies on). Renewal and change view.
The questions of the Cyber Crime Supplemental Application - Electronic Funds Transfers (form A-PL-SUPP-364 10-21), mapped to the ISO 27001:2022 controls, the SOC 2 criteria, the NIST CSF 2.0 outcomes, the ACSC Essential Eight requirements, the APRA CPS 234 paragraphs, the CIS Controls v8 safeguards and the PCI DSS 4.0 requirements each one reaches. The source document, Cyber Crime Supplemental Application - Electronic Funds Transfers (form A-PL-SUPP-364 10-21) (read 2026-10-12). The date shown is the date this copy was read, not a version the form itself states. This page quotes only the question each mapped row needs and states its source; it does not publish the carrier's form. A complete form would be held only under a stated policy for copyrighted forms. Capitol Indemnity Corporation (CapSpecialty) is a source document, never a customer.
This document
| Form identifier | A-PL-SUPP-364 |
|---|
| Edition or version | form A-PL-SUPP-364 (10-21) |
|---|
| Jurisdiction | United States |
|---|
| Product | Cyber Crime, electronic funds transfer cover |
|---|
| Application type | supplemental application |
|---|
| Scope conditions | a supplemental application attached to and forming part of the cyber crime application for the policy indicated; the answers are representations the applicant makes on behalf of all proposed insureds |
|---|
| Page references | pages 1 to 2 |
|---|
This document's questions reach 23 of 487 controls. Whether an applicant is offered cover is the carrier’s underwriting decision. 0 questions here are flagged as a priority underwriting question and 0 flagged warranty (an answer the carrier relies on, which can affect underwriting or cover if wrong).
Application question Does the Applicant require that requests to transfer of funds by wire, bank-to-bank, or other electronic funds transfer be accompanied by supporting documentation, such as an invoice?
Capitol Indemnity Corporation (CapSpecialty) application question
Facets (activity, control, population, threshold, frequency, exception): control: Does the Applicant require that requests to transfer of funds by wire, bank-to-bank, or other electronic funds transfer be accompanied by supporting documentation, such as an invoice?
ISO 27001:2022 A.5.3 Segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.6.3 Information security awareness, education and training
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.8.5 Secure authentication
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC6.3 Role-based access, least privilege and segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC3.3 Considering fraud risk (COSO principle 8)
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
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 mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
Application question For such requests, does Applicant confirm the identity of the requestor and authenticity of payment instructions by telephone with the requestor? If yes, is the validity of the telephone number confirmed?
Capitol Indemnity Corporation (CapSpecialty) application question
Facets (activity, control, population, threshold, frequency, exception): control: For such requests, does Applicant confirm the identity of the requestor and authenticity of payment instructions by telephone with the requestor? If yes, is the validity of the telephone number confirmed?
ISO 27001:2022 A.5.3 Segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- a dated record of the verification for the specific change, with the person who checked and the source used
ISO 27001:2022 A.5.19 Information security in supplier relationships
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- a dated record of the verification for the specific change, with the person who checked and the source used
SOC 2 CC6.3 Role-based access, least privilege and segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- a dated record of the verification for the specific change, with the person who checked and the source used
SOC 2 CC3.3 Considering fraud risk (COSO principle 8)
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- a dated record of the verification for the specific change, with the person who checked and the source used
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 mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- a dated record of the verification for the specific change, with the person who checked and the source used
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 practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- a dated record of the verification for the specific change, with the person who checked and the source used
Application question Does Applicant have a dual payment approval process for such transfers, and effective separation of authority?
Capitol Indemnity Corporation (CapSpecialty) application question
Facets (activity, control, population, threshold, frequency, exception): control: Does Applicant have a dual payment approval process for such transfers, and effective separation of authority?
ISO 27001:2022 A.5.15 Access control
Direct mapping: this control is what the question asks about. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)- the access rule and the role or group model that enforces it
- a dated access review showing rights were confirmed or removed
- a sample of how access is granted and revoked for a leaver
ISO 27001:2022 A.5.16 Identity management
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)- the access rule and the role or group model that enforces it
- a dated access review showing rights were confirmed or removed
- a sample of how access is granted and revoked for a leaver
ISO 27001:2022 A.5.18 Access rights
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)- the access rule and the role or group model that enforces it
- a dated access review showing rights were confirmed or removed
- a sample of how access is granted and revoked for a leaver
SOC 2 CC6.1 Logical access security over protected information assets
Direct mapping: this control is what the question asks about. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)- the access rule and the role or group model that enforces it
- a dated access review showing rights were confirmed or removed
- a sample of how access is granted and revoked for a leaver
SOC 2 CC6.2 Registering and authorising users before issuing credentials
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)- the access rule and the role or group model that enforces it
- a dated access review showing rights were confirmed or removed
- a sample of how access is granted and revoked for a leaver
NIST CSF 2.0 PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
Direct mapping: this control is what the question asks about. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)- the access rule and the role or group model that enforces it
- a dated access review showing rights were confirmed or removed
- a sample of how access is granted and revoked for a leaver
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 practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)- the access rule and the role or group model that enforces it
- a dated access review showing rights were confirmed or removed
- a sample of how access is granted and revoked for a leaver
ACSC Essential Eight ADMIN Restrict administrative privileges
Direct mapping: this control is what the question asks about. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)- the access rule and the role or group model that enforces it
- a dated access review showing rights were confirmed or removed
- a sample of how access is granted and revoked for a leaver
CIS Controls v8 6.8 Define and Maintain Role-Based Access Control
Direct mapping: this control is what the question asks about. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)- the access rule and the role or group model that enforces it
- a dated access review showing rights were confirmed or removed
- a sample of how access is granted and revoked for a leaver
CIS Controls v8 6.1 Establish an Access Granting Process
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)- the access rule and the role or group model that enforces it
- a dated access review showing rights were confirmed or removed
- a sample of how access is granted and revoked for a leaver
CIS Controls v8 6.2 Establish an Access Revoking Process
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)- the access rule and the role or group model that enforces it
- a dated access review showing rights were confirmed or removed
- a sample of how access is granted and revoked for a leaver
PCI DSS 4.0 Requirement 7 Restrict Access to System Components and Cardholder Data by Business Need to Know
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)- the access rule and the role or group model that enforces it
- a dated access review showing rights were confirmed or removed
- a sample of how access is granted and revoked for a leaver
Application question Does the Applicant have transaction limits in place for such transfers?
Capitol Indemnity Corporation (CapSpecialty) application question
Facets (activity, control, population, threshold, frequency, exception): control: Does the Applicant have transaction limits in place for such transfers?; population: transaction
ISO 27001:2022 A.5.3 Segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.6.3 Information security awareness, education and training
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.8.5 Secure authentication
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC6.3 Role-based access, least privilege and segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC3.3 Considering fraud risk (COSO principle 8)
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
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 mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
Application question Does Applicant train employees on detecting and responding to social engineering methods, including those used in the context of electronic funds transfers?
Capitol Indemnity Corporation (CapSpecialty) application question
Facets (activity, control, population, threshold, frequency, exception): control: Does Applicant train employees on detecting and responding to social engineering methods, including those used in the context of electronic funds transfers?; population: employees
ISO 27001:2022 A.6.3 Information security awareness, education and training
Direct mapping: this control is what the question asks about. Limit: Establishes that training is provided; it does not establish that every user completed it or changed behaviour.
Evidence to have on file (guidance, our wording)- the security-awareness programme content and its schedule
- the completion record for the last round of training, with the date
- a sample of a phishing-simulation result and the follow-up
ISO 27001:2022 A.5.3 Segregation of duties
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.8.5 Secure authentication
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC1.4 Attracting, developing and retaining competent people (COSO principle 4)
Direct mapping: this control is what the question asks about. Limit: Establishes that training is provided; it does not establish that every user completed it or changed behaviour.
Evidence to have on file (guidance, our wording)- the security-awareness programme content and its schedule
- the completion record for the last round of training, with the date
- a sample of a phishing-simulation result and the follow-up
SOC 2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes that training is provided; it does not establish that every user completed it or changed behaviour.
Evidence to have on file (guidance, our wording)- the security-awareness programme content and its schedule
- the completion record for the last round of training, with the date
- a sample of a phishing-simulation result and the follow-up
NIST CSF 2.0 PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind
Direct mapping: this control is what the question asks about. Limit: Establishes that training is provided; it does not establish that every user completed it or changed behaviour.
Evidence to have on file (guidance, our wording)- the security-awareness programme content and its schedule
- the completion record for the last round of training, with the date
- a sample of a phishing-simulation result and the follow-up
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 practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
PCI DSS 4.0 Requirement 12 Support Information Security with Organizational Policies and Programs
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes that training is provided; it does not establish that every user completed it or changed behaviour. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)- the security-awareness programme content and its schedule
- the completion record for the last round of training, with the date
- a sample of a phishing-simulation result and the follow-up
Application question Does the Applicant have security procedures in place for electronic funds transfers? Are they automated?
Capitol Indemnity Corporation (CapSpecialty) application question
Facets (activity, control, population, threshold, frequency, exception): control: Does the Applicant have security procedures in place for electronic funds transfers? Are they automated?
ISO 27001:2022 A.5.3 Segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.6.3 Information security awareness, education and training
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.8.5 Secure authentication
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC6.3 Role-based access, least privilege and segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC3.3 Considering fraud risk (COSO principle 8)
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
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 mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
Application question How often does Applicant transfer funds by any electronic funds transfer method?
Capitol Indemnity Corporation (CapSpecialty) application question
Facets (activity, control, population, threshold, frequency, exception): control: How often does Applicant transfer funds by any electronic funds transfer method?
ISO 27001:2022 A.5.3 Segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.6.3 Information security awareness, education and training
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.8.5 Secure authentication
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC6.3 Role-based access, least privilege and segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC3.3 Considering fraud risk (COSO principle 8)
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
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 mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)- 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
- the callback or out-of-band verification for a change to payee bank details, with a dated example
Application question What is the average amount of an electronic funds transfer?
Capitol Indemnity Corporation (CapSpecialty) application question
This is a scoping question, not a control requirement. It reaches no control.
No mapping identified for this line in the documents. That is not a statement that a document does not ask it.
The other applications, each with its own page: Coalition, Chubb, CFC Underwriting, Beazley, Hiscox, AmTrust, Great American Insurance Group, Tokio Marine HCC, AXIS Insurance, Travelers, RLI, Corvus Insurance, Cowbell Cyber, At-Bay, QBE, The Hanover Insurance Group, The Hartford, CNA, Encore Fiduciary, Everest Insurance, RSA, Munich Re, Hiscox UK, AIG, Aon, Arch Insurance, DUAL Corporate Risks, Argonaut Insurance Company, Northbridge General Insurance Corporation, Trisura Guarantee Insurance Company, Aspen American Insurance Company, Capitol Indemnity Corporation (CapSpecialty), ATC Insurance Solutions Pty Ltd, SURA Technology Risks Pty Ltd (SURA Cyber), Apogee Insurance Group, SHORE Underwriting, London Australia Underwriting Pty Ltd, Discovery Insure Ltd, BOXX Insurance, The Hartford Steam Boiler Inspection and Insurance Company, The Cincinnati Insurance Company, USLI, Philadelphia Insurance Companies, Delta Insurance, Markel, Liberty Mutual Insurance Europe Limited, Emergence Insurance Pty Ltd, Ocean Underwriting. Compare this with any of them on the comparison page; the controls the documents share are ranked on the island. Worked answers: what counts as MFA and the funds-transfer question. For a renewal: the broker renewal checklist and the pre-renewal client review template. What is covered, and what is next: coverage.
Controls not asked in this document (464)
None of this document's questions reach 464 of the 487 controls (for example A.5.1, A.5.2, A.5.4, A.5.5, A.5.6, A.5.7, A.5.8, A.5.9). That is a fact about this document, not about what the carrier underwrites on: a carrier's fuller forms and supplements ask controls this summary does not, multi-factor authentication, offline backups and patching among them. A control here is not asserted as required, and not asserted as not required. A control the tool does not map is reported as no mapping identified, never as a control the document does not ask.