What is the use of "GRC Profile Generation" scheduled job.

[Rahul Kumar8]

Hi All,

 What is the use of "GRC Profile Generation" scheduled job.

use case: Create profile based on Entity filter,  other use case I don't know.

this schedule job OOTB and run every a hour .

Reduce this scheduled job in time if there is any effect.

please help me to find out.

Thanks,

Rahul 

[careltje]

This scheduled job creates your profiles (or entities nowadays) based on the 'profile filter' (or entity filter) in the profile type (or entity type nowadays) records. 

So ones you define your profile filter in the profile type and click the Ui action in the related links 'generate profiles from profile filter' it will basically trigger the initial run of the script that is called by the job. After this, the job will run every hour, making sure that your profiles and the appropriate controls and risks are generated and assigned.

[Rahul Kumar8]

Hi Careltje,

Thank you for reply,

What is an effect when I change the time of this scheduled job?

Thanks,

Rahul

[Phil Swann]

Nothing, really. As long as it runs and you know when it runs. 

It used to run every 5 mins but was more recently changed to run hourly (NY?)

[Jan Spurlin · Accepted solution]

@careltje is correct. The job runs to keep your profiles up to date. It is possible that if one of your Profile Type filters has an attribute such as "server is operational" based on that operational state attribute on the record, if that server becomes retired, then the profile needs to be retired.

When a profile is inactivated, then all the controls and risks associated with it are retired.  Any open attestations or assessments are canceled. So, it cascades what happens without the user having to do so manually.

It is a good practice to make sure when defining an Entity Filter to consider both what should be included AND when an entity should be retired.

One more note - if an entity is related to multiple Entity Types. It is possible for the entity to become invalid for one, but not the other. When this occurs only the controls/risks/assessments etc associated with the invalid one will be retired/canceled. The records associated with the still valid one will remain in place.