<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Capability-Security on Ilya Rusalowski Hub</title><link>https://rivik.github.io/tags/capability-security/</link><description>Recent content in Capability-Security on Ilya Rusalowski Hub</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 03 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rivik.github.io/tags/capability-security/index.xml" rel="self" type="application/rss+xml"/><item><title>180 Breaches a Second: How Software Broke Its Promise, and the Radical Fix Hiding in Plain Sight</title><link>https://rivik.github.io/180-breaches-a-second/</link><pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate><guid>https://rivik.github.io/180-breaches-a-second/</guid><description>180 accounts are breached every second — and most of it comes down to reused passwords and missing MFA. A look at the software quality collapse behind the headlines, and why the fix is the same infrastructure-level move HTTPS once made: passkeys, on-device DLP, and capability-scoped AI agents.</description></item></channel></rss>