<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Attack-Speed on CuraSec</title><link>https://curasec.metacog.co.kr/tags/attack-speed/</link><description>Recent content in Attack-Speed on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 22 Oct 2026 15:52:23 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/attack-speed/index.xml" rel="self" type="application/rss+xml"/><item><title>Machine-speed attacks demand automated detection and containment</title><link>https://curasec.metacog.co.kr/insights/2026-10-22-machine-speed-attacks-require-machine-speed-detection-and-re/</link><pubDate>Thu, 22 Oct 2026 15:52:23 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-22-machine-speed-attacks-require-machine-speed-detection-and-re/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> The examples — stolen GitHub tokens, malicious AI installers, MFA phishing — are real attack patterns worth understanding, but the piece offers no specific CVEs, patches, or configuration actions; it reinforces why short-lived credentials and automated revocation matter in pipeline design.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> The attack timeline framing is useful context for tuning alert SLAs and investing in SOAR playbooks, but no IOCs, Sigma rules, or ATT&amp;amp;CK mappings are provided — nothing to hunt or deploy today.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>