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

Rahul Kumar8 · ‎10-19-2020

Hi All,

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

Jan Spurlin · ‎10-19-2020

@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.

View solution in original post

Rahul Kumar8 · ‎10-19-2020

Hi Jan,

Thank you for reply,

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

Thanks,

Rahul

Jan Spurlin · ‎10-19-2020

Well... if you don't run the job, then you are at risk of having controls and risks that should be retired that are not.

Here are some things to consider when deciding how to set the frequency of that job:

If you are in the implementation phase and filters are being added/changed frequently - then leave it as is.
If you are past implementation then consider setting it to a frequency that is tied to the frequency of change of the source table of the filters.

The filters are frequently tied to the CMDB tables or one of the Foundation tables - (Company, Department, Location, etc).
How often are these tables updated? If they are only updated daily -then setting the GRC job to run less frequently than every hour makes sense.

Keep in mind that if there is a one-time special mass update of the source tables you can always force run the job.

Phil Swann · ‎10-22-2020

Great reply, didn't see this one first.

RE:

Keep in mind that if there is a one-time special mass update of the source tables you can always force run the job.

This is as a system admin, not a regular user.

edit, ps. I always execute manually during demos and show & tells / development

Phil Swann · ‎10-22-2020

we need a proper post on Entities, talking about the flow... probably I will be covering this on the GRC/IRM: Full Flow series, as GRCUtils is coming up soon... will try and prepare some clips which break down and explain things like ownership and what I often refer to as 'first past the post' when things like multiple Entity Types get concerned...

Phil Swann · ‎10-22-2020

Be aware the API changes in V11, to a restricted ImportProfiles API but this is just making a call back to the original GRCUtils API