<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Third-Party-Access on CuraSec</title><link>https://curasec.metacog.co.kr/tags/third-party-access/</link><description>Recent content in Third-Party-Access on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 06 Oct 2026 17:10:43 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/third-party-access/index.xml" rel="self" type="application/rss+xml"/><item><title>Denmark CPR Registry Breach Exposes 8.8M National IDs via Company Account</title><link>https://curasec.metacog.co.kr/insights/2026-10-06-denmark-says-attackers-accessed-cpr-data-for-8-8-million-peo/</link><pubDate>Tue, 06 Oct 2026 17:10:43 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-06-denmark-says-attackers-accessed-cpr-data-for-8-8-million-peo/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> The attack exploited a private company&amp;rsquo;s delegated API access to a national ID registry rather than a software vulnerability — a useful reminder to audit and scope any third-party data access credentials your systems issue or consume.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No IOCs or ATT&amp;amp;CK-mapped TTPs are provided, but the pattern — abusing a legitimate, authorized account to bulk-exfiltrate sensitive records — is worth adding to threat models for detecting anomalous query volumes against data APIs your estate exposes.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Illustrates how third-party contractual data-access rights can become an attack vector at national scale; useful context for the next vendor risk review cycle, particularly for any SaaS providers with privileged access to your identity or HR data stores.&lt;/li>
&lt;/ul></description></item></channel></rss>