<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Refactθ blog</title>
<link>https://refact0.com/blog/</link>
<atom:link href="https://refact0.com/blog/rss.xml" rel="self" type="application/rss+xml"/>
<description>Cyber security news and guidance from Refactθ. Every claim is sourced and dated.</description>
<language>en-za</language>
<lastBuildDate>Mon, 02 Nov 2026 06:00:00 GMT</lastBuildDate>
<item><title>This week in cyber security: Binance&apos;s US$6.3bn theft, exploited PHP flaws and FNB&apos;s POPIA fine</title><link>https://refact0.com/blog/this-week-in-cyber-security-2026-11-02/</link><guid isPermaLink="true">https://refact0.com/blog/this-week-in-cyber-security-2026-11-02/</guid><pubDate>Mon, 02 Nov 2026 06:00:00 GMT</pubDate><description>Attackers took about US$6.3bn from Binance, PHP and GitLab flaws were exploited, VPN gateways came under attack, police took down a criminal host, and the Information Regulator fined FNB R1m.</description><category>Roundups</category><category>Crypto</category><category>Vulnerabilities</category><category>Law enforcement</category><category>South Africa</category><category>POPIA</category></item>
<item><title>Reporting a security compromise under POPIA: what to do, and when</title><link>https://refact0.com/blog/reporting-a-security-compromise-under-popia/</link><guid isPermaLink="true">https://refact0.com/blog/reporting-a-security-compromise-under-popia/</guid><pubDate>Mon, 02 Nov 2026 06:00:00 GMT</pubDate><description>Every security compromise must be reported to the Information Regulator and to the people affected. What section 22 of POPIA requires, what changed in 2025, and what to do if you&apos;re told.</description><category>Advisories</category><category>South Africa</category><category>POPIA</category><category>Data breaches</category></item>
</channel>
</rss>
