Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Arif Kurnaz
Your evidence folder is complete. Meanwhile, someone just opened a shell in your container.
Since 11 September 2026, the EU Cyber Resilience Act asks you to report an actively exploited vulnerability within 24 hours. Twenty-four hours is enough to take away the comfort of "we'll collect the evidence before the audit." I have watched a lot of teams in the same spot. Evidence collection runs like a project: the audit gets close, and out come the screenshots, the exports, the folder. A security incident does not wait for any of that.
Attestkeep 1.0 is out, and the comment thread is in the changelog
Six days ago I posted SOC 2, CRA, NIS2: they all ask your cluster the same five questions. I expected a few reactions. What I got was three people reading the mechanism instead of the claims, and two of them found a hole that mattered. Today the tool behind that post reached 1.0. Most of what changed between the post and the release came out of that thread, and it would be strange to write a release post that pretends otherwise.
SOC 2, CRA, NIS2: they all ask your cluster the same five questions
In eleven days, on 11 September 2026, the reporting obligations of the EU Cyber Resilience Act start applying to anyone who puts a product with digital elements on the European market. Not the full regulation. Just the part where, if you find out an actively exploited vulnerability is in your product, you have 24 hours to tell ENISA about it. I have watched a lot of engineering teams meet this class of deadline for the first time. It usually goes the same way.
Ternary Semantic Brain Core — Zero Hard-Coding, Language-Independent Meaning Engine
I built a meaning-learning engine that works without LLMs, embeddings, or translation tables. Everything is stored as 2-bit ternary values {-1, 0, +1}. It learns meaning purely from word co-occurrence in plain text. What makes it different No hard-coded linguistic knowledge. No stoplists, POS tags, tokenizer, fixed vocabulary, or translation tables. All linguistic structure emerges from training data. Language-independent. Tested with English + Turkish.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Arif
Contact Arif, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack