On your wireless networks, do you use security at least as strong as WPA authentication and encryption, and do you require two factor authentication (e.g. some combination of VPN or Access token, and password/account logon) before allowing wireless connections to your network?
This is application question 28 of 38 on the Aspen American Insurance Company ASPBRPAP008 and ASPDTAP017FL. It is a control question and reaches 13 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.
Priority underwriting question: a "no" here is a subject a cyber underwriter weighs most. A carrier may still accept a compensating-controls explanation, so it is not a binary decline.
Facets: control: On your wireless networks, do you use security at least as strong as WPA authentication and encryption, and do you require two factor authentication (e.g. some combination of VPN or Access token, and password/account logon) before allowing wireless connections to your network?; population: account
What this question reaches
- ISO 27001:2022 A.8.5: Secure authentication (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group - ISO 27001:2022 A.5.17: Authentication information (supporting)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group - ISO 27001:2022 A.6.7: Remote working (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.1: Logical access security over protected information assets (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group - SOC 2 CC6.6: Protection against threats from outside the system boundary (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 - NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group - NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization (supporting)
Establishes the password or credential rule asked about; it does not establish the strength or reuse state of every credential held.
Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history - ACSC Essential Eight MFA: Multi-factor authentication (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group - CIS Controls v8 6.4: Require MFA for Remote Network Access (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group - CIS Controls v8 6.5: Require MFA for Administrative Access (supporting)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group - CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications (supporting)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group - PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group - 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: mfa. Owner a broker routes it to: IT identity and access owner.
The same control on other applications
Coalition Q6, Chubb Q21, Chubb Q23, Beazley Q3, Beazley Q4, Hiscox Q25, Hiscox Q28, Hiscox Q29, Hiscox Q40, Hiscox Q67, Great American Insurance Group Q9, Great American Insurance Group Q18.
Map your own answers in the tool. See the Aspen American Insurance Company page, the controls index, the island and the answers.