Which of the following is NOT commonly leveraged in Entity filters?

• A. Company [core_company]
• B. Services [cmdb_ci_service]
• C. Location [cmn_location]
• D. Audit Engagement [sn_audit_engagement]

Answer: (D)

Entity filters are designed to narrow the scope of what you’re evaluating by using attributes that define the organizational and service context of the items being managed. When you filter entities, you’re typically selecting records based on where they belong in the business, what service they deliver, or where they’re located.

Company and location are classic scope dimensions you’d expect to filter by. Filtering by a company narrows to a single tenant or customer, while filtering by location pinpoints sites or geographic boundaries. The service field (cmdb_ci_service) is also a common filter because it lets you focus risk or controls on specific services or service lines within the organization.

Audit Engagement, on the other hand, comes from the audit management space and is used to group audits and related work streams. It isn’t a standard dimension used to define the scope of entities in IRM filtering. Therefore, it’s not commonly leveraged in Entity filters.

So, the best fit for common entity-filter usage is the combination of company, service, and location, while audit engagement isn’t a typical filter dimension.