An organization investigating access to a cloud file may find detailed records of bucket configuration changes but no record of the file read itself. Cloud logging products can treat management operations and data operations as separate event categories with separate configuration.

Begin with the investigation questions your logs need to answer. Check whether the configured events can show who read a file, as well as who changed its storage permissions.

Match event categories to investigation needs

AWS CloudTrail distinguishes management events from data events, including supported object-level operations. Data-event coverage depends on configured selectors and service support, and can have separate charges. AWS's data-event documentation describes this scope.

An illustrative document service needs to establish who changed storage permissions and who read a sensitive test object. Those questions can require different events. A log showing the permission change cannot be used as evidence that a later read did or did not happen.

Inventory selection and retention

Record which accounts, regions, resources, and operations are included. Identify exclusions and sampling where applicable. Then record where events are delivered, how long they remain searchable, and who can modify the logging configuration or delete retained records.

The configured retention period is only part of the investigation window. Delivery failures, disabled collectors, and query restrictions can reduce usable coverage. A team needs to know both what was intended to be recorded and what evidence actually arrived.

Generate representative events safely

Create a harmless test object and use a dedicated identity to perform agreed read, write, and configuration actions. Note the timestamps and request identifiers. Retrieve the resulting events through the same interface the response team would use during an investigation.

Verify that the event identifies the relevant principal, operation, resource, and outcome. Some workflows involve assumed roles or delegated services, so the visible identity may need additional context to connect it to a human or application request. Document that correlation path.

State the limits of a negative finding

If no event is found, check whether the operation was in scope for logging, whether delivery completed, and whether the query covered the correct location and interval. The absence of an event in an incomplete dataset does not establish that the action never occurred.

Make a table linking each investigation question to its event source, tested coverage, and retention period. Use the gaps to decide where cloud data events or application logs are needed. Keep it available to the response team.

Sources

AWS: CloudTrail Event History. The document service and test events are illustrative.

Back to the blogExplore Ceron