<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Threat-Scanning on CuraSec</title><link>https://curasec.metacog.co.kr/tags/threat-scanning/</link><description>Recent content in Threat-Scanning on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 13 Jul 2026 13:18:50 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/threat-scanning/index.xml" rel="self" type="application/rss+xml"/><item><title>Active Scanning Detected Targeting MCP Servers and AI Credentials</title><link>https://curasec.metacog.co.kr/insights/2026-07-13-someone-is-scanning-for-your-mcp-servers-and-ai-assistant-cr/</link><pubDate>Mon, 13 Jul 2026 13:18:50 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-13-someone-is-scanning-for-your-mcp-servers-and-ai-assistant-cr/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If you expose MCP server endpoints or store AI assistant API keys in reachable configs, audit those surfaces now — rotate any credentials that may have been discoverable and restrict MCP server network exposure to trusted origins only.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Build or tune detections for inbound scanning probes targeting MCP-related ports and endpoints; begin collecting logs from any AI assistant integrations to baseline credential-use patterns before abuse occurs.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Opportunistic scanning of AI assistant infrastructure is an early signal that attackers are mapping this attack surface as enterprise AI adoption grows — useful context when reviewing AI tool procurement and access-control policies.&lt;/li>
&lt;/ul></description></item></channel></rss>