AWS Certified Security - Specialty free question 1 / 10 · Domain 1: Detection
A contracts bucket is owned by the business account. A trail in the audit account lists this bucket as a target for data events. A user in the business account runs GetObject on an object in the bucket. What does the audit account's trail do?
- It does not log the event. The activity did not happen in the audit account, and the audit account does not own the bucket
- It logs the event. Every trail that specifies the object receives the same copy, whether or not the owner has its own trail
- It logs the event. Activity on an object specified in the audit trail is covered, whichever account performs it
- It does not log the event. A bucket owned by another account cannot be specified for data events
Show the answer and explanation
Answer: A
Why this is correct
When you configure a trail to log data events, you can also specify S3 objects that belong to other AWS accounts. When an event occurs on a specified object, CloudTrail evaluates whether the event matches the trails in each account, and the trails that match log the event for their own account. A trail that specifies objects its own account owns logs activity from other accounts as well. A trail that specifies objects owned by another account logs only activity that happens in its own account, not activity in the other account. The business user's GetObject is neither activity in the audit account nor activity on an object the audit account owns.
Why the other options are wrong
"It logs the event. Activity on an object specified in the audit trail is covered, whichever account performs it" … Logging activity from any account applies only when the trail specifies objects its own account owns. For objects owned by another account, the trail logs only activity that happens in its own account.
"It logs the event. Every trail that specifies the object receives the same copy, whether or not the owner has its own trail" … CloudTrail evaluates the trails in each account against the event, and a matching trail logs it for its own account. A copy is not delivered to every trail that merely lists the object.
"It does not log the event. A bucket owned by another account cannot be specified for data events" … A data events trail can specify S3 objects that belong to other AWS accounts. That is possible, so it is not the reason the event goes unlogged.
Key point
In general, both the caller and the resource owner can receive the event. To keep a record of activity inside the owner's account, log it with a trail in the owner's account. If trails in two accounts log the same event, you pay data event charges twice.