RCP must limit KMS key access to the Organization for regulated accounts
이 페이지는 아직 한국어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우
언제든지 연락주시기 바랍니다.Description
A Resource Control Policy (RCP) must be applied to all regulated AWS accounts to limit KMS key access to the AWS Organization. Without an RCP restricting KMS operations by organization boundary, principals outside the organization could potentially encrypt, decrypt, or generate data keys using KMS keys in member accounts. An RCP that denies KMS data-plane and grant operations if aws:PrincipalOrgID does not match the organization ID establishes a mandatory data perimeter for regulated workloads.
This rule also flags RCPs that use NotAction to exempt KMS actions from a deny statement. A NotAction-based exemption creates a gap that could be exploited if the corresponding explicit deny is ever removed.
Note: This is a mandatory control for regulated accounts. AWS service principals should be exempted using aws:PrincipalIsAWSService conditions. Trusted external accounts can be exempted using aws:PrincipalAccount conditions where required.
Create a Resource Control Policy that explicitly denies KMS operations using Action (not NotAction) from principals outside the organization and attach it to the OUs containing regulated accounts. Remove any NotAction-based deny statements that exempt KMS actions. The RCP should deny kms:* or specific KMS data-plane actions with an aws:PrincipalOrgID condition. Refer to the RCP syntax documentation and the data perimeter policy examples for guidance.
