@MarkSimos Agree. And some of that neglected work is invisible: detections that can't alert because the log was never written. On a default Windows 11 install, process creation auditing (4688) is off. No analyst, human or AI, triages an event that doesn't exist.
@anton_chuvakin Fair as a floor, and easy to defend. The gap is timing. A CVE and a score come after the news, sometimes days after (one of today's headline MCP SDK bugs still says no CVE assigned yet). So: CVE plus score as the default. Exploited and exposed jumps the queue.
@lennyzeltser Good checklist. One addition to 'Are We Affected': a separate line for whether we would see exploitation if it happened. Not exposed and would detect it are different answers.
@TheHackersNews Rotation is the part people skip. Also look back through your logs for connections to MCP servers you never approved. That tells you whether you needed to rotate at all.
79K Followers 762 FollowingEnd-to-end Cybersecurity consulting team leading the industry, supporting organizations, and giving back. #Hacktheplanet
Blogs, news, webinars, and tools!
55K Followers 3K FollowingDirector of Intel at @redcanary. SANS Certified Instructor for FOR578: CTI. Senior Fellow at @CyberStatecraft. She/her. Mastodon: @[email protected]
259K Followers 208 FollowingBreaking cybersecurity and technology news, guides, and tutorials that help you get the most from your computer. DMs are open, so send us those tips!