Return single domain or control to correct inheritance
HITRUST should create a feature to allow inheritance by domain/control rather than the whole assessment being returned for a single control/domain inheritance request.
Ria Halcomb commented
For External Inheritance
I suggest someone at HITRUST look into changing the External Inheritance workflow. The current process is extremely cumbersome. When a control is identified the entire assessment has to be flipped back to the entity being assessed. Why not make this process unique & independent? Make each control able to be sent for External Inheritance separately.
Currently we are in the QA process & our external assessor is reaching out to us due to HITRUST stating a single control needs to be assigned for External Inheritance. Only problem is it looks as though the entire assessment will have to be assigned back to us for us to then send this ONE control out for External Inheritance. Stopping the entire process. This is ridiculous.
Also why not gather all of the similar changes together so we can complete the External Inheritance changes all at once. Why send each piece individually adding to the burden of the process?