News

The regulatory changes and threat trends shaping our clients' obligations, with what each one means in practice.

Updated . Regulatory dates last verified 2 November 2026 against official sources and primary legal reporting. Timelines change often; confirm with the issuing authority before relying on a date.

Daily brief

Today: lock down MSP remote access after the SCKit ScreenConnect campaign, patch Apache HTTP/2 servers, revoke stale vendor access as Expedia confirms a supplier breach, and watch for fake meeting links from North Korea's FaceStealer.

Illustration: SenasoftConsult

Attackers use a ScreenConnect add-on to plant rogue remote-access clients on at least 288 computers at 48 organizations served by MSPs

Starting November 11, attackers used cloud-hosted ScreenConnect panels run by managed service providers to install attacker-controlled clients and a toolkit researchers call SCKit, reaching every affected machine within about 90 minutes, according to Huntress. Huntress and Microsoft (in a November 13 analysis) tie the entry point to the third-party RMM+ extension, whose versions 1.0.31 and 1.0.32 accepted a blank shared access key; ConnectWise disabled five such extensions across about 400 partner environments and says it found no flaw in ScreenConnect itself. SCKit tries to spread to technicians who connect to an infected endpoint, which ScreenConnect client 26.6.5 and later block.

Why it matters: If you use an MSP, ask today whether it runs ScreenConnect with third-party extensions and whether its technician clients are on 26.6.5 or later. MSPs should keep the named extensions disabled, revoke ScreenConnect and identity-provider sessions, rotate credentials, and rebuild any endpoint whose integrity cannot be confirmed.

Sources: Microsoft Security Blog, CyberScoop

Illustration: SenasoftConsult

Vulnerability

Apache fixes CVE-2026-119618, a critical HTTP/2 flaw that can let unauthenticated attackers run code on web servers

Apache released HTTP Server 2.4.71 on November 11 to fix CVE-2026-119618, a race condition in the mod_http2 module that can corrupt heap memory and lead to remote code execution; versions 2.4.55 through 2.4.70 with HTTP/2 enabled are affected, as are standalone mod_h2 builds 2.0.8 through 2.0.42. Red Hat rates it 9.8 on CVSS and says public research has shown a reliable exploit, while Wiz reported no exploit available and no attacks in the wild as of November 12. Debian stable releases and Amazon Linux were still listed as vulnerable or pending at the time of reporting.

Why it matters: Inventory internet-facing Apache servers and upgrade to 2.4.71 or your vendor's fixed package, then restart the service. Where you cannot patch yet, remove h2 and h2c from the Protocols directive so the server offers HTTP/1.1 only, and confirm the change took effect.

Sources: The Hacker News, Bitsight

Illustration: SenasoftConsult

Industry

Expedia confirms attackers reached its systems through a compromised data platform vendor as the n0n group claims nearly one billion traveler records

Expedia Group confirmed on November 12 that attackers entered its systems through a compromised third-party data platform provider in a supply chain attack that also hit other companies; it has not named the vendor or confirmed what data was taken. The extortion group n0n claims more than 830 million loyalty program records and hundreds of millions of account records. Separately, Wiz and Sentra documented an October 14 to 26 campaign that used compromised credentials tied to former vendor Qubole to download data from customers' cloud environments, finding that many former customers had never revoked the access they granted; Expedia has not said whether its breach is linked.

Why it matters: Offboarding a vendor is not complete until its keys, roles and cloud permissions are revoked. Review every third-party integration with read access to your data warehouses, remove access for vendors you no longer use, and set alerts for bulk downloads by service accounts.

Sources: Skift, Security Affairs

Illustration: SenasoftConsult

Threat

FBI takes down infrastructure behind North Korea's FaceStealer fake-meeting scheme, blamed for more than $400 million in crypto theft

On November 12 the US government said it had court authorization to dismantle cloud infrastructure used by FaceStealer, a North Korean scheme that sends fake Zoom or Teams links and a bogus "you're on mute" update that installs crypto-stealing malware. The FBI attributes the activity to the group tracked as Sapphire Sleet, UNC1069 or BlueNoroff, says it has taken more than $400 million over 18 months, and says it seized more than 900 webcam videos of targeted tech workers. The same action sought to seize or restrain more than $1.2 billion stolen in the October 29 Binance theft.

Why it matters: Tell finance, engineering and executive staff that a meeting link prompting a software update or audio fix is a warning sign, even from a known contact whose account may be hijacked. Allow meeting clients only from managed installs and verify unexpected invitations through a second channel.

Sources: The Register

Key dates ahead

Deadlines our clients are planning around, in date order.

  • 2 Dec 2026EU AI Act: marking of AI-generated content for systems already on the market
  • 11 Dec 2026Cybersecurity Information Sharing Act of 2015 expires unless extended
  • July 2027HIPAA Security Rule final action (target, not binding)
  • 2 Dec 2027EU AI Act: high-risk obligations for stand-alone (Annex III) systems
  • 11 Dec 2027EU Cyber Resilience Act: full application
  • To be setCIRCIA reporting begins on the final rule's effective date
  • To be setCMMC Phase II (third-party Level 2 assessments): suspended until further notice

Regulatory watch

New obligations and the status of pending rules in the U.S. and EU. Each entry shows its jurisdiction and legal status.

Last verified 2 November 2026.

New obligation EU · Binding regulation

EU Cyber Resilience Act: vulnerability and incident reporting is now mandatory

Since 11 September 2026, manufacturers of products with digital elements sold in the EU must report actively exploited vulnerabilities and severe security incidents through ENISA's new Single Reporting Platform. An early warning is due within 24 hours, a full notification within 72 hours, and a final report within 14 days for vulnerabilities or one month for incidents. This applies to products already on the market, not only new ones. The rest of the Act applies from 11 December 2027.

What it means for you: Manufacturers and software vendors selling into the EU need a working process to detect, triage, and report exploitation within 24 hours. If you rely on such vendors, ask how they are meeting this duty.

Sources: ENISA, Hogan Lovells Cadwalader

Status change U.S. federal, defense contracts · Binding rule, Phase II suspended

CMMC Phase II suspended: third-party Level 2 certification will not start on 10 November

On 13 July 2026 the Department of Defense (also styled the Department of War) suspended CMMC Phase II, which would have required third-party (C3PAO) Level 2 assessments in applicable solicitations from 10 November 2026. Later milestones are on hold until further notice, and no new date has been set. During the suspension, contracting officers may require only Level 1 or Level 2 self-assessments.

What it means for you: The certification deadline has moved, but the security obligations have not. DFARS 252.204-7012 and the 110 NIST SP 800-171 controls still apply, and inaccurate self-assessments still carry contractual and False Claims Act risk. Keep remediation and evidence on track so you are ready when Phase II resumes.

Sources: DoD CIO implementing memorandum, Morgan Lewis, Wiley

Status update U.S. federal · Statute in force; final rule pending

CIRCIA: the final rule is now under White House review

On 1 October 2026 CISA sent the final rule under the Cyber Incident Reporting for Critical Infrastructure Act to the White House Office of Information and Regulatory Affairs. That review can take up to 90 days, so publication is likely early in 2027, and the reporting duties are expected to take effect no sooner than 60 days after publication. Until the rule takes effect, CISA states that organizations are not required to report.

What it means for you: The statute sets 72 hours for covered incidents and 24 hours for ransom payments; those windows apply only once the final rule is in force, and its text will settle which entities are covered. Use the review period to confirm whether you are likely to be covered and to assign who decides when to report.

Sources: CISA, Covington (Inside Privacy)

Status update U.S. federal · Statute, temporary extension

Cyber threat information-sharing law extended only to 11 December 2026

The Cybersecurity Information Sharing Act of 2015, which gives companies legal protections when they share cyber threat indicators with the government and each other, was extended to 11 December 2026 by the stopgap funding law signed on 2 September. A long-term reauthorization has not passed.

What it means for you: If the law lapses, the liability and antitrust protections for sharing threat information could lapse with it. Legal and security teams should agree now on how they will share threat information if that happens.

Sources: The White House (H.R. 6500), Defense One, Federal News Network

Regulatory watch EU · Binding regulation

EU AI Act: high-risk deadlines deferred, transparency duties now apply

The EU's Digital Omnibus on AI entered into force on 27 July 2026. It defers obligations for stand-alone high-risk AI systems to 2 December 2027 and for AI embedded in regulated products to 2 August 2028. The Article 50 transparency obligations were not deferred and have applied since 2 August 2026; providers of generative AI systems placed on the market before that date have until 2 December 2026 to add machine-readable marking of AI-generated content (Article 50(2)).

What it means for you: The extra time is best used to inventory AI systems, classify their risk, and build a management system such as ISO/IEC 42001 that will support compliance when the deadlines arrive.

Sources: Regulation (EU) 2026/1744 (EUR-Lex), DLA Piper, Usercentrics

Regulatory watch U.S. federal · Proposed rule, not yet binding

HIPAA Security Rule overhaul: final action now targeted for July 2027

HHS proposed the largest update to the HIPAA Security Rule in two decades in January 2025, including mandatory encryption of ePHI, multi-factor authentication, and stricter oversight of business associates. The federal regulatory agenda has moved the final rule to a July 2027 target, and it could still change or be withdrawn.

What it means for you: The current Security Rule is still being enforced, and risk analysis remains the most frequently cited deficiency. A current, documented risk analysis is the best preparation for either outcome.

Sources: Unified Agenda, RIN 0945-AA22 (reginfo.gov), Clark Hill, The HIPAA Journal

Threat trends

What the latest evidence says about how breaches happen.

Threat trend

Exploited vulnerabilities and third parties now drive breaches

Verizon's 2026 Data Breach Investigations Report found that exploitation of vulnerabilities was the leading way in, at 31% of breaches, while credential abuse fell to 13%. Third parties were involved in 48% of breaches, and ransomware appeared in 48%. Patching slowed: the median time to fully remediate rose to 43 days, and only 26% of vulnerabilities in CISA's Known Exploited Vulnerabilities catalog were fully remediated.

What it means for you: Prioritize patching by known exploitation rather than severity score alone, and review critical vendors continuously rather than once a year. Both are now where most breaches start.

Sources: SecurityWeek, Help Net Security

This month

Cybersecurity Awareness Month 2026: “Don't Make It Easy for Them”

The National Cybersecurity Alliance opened the 23rd Cybersecurity Awareness Month on 1 October with a focus on four everyday habits: strong, unique passwords; multi-factor authentication; keeping devices updated; and caution with suspicious messages.

What it means for you: October is a good moment for a short staff refresher and a check that multi-factor authentication is enforced on email, remote access, and administrator accounts.

Sources: National Cybersecurity Alliance

Earlier news

Previous editions, kept for reference. Some details have since changed; see the current items above for the latest status.

September 2026 edition3 items: HIPAA, CIRCIA, EU AI Act

The CIRCIA item below reflects CISA's September target, which has since passed without a final rule.

Regulatory watch

HIPAA Security Rule overhaul: final action now targeted for July 2027

HHS proposed the largest update to the HIPAA Security Rule in two decades in January 2025, including mandatory encryption of ePHI, multi-factor authentication, and stricter oversight of business associates. The federal regulatory agenda has since moved the final rule to a July 2027 target, and it could still change or be withdrawn.

What it means for you: The current Security Rule is still being enforced, and risk analysis remains the most frequently cited deficiency. A current, documented risk analysis is the best preparation for either outcome.

Sources: Clark Hill, The HIPAA Journal

Regulatory watch

CIRCIA final rule targeted for September 2026

CISA missed the October 2025 statutory deadline for the CIRCIA final rule, held stakeholder town halls in June 2026, and now targets September 2026 for publication. Once in effect, covered entities across 16 critical-infrastructure sectors must report covered cyber incidents within 72 hours and ransom payments within 24 hours.

What it means for you: Those reporting clocks are set in the statute. Organizations that may be covered should confirm scope now and build the reporting decision into their incident response plans. Check cisa.gov/circia for publication status.

Sources: Hunton Andrews Kurth, Federal News Network

Regulatory watch

EU AI Act: high-risk deadlines deferred, transparency duties now apply

The EU's Digital Omnibus on AI entered into force on 27 July 2026. It defers obligations for stand-alone high-risk AI systems to 2 December 2027 and for AI embedded in regulated products to 2 August 2028. The Article 50 transparency obligations were not deferred.

What it means for you: The extra time is best used to inventory AI systems, classify their risk, and build a management system such as ISO/IEC 42001 that will support compliance when the deadlines arrive.

Sources: DLA Piper, Usercentrics

Firm announcements

Announcement

SenasoftConsult launches a new website and visual identity

The new site brings together the firm's services, its approach, its research focus, and its leadership team, alongside a refreshed logo and brand system built for clarity across print and screen.