<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Watermarking on CuraSec</title><link>https://curasec.metacog.co.kr/tags/watermarking/</link><description>Recent content in Watermarking on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 31 Aug 2026 19:07:02 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/watermarking/index.xml" rel="self" type="application/rss+xml"/><item><title>TaintedPixels: Proactive Watermarking to Expose Deepfake Videos</title><link>https://curasec.metacog.co.kr/insights/2026-08-31-can-tainted-pixels-expose-deepfake-videos/</link><pubDate>Mon, 31 Aug 2026 19:07:02 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-31-can-tainted-pixels-expose-deepfake-videos/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Novel proactive defense that embeds perturbations into facial video regions to surface manipulation artifacts post-edit — no deployable product yet, but relevant to teams building video authentication or media integrity pipelines.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Federated Learning Watermarking + Lattice-Based Secure Aggregation Framework</title><link>https://curasec.metacog.co.kr/insights/2026-08-24-keyed-provenance-watermarking-with-complementary-lattice-bas/</link><pubDate>Mon, 24 Aug 2026 13:10:29 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-24-keyed-provenance-watermarking-with-complementary-lattice-bas/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Academic research proposing a combined data-provenance watermarking and post-quantum secure aggregation scheme for federated learning; no exploitation signals or patch action required, but relevant if you are designing or hardening an FL pipeline.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Anthropic plans text watermarking for Claude AI-generated content</title><link>https://curasec.metacog.co.kr/insights/2026-08-15-how-anthropic-plans-to-watermark-claude-s-ai-generated-text/</link><pubDate>Sat, 15 Aug 2026 11:32:14 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-15-how-anthropic-plans-to-watermark-claude-s-ai-generated-text/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Emerging AI watermarking techniques may influence how teams detect or validate AI-generated content in pipelines; no action required today as this is still a planned capability.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> AI content provenance is a developing governance area; worth tracking for future policy on AI-generated content in internal and customer-facing communications.&lt;/li>
&lt;/ul></description></item><item><title>RaMark: Radioactive Watermarking for Synthetic Tabular Data</title><link>https://curasec.metacog.co.kr/insights/2026-07-13-ramark-radioactive-watermarking-for-generated-tabular-data/</link><pubDate>Mon, 13 Jul 2026 14:30:14 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-13-ramark-radioactive-watermarking-for-generated-tabular-data/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Novel technique for embedding persistent watermarks in synthetic tabular data that survive generative model retraining — worth tracking if your team uses synthetic data for privacy-sensitive data sharing pipelines.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Research relevant to organizations using synthetic data for privacy-preserving data sharing; useful context for evaluating ownership verification controls in that space, but no immediate action required.&lt;/li>
&lt;/ul></description></item></channel></rss>