<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cameras on CuraSec</title><link>https://curasec.metacog.co.kr/tags/cameras/</link><description>Recent content in Cameras on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 20 Jul 2026 13:16:24 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/cameras/index.xml" rel="self" type="application/rss+xml"/><item><title>Active scans detected targeting Hikvision camera API endpoints</title><link>https://curasec.metacog.co.kr/insights/2026-07-20-scans-for-hikvision-intelligent-security-api-sun-jul-19th/</link><pubDate>Mon, 20 Jul 2026 13:16:24 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-20-scans-for-hikvision-intelligent-security-api-sun-jul-19th/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If your environment includes Hikvision cameras, audit whether their Intelligent Security API is exposed to the internet and place them behind a firewall or VPN; no new CVE is cited but active scanning indicates exploitation interest.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Add or tune detections for inbound probes against Hikvision API paths (e.g., /ISAPI/ endpoints) in perimeter logs; SANS honeypots are detecting active internet-wide scans worth tracking as a precursor to exploitation.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>