(b) segregated with 2-factor authentication access control?
This is application question 25 of 45 on the Tokio Marine HCC NGP-NBA. It is a control question and reaches 14 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.
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.
Flagged warranty: an answer the carrier relies on, which can affect underwriting or cover if wrong. What a warranty flag means here.
Facets: control: (b) segregated with 2-factor authentication access control?
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.5.15: Access control (supporting)
Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed - 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.2: Registering and authorising users before issuing credentials (supporting)
Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed - 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 access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed - 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 - ACSC Essential Eight ADMIN: Restrict administrative privileges (supporting)
Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed - 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 7: Restrict Access to System Components and Cardholder Data by Business Need to Know (supporting)
Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed
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 Tokio Marine HCC page, the controls index, the island and the answers.