Why would you create Entity classes?

Why would you create Entity classes?

• A. To show relationships between tables or objects you are tracking that doesn't otherwise exist anywhere in ServiceNow
• B. To be assigned to risk statements, which generate risks for every Entity listed in the Entity Class
• C. To be assigned to Control Objectives, which generate Controls for every Entity listed in the Entity class
• D. To show relationships between Entities and Policies and map them directory to Citations

Answer: (A)

Entity classes are used to model relationships between entities when the ServiceNow data model doesn’t already provide a built-in link. By creating an Entity Class, you establish a structured way to relate disparate entities you’re tracking, so you can understand how one entity connects to another and how those connections influence risk and controls. This makes it possible to reason about risk across related entities and to map those relationships into risk statements, controls, or policies later, without assuming the class automatically creates risks or controls for every entity. The class simply defines the relationships; risks, controls, and citations are added or linked based on those relationships rather than being generated by the class itself.

Entity classes are used to model relationships between entities when the ServiceNow data model doesn’t already provide a built-in link. By creating an Entity Class, you establish a structured way to relate disparate entities you’re tracking, so you can understand how one entity connects to another and how those connections influence risk and controls. This makes it possible to reason about risk across related entities and to map those relationships into risk statements, controls, or policies later, without assuming the class automatically creates risks or controls for every entity. The class simply defines the relationships; risks, controls, and citations are added or linked based on those relationships rather than being generated by the class itself.