Do you identify & categorise third party vendors based on their access to company systems and/or data?
This is application question 83 of 121 on the Munich Re MRS Insurance Application Cyber Risk. It is a control question and reaches 12 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.
Facets: control: Do you identify & categorise third party vendors based on their access to company systems and/or data?
What this question reaches
- ISO 27001:2022 A.5.12: Classification of information (direct)
Establishes the classification or labelling practice named; it does not establish that every asset is correctly classified.
Evidence to have on file: the classification scheme and the handling rule for each level; a sample of an asset or record carrying its classification - ISO 27001:2022 A.5.13: Labelling of information (supporting)
Establishes the classification or labelling practice named; it does not establish that every asset is correctly classified.
Evidence to have on file: the classification scheme and the handling rule for each level; a sample of an asset or record carrying its classification - ISO 27001:2022 A.5.19: Information security in supplier relationships (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - SOC 2 CC6.1: Logical access security over protected information assets (direct)
Establishes the classification or labelling practice named; it does not establish that every asset is correctly classified.
Evidence to have on file: the classification scheme and the handling rule for each level; a sample of an asset or record carrying its classification - SOC 2 CC9.2: Assessing and managing vendor and business partner risk (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - NIST CSF 2.0 ID.AM-05: Assets are prioritized based on classification, criticality, resources, and impact on the mission (direct)
Establishes the classification or labelling practice named; it does not establish that every asset is correctly classified.
Evidence to have on file: the classification scheme and the handling rule for each level; a sample of an asset or record carrying its classification - NIST CSF 2.0 ID.AM-07: Inventories of data and corresponding metadata for designated data types are maintained (supporting)
Establishes the classification or labelling practice named; it does not establish that every asset is correctly classified.
Evidence to have on file: the classification scheme and the handling rule for each level; a sample of an asset or record carrying its classification - APRA CPS 234 para 20: Classify information assets by criticality and sensitivity (direct)
Establishes the classification or labelling practice named; it does not establish that every asset is correctly classified.
Evidence to have on file: the classification scheme and the handling rule for each level; a sample of an asset or record carrying its classification - APRA CPS 234 para 16: Assess the security capability of related and third parties (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - APRA CPS 234 para 22: Evaluate the design of third-party controls (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - APRA CPS 234 para 28: Assess reliance on third-party control testing (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review
Subject: classification. Owner a broker routes it to: IT asset management owner.
The same control on other applications
Great American Insurance Group Q4, Corvus Insurance Q10, Munich Re Q21, Arch Insurance Q41, Trisura Guarantee Insurance Company Q22, Trisura Guarantee Insurance Company Q23, Trisura Guarantee Insurance Company Q33, Aspen American Insurance Company Q21, BOXX Insurance Q19, Delta Insurance Q22, Liberty Mutual Insurance Europe Limited Q37, Liberty Mutual Insurance Europe Limited Q38.
Map your own answers in the tool. See the Munich Re page, the controls index, the island and the answers.