Parent and Child Control Objectives

[Bob3451]

I am working on testing Parent and Child Control Objectives, but with not much success.  I created a Child CO and associated it to a Parent CO.  The Parent CO is already associated to the Business Application Entity Type and I can see the Child CO is associated to the Parent CO when I view it.  

I created a new application and associated it to the Entity Type.  My was hoping to see that controls for the Child CO would be generated, but I am only seeing the Parent controls.  The concept that I am trying to test for is the following:

• Parent Control Objective is Created by UCF (Enable data at rest encryption)
• Child Control Objective is Manually created to provide technical control actually used, so in this case let's say 2 Child COs (AES-256, AES-128)
• The controls for each are automatically generated when the CO is associated to an Entity Type, but since the Child is associated to the Parent it is not necessary to manual associate it to the Entity type.
• The Child controls are automatically added to the assets associated with the Entity Type.

My theory is that it does not work like this and requires that I manually associate the Child CO to the Entity Type.  If that is correct, does anyone else seen benefit it submitting this a requirement for consideration?

[Community Alums · Accepted solution]

Hi @Bob3451 ,

Your theory is correct, you will need to manually associate the Child CO to the Entity Type to generate controls.

Now, it has to work in that way, because you might want to associate a diffrent Enity type to child CO, as it's not always the same entity type gets associated what's been used for parent CO.

Rather, if this happens then you will end up getting unnecessary controls generated which will generated numerous notifications for so many entity owners.

[Bob3451]

Thanks Sandeep.  Appreciate the confirmation.

Bob

[Community Alums]

Welcome @Bob3451 , Glad to see i could help you with your learning journey 😀

[Kiril Dimov]

I have a question here: If we have Parent CO and the Entity type is linked to the Parent CO, it will generate automatically Controls for this Parent CO. But actually we need Controls for the Child COs and not for the Parent CO, as if we have for both these controls will be overlapping somehow - one more generic Control (for the Parent CO) and 2 more granular for the Child COs. So how can we cope with that?