#DFIR #ThreatHunting | @SANSInstitute instructor | SANS Course Author | CISSP (etc) holder | https://xitter.cf/t.co/00tACAnVLd | Rarely used account.

North East Wales or Bluesky
Joined November 2009
Some good news today in that one of the few remaining holdouts making me keep access to Twitter has finally moved to a new platform. If you want hasty responses from me, you will be better off finding me elsewhere.
3
27
1,677
Attackers now weaponise new vulnerabilities within days of disclosure. That changes patch management from an IT chore into a business decision, and it raises a harder question: how do you know nobody got in before you patched? halkynconsulting.co.uk/a/202…
5
440
Registers are the CPU's working storage, and every debugger, crash dump and disassembly listing assumes you know them. This guide tours the x86-64 register set from an analyst's perspective. halkynconsulting.co.uk/a/202…
2
3
343
Before trying to fill another role, see what the people already on the team can do. That is Christopher Bloor's advice.
1
3
9
6,302
The systemd journal holds a great deal of investigative value, provided retention settings kept it. This guide covers journalctl for responders, offline analysis, and the configuration that determines whether the evidence survived. halkynconsulting.co.uk/a/202…
1
3
318
A few of the #DFIR books that shaped my work plus 373 more books that helped too. dfir.training/blog/what-400-…
3
6
30
1,697
I went through 400 #DFIR books spanning 46 years. I think DFIR has drifted away from investigating human behavior and acts and toward artifacts and computer events. That bothers me. Here’s what I found. 🧵
2
18
2
69
7,858
Today’s FIND EVIL! winners broadcast is off. Our broadcast platform failed.
3
3
3
3,935
made a tool to monitor for ms telemetry.....
1
1
1
40
8,239
I hate doing videos…. But seriously someone needs to speak about this who has, actually done this stuff for a living, with actual hands on plan, design, deploy, test, defend, depend experience…..
Read this carefully. An AI agent broke out of its testing environment, found a vulnerability humans had missed and used it to hack into another company… all by itself. What stopped it wasn’t a human but another AI agent, running defensive systems on the target's infrastructure. That 👆 is the security model of the next decade in one paragraph. Agent versus agent, at machine speed, with humans reading the report after it all happened. Sam Altman will brief Washington on this next week, but the UK needs to have the same conversation, a domestic frontier lab and sovereign compute at the scale this now demands. Right now, we are sitting downstream of decisions taken in San Francisco which are vetted in Washington. That’s why it’s so important that AI now has a voice at the Cabinet table. ft.com/content/9db74b25-45ad…
37
42
7
360
44,295
Taz Wake retweeted
Have you looked at the patterns of sextortion and extortion? have you then thought... this pattern seems familiar.... trying to shame someone by them not having #DNSSEC enabled? Don't worry if not, I have! I have seen this occurring for years and years..... so I thought I would write a blog about it: pwndefend.com/2026/06/06/usi…
2
4
29
2,376
New episode with @tazwake. Are we over-relying on tools vs fundamentals? 🎧 Full conversation with Taz Wake on the Cyber Leaders Podcast: go.sans.org/cPmBGi
1
3
5
1,125
I have a thing about mapping incidents to very granular taxonomies.... like an itch in my brain... because disability of incidents is a really difficult/variable thing... and trying to map things to a very specific taxonomy I think is difficult but also I think maybe flawed....
I question if MITRE att&ck is the right framework for this.... I've been talking about that with mates for a while..... I think that mapping every incident to ATT&CK isn't realistic, I think because of the granularity and the fact that in some/many incidents you can't see everything means: people won't want to complete 9000 pages of incident reporting forms people will make mistakes the data at the end will be flawed cyber.gov.au/about-us/view-a…
2
4
15
3,426
I love cisos who have loads of bullshit marketing and then their orgs get mega owned by kids #awkward
6
4
49
3,333
This is largely bullshit by @NJ_Timothy - if you believe it enough to reshare it as if true, you have major issues. Religious "courts" are non-legally binding arbritration services.
Sharia courts have created a parallel legal system in this country. Their “judges” often justify domestic violence and marital rape. But according to Labour, sharia courts are part of what makes us British.
2
259
🌟 #SANSCommunityNight in Copenhagen isn’t just an event. It’s where real connections happen. Join us Tue, Aug 26 for an evening of fresh ideas with @TazWake, honest conversation, and the kind of community that makes InfoSec feel human. 👉 sans.org/u/1Cg3
1
380
This might be a niche persistence mechanism, but during an investigation, I stumbled upon the following file on a Linux server: /home/<user>/.config/autostart/set_trusted.desktop With the following content: [Desktop Entry] Encoding=UTF-8 Exec=/usr/bin/set_trusted.sh Name=Set trusted Comment=Set desktop file trusted Terminal=false OnlyShowIn=GNOME Type=Application X-GNOME-Autostart-enabled=true Do you spot the "exec" command? An attacker could replace the legitimate path to the "set_trusted.sh" file with an arbitrary file, thereby (potentially?) gaining code execution whenever the user logs in. I don't know how widespread that feature is, and how many distributions are supporting it (Nautilus?), but maybe it will come in handy for someone :)
1
5
1
22
4,389
This is pretty awesome. I'd also recommend tracking down one of @4a696d's talks. You wont regret it.
So this one has been a while coming. If you've seen any of the talks or workshops I've done recently you'll have heard me talking about the way we are thinking about attacks on generative AI. Well, it's finally here. hiddenlayerai.github.io/ape-…
6
324
So this one has been a while coming. If you've seen any of the talks or workshops I've done recently you'll have heard me talking about the way we are thinking about attacks on generative AI. Well, it's finally here. hiddenlayerai.github.io/ape-…
5
1
16
2,251
🔐 Not all prompt injections are the same. We just released a taxonomy of adversarial prompt engineering, mapping the why, how, and what behind LLM prompt attacks. Built for red teamers, defenders & researchers. Open to the community. 🔗 hiddenlayer.com/innovation-h…
3
9
1,255
📄 The Linux #IncidentResponse & #ThreatHunting poster by @4enzikat0r & @tazwake is your forensic roadmap, helping you analyze timestamps, track persistence mechanisms, & uncover hidden malware. 📥 Download your FREE copy!: buff.ly/fJ3k3NK #DFIR #Linux
1
39
132
7,587