Subscribe

Follow by feed

New articles arrive in your reader without an email address, an account, or anything that records whether you opened them.

Paste this into your feed reader

https://securityartifacts.com/feed.xml

Most readers also find it on their own if you give them securityartifacts.com.

What is in the feed

Full archive
  • Mini-guide: pivoting on the logon ID, or how one number turns a log into a session

    The Security log records events. An investigation needs sessions. The logon ID is the join between them: how to follow one from the logon through every process it started to the logoff, and the three places the thread breaks.

    14 October 2026

  • Guided lab: the svchost that lived in Public

    Data staged with an archiver and sent out with a renamed copy of a legitimate sync tool. Identify the binary from one field, reconstruct what was taken from a command line, and be exact about what endpoint telemetry cannot tell you about volume.

    9 October 2026

  • Guided lab: the credential dump that used nothing but Windows

    An LSASS dump taken with a DLL that ships in System32, called by ordinal so the obvious rule misses it. Work out which process touched LSASS, which access mask matters, and whose credentials you now have to assume are gone.

    21 September 2026

  • Mini-guide: the five fields of a 4624 that decide what a logon means

    Event 4624 has more than twenty fields and most triage reads two of them. The five that change the conclusion, what each one is really recording, and the values that catch people out.

    21 September 2026

  • Guided lab: six service tickets in four seconds

    A burst of Kerberos service ticket requests from one workstation, every one of them legitimate as far as the domain controller is concerned. Find what makes the cluster abnormal, separate it from a legacy application, and say what the log cannot tell you.

    21 September 2026

  • Mini-guide: a PowerShell alert in ninety seconds, in the order that settles it fastest

    Most PowerShell alerts are administration. Five questions, ordered so the cheapest one that can close the alert comes first, with the answer that means stop and the answer that means keep going.

    21 September 2026

  • Guided lab: forty failures, no lockouts, one success

    A password spray that stayed under the lockout threshold and never produced a failed-logon event on the server it was aimed at. Find where the failures were recorded, identify the account that fell, and explain why the dashboard showed nothing.

    21 September 2026

  • Guided lab: a service that existed for nine seconds

    Remote execution over the admin share, reconstructed from the target. Tie four events in three logs into one action, work back to the host it came from, and handle the version where the service is not called PSEXESVC.

    21 September 2026

  • Evidence Gap Challenge No. 2: the proxy only kept the domain

    A developer laptop, a package that should not have been installed, and a proxy that logged where the traffic went but not what was asked for. Work out what the truncation costs you, what you can still prove, and whether a full-URL log would have been worth what it costs to keep.

    12 September 2026

  • Case study: one appliance, and the disclosure that followed

    CL0P against MOVEit Transfer, worked as a case rather than read as news. A zero-day in an internet-facing file transfer product, a web shell, and a scope question that has nothing to do with how many hosts were touched. Nine questions, and the answers are in the advisory.

    12 September 2026

  • Evidence Gap Challenge No. 3: four people knew that password

    An operational technology jump host, a shared engineering account, and a change nobody will own. Every log works, every timestamp is right, and attribution is still impossible. Work out what that costs, and what you would have needed to collect to make a name provable.

    12 September 2026

  • Case study: the update was signed, and that was the problem

    A trusted software update that carried a backdoor, worked as a case. Signing proved the build was the vendor's; it proved nothing about what was in it. Eight questions on detection, scope and the uncomfortable part, which is that nothing your endpoint controls were watching for was wrong.

    12 September 2026

  • The operator set the clock, and set only one of them

    Timestomping is a decision, not an accident, and the decision is visible. NTFS keeps eight timestamps per file and the ordinary Windows API writes four of them. What the other four say about the tool the operator chose, the checklist they were working from, and where they stopped.

    9 September 2026

  • Evidence Gap Challenge No. 1: the laptop was reimaged on Tuesday

    A supplier is out €96,000 and the only endpoint that mattered was wiped on day one, by a helpdesk following the documented process correctly. Here is every artefact that still exists. Work out what you can prove, what you can only say is consistent, and the one collection change that would have moved the most from the second column to the first.

    9 September 2026

  • False-Positive Hall of Fame No. 1: six alerts that were the software working

    Chrome opens a pipe that Cobalt Strike also opens. Chrome's updater reads LSASS. Discord ships a signed binary that launches other binaries. Six alerts that fire on normal software, each with the benign explanation and the discriminator, and a count of how often the public rulebase admits any of this.

    9 September 2026