Do you authenticate and encrypt all remote access to your network and require all such access to be from systems at least as secure as your own?
This is application question 15 of 38 on the Aspen American Insurance Company ASPBRPAP008 and ASPDTAP017FL. It is a control question and reaches 10 controls. The wording is the carrier's, quoted verbatim.
Held from the Cyber Supplemental Application (form ASPBRPAP008 0218) and Professional Protector Plan Cyber Liability and Data Breach Supplemental Application (form ASPDTAP017FL 0317) (read 2026-10-12), jurisdiction United States. All Aspen American Insurance Company questions.
Facets: control: Do you authenticate and encrypt all remote access to your network and require all such access to be from systems at least as secure as your own?; population: all remote access
What this question reaches
- ISO 27001:2022 A.6.7: Remote working (direct)
Establishes how remote access is provided or restricted; it does not establish the endpoint posture of the connecting device.
Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely - ISO 27001:2022 A.8.20: Networks security (supporting)
Establishes how remote access is provided or restricted; it does not establish the endpoint posture of the connecting device.
Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely - ISO 27001:2022 A.8.22: Segregation of networks (supporting)
Establishes how remote access is provided or restricted; it does not establish the endpoint posture of the connecting device.
Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely - SOC 2 CC6.6: Protection against threats from outside the system boundary (direct)
Establishes how remote access is provided or restricted; it does not establish the endpoint posture of the connecting device.
Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely - SOC 2 CC6.1: Logical access security over protected information assets (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 - NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage (direct)
Establishes how remote access is provided or restricted; it does not establish the endpoint posture of the connecting device.
Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely - 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.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 8: Identify Users and Authenticate Access to System Components (direct)
Establishes how remote access is provided or restricted; it does not establish the endpoint posture of the connecting device.
Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely - 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: remote_access. Owner a broker routes it to: Network and infrastructure owner.
The same control on other applications
Beazley Q3, Hiscox Q6, Hiscox Q28, Hiscox Q29, AmTrust Q10, Tokio Marine HCC Q12, Tokio Marine HCC Q13, Tokio Marine HCC Q14, Tokio Marine HCC Q15, Tokio Marine HCC Q16, Tokio Marine HCC Q18, AXIS Insurance Q24.
Map your own answers in the tool. See the Aspen American Insurance Company page, the controls index, the island and the answers.