<?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>Adaptive Security on After the Code</title><link>https://windshock.github.io/en/tags/adaptive-security/</link><description>Recent content in Adaptive Security on After the Code</description><generator>Hugo -- 0.145.0</generator><language>en-US</language><lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://windshock.github.io/en/tags/adaptive-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Security Controls Aren't Lacking — They're Inconvenient: Why Security Needs Customer Context</title><link>https://windshock.github.io/en/post/2026-05-11-adaptive-security-customer-context/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://windshock.github.io/en/post/2026-05-11-adaptive-security-customer-context/</guid><description>Security controls already exist. The real problem is that we cannot decide which customer, at which moment, deserves how much friction. As the closing chapter of the CAPTCHA·ATO series, this post is about moving from quantity of controls to context of controls — adaptive security as an operational discipline.</description></item></channel></rss>