What is the process behind for generating controls in GRC ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Team,
When I add an entity manually to an entity type which is associated with control objective, generates a control for that entity.
Please help me to understand the underlying process. How the control is generated and with the control owner as an entity owner.
Thanks,
Majji
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @KoteswaraMa
Level1:
Control Objective is the Template that defines what should be adhered to.
Entity Type is the reference to the list of records with or without a defined filter of ServiceNow. Every record of it is called Entity.
Ex: Entity Type is Windows Servers, with Entity Owner defined here.
All the windows servers becomes Entities.
Level2:
When the Entity Type and Control Objective are connected, Every Entity generated through the Entity Type gets a control attached to it with Entity Owner as the Control Owner, also Risk Owner if a Risk Statement would be have attached to the Entity Type.
If the above information helps you, Kindly mark it as Helpful and Accept the solution.
Regards,
Najmuddin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thanks for your response. I understood the steps/flow how the control can be created. However, I am looking for the back end mechanism responsible for controls creation and assignment of the entity owner as control owner. I would appreciate if you can provide the backend process.
Thanks,
Majji
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
backend process for control generation in ServiceNow GRC:
How Controls Are Generated
When you link an Entity Type to a Control Objective, ServiceNow’s Item Generation engine (a.k.a. Control Synthesis) creates a Control record for each matching entity.
The new control is stored in sn_grc_control.
How Control Owner is Assigned
By default, the Entity Owner (owned_by field on the entity) is copied into the Control Owner (owned_by on the control).
This happens because the “Sync with Entity Owner” option is enabled by default.
If unchecked, you can assign a different owner manually.
Mechanism Behind the Scenes
Driven by backend scripts/flows (e.g., item generation engine, script includes, BRs).
Works automatically and often runs asynchronously.
No need to manually create controls—relationships drive the creation.
In short:
Entity + Control Objective → Control auto-generated.
Entity Owner → becomes Control Owner (via sync).
Shashank Jain
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thank you for providing the details. Can you please share which script exactly creating control and updating the control owner when an entity is add manually to an entity type which is associated with control objective?
Thanks,
Majji