Is multi-factor authentication (MFA) required for access to privileged user accounts?
This is application question 17 of 41 on the Aon Aon Cyber Application. It is a control question and reaches 14 controls. The wording is the carrier's, quoted verbatim.
Held from the Aon Cyber Application (revenues under $250M) and Cyber Application for Small Businesses (revenues under $100M) (read 2026-10-12), jurisdiction Canada. All Aon 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: Is multi-factor authentication (MFA) required for access to privileged user accounts?; population: user
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.8.2: Privileged access rights (supporting)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - 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.3: Role-based access, least privilege and segregation of duties (supporting)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - 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-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties (supporting)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - 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 control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - CIS Controls v8 6.5: Require MFA for Administrative 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.4: Require MFA for Remote Network 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 control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access
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 Aon page, the controls index, the island and the answers.