LogLens

Open-weight Llama 3.1 8B · SHA-256 sealed · MITRE ATT&CK

Find who changed what.Prove the log was not touched.

Rules flag events, open-weight AI (Llama 3.1 8B by Meta, Llama licence) explains them, a SHA-256 hash with a signed server receipt seals the evidence.

Case No case open Waiting for evidence

Open a case

Intake

Pick a sample case (three made up for the demo, one real public log) or paste / upload your own log.

Sent with each server receipt: this name, the file name, size and SHA-256 go to a shared demo ledger (no login). The log text does not.

Formats, storage & privacy

Timelines: ERP audit CSV, Linux auth.log, Apache/Nginx access and Apache error logs. Any other file (PDF, image) is hashed as evidence.

Saved in this browser only (localStorage): a copy of the locked log, its SHA-256 and the audit trail, so the case survives a reload. New case clears them.

  1. 01

    Open the log

    ERP audit CSV, Linux auth.log, Apache/Nginx access or Apache error log. It is hashed (SHA-256) the moment it opens.

  2. 02

    Rules flag events

    16 explainable rules, each with a reason and a MITRE ATT&CK ID; flagged events are joined into an attack chain.

  3. 03

    Open-weight AI explains

    Llama 3.1 8B writes the story in English or Hindi, cross-checked against the rules. AI down: a labelled rule summary shows.

  4. 04

    Seal and verify

    Signed server receipt, then verify the same file again: MATCH or TAMPERED, with the changed line.