<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Breach Disclosure | FirewallSync</title><link>https://firewallsync.com/tags/breach-disclosure/</link><description>Practical cybersecurity writing for engineering teams that ship fast.</description><language>en-us</language><image><url>https://firewallsync.com/icon-512.png</url><title>FirewallSync</title><link>https://firewallsync.com/</link></image><lastBuildDate>Wed, 18 Nov 2026 04:59:00 +0000</lastBuildDate><atom:link href="https://firewallsync.com/tags/breach-disclosure/index.xml" rel="self" type="application/rss+xml"/><item><title>Equinor Cyberattack: What the Energy Giant Has Confirmed</title><link>https://firewallsync.com/posts/equinor-cyberattack-it-systems-what-we-know/</link><guid>https://firewallsync.com/posts/equinor-cyberattack-it-systems-what-we-know/</guid><pubDate>Wed, 18 Nov 2026 04:59:00 +0000</pubDate><dc:creator>Craig Leslie</dc:creator><category>Security Operations</category><description>Norwegian energy company Equinor said on Tuesday, November 17, 2026 that it has detected an ongoing cyberattack against certain IT systems. It says operations and production are unaffected, there are no indications data was stolen, and authorities are being informed. Here is what is confirmed, what is not, and what engineers can take from it.</description><enclosure url="https://firewallsync.com/posts/equinor-cyberattack-it-systems-what-we-know/cover_hu15581343868057772531.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/equinor-cyberattack-it-systems-what-we-know/cover_hu15581343868057772531.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/equinor-cyberattack-it-systems-what-we-know/cover_hu15581343868057772531.jpg" alt="Several offshore drilling rigs and platforms silhouetted on calm water under a dark sky with an orange sunset" width="1200" height="630"></p><p><strong>What happened:</strong> Norwegian energy company Equinor said on Tuesday, November 17, 2026 that it &ldquo;has detected an ongoing cyber-attack against certain IT systems.&rdquo; It says operations and production are not affected and that &ldquo;There are no indications that data has been stolen.&rdquo; Equinor has not said which systems, how the attack started or who is behind it.</p>
<p>This is a short, early disclosure, much like the one <a href="/posts/coles-cyber-security-incident-what-we-know/">Coles made in Australia a day earlier</a>. Below is what the company has confirmed, what it has not, and what engineers running IT next to industrial operations can check in their own environments.</p>
<h2 id="what-equinor-has-said">What Equinor has said</h2>
<p>The statement on <a href="https://www.equinor.com/news/20261711-equinor-detected-cyber-attack">equinor.com</a>, published at 18:55 CET on November 17 and last modified at 19:40, says:</p>
<ul>
<li>Equinor &ldquo;has detected an ongoing cyber-attack against certain IT systems.&rdquo;</li>
<li>&ldquo;Relevant resources have been mobilised to neutralise the attack and regain full integrity.&rdquo;</li>
<li>&ldquo;There are no indications that data has been stolen.&rdquo;</li>
<li>&ldquo;The attack has not affected Equinor&rsquo;s operations and production.&rdquo;</li>
<li>&ldquo;Relevant authorities are being informed.&rdquo;</li>
<li>Equinor &ldquo;will provide updates when new information is available.&rdquo;</li>
</ul>
<p>Reuters reported the same points the same day, citing the company: it had seen &ldquo;no data theft or impact on operations&rdquo; and was &ldquo;mobilising resources to neutralise the cyberattack and regain full integrity&rdquo; (<a href="https://www.globalbankingandfinance.com/equinor-detects-cyberattack-against-systems/">via Global Banking &amp; Finance Review</a>; <a href="https://www.thestar.com.my/tech/tech-news/2026/11/18/equinor-detects-ongoing-cyberattack-output-unaffected-">via The Star</a>). No Equinor spokesperson was quoted by name.</p>
<h2 id="timeline">Timeline</h2>
<table>
  <thead>
      <tr>
          <th>Date</th>
          <th>Event</th>
          <th>Source</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Late Oct 2026</td>
          <td>NSM raises Norway&rsquo;s national cyber risk level to HIGH (reported by DNV on October 28; University of Oslo IT notice November 3)</td>
          <td><a href="https://www.dnv.com/cyber/insights/articles/nsm-raises-norways-cyber-risk-level-to-high/">DNV</a>, <a href="https://www.uio.no/english/services/it/news/2026/risk-level.html">UiO</a></td>
      </tr>
      <tr>
          <td>Nov 17, 18:55 CET</td>
          <td>Equinor publishes statement on an ongoing attack against certain IT systems</td>
          <td><a href="https://www.equinor.com/news/20261711-equinor-detected-cyber-attack">Equinor</a></td>
      </tr>
      <tr>
          <td>Nov 17</td>
          <td>Reuters reports the statement</td>
          <td><a href="https://www.thestar.com.my/tech/tech-news/2026/11/18/equinor-detects-ongoing-cyberattack-output-unaffected-">The Star (Reuters)</a></td>
      </tr>
      <tr>
          <td>Nov 18 (as of 05:00 UTC)</td>
          <td>No further Equinor update found</td>
          <td>Our search of Equinor&rsquo;s site and news coverage</td>
      </tr>
  </tbody>
</table>
<h2 id="confirmed-vs-not-confirmed">Confirmed vs not confirmed</h2>
<table>
  <thead>
      <tr>
          <th>Question</th>
          <th>Status</th>
          <th>Detail</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Was there an attack?</td>
          <td>Confirmed by Equinor</td>
          <td>&ldquo;ongoing cyber-attack against certain IT systems&rdquo;</td>
      </tr>
      <tr>
          <td>Is it still ongoing?</td>
          <td>Equinor called it ongoing on Nov 17</td>
          <td>No update since</td>
      </tr>
      <tr>
          <td>Production or operations affected?</td>
          <td>Equinor says no</td>
          <td>&ldquo;has not affected Equinor&rsquo;s operations and production&rdquo;</td>
      </tr>
      <tr>
          <td>Data stolen?</td>
          <td>Equinor says no indication</td>
          <td>&ldquo;no indications that data has been stolen&rdquo; (interim)</td>
      </tr>
      <tr>
          <td>Which systems?</td>
          <td>Not disclosed</td>
          <td>Only &ldquo;certain IT systems&rdquo;</td>
      </tr>
      <tr>
          <td>How did attackers get in?</td>
          <td>Not disclosed</td>
          <td></td>
      </tr>
      <tr>
          <td>Ransomware?</td>
          <td>Not disclosed</td>
          <td>Equinor has not said either way</td>
      </tr>
      <tr>
          <td>Who is responsible?</td>
          <td>Not disclosed</td>
          <td>No public claim found in the coverage we reviewed</td>
      </tr>
      <tr>
          <td>Authorities involved?</td>
          <td>Equinor says they are being informed</td>
          <td>None named</td>
      </tr>
  </tbody>
</table>
<h3 id="what-is-not-confirmed">What is not confirmed</h3>
<p>Some coverage has framed the incident against European gas supply or other recent Norwegian incidents. Equinor has reported no effect on production, no supply disruption has been reported, and no source we found links this attack to any other incident. Any claim about the attackers&rsquo; identity or motive is speculation at this stage.</p>
<h2 id="the-wider-context-norways-risk-level">The wider context: Norway&rsquo;s risk level</h2>
<p>Norway&rsquo;s National Security Authority (NSM) raised the national cyber risk level to HIGH in late October 2026. The University of Oslo&rsquo;s IT service describes HIGH as &ldquo;the second highest level on a five-step scale ranging from Very low to Extremely high,&rdquo; with Moderate as the normal state, and cites NSM&rsquo;s reference to &ldquo;a demanding security policy situation&rdquo; and &ldquo;a large increase in successful cyberattacks against Norwegian organizations.&rdquo; This is background, not evidence about the Equinor attack.</p>
<h2 id="what-engineers-can-take-from-it">What engineers can take from it</h2>
<p>Equinor&rsquo;s statement draws a line many energy and manufacturing companies rely on: the attack is in IT systems, and operations are not affected. Whether that line holds depends on architecture you can check now, before you need it:</p>
<ul>
<li><strong>Know your IT/OT dependencies.</strong> List the IT services that operations depend on: identity, historians, scheduling and dispatch, remote access, licensing servers. An IT-only incident can still stop production if plants rely on those services.</li>
<li><strong>Make &ldquo;no data theft&rdquo; a measured claim.</strong> Equinor&rsquo;s statement is an interim finding. Your ability to say the same depends on egress logging and retained network flow data covering the attack window. Our piece on <a href="/posts/logging-for-incidents-not-for-dashboards/">logging for incidents rather than dashboards</a> covers what to keep.</li>
<li><strong>Pre-write the first statement.</strong> Equinor&rsquo;s disclosure says what is affected, what is not, what is being done, who has been told, and that updates will follow, all within hours. Rehearse that in a <a href="/posts/the-tabletop-exercise-gap-testing-incident-response-for-real/">tabletop exercise</a> rather than drafting it during the incident.</li>
<li><strong>Watch for phishing that uses the news.</strong> Suppliers and partners of a named victim are likely targets for &ldquo;updated bank details&rdquo; or &ldquo;incident notification&rdquo; lures in the weeks after a disclosure.</li>
<li><strong>Industrial-control exposure is a separate question.</strong> If your operations network has internet-reachable controllers, the recent <a href="/posts/supermarket-freezer-hacks-refrigeration-controllers-cisa-fbi-warning/">CISA-FBI warning on refrigeration controllers</a> shows how attackers find them.</li>
</ul>
<p>We will add a dated update at the top of this article if Equinor publishes material new information.</p>
<h2 id="sources">Sources</h2>
<table>
  <thead>
      <tr>
          <th>Claim</th>
          <th>Source</th>
          <th>Status</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Attack on certain IT systems; ongoing; no indications of data theft; operations and production unaffected; authorities informed</td>
          <td><a href="https://www.equinor.com/news/20261711-equinor-detected-cyber-attack">Equinor statement, Nov 17, 2026</a></td>
          <td>Verified (primary)</td>
      </tr>
      <tr>
          <td>Reuters report of the statement</td>
          <td><a href="https://www.thestar.com.my/tech/tech-news/2026/11/18/equinor-detects-ongoing-cyberattack-output-unaffected-">The Star (Reuters)</a>, <a href="https://www.globalbankingandfinance.com/equinor-detects-cyberattack-against-systems/">Global Banking &amp; Finance Review (Reuters)</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>No attacker identity or ransomware detail disclosed</td>
          <td><a href="https://www.ibtimes.sg/equinor-hacked-norwegian-energy-giant-detects-cyberattack-internal-systems-96339">International Business Times Singapore</a> and the Equinor statement</td>
          <td>Verified as of Nov 18</td>
      </tr>
      <tr>
          <td>NSM raised national cyber risk level to HIGH; scale description</td>
          <td><a href="https://www.uio.no/english/services/it/news/2026/risk-level.html">University of Oslo IT</a>, <a href="https://www.dnv.com/cyber/insights/articles/nsm-raises-norways-cyber-risk-level-to-high/">DNV</a></td>
          <td>Qualified (NSM&rsquo;s own page not retrieved)</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item><item><title>Coles Cyber Incident: What the Supermarket Has Confirmed</title><link>https://firewallsync.com/posts/coles-cyber-security-incident-what-we-know/</link><guid>https://firewallsync.com/posts/coles-cyber-security-incident-what-we-know/</guid><pubDate>Tue, 17 Nov 2026 04:56:00 +0000</pubDate><dc:creator>John Marshall</dc:creator><category>Security Operations</category><description>Australian supermarket group Coles told the ASX on Monday, November 16, 2026 that it is investigating a cyber security incident in its IT environment. It says stores and online shopping are running normally and it has found no evidence so far that customer, team or supplier data was compromised or removed. Here is what is confirmed, what is not, and what engineers can take from the disclosure.</description><enclosure url="https://firewallsync.com/posts/coles-cyber-security-incident-what-we-know/cover_hu13157297189200271938.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/coles-cyber-security-incident-what-we-know/cover_hu13157297189200271938.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/coles-cyber-security-incident-what-we-know/cover_hu13157297189200271938.jpg" alt="A long row of nested blue shopping carts lined up against a bright yellow wall on a dark asphalt car park" width="1200" height="630"></p><p>Australian supermarket group Coles told the Australian Securities Exchange on Monday, November 16, 2026 that it is &ldquo;investigating a cyber security incident.&rdquo; The company says its stores and online shopping are running normally and that it has found no evidence so far that customer, team or supplier data was compromised or removed. It has not said what happened, which systems are involved or when the incident began.</p>
<p>We have not been able to retrieve the ASX announcement itself. The quotes below come from three outlets that reported it on November 16 and 17: <a href="https://www.forbes.com.au/news/world-news/coles-investigates-cyber-security-incident/">Forbes Australia</a>, <a href="https://ia.acs.org.au/article/2026/coles-launches-investigation-into-cyber-incident.html">Information Age</a> (the Australian Computer Society&rsquo;s publication) and <a href="https://insideretail.com.au/digital/security/coles-investigating-cyber-security-incident-202611">Inside Retail</a>, with <a href="https://www.teiss.co.uk/news/australian-retailer-coles-investigates-cyber-security-incident-finds-no-evidence-of-customer-data-breach-18466">teiss</a> in the UK reporting the same statement.</p>
<h2 id="what-coles-has-said">What Coles has said</h2>
<p>As quoted by those outlets, Coles&rsquo; update says:</p>
<ul>
<li>It is &ldquo;investigating a cyber security incident.&rdquo;</li>
<li>&ldquo;Coles is also working with global cyber security experts to contain and secure the Coles IT environment.&rdquo;</li>
<li>It is working with the Australian Cyber Security Centre (ACSC) and will &ldquo;engage with appropriate agencies and regulators as investigations continue.&rdquo;</li>
<li>&ldquo;Operations continue and customers are able to shop as normal with Coles in stores and online.&rdquo;</li>
<li>Its findings so far have not uncovered evidence of &ldquo;customer, team or supplier data&rdquo; being compromised or removed.</li>
<li>&ldquo;We apologise for any concerns this may cause our customers and key stakeholders.&rdquo;</li>
</ul>
<h2 id="timeline">Timeline</h2>
<table>
  <thead>
      <tr>
          <th>Date (AEDT)</th>
          <th>Event</th>
          <th>Source</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Friday, November 13, 2026</td>
          <td>Coles&rsquo; email system reportedly affected by a Microsoft outage; store operations continued. Not linked to the incident by Coles.</td>
          <td>Information Age</td>
      </tr>
      <tr>
          <td>Monday, November 16, 2026, morning</td>
          <td>Coles tells the ASX it is investigating a cyber security incident.</td>
          <td>Forbes Australia, Inside Retail, Information Age</td>
      </tr>
      <tr>
          <td>November 16 to 17, 2026</td>
          <td>No update reported on scope, cause or attribution.</td>
          <td>Reporting reviewed for this article</td>
      </tr>
  </tbody>
</table>
<p>Coles has not said when the investigation began or when it expects to give another update.</p>
<h2 id="confirmed-vs-not-confirmed">Confirmed vs not confirmed</h2>
<table>
  <thead>
      <tr>
          <th>Question</th>
          <th>Status</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Coles is investigating a cyber security incident in its IT environment</td>
          <td><strong>Confirmed by Coles</strong></td>
      </tr>
      <tr>
          <td>Stores and online shopping operating normally</td>
          <td><strong>Confirmed by Coles</strong></td>
      </tr>
      <tr>
          <td>ACSC and external experts engaged</td>
          <td><strong>Confirmed by Coles</strong></td>
      </tr>
      <tr>
          <td>Customer, team or supplier data stolen</td>
          <td><strong>No evidence so far, per Coles</strong>; investigation continuing</td>
      </tr>
      <tr>
          <td>Type of incident (ransomware, intrusion, account compromise or other)</td>
          <td><strong>Not disclosed</strong></td>
      </tr>
      <tr>
          <td>Systems affected</td>
          <td><strong>Not disclosed</strong></td>
      </tr>
      <tr>
          <td>When the incident started or was detected</td>
          <td><strong>Not disclosed</strong></td>
      </tr>
      <tr>
          <td>Who is responsible</td>
          <td><strong>Not disclosed</strong>; no public claim found in the reporting we reviewed</td>
      </tr>
      <tr>
          <td>Liquorland click-and-collect problems for &ldquo;a small number&rdquo; of customers</td>
          <td>Reported by Information Age; <strong>not linked to the incident by Coles</strong></td>
      </tr>
      <tr>
          <td>Internal system problems described by Reddit users</td>
          <td>Mentioned by Information Age, which did not confirm them; <strong>unverified</strong></td>
      </tr>
  </tbody>
</table>
<p>Information Age also noted the recent attacks on supermarket refrigeration controllers in Europe as context while stating no link to Coles; we <a href="/posts/supermarket-freezer-hacks-refrigeration-controllers-cisa-fbi-warning/">covered the CISA-FBI warning on those attacks</a> last week. Nothing published so far connects them.</p>
<h2 id="how-to-read-this-kind-of-disclosure">How to read this kind of disclosure</h2>
<p>A listed company&rsquo;s first disclosure is written to satisfy market rules while the investigation is still running, so it tells you what the company can stand behind today and little else. A few points engineers and security teams can take from the wording:</p>
<ul>
<li><strong>&ldquo;No evidence so far&rdquo; is a point-in-time finding.</strong> It depends on what logs exist and how far responders have got. Plenty of breach notices start this way and are revised later. Treat it as &ldquo;not yet known&rdquo;, not &ldquo;nothing taken&rdquo;.</li>
<li><strong>&ldquo;Contain and secure the IT environment&rdquo; says responders are still active.</strong> It does not say whether the intruder is out. Expect follow-up notices.</li>
<li><strong>Normal operations are not the same as no impact.</strong> Point-of-sale and e-commerce can keep running while corporate IT, email or back-office systems are isolated. Coles has not said which, if any, systems were taken offline.</li>
</ul>
<h2 id="what-to-check-if-you-work-with-coles">What to check if you work with Coles</h2>
<p>If your organisation supplies Coles or integrates with its systems, Coles&rsquo; statement gives you no reason to assume your data is affected. A few low-cost steps still make sense while the investigation is open:</p>
<ol>
<li><strong>Watch for phishing that cites the incident.</strong> Public breach news is a common lure for fake &ldquo;verify your account&rdquo; or &ldquo;update your payment details&rdquo; emails. Confirm any request through a contact you already have, not one in the message.</li>
<li><strong>Know which credentials and integrations you share.</strong> List API keys, SFTP accounts, EDI connections and supplier-portal logins tied to Coles so you can rotate them quickly if Coles asks or if the scope changes.</li>
<li><strong>Look for an update before acting on rumours.</strong> Coles has said it will engage regulators as the investigation continues; a material change would normally appear as a further ASX announcement.</li>
</ol>
<h2 id="sources">Sources</h2>
<ul>
<li><a href="https://www.forbes.com.au/news/world-news/coles-investigates-cyber-security-incident/">Forbes Australia: Coles investigates cyber security incident</a> (November 16, 2026)</li>
<li><a href="https://ia.acs.org.au/article/2026/coles-launches-investigation-into-cyber-incident.html">Information Age: Coles launches investigation into cyber incident</a> (November 17, 2026)</li>
<li><a href="https://insideretail.com.au/digital/security/coles-investigating-cyber-security-incident-202611">Inside Retail: Coles investigating &lsquo;cybersecurity incident&rsquo;</a> (November 16, 2026)</li>
<li><a href="https://www.teiss.co.uk/news/australian-retailer-coles-investigates-cyber-security-incident-finds-no-evidence-of-customer-data-breach-18466">teiss: Australian retailer Coles investigates cyber security incident</a> (November 16, 2026)</li>
</ul>
]]></content:encoded></item></channel></rss>