<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secret-Scanning on CuraSec</title><link>https://curasec.metacog.co.kr/tags/secret-scanning/</link><description>Recent content in Secret-Scanning on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 13 Jul 2026 14:30:14 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/secret-scanning/index.xml" rel="self" type="application/rss+xml"/><item><title>Secret Scanner Agent: LLM multi-agent secret + access-context extraction</title><link>https://curasec.metacog.co.kr/insights/2026-07-13-secret-scanner-agent-extracting-secrets-and-access-context-f/</link><pubDate>Mon, 13 Jul 2026 14:30:14 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-13-secret-scanner-agent-extracting-secrets-and-access-context-f/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Novel research on using multi-agent LLMs to extract both credentials and the resources they unlock from unstructured documents — worth tracking as a potential complement to regex-based secret scanners in IR workflows, but no production-ready tool to adopt today.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> The concept of automatically surfacing both a leaked credential and its &amp;lsquo;door&amp;rsquo; (target account, cloud resource, endpoint) from emails, tickets, and chat threads maps well to IR triage gaps; worth monitoring for usable tooling derived from this research.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>