---
sourceDocument: Yokohama Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/governance-risk-compliance

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Entity tiers in GRC

# Entity tiers in GRC {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

By creating entity tiers, you can prioritize the entity classes.

When you create entity tiers, you apply a level or hierarchy to the entity classes. This level
applies to all the entities in those entity classes. Entity tiers enable you to select and view
the risk status of the most critical items in the business. Consider the following example.
Assume that the Chief Risk Officer (CRO) of your organization wants to see the risk status of
only the most critical financial business applications. If you have created a hierarchy or set of
tiers for the entities, then you can filter the tier 1 entities and present the required data.
Each entity class can belong to only one tier.

By creating entity tiers, you can better understand how your lower tier entities affect your
higher tier entities. For example, assume that you created the entity hierarchy where Business is
tier 1, Application is tier 2, and IT asset is tier 3. Therefore, the risks of the entities of
tier 3 affect the entities of tier 2 and that in turn affects tier 1. This roll-up or aggregation
provides accurate risk scores.