Acorn application guide

Log2Timeline

Good timeline work starts with an explicit source and time basis. The Plaso setup route exposes those decisions before processing.

Processing options shown

Which input, parser settings and time basis should a timeline processing run use?

Start with

A proposed source, parser choices, hashing controls and time-zone settings in the Plaso setup interface.

What you can take away

Processing options only; this capture did not run log2timeline or psort.

The native Plaso front end identifies the source folder and exposes parser, output, hashing and time-zone settings before timeline processing. Extraction and display time zones are separate controls.

Open the screenshot and choose “View actual size” to read the records at their original resolution.

A practical starting point

How the workflow fits together.

Identify the source and the examination period.
Review parser, hashing and time-zone settings for that source.
Validate the processing run and inspect its actual output before drawing a chronology.

Useful next steps

Start with your requirements

Bring a sample question.

Ask us to demonstrate this workflow with suitable public or constructed material. Do not send confidential evidence in an initial enquiry.

Planned for Q1 2027

Be first to hear. Save 10% at launch.

Request Acorn launch news and details of the planned 10% offer. No deposit or purchase commitment.

Notify me at launch ↗

Launch-update requests go to the SQFR team for review. Final offer terms and product availability are still to be confirmed.

About the screenshots and illustrations

Application screens are selected from the September 2026 Acorn screenshot pack. Captions distinguish native setup views, constructed training records and public-corpus results. They are not private client cases, and a displayed control does not establish that every operation was completed.

Relevant public sources include DeepBlueCLI training event logs and Plaso test data. Check the relevant source terms before redistributing an underlying dataset.

Workspace scenes and sector mascot variants are generated illustrations. They do not show actual police, judicial, military or university deployments or endorsements. The original Squirrel Forensics identity is retained.