In an r2 assessment, if the responsibility for a Requirement Statement is split between the...

When a Requirement Statement’s responsibility is shared between a client and service providers (e.g., cloud vendors or managed security providers), HITRUST requires ablended scoring approach. Assessors must evaluate all parties’ contributions and assign a composite score that reflects the total control environment. This prevents organizations from over-relying on inherited provider scores without demonstrating their own responsibilities (e.g., configuration, monitoring). It also prevents dismissing requirements as N/A since partial responsibility still exists. By combining the provider’s validated assessment results with the client’s implementation evidence, HITRUST ensures a complete and accurate reflection of risk. Sole reliance on provider scores would overlook gaps in client-side processes.