Holy shit, i did it, lol. It looks terrible, but it works.
For people who haven't been keeping up with this project, I've been doing ceramics for a couple years now, and recently people kept tagging me in posts about a European feminist hacker collective that was making circuit boards out of court they dug out of the ground and fired in a campfire.
After having an epiphany about some experimental copper ceramics glazes i made last year, i thought i would see if i could solder to them, and i found that i could.
Sooo ... I made a stamp and stamped out some really basic boards for an astable multivibrator (two blinky lights) circuit. I filled the recessed traces with copper powder and had them fired in our pottery kiln.
Now i have ceramic circuit boards.
"The greatest illusion in modern tech is the daily standup
Every morning, 14 senior engineers join a mandatory Zoom call just to invent new ways to say 'I'm still stuck on the same timeout error as yesterday' while a Scrum Master with zero technical context enthusiastically tries to map our collective dread onto a burndown chart by demanding to know if a 2-line config change is a 5 or an 8 in Fibonacci story points
We aren't writing code anymore. We are just participating in a live-action Jira roleplay"
Now, apply that to your IDS. create rules to observe MAC addresses, machine GUIDs, hardware components in critical systems, usernames, hostnames, domain names.
and not just in plain text ASCII. create base64 versions of the host artifact.
UUencoding, decimal/base10 encoding. single-byte XOR. Observe on TCP, UDP, ICMP, etc.
and you have an alternative honeytoken implementation.
510) Yoyobot. A robot that's also a yo-yo. Teaches you tricks but mostly just yells "Wheeeee!" as it goes up and down. #SmallRobotsRemastered
IT HAS ARRIVED! BEHOLD THE BAG OF THE TOOTING TOOTERS!
*ahem*
Quite pleased with how it turned out 😁
updating a slide deck I'm presenting next week, and I'm featuring that medusa RAT sample I found about a day ago as an example of host-specific artifacts that users can make suricata rules out of.
A lot of RATs and infostealers like to do shit like this, and give a detailed host report about the system they ended up on. So, stuff like hostnames, IP addresses, Hardware GUIDs, usernames, MAC addresses, Serial Numbers, model names of hardware components are very frequently featured.
Unfortunately, these are artifacts that are unique to the hosts and environment so I can't create generic Suricata rules for them. But you can.
I call this tactic "honeytoken IDS rules". And it works the same way as honeytokens/canary tokens work.
If you're not familiar with honeytokens, take a look at this: https://canarytokens.org/generate
Its a site that lets you generate bits of data that, to an adversary are going to be extremely tantalizing. But, when loaded, viewed, or observed in some way, will notify defenders that the data in question have been exfiltrated in some way.
This is how the AI bubble bursts: https://www.theverge.com/ai-artificial-intelligence/917380/ai-monetization-anthropic-openai-token-economics-revenue
There is no conceivable way to break even for the AI industry—let alone to repay an investment that requires $2Tn a year from now to the end of the decade. That's about 3% of the entire planetary GNP. Just to break even.
Steve:
frequent overthinker, compulsive fixer, digester-then-explainer, "why?" question relishing father, minor-irritant partner, excessive disassembler, original-form hacker, high-efficiency googler, borderline-competent car-fixer, expert-level car-breaker, faster-by-qwerty communicator, indiscriminate photo-taker, Leatherman owner.