Does the applicant encrypt personal information in the following scenarios: a. "At rest" within computer databases or on back-up storage devices; b. "In transit" via email or other electronic means of communication; c. Stored on mobile devices including laptops flash drives, and mobile phones?
This is application question 22 of 31 on the USLI Cyber APP 11/16. It is a control question and reaches 13 controls. The wording is the carrier's, quoted verbatim.
Held from the Cyber Liability and Data Security + application (form Cyber APP 11/16) (read 2026-10-15), jurisdiction United States. All USLI questions.
Facets: control: Does the applicant encrypt personal information in the following scenarios: a. "At rest" within computer databases or on back-up storage devices; b. "In transit" via email or other electronic means of communication; c. Stored on mobile devices including laptops flash drives, and mobile phones?
What this question reaches
- ISO 27001:2022 A.8.24: Use of cryptography (direct)
Establishes protection of data while it moves; it does not establish protection of the same data at rest.
Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service - ISO 27001:2022 A.5.14: Information transfer (supporting)
Establishes protection of data while it moves; it does not establish protection of the same data at rest.
Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service - ISO 27001:2022 A.8.13: Information backup (supporting)
Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill - SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal (direct)
Establishes protection of data while it moves; it does not establish protection of the same data at rest.
Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service - 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 - NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected (direct)
Establishes protection of data while it moves; it does not establish protection of the same data at rest.
Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service - NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected (direct)
Establishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
Evidence to have on file: the database encryption configuration, naming the algorithm, key length and where the keys are held; a report or sample showing the customer databases or data stores covered by encryption at rest - ACSC Essential Eight BACKUP: Regular backups (supporting)
Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill - CIS Controls v8 3.10: Encrypt Sensitive Data in Transit (direct)
Establishes protection of data while it moves; it does not establish protection of the same data at rest.
Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service - CIS Controls v8 3.11: Encrypt Sensitive Data at Rest (direct)
Establishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
Evidence to have on file: the database encryption configuration, naming the algorithm, key length and where the keys are held; a report or sample showing the customer databases or data stores covered by encryption at rest - CIS Controls v8 11.2: Perform Automated Backups (supporting)
Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill - PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks (supporting)
Establishes protection of data while it moves; it does not establish protection of the same data at rest.
Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service - PCI DSS 4.0 Requirement 3: Protect Stored Account Data (supporting)
Establishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
Evidence to have on file: the database encryption configuration, naming the algorithm, key length and where the keys are held; a report or sample showing the customer databases or data stores covered by encryption at rest
Subject: encryption_in_transit. 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 USLI page, the controls index, the island and the answers.