COMING SOON · Q1 2027 Planned releaseGet notified + 10% launch offer ↗
← Acorn overview

Acorn application guide

Event Log Viewer

An event match is a place to start reading. Event Log Viewer keeps the underlying record and decoded command context close to the review, so an examiner can separate what was recorded from a proposed action, duplicated rule match or inferred outcome.

Demonstrated on public training data

Which Windows events support a concern, and what does a decoded command actually contain?

Start with

  • Windows event records, including PowerShell-related records from public test logs.

What you can take away

  • Native event-detail and decoded-command views with rule matches.
Eighteen rule matches identify archive-decoding PowerShell command lines in public training logs. The selected record preserves the encoded command, source event and a decoded gzip script fragment. View full screen
Eighteen rule matches identify archive-decoding PowerShell command lines in public training logs. The selected record preserves the encoded command, source event and a decoded gzip script fragment.

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.

  1. Choose the event source and the period or behaviour being investigated. Retain the source file and the identifiers needed to revisit the selected records.

  2. Inspect the matched events and any decoded command text. Distinguish several matches on one event from several separate actions.

  3. Check the interpretation against related logs or other evidence, and independently inspect a material record where appropriate. State what the available logging does and does not establish.

Evaluate the workflow

Questions worth bringing to a demonstration.

  • Can I revisit the selected event in its source rather than relying only on the rule-match label?
  • How are duplicate matches, recorded times and decoded command text distinguished during review?
  • Which further record would support or contradict the proposed execution or incident sequence?

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.

Zoom in, then scroll to inspect the detail.

Open full-resolution image ↗

A useful first conversation

Let’s look at your workflow.

Tell us what you examine, where you work and what you need to deliver.

Use the enquiry form to outline your role, intended use and potential order quantity. Do not send case material through a general enquiry.

Your enquiry goes to the SQFR team. Please do not include passwords or case evidence.