foreign share the wealth today we will be talking at a high level about GRC irm's new Utah feature for policy compliance application and common controls as it has stood previously you would be only able to do standard controls where you tied the entity type to the control objective or vice versa The Entity is within that entity type would then create that one-to-one relationship with the control derived from the control objective as you see here however this can become tedious especially if all the controls buy by the same attestations for those controls this is where common controls come into play here you see a standard control converting into a comma control via this function Arrow which we'll dive into more in Greater detail in the demo this now common control can now have what's called a reliant entity type and a reliant entity this way you will only have to attest to the control once and have it roll into each of these entities so let's look at how this works in the servicenow compliance workspace now we are in the compliance workspace and servicenow I'll begin by going into the list View and searching to my controls earlier I talked about the function arrow and this is the new field that came in Utah release where you can choose between a standard and converting it to a common control so let's dive into a controlled a standard control here is the overview of the control but if we want to change it to a common control we will go to more actions to converts to Common and here it'll double check to see if we want to convert it to Common to where it will allow us to add Reliance entities once we successfully converted to a common control these two new related lists will appear saying Reliant entities and Reliant entity types so there are two ways to adding a reliant entity and that's via this add button to look at your whole list of entities or if we know the control objective and we only want to look at a finite amount of controls or entities Reliance entities we can click this ad from existing control to which I will choose the San Diego and London office to add here you'll now see that the Reliant entities of the San Diego office and the London office are now added as Reliant entities now if we wanted to add a entity type we can do so here hitting the add button and for the sake of the demo let's add business applications and you'll start to have your Reliant ftds coming through from that entity type this added from entity type is a great way to differentiate how these Reliance entities have come in the first place once you relate all of your Reliant entities and Reliant density types you can now move forward with attesting the comma control which will roll up into each of these Reliant entities that are tied to it you have now seen how to convert a standard control into the common control final things to note is that this will only work in the workspace as well as you can only relate the lines entities if the controls are in either draft state or a test state thank you for watching our share the wealth surrounding the newest Utah feature and policy compliance application for GRC irm if you wish to learn more about our GRC irm practice feel free to reach out to anyone on our team and we'll route you to the center of excellence for GRC irm be sure to like And subscribe to be on the lookout for our next GRC irm video in relating comma controls to your risk register [Music] thank you foreign [Music]