lurkster.

DFIR INTELLIGENCE LAYER · PRE-LAUNCH RESEARCH

Less assembling.
More investigating.

Your forensic tools produce the evidence. Lurkster would help you connect it to answers.

We’re exploring a new layer for cloud evidence preservation, BEC investigations and findings you can trace back to the source. Built around the examiner’s judgement.

Help shape Lurkster

Not built yet. Register your interest to hear what happens next.

FROM SIGNAL TO FINDINGCONCEPT
Cloud logsForensic artefactsCase records
ILLUSTRATIVE REVIEW ITEMExaminer review

A forwarding rule changed.
What happened next?

Connect the event, the session and the source records. Make gaps visible before drawing a conclusion.

Workflow illustration — not a working product or a real case.

FOR THE PEOPLE BEHIND THE FINDINGS

DFIR examiners / Investigation leads / Specialist response teams

01 / THE PROBLEM WE’RE TESTING

The investigation starts.
The manual work piles up.

Logs to preserve. Exports to reconcile. Findings to cross-check. We want to understand where that work slows your team down most.

01

Preserve before the window closes

Could a repeatable collection workflow help you capture cloud evidence, record its provenance and make collection gaps explicit?

INITIAL FOCUS · PRESERVATION
02

Follow the compromise across records

Could structured BEC and account takeover checks help you move from disconnected exports to a reviewable first view of what happened?

PROPOSED NEXT STEP · ANALYSIS
03

Show how you reached the finding

Could source-linked drafts and repeatable tool validation make it easier to check the work and explain your method?

DESIGN PRIORITY · TRACEABILITY

02 / THE APPROACH

An extra layer.
With you in control.

Lurkster is intended to work alongside established forensic tools. These are our proposed design principles, not claims of capabilities available today.

Keep the source in sight

Every proposed finding should point back to its evidence. Uncertainty and logging gaps should be visible.

Validate before use

Test collectors, checks and AI methods against known answers before approving them for client matters.

Protect the evidence boundary

Explore deployment in provider-controlled infrastructure, with governed model access and case-level permissions.

The examiner decides

Automation may organise and draft. A named examiner would review and accept findings and retain responsibility for opinions.

WHAT COULD COME LATER

Cross-source timelines, exfiltration correlation and evidence-linked report drafting. Your feedback will help decide the sequence—and what is worth building at all.

03 / HELP DECIDE WHAT GETS BUILT

Would this earn
a place in
your workflow?

Join the interest list for development updates and a launch notification if Lurkster is released.

Tell us which problem matters most. If you’d like to go further, volunteer for a short research conversation about your current workflow.

Where things stand

Lurkster is a product concept. There is no working product, confirmed release date or pricing yet. Registration is free and does not reserve access or commit you to buy.

A FEW THINGS TO KNOW

Can I try Lurkster today?

Not yet. We’re validating demand before building the product. This website collects interest and research preferences; it does not process evidence or offer incident response.

Is this a replacement for my forensic tools?

The concept is an intelligence layer alongside established collectors, parsers and case systems. Specific integrations are still to be decided. No vendor partnership or integration is being claimed.

What about AI and sensitive evidence?

The proposal uses deterministic checks for facts, with AI limited to organising, explaining and drafting from cited records. Evidence controls and validation would need to be implemented and tested before client use. Don’t send us evidence through this website.

What happens after I register?

We’ll retain your details for the updates you requested. If you separately volunteer for research, we may contact you about a conversation. You can request removal at any time. Signup does not mean the product will definitely be built.