Is the payment card data stored on your network 100% tokenised?
This is application question 34 of 43 on the Ocean Underwriting Ocean Underwriting Cyber Insurance Proposal Form. It is a control question and reaches 11 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.
Facets: control: Is the payment card data stored on your network 100% tokenised?; threshold: 100%
What this question reaches
- ISO 27001:2022 A.8.24: Use of cryptography (direct)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names - ISO 27001:2022 A.8.11: Data masking (supporting)
Establishes masking or tokenisation where the question names it; it does not establish that every sensitive field is masked in every system.
Evidence to have on file: the masking or tokenisation configuration showing where it is applied; a sample of the output with the sensitive fields masked - ISO 27001:2022 A.5.15: Access control (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 - SOC 2 CC6.1: Logical access security over protected information assets (direct)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names - SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal (supporting)
Establishes masking or tokenisation where the question names it; it does not establish that every sensitive field is masked in every system.
Evidence to have on file: the masking or tokenisation configuration showing where it is applied; a sample of the output with the sensitive fields masked - NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected (direct)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names - NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected (supporting)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names - CIS Controls v8 3.11: Encrypt Sensitive Data at Rest (direct)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names - CIS Controls v8 3.10: Encrypt Sensitive Data in Transit (supporting)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names - PCI DSS 4.0 Requirement 3: Protect Stored Account Data (direct)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names - PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks (supporting)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names
Subject: encryption. Owner a broker routes it to: Security and data protection owner.
The same control on other applications
Coalition Q3, Coalition Q4, Chubb Q7, Chubb Q9, Hiscox Q3, Hiscox Q5, Hiscox Q7, Hiscox Q8, Hiscox Q24, Hiscox Q59, Hiscox Q60, Hiscox Q61.
Map your own answers in the tool. See the Ocean Underwriting page, the controls index, the island and the answers.