(2) Do you utilize IP whitelisting to further protect remote access connections?
This is application question 14 of 45 on the Tokio Marine HCC NGP-NBA. It is a control question and reaches 11 controls. The wording is the carrier's, quoted verbatim.
Held from the NetGuard Plus Cyber Liability Insurance Application (US) (read 2026-10-11), jurisdiction United States. All Tokio Marine HCC questions.
Facets: control: (2) Do you utilize IP whitelisting to further protect remote access connections?
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 - 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 DE.CM-01: Networks and network services are monitored to find potentially adverse events (supporting)
Establishes the network control asked about; it does not establish the full architecture or that no path bypasses it.
Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path - CIS Controls v8 12.2: Establish and Maintain a Secure Network Architecture (supporting)
Establishes the network control asked about; it does not establish the full architecture or that no path bypasses it.
Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path - CIS Controls v8 12.4: Establish and Maintain Architecture Diagram(s) (supporting)
Establishes the network control asked about; it does not establish the full architecture or that no path bypasses it.
Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path - CIS Controls v8 12.5: Centralize Network Authentication, Authorization, and Auditing (AAA) (supporting)
Establishes the network control asked about; it does not establish the full architecture or that no path bypasses it.
Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path - PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components (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 - PCI DSS 4.0 Requirement 1: Install and Maintain Network Security Controls (supporting)
Establishes the network control asked about; it does not establish the full architecture or that no path bypasses it.
Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path
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 Q15, Tokio Marine HCC Q16, Tokio Marine HCC Q18, AXIS Insurance Q24, AXIS Insurance Q25.
Map your own answers in the tool. See the Tokio Marine HCC page, the controls index, the island and the answers.