Skip to main content
Back
DemonstrationAWS
2 min read

Thinkst tests whether a CloudTrail archive proves a complete history

Environment
Thinkst’s AWS logging demonstration
When
Demonstration date unreportedDisclosed Aug 29, 2017
Entry
Thinkst examined the audit history available when an administrator controlled logging and storage in the test environment.

Thinkst examined the audit history available when an administrator controlled logging and storage in the test environment. Thinkst showed that the available archive could be incomplete even when a check of the remaining material succeeded.

What the demonstration did

Research team
Thinkst
Internet
AWS audit archive
CloudTrail archive

Replaying the AWS audit archive demonstration

  1. 1

    Logging administration

    Demonstration date unreported

    Thinkst examined the audit history available when an administrator controlled logging and storage in the test environment.

  2. 2

    Delivered log versions

    Demonstration date unreported

    Thinkst showed that the available archive could be incomplete even when a check of the remaining material succeeded.

Impact

Thinkst’s demonstration showed that an administrator with control over a test logging environment could leave an incomplete audit history. A successful check on the material still available did not establish that every expected record remained.

Would the controls have stopped it?

Preserve delivered log versions and monitor delivery separately

S3 Object Lock in compliance mode can preserve delivered object versions for a defined retention period, including against the account administrator. AWS introduced it in 2018, after this demonstration. Monitor expected deliveries and configuration changes from an independently administered account because retention cannot preserve records that never arrive.

Incident control assessments

0
Prevented
1
Contained
1
Not covered

How it could have been prevented

The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.

Research team
Thinkst
Internet
AWS audit archive
CloudTrail archive

Replaying the AWS audit archive demonstration

1 · Logging administration

1 Not covered

2 · Delivered log versions

1 Contained

Key facts

  • Thinkst presented the research at Black Hat USA 2017.
  • The demonstration assumed broad administrative control over the AWS logging environment.
  • The researchers distinguished validation of available records from proof that the history was complete.
  • Their report discusses independent monitoring and timely review of audit evidence.

Sources

Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.

  1. 1.
    Disrupting AWS S3 LoggingThinkst · Aug 29, 2017 · ResearchFirsthand account of the test environment, observations and disclosure.
  2. 2.
    Validating CloudTrail log file integrityAWS · undated · Vendor reportProvider documentation for the scope and limits of Validating CloudTrail log file integrity.
  3. 3.
    Locking objects with Object LockAWS · undated · Vendor reportProvider documentation for the scope and limits of Locking objects with Object Lock.
  4. 4.
    AWS Announces Amazon S3 Object Lock in all AWS RegionsAWS · undated · Vendor reportProvider documentation for the scope and limits of AWS Announces Amazon S3 Object Lock in all AWS Regions.

The estate in the replay follows the researchers' description of their own test environment. Verdicts describe what a control does when it is in place before the run. They are not an assessment of any company's security program.

More cloud attack breakdowns

All breakdowns