Your CTO thinks your AWS account was hacked. As CloudTrail has been enabled in the AWS account, you want to analyze the API activities from the logs. How would you ensure that the CloudTrail log files were not modified or deleted after CloudTrail delivered them?

Answer options:

A.Use CloudTrail Log File Integrity Validation.
B.Use AWS Config SNS Subscriptions and process events in real-time.
C.Use CloudTrail backed up to AWS S3 and Glacier.
D.Use AWS Config Timeline forensics.

Answer – A
The AWS Documentation mentions the following.
To determine whether a log file was modified, deleted, or unchanged after CloudTrail delivered it, you can use CloudTrail log file integrity validation. This feature is built using industry standard algorithms: SHA-256 for hashing and SHA-256 with RSA for digital signing. This makes it computationally infeasible to modify, delete or forge CloudTrail log files without detection. You can use the AWS CLI to validate the files in the location where CloudTrail delivered them.
Validated log files are invaluable in security and forensic investigations. For example, a validated log file enables you to assert positively that the log file itself has not changed, or that particular user credentials performed specific API activity. The CloudTrail log file integrity validation process also lets you know if a log file has been deleted or changed, or assert positively that no log files were delivered to your account during a given period of time.
Options B, C and D are invalid because you need to check for Log File Integrity Validation for CloudTrail logs.
For more information on CloudTrail log file validation, please visit the below URL:
http://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-log-file-validation-intro.html