QuestionQ79

VerifiedIncident Response

A security engineer is responding to an incident affecting an AWS account. The account ID is 1234156789012. The attack created workloads distributed across multiple AWS Regions.

The security engineer contains the attack and removes every compute and storage resource from all affected Regions. However, the attacker also created an AWS KMS key. Its key policy explicitly grants an IAM principal kms:* permissions.

The key was scheduled for deletion the day before, but it remains enabled and usable. Its ARN is arn:aws;kms:us-east-2:123456789012:key/mrk-0bb0212cd9864fdea0dcamzo26efb5670. The security engineer needs to delete the key as quickly as possible.

Which solution meets this requirement?

Explanation

An AWS KMS key whose ID begins with mrk- is a multi-Region key. AWS KMS does not delete a multi-Region primary key until all of its replica keys have been deleted. Scheduling deletion for each replica with the minimum allowed 7-day waiting period is therefore required to allow the primary key deletion to complete as soon as AWS KMS permits.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!