P.K. SHARMA

Cyber security intelligence, AI governance, practitioner analysis

Skagerak says 'attempt', Dark Reading says 'breached'; NSM said 'high' 21 days before Equinor's first notice

Skagerak Energi's 18 November notice says activity that may be an attempt; Dark Reading's title says breached; Equinor now says its attack is stopped. NSM stated the national cyber level as high 21 days before Equinor's first notice (derived).

By · LinkedIn · · 27 min read

NSM stated the national cyber level as high 21 days before Equinor's first notice, and then three words appeared

On 27 October 2026 Norway's National Security Authority (NSM) published a page headed, in this site's translation, "NSM raises the national cyber risk level to HIGH". Equinor's first notice of a cyber-attack is stamped 17 November 2026, 18:55 CET, which is 21 days later (derived: 4 days to 31 October plus 17 days). Skagerak Energi's press release is dated 18 November 2026, 22 days after NSM's page (derived). Two days after Skagerak, on 20 November at 08:55 CET, Equinor's page says its attack has been stopped.

The companies and the publication use different words for the days in between. Skagerak's press release says it has detected activity that may be an attempt at a cyberattack. Equinor's page says cyber-attack, then stopped. The trade publication Dark Reading titled its 19 November piece "Second Norwegian Energy Company Breached in Two Days". This site read the saved pages on 20 November 2026 between about 15:12 and 15:25 UTC: Equinor's page at about 15:12 UTC (16:12 CET), Dark Reading at about 15:18, NSM and PST at about 15:19, and Skagerak's two pages, rendered in a browser, at 15:25 UTC.

That is the checkable fact, and what it does not establish matters more. NSM's level is context. No saved page links it to either incident, and NSM's page was written 21 days before the first of them. The saved pages do not state:

  • Whether the two incidents are linked. Equinor says its attack does not appear to be specifically targeting Equinor. Dark Reading says no specific link has been drawn. Neither company says anything about the other.
  • Who is behind either one, or what the entry route was.
  • Whether operational technology was touched. Equinor says certain IT systems. Skagerak says certain of the group's IT systems. Neither says anything about the systems that run a plant or a platform.
  • What "stopped" means technically in Equinor's 20 November update, or how Equinor concluded it.
  • What "attempt" means in Skagerak's notice: whether anything got in, or whether something was caught at the edge.
  • Whether any other Norwegian energy company was hit. Dark Reading says others were put on alert. No primary says so.

The saved pages print no indicator of compromise, no CVE, no file name and no technical artifact for either incident, so this brief has none to give. Its only code-like material is NSM's own list of 21 numbered measures, translated, near the end.

The clock: ten stamps, five sources, 24 days

Diagram 1 puts every dated item on two scales. The top scale runs 27 October to 20 November. The bottom one zooms into 17 to 20 November, where Equinor's four statements, Skagerak's two notices and Dark Reading's piece all fall. Norway is on CET (UTC+1) from 25 October, and NSM's own page data carries a +01:00 offset on 27 October, so every CET time here is UTC+1 as the pages print it.

Three spans are worth stating, all derived. Equinor's first notice to its stop update is 62 hours, 2 days 14 hours (17 November 18:55 to 19 November 18:55 is 48 hours; 19 November 18:55 to 20 November 08:55 is 14 hours; 48 plus 14 is 62). Equinor's first notice to its 19 November update is 40 hours 45 minutes, and that update to the stop update is 21 hours 15 minutes. Skagerak's notice is dated only by day: 18 November starts 5 hours 5 minutes after Equinor's first notice and ends 29 hours 5 minutes after it, so the gap between the two companies' first notices lies somewhere in that window. The calendar gap is one day (derived). Dark Reading's "two days" in its title counts 17 and 18 November as two calendar days, and the primaries are consistent with that count.

Drawn from the saved pages read on 20 November 2026; positions from one time scale per axis. Every span is derived. Skagerak's update has no date and is not placed.

Table 1. Every dated statement in the saved pages, by time. Skagerak text is this site's translation; the other quotations are as printed.

When (as printed)SourceWhat it says
27 Oct 2026 (published and updated)NSMPage headline, translated: NSM raises the national cyber risk level to HIGH. "For the first time NSM shares the national cyber risk level openly and unclassified."
12 Nov 2026 (published; page data: modified 16 Nov)PSTPage headline, translated: "The sabotage threat in Norway is heightened". Its subject is sabotage by damage, explosives, drones and arson, not IT systems.
17 Nov 2026, 18:55 CETEquinor"Equinor has detected an ongoing cyber-attack against certain IT systems." "There are no indications that data has been stolen."
18 Nov 2026 (date only; no time printed)Skagerak EnergiPress release: "activity that may be an attempt at a cyberattack" The incident "has not affected" operations or production.
18 Nov 2026, 09:47 CETEquinor"As this is not a virus attack, there is no risk of the attack spreading." "Production remains unaffected." Nothing about data.
Not printed (Dark Reading dates it 19 Nov)Skagerak Energi, updateTranslated: it "has now got a better overview"; still "no indications that information has gone astray".
19 Nov 2026, 11:40 CETEquinor"The cyber-attack detected by Equinor is still ongoing"; "The attack does not appear to be specifically targeting Equinor."
19 Nov 2026, 20:14 UTC (21:14 CET)Dark Reading (secondary)Title: "Second Norwegian Energy Company Breached in Two Days"
20 Nov 2026, 08:55 CETEquinor"The cyber-attack against Equinor has now been stopped." "Production is running as normal"
20 Nov 2026, 09:12 CETEquinor pagePrinted "Last modified": 17 minutes after the stop update (derived).

Two things about the order. Skagerak's press release prints a date and no time, so where it falls against Equinor's 09:47 CET update on 18 November is not stated, and Dark Reading's remark that Skagerak disclosed "in between" Equinor's Wednesday and Thursday updates cannot be checked on the saved page. And the saved Equinor page was read at about 16:12 CET on 20 November, 7 hours 17 minutes after its stop update (derived: 16:12 minus 08:55).

Skagerak Energi's two notices, translated: an attempt in the headline, a maybe in the body

Skagerak Energi, a Norwegian energy group with its address in Porsgrunn, published its first notice as a press release dated "Porsgrunn, 18 November 2026" (saved page). Its update (saved page) prints no date and no time. This site read both as rendered text at 15:25 UTC on 20 November 2026. Every line below is this site's translation of the saved Norwegian text, and the Norwegian is not reproduced.

Table 2 sets the two notices side by side. Read the first row and the second together. The headline says Skagerak was exposed to an attempted cyberattack, flatly. The body, a few lines down, says it has detected activity that "may be" an attempt. The first is a category and the second is a hedge, and both are on the same page. The update repeats the category in its headline and drops the hedge: its body talks only of "the incident" and "activity mentioned earlier".

Table 2. Skagerak Energi's two notices, row by row. All text is this site's translation of the saved Norwegian pages; the update prints no date.

TopicFirst notice, 18 Nov 2026Update, no date printed
Headline"Skagerak Energi exposed to attempted cyberattack""Update on attempted cyberattack"
What was found"activity that may be an attempt at a cyberattack linked to certain of the group's IT systems""Activity mentioned earlier"; the body does not say attempt, cyberattack or IT systems.
Operations or production"The incident has not affected the group's operations or production."The incident "has not affected normal operations or production".
Information"there are no indications that information has gone astray"There are "still no indications that information has gone astray".
Response"Necessary resources have been deployed to handle the incident." Work is under way to get a complete overview with relevant partners."We have put necessary measures in place, and through this have got a good overview of the situation."
Authorities"Relevant authorities have been informed of the incident."Not mentioned.
How long"It is for now too early to say how long this work will take."Not mentioned. "In the time ahead we will follow developments closely."
Next"Skagerak Energi will give updates when there is new information.""We will give further updates if information of significance comes."

Five differences between the two notices, each as the saved text prints it.

  • "Attempt" is in the headline of both, and in the body of neither as a fact. The first body says "may be an attempt". The update body does not use the word.
  • Operations became "normal operations". The first notice says the incident has not affected the group's operations or production. The update says it has not affected normal operations or production. This site does not say the change means anything; the page does not say.
  • The authorities line is not repeated. The first notice says relevant authorities have been informed. The update does not mention authorities.
  • IT systems are named once. The first notice limits the activity to certain of the group's IT systems. The update names no system.
  • It never says stopped, ended or contained. Equinor's page ends in a stop update. Skagerak's update ends with continued monitoring "in cooperation with relevant partners", which is the opposite of a closing statement.

Two further things are not in either notice: any time of day, and any word on what the "activity" was. The update says Skagerak now has "a good overview" and does not share it.

Equinor's page now holds four statements, and the last one drops the word integrity

Equinor's page (saved page) is one URL that held two statements when this site read it on 18 November. It now holds four, newest first, under the headline "Cyber-attack stopped". The address still carries the earlier wording in its path. Two statements arrived after that earlier read: 19 November at 11:40 CET and 20 November at 08:55 CET.

Table 3 follows each topic through the four. Three movements are worth seeing. On data, the 17 November notice says no indications of theft, the 18 November update says nothing about data, and from 19 November the sentence returns with a new word, "altered". On the attack's state, it is "ongoing" on 17 and 19 November, "not a virus attack" on 18 November, and "stopped" on 20 November. And on restoring the systems: the 17 November notice says resources are mobilised "to regain full integrity", the 18 and 19 November updates say work continues to restore it, and the 20 November update says the attack is stopped without saying whether integrity is restored. That last point is derived from the saved text, which has the word integrity in the first three statements and not in the last.

Table 3. Equinor's four statements, as printed on the page this site read at about 15:12 UTC on 20 November 2026.

StatementState of the attackDataProduction, targeting, authorities
17 Nov, 18:55 CET"Equinor has detected an ongoing cyber-attack against certain IT systems."No indications that data "has been stolen"Operations and production not affected; authorities "being informed"
18 Nov, 09:47 CETClearer understanding of how it was carried out and which systems; "not a virus attack"; no risk of spreading; work to neutralise it is ongoingNot mentionedProduction "remains unaffected"; dialogue with national security authorities
19 Nov, 11:40 CET"The cyber-attack detected by Equinor is still ongoing"; work "to stop the attack and restore full integrity" continuesNo indications data "has been stolen or altered"Production "running as normal"; "does not appear to be specifically targeting Equinor"; reported to the police
20 Nov, 08:55 CET"The cyber-attack against Equinor has now been stopped."No indication data "has been stolen or altered"Production "running as normal"; no indication of "negative consequences" for employees, partners or suppliers; reported to the police

Neither "not a virus attack" (18 November) nor "not specifically targeting Equinor" (19 November) is repeated on 20 November, and neither is withdrawn. The stop update names no method, no system, no actor and no basis for the word "stopped". It also does not say what became of the "work to stop the attack" on 19 November: stopped by whom, or by what. The 17 November notice already said resources were mobilised "to neutralise the attack", so "stopped" is the first statement that the neutralising succeeded, 62 hours after the first notice (derived).

Three words for one week: attack, attempt, breached

Diagram 2 sets the key word of each statement beside what that statement says about data, operations or production, and authorities. It uses Equinor's and Dark Reading's words as printed and Skagerak's in this site's translation.

Drawn from the saved pages read on 20 November 2026. Equinor and Dark Reading text as printed; Skagerak text is this site's translation. Dashed cells: not stated.

A comforting label is not a control, and the week offers several. "Attempt" says nothing was achieved, and Skagerak's body only says it may be one. "Not a virus attack" says what the attack is not. "Stopped" says an end was reached, without saying by what means or what the attacker kept. "No indication" is a statement about what has been seen so far, by the party that is checking. Each is a reasonable thing for a company to say on the day it says it. None is a measurement a reader outside the company can test.

"Breached" is the odd one out. Neither company's notice uses it (this site searched the saved Equinor page and both Skagerak pages, and the Norwegian words for breach and break in are absent). It is Dark Reading's word, in its title and body, and the piece says in the same breath that no specific link has been drawn between the incidents. It was published at 20:14 UTC on 19 November, 11 hours 41 minutes before Equinor's stop update (derived: 21:14 CET to 08:55 CET), when Equinor's page still said "still ongoing". Whether "breached" is right depends on what each company's systems saw, and the saved primaries do not say.

What Dark Reading claims, and what the primaries say about each claim

Dark Reading is on this site's list of sources it does not cite for facts, so its piece is used here only to see what is claimed. The article is by a named contributing writer; this site prints no name. Its sub-headline reads "No specific link has been drawn between the two incidents", and the body says "there is no evidence yet that the two attacks are connected". It also says "Neither company responded as of press time." about its approach to both companies. Table 4 takes each claim that goes beyond the primaries and sets it against the saved pages.

Table 4. Claims in the Dark Reading piece of 19 November 2026 (secondary, page data 20:14 UTC) against the saved primaries. The left column is Dark Reading's claim, not a fact.

Dark Reading saysThe saved primaries say
Title: "Second Norwegian Energy Company Breached in Two Days"; body says the two announced that they had been "breached"Equinor says cyber-attack. Skagerak says activity that may be an attempt, and no indication information has gone astray. Neither uses breach.
Skagerak "admitted to the same" as EquinorSkagerak's notice says "may be an attempt". It does not say it was breached, and does not mention Equinor.
No specific link drawn; no evidence yet that the attacks are connectedConsistent with the primaries: neither says anything about a link.
One Equinor employee told Reuters the email system was downNot on Equinor's page, which names no system. This site did not read Reuters.
Aker BP and Statkraft put on alert (Aker BP mobilised emergency preparedness)Not on any saved primary. This site read no statement from either company.
PST warned about "the threat of cyber sabotage"The saved PST page is about sabotage by damage, explosives, drones and arson, and prints no word on cyber or IT systems (this site searched it).
NSM "declassified its national cyber-risk assessment"NSM's page says it shares the national cyber risk level "openly and unclassified" for the first time. It does not say it declassified an assessment.
Skagerak reported its better overview "the next day" (19 Nov)Skagerak's saved update prints no date. The 19 Nov date rests on Dark Reading alone.

Two of the rows are plain mismatches of wording. The headline word "breached" does not appear in either company's notice, and the PST page that Dark Reading describes as a warning about cyber sabotage contains nothing about cyber. The remaining rows are claims this site could not check, because they rest on pages it did not read: a news agency's report, two companies' statements to the press, and government advice to households. They are listed so a reader knows what to look for, not as facts.

NSM's 27 October page: a level stated 21 days before, and what it says about critical infrastructure

NSM's page (saved page) is stamped "Published" and "Updated" 27 October 2026 (printed as 27.10.2026, read day first; the page's own data gives 2026-10-27, 12:14 CET for publication and 16:54 CET for the update). This site read it at about 15:19 UTC on 20 November. Its headline, in translation, is "NSM raises the national cyber risk level to HIGH". The body says "For the first time NSM shares the national cyber risk level openly and unclassified." and, quoting NSM's director, "NSM has not gone public with this type of assessment before."

The scale has five levels, which the page prints as VERY LOW, LOW, MODERATE, HIGH and EXTREMELY HIGH. "The MODERATE level is regarded as the normal state in the cyber domain", where cyber operations against Norwegian organisations are expected. At HIGH, in the page's words, "A high risk level requires Norwegian organisations to put preventive measures in place immediately." Diagram 3 draws the scale and what the page says around it.

Drawn from NSM's page as saved on 20 November 2026. Level names are this site's translation; the five names and their order are as the page prints them.

What the page says about critical infrastructure. It names five groups at high risk: the defence sector, the defence industry, the space sector, critical infrastructure, and service providers to organisations of significance for national security. About these it says NSM "sees that these are repeatedly exposed to mapping, attempted compromises and compromises, ransomware attacks and denial of service attacks" (this site's translation). It adds that NSM's experience is that threat actors exploit technical vulnerabilities in critical infrastructure. Energy is not named in the page as a sector. The page names no incident and no company.

The tripling. NSM's director is quoted: "In the past half year we have seen a tripling of successful cyber operations against Norwegian organisations." Two limits. The statistic is about Norwegian organisations in general, not about critical infrastructure or energy, so a reading of it as a rise in attacks on critical infrastructure goes beyond the page. And it counts successful operations, not attempts, so it does not tell a reader which of this week's two words fits better.

The AI line. The page says rapid escalation in the use of AI is helping to affect the situation, and says use of language models and agentic AI systems in cyber operations "is not at present documented in Norway", while still affecting the damage potential that sets the level (this site's translation). No saved page says either incident involved AI.

"Raises". The headline says NSM raises the level to HIGH. The body does not say what the level was before, or when. This site cannot say whether the level changed on 27 October or was first made public that day. What the page does say is that it is the first time NSM shares the level openly.

The caveat on the page is NSM's own: its measures "do not remove all risk from cyber operations" but raise an organisation's ability to handle it (translation). The page also says better baseline security in Norwegian organisations helps lower the national level, so the level is partly a function of what organisations do.

PST's 12 November page: a sabotage threat, in physical terms, five days before Equinor

The Norwegian Police Security Service (PST) page (saved page) is headed, in translation, "The sabotage threat in Norway is heightened". It prints "Published 12 Nov 2026" and its page data adds a modification time of 16 November 2026, 15:04 UTC; this site read it at about 15:19 UTC on 20 November. 12 November is 5 days before Equinor's first notice and 6 before Skagerak's (derived).

What it says, in this site's translation: "As a result of a serious development in 2026, the sabotage threat in Norway is now heightened." Methods named are "various methods, such as damage to property, explosives and drones", with arson also named. A PST department director is quoted as saying there is good reason to expect Russian intelligence to carry out sabotage in Norway in the coming year. The most likely targets are the defence industry and defence related organisations and their suppliers, and "Critical infrastructure can also be hit, for example objects within the energy sector." And two sentences a reader should keep apart: "PST has not uncovered attempts at sabotage operations against Norwegian targets." and "PST is aware that actors linked to Russian intelligence have mapped infrastructure and targets in Norway."

Three points. First, the page is about sabotage in the physical sense, and the saved text contains no word on cyber, IT systems or data (this site searched it); Dark Reading's description of it as a cyber sabotage warning is Dark Reading's. Second, it says PST had not uncovered attempts at sabotage against Norwegian targets as of 12 November, a statement about sabotage, not about computer intrusions. Third, nothing on the page refers to Equinor, Skagerak or any incident, and nothing in the saved incident pages refers to PST or to any state actor. This brief does not link the two.

NSM's package, as printed and translated: the headings and the 21 measures

The end of NSM's page carries the package the first paragraph promises. This site read it in full and lists it here because a reader at an energy company will want to map it to their own estate. The headings are as the saved page prints them, in translation. Everything in the tables is NSM's, nothing is this site's, and the page says the measures "are not new": many are in NSM's baseline principles for ICT security, and it points further to NSM's baseline principles, IEC 62443, NEK 820 and NIST SP 800-82.

Table 5. The package headings on NSM's page, translated, with what each holds (read at about 15:19 UTC on 20 November 2026).

Heading (translated)What it holds
Measures package to improve Norwegian baseline security at a high cyber risk levelThe package introduced at the foot of the page. Starts with a pointer to a self assessment service the page names.
Recommended measures from NSMSection holding the four groups below.
For maintaining critical infrastructurePhishing resistant multi-factor authentication, hardening, good logging and detection, updating and phasing out devices. "In addition NSM recommends implementing zones and conduits with authentication and control of network traffic." "It is also recommended to limit available software on devices in such zones depending on the established security level, and to implement sufficient access control." "It is further recommended to establish, as a minimum, a sustainable system that can run the function even during an incident."
Risk management for supply chainsOrganisations should manage risk across their own supply chains, including origin of components, services and software, and require suppliers to impose the same on their sub-suppliers. NSM says cyber operations also hit subcontractors to organisations of significance for national security.
Map devices and softwareFollow principle 1.2 with suitable tools. One option the page names is NIST Common Platform Enumeration, to see quickly whether and where new vulnerabilities are exposed.
Validate that security measures work as intendedVerify that measures are correctly implemented. Example given: multi-factor authentication must withstand bypass by social engineering or phishing.
Other measures from NSM's baseline principles for ICT securityThe 21 numbered measures in Table 6.

Three recommendations under the critical infrastructure heading are the ones this site reads as closest to a reader who runs plant systems. They are quoted as translated in Table 5 and summarised here so they are not lost in a longer cell: zones and conduits with authentication and control of network traffic; limiting the software available on devices in such zones; and, as a minimum, a system that can run the function even during an incident. The last of these is NSM's, and it is the one the reader checklist below picks up.

Table 6. The 21 numbered measures NSM highlights from its baseline principles for ICT security, in the page's order, translated. Page says NSM highlights 21; this site counted 21 (derived).

NumberMeasure (translated)
1.2.3Map the devices in use in the organisation.
1.2.4Map the software in use in the organisation.
1.3.3Map roles and responsibilities in the organisation related to ICT security.
2.1.2Buy modern and up to date hardware and software.
2.1.9Take responsibility for the organisation's security also when services are outsourced.
2.2.1Establish and maintain a holistic security architecture.
2.2.3Divide the organisation's network according to its risk profile.
2.3.1Establish a centrally managed regime for security updates.
2.3.2Configure devices so that only known software runs on them.
2.3.3Deactivate unnecessary functionality.
2.3.7Change all default passwords on the ICT products before they go into production.
2.4.1Establish access control on as many network ports as possible.
2.5.1Control data flow between the organisation's segmented network zones.
2.6.4Minimise privileges for end users and special users.
2.6.5Minimise privileges on operations accounts.
2.6.7Use multi-factor authentication.
2.9.1Make a plan for regular backup of all organisation data.
2.9.3Test backups regularly.
3.2.3Decide which parts of the ICT system are to be monitored.
3.2.4Decide which data is security relevant and should be collected.
4.1.1Establish a framework for incident handling.

The page ends on a caveat, translated: the measures do not remove all risk from cyber operations, but raise an organisation's ability to handle the situation and can reduce the consequences. It names no indicator of compromise and no vulnerability.

What the pages state, and what they do not

The house table. Left, what the saved pages say. Right, what a reader would need and does not get.

Table 7. Stated and not stated, by question, across the six saved pages (20 November 2026).

QuestionStatedNot stated
Whether the incidents are linkedEquinor: does not appear to be specifically targeting Equinor (19 Nov). Dark Reading: no specific link drawn.Any statement by either company about a link, or about the other.
What the Skagerak activity was"Activity that may be an attempt"; an "incident"; "a good overview" reached.What it was, where it was, what it did, whether anything got in.
What stopped at Equinor"The cyber-attack against Equinor has now been stopped."How, by whom, on what evidence, whether access is closed, whether integrity is restored.
DataNo indication of theft (Equinor, 17 Nov), of theft or alteration (19, 20 Nov); no indication information has gone astray (Skagerak).Whether anything was accessed. "No indication" is not the same as "not accessed".
Operational technologyIT systems named by both; production not affected (both).Whether OT was touched, segregated or reachable.
Actor and routeNothing.Any actor, group, entry route or tool.
Risk level and incidentsNSM: HIGH, 27 Oct, critical infrastructure at high risk. PST: sabotage threat heightened, 12 Nov.Any statement by NSM or PST tying their pages to Equinor or Skagerak.
Other firmsNothing in a primary.Whether any other energy company was hit. Dark Reading names two it says put themselves on alert.

Where the pages differ, with nothing resolved

Each point below is a difference between what pages print. None is resolved.

  • Attempt, cyber-attack, breached. Skagerak's body says activity that may be an attempt at a cyberattack, while its headline says attempted. Equinor's page says cyber-attack, then stopped. Dark Reading's title says breached. Three words, two companies, one secondary.
  • "Not a virus" and "not specifically targeting" against the 20 November update. The first appears on 18 November, the second on 19 November. The 20 November update repeats neither and withdraws neither. It says the attack has been stopped.
  • Two incidents in "two days". The primaries print 17 November (Equinor, 18:55 CET) and 18 November (Skagerak, date only). That is two calendar days and a gap of one day (derived); in hours it is somewhere between 5 hours 5 minutes and 29 hours 5 minutes (derived). Dark Reading's title and its "consecutive days" fit the calendar count.
  • Skagerak's update has no date. The saved page prints none. Dark Reading says it came "the next day", and that rests on Dark Reading alone.
  • NSM's level and the tripling against the incident pages. NSM wrote on 27 October that the level was HIGH and that successful operations against Norwegian organisations had tripled in half a year. Neither incident page mentions NSM, the level, or any trend.
  • Production. Equinor says production is running as normal. Skagerak says the incident has not affected operations or production, and in the update, normal operations. Both say production is unaffected. Neither says anything about OT.
  • Dark Reading against PST and NSM. Dark Reading calls PST's page a cyber sabotage warning (the saved page has no cyber content) and says NSM declassified an assessment (NSM says it shares the level openly and unclassified).
  • The story the headline tells. An ordinary reading of a headline that says "breached" is that data or systems were accessed. Neither company says that. Both say there is no indication that data or information left.

What to do, in order

First, what NSM says, because it is the only primary here that tells readers what to do: at a high level, preventive measures are to be put in place immediately (its words, translated: "A high risk level requires Norwegian organisations to put preventive measures in place immediately."). The list below is this site's suggestion, built on that, for an energy sector professional or anyone who runs critical systems. It is not NSM's advice except where marked, and it is not Equinor's or Skagerak's.

Take this with you

Suggestions, in order (this site's, except where marked as NSM's)

  • Know your national level. In Norway, NSM's page states HIGH as of 27 October 2026 and asks for preventive measures immediately. Outside Norway, find your own authority's level and its date, and note whether it is published or shared only privately.
  • Read NSM's package headings and map each one to your own estate, IT and OT separately (NSM's list: critical infrastructure measures, supply chain risk management, mapping devices and software, validating that measures work, and the 21 numbered measures). Start with the self assessment service the page points to, if you are in Norway.
  • Separate IT and OT access paths, and confirm you can run production with IT systems isolated. NSM's own line is a minimum sustainable system that can run the function even during an incident; testing that is this site's suggestion.
  • Prepare statements that distinguish attempt, incident and breach, and use exact words: what was seen, what was not, what you do not yet know, and when you will next update. Date and time every revision, and do not let a hedge in the body be undone by a headline.
  • Ask suppliers for their own incident notice contacts, in writing, and what they will tell you first. NSM's page says cyber operations also hit subcontractors to organisations of significance for national security.

The question the week leaves open

Skagerak calls what it found an attempt, Equinor calls what it found stopped, and Dark Reading calls both a breach. If a customer, a regulator or an insurer asked each company, in writing, what would have to be true for its own word to be wrong, what would the two companies be able to point to?

Key facts

Sources

  1. PrimaryPress release dated 18 November 2026 (Norwegian), read as rendered text at 15:25 UTC on 20 November 2026: activity that may be an attempt at a cyberattack; used with this site's translationSkagerak Energiaccessed 2026-11-20
  2. PrimaryUpdate to the press release (Norwegian), no date printed on the saved page, read at 15:25 UTC on 20 November 2026; used with this site's translationSkagerak Energiaccessed 2026-11-20
  3. PrimaryCyber-attack stopped: one living page holding four statements, 17 Nov 18:55, 18 Nov 09:47, 19 Nov 11:40 and 20 Nov 08:55 CET, last modified 20 November 2026 09:12; read at about 15:12 UTC on 20 November 2026Equinor ASAaccessed 2026-11-20
  4. PrimaryPage on the national cyber risk level (Norwegian), published and updated 27 October 2026: level HIGH, five level scale, critical infrastructure at high risk, package of measures; read at about 15:19 UTC on 20 November 2026; used with this site's translationNorwegian National Security Authority (NSM)accessed 2026-11-20
  5. PrimaryPage on the heightened sabotage threat (Norwegian), published 12 November 2026, page data modified 16 November 2026; read at about 15:19 UTC on 20 November 2026; used with this site's translationNorwegian Police Security Service (PST)accessed 2026-11-20
  6. Reported bySecond Norwegian Energy Company Breached in Two Days, 19 November 2026 (secondary): used only for its title and for the claims attributed to it; not a source of facts in this briefDark Readingaccessed 2026-11-20

Share this briefing

Know someone who owns this problem? Send it to them.

Related briefings

The briefing, in your inbox

Practitioner analysis of cyber and AI security news. No vendor noise.

How often

Every new briefing in one email, at 7am, or at 7am, 12:30pm and 6pm. Nothing is sent when nothing is new. Unsubscribe any time.