<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Breach Report on James Jardine</title><link>https://jamesgaryjardine.com/tags/breach-report/</link><description>Recent content in Breach Report on James Jardine</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 14 Jun 2026 13:59:59 +0000</lastBuildDate><atom:link href="https://jamesgaryjardine.com/tags/breach-report/index.xml" rel="self" type="application/rss+xml"/><item><title>Fake Breach Reports: Serious or Silly?</title><link>https://jamesgaryjardine.com/fake-breach-reports-serious-or-silly/</link><pubDate>Sun, 14 Jun 2026 13:59:59 +0000</pubDate><guid>https://jamesgaryjardine.com/fake-breach-reports-serious-or-silly/</guid><description>&lt;p&gt;There was an interesting report that recently came out regarding fake data breach reports being submitted to the Main Data Breach Reporting Portal. The fake reports were focused on VRChat and Discord. According to the reports (article linked below), a user was able to submit a breach notification to the portal of a company they are not a part of. It might not seem like a big deal, but the more I think about it, the more I consider different risks and costs for the companies at hand. In addition, there is a potential risk for a sophisticated social engineering attack from this. Let’s talk about it.&lt;/p&gt;</description></item></channel></rss>