<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pii-Protection on CuraSec</title><link>https://curasec.metacog.co.kr/tags/pii-protection/</link><description>Recent content in Pii-Protection on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 19 Oct 2026 18:41:36 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/pii-protection/index.xml" rel="self" type="application/rss+xml"/><item><title>Veil-then-Reveal: PII Pseudo-Anonymization for Zero-Trust LLM Use</title><link>https://curasec.metacog.co.kr/insights/2026-10-19-veil-then-reveal-protecting-pii-privacy-via-reversible-pseud/</link><pubDate>Mon, 19 Oct 2026 18:41:36 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-19-veil-then-reveal-protecting-pii-privacy-via-reversible-pseud/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Novel framework for replacing PII with realistic same-type surrogates before prompts leave the device, preserving linguistic context while keeping plaintext off remote providers. Worth evaluating if building systems that feed sensitive documents into external LLM APIs.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> This research surfaces a practical gap: organizations using external LLM APIs may inadvertently expose PII through prompt logging and retention — useful framing for an AI data-governance policy before the next audit cycle.&lt;/li>
&lt;/ul></description></item></channel></rss>