Payment Card Information (PCI) (e.g., credit card, debit card numbers or other financial account numbers?
This is application question 29 of 51 on the Everest Insurance Everest Cyber Elevation. It is a control question and reaches 9 controls. The wording is the carrier's, quoted verbatim.
Held from the Everest Cyber Elevation Insurance Policy New Business Application (read 2026-10-11), jurisdiction United States. All Everest Insurance questions.
Facets: control: Payment Card Information (PCI) (e.g., credit card, debit card numbers or other financial account numbers?; population: account
What this question reaches
- ISO 27001:2022 A.5.3: Segregation of duties (direct)
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 - 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 - ISO 27001:2022 A.8.5: Secure authentication (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 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 CC3.3: Considering fraud risk (COSO principle 8) (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 - 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 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 - NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected (supporting)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment - PCI DSS 4.0 Requirement 3: Protect Stored Account Data (supporting)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment - PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks (supporting)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment
Subject: funds_transfer. 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, Beazley Q20, Hiscox Q41, Hiscox Q67, Tokio Marine HCC Q30, Tokio Marine HCC Q31, Tokio Marine HCC Q32, AXIS Insurance Q58.
Map your own answers in the tool. See the Everest Insurance page, the controls index, the island and the answers.