Do you log the activity of service accounts that are able to override system or application controls (e.g. elevation Yes No of privileges, lateral movement etc.?
This is application question 42 of 121 on the Munich Re MRS Insurance Application Cyber Risk. It is a control question and reaches 15 controls. The wording is the carrier's, quoted verbatim.
Held from the Insurance Application - Cyber Risk (UK) (read 2026-10-11), jurisdiction United Kingdom. All Munich Re 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: Do you log the activity of service accounts that are able to override system or application controls (e.g. elevation Yes No of privileges, lateral movement etc.?; population: accounts
What this question reaches
- ISO 27001:2022 A.8.2: Privileged access rights (direct)
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 - ISO 27001:2022 A.8.3: Information access restriction (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 - ISO 27001:2022 A.5.15: Access control (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.3: Role-based access, least privilege and segregation of duties (direct)
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 (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-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 (direct)
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 DE.CM-01: Networks and network services are monitored to find potentially adverse events (supporting)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged - ACSC Essential Eight ADMIN: Restrict administrative privileges (direct)
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 APP: Application control (supporting)
Establishes that application control is used where the wording names it; it does not establish the coverage of every host or that the ruleset is current.
Evidence to have on file: the application-control ruleset and the hosts it is applied to; a sample of an allowed or blocked execution event and its handling - APRA CPS 234 para 23: Detect and respond to incidents promptly (supporting)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged - CIS Controls v8 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts (direct)
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 (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 8.2: Collect Audit Logs (supporting)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged - PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components (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 - 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: privileged_access. Owner a broker routes it to: IT identity and access owner.
The same control on other applications
Great American Insurance Group Q20, Great American Insurance Group Q21, Tokio Marine HCC Q17, AXIS Insurance Q28, Corvus Insurance Q8, QBE Q2, QBE Q19, QBE Q21, CNA Q8, CNA Q26, Encore Fiduciary Q32, Encore Fiduciary Q33.
Map your own answers in the tool. See the Munich Re page, the controls index, the island and the answers.