Skip to content

Framework Watch W4526 Oct – 10 Nov 2026

SOC 2 gets its first rewrite since 2017, and NIS2 moves from law to audits

The first Framework Watch covers the last two weeks, because the biggest story of the autumn landed on 28 October: the AICPA wants to restructure the SOC 2 Trust Services Criteria for 2027 and add AI risk to them. Meanwhile PCI SSC clarified what it expects from service providers, the first horizontal Cyber Resilience Act standards are about to be published, and NIS2 is moving from transposition to supervision in three large member states.

Published by the ScanComb compliance team · RSS

This issue at a glance

  1. SOC 2Proposed: engagements beginning on or after 31 Dec 2027AICPA proposes the 2027 SOC 2 Trust Services CriteriaExposure draft consolidates the criteria, regroups the common criteria and adds AI risk points of focus. Comments close 15 January 2027.
  2. PCI DSSPublished 10 Nov 2026PCI SSC explains who counts as a service provider and what they owe customersNew information supplement on Requirements 12.8 and 12.9, multi-tenant and nested providers, responsibility matrices and AOCs. No requirement changes.
  3. EU CRAPublication scheduled 17 Nov 2026First horizontal CRA standards, EN 40000-1-1 and -1-2, due on 17 NovemberVocabulary and cyber-resilience principles passed the CEN-CENELEC vote; publication is scheduled for 17 November. No CRA standard is cited in the Official Journal yet.
  4. NIS2 · FranceAssembly debate from 9 Nov 2026France's NIS2 bill reaches the National Assembly, two years lateThe resilience bill transposing NIS2, CER and DORA is in plenary debate. Deputies deleted the Senate's encryption article 16 bis on 10 November.
  5. NIS2 · GermanyQ4 2026BSI to chase unregistered NIS2 entities this quarterRegistration under the NIS2 implementation act was due on 6 March 2026. The BSI has said it will contact entities that obviously should have registered in Q4 2026.
  6. NIS2 · ItalyDeadline 31 Oct 2026Italy's deadline for ACN security measures passed on 31 OctoberEntities notified by ACN had until 31 October 2026 to implement the baseline security measures. Supervision and inspections start from November.
SOC 2Draft for commentHigh impact

AICPA proposes the 2027 SOC 2 Trust Services Criteria

Proposed: engagements beginning on or after 31 Dec 2027

What changed

On 28 October 2026 the AICPA's SOC 2 Working Group published an exposure draft of the proposed 2027 Trust Services Criteria and Description Criteria. It is the first full rework of the criteria since the 2017 edition (points of focus were revised in 2022). The draft merges duplicated concepts, removes some criteria, adds others where the working group wants more emphasis, and rewrites existing wording.

An analysis by SOC2Auditors.org counts 50 criteria instead of 61, with the common criteria shrinking from 33 to 20 and regrouped from CC1–CC9 into CC1–CC8. Availability and Confidentiality each gain one criterion. New points of focus cover AI governance, model monitoring, prompt manipulation, data poisoning, transparency of AI-generated output, training data and automated decision-making. There is no separate AI criterion: the AI language sits inside existing criteria.

How it affects you

Nothing changes for reports issued today: the 2017 criteria with the 2022 points of focus stay in force, and the proposal still needs approval in 2027. But early adoption is allowed, and a 2028 audit period starts during 2027. Teams that map controls by criterion number (CC6.1, CC8.1 and so on) will have to remap, because several criteria move to new groups. SaaS companies that ship AI features should expect auditors to ask how models, prompts and training data are governed.

What to do

  • Keep running your current SOC 2 program on the 2017 criteria; do not rebuild controls around a draft.
  • Read the exposure draft and send comments before 15 January 2027 if the AI points of focus do not fit your product.
  • List where your policies, evidence and tooling reference criterion IDs, so a remap is a mapping exercise, not a rewrite.
  • If you ship AI features, start documenting model inventory, prompt-injection testing and training-data sources now.

Background: SOC 2 explained

PCI DSSNew guidanceMedium impact

PCI SSC explains who counts as a service provider and what they owe customers

Published 10 Nov 2026

What changed

PCI SSC published the information supplement Understanding PCI DSS Service Providers v1.0, written with its Board of Advisors and the Global Executive Assessor Roundtable. It includes a decision flow for whether a vendor is a third-party service provider (TPSP), explains when a provider can "impact the security" of a customer's cardholder data environment (managed networks, remote administration, hosting, backup), and treats administrative control as the deciding factor for multi-tenant platforms. It also covers nested providers, a seven-step TPSP management lifecycle, examples of responsibility splits, what belongs in a provider's Attestation of Compliance, and an appendix of service-provider-only requirements in PCI DSS v4.x.

How it affects you

The supplement does not change PCI DSS, but assessors will read Requirements 12.8 (managing providers) and 12.9 (provider acknowledgement and support) through it. Cloud and SaaS vendors in a merchant's payment flow should expect sharper questions: a written responsibility matrix, evidence of compliance per service, and clarity about which sub-providers sit behind them.

What to do

  • Merchants: check your TPSP list against the decision flow and confirm each provider's AOC covers the services you actually use.
  • Service providers: publish a responsibility matrix per service and name the nested providers behind it.
  • Review contracts for the Requirement 12.9 acknowledgement and for how you answer customer evidence requests.

Background: PCI DSS explained

EU CRAStandard publishedMedium impact

First horizontal CRA standards, EN 40000-1-1 and -1-2, due on 17 November

Publication scheduled 17 Nov 2026

What changed

EN 40000-1-1 (vocabulary) and EN 40000-1-2 (principles for cyber resilience) cleared the CEN-CENELEC formal vote on 1 October 2026 and are scheduled for publication on 17 November 2026, slightly later than the 30 October target. They are the first of the roughly 41 harmonised standards requested under mandate M/606. EN 40000-1-3, the standard for secure development and vulnerability handling, is still a draft.

How it affects you

Published is not the same as cited: until the Commission cites a standard in the Official Journal, following it gives no presumption of conformity under Article 27. Still, 1-1 and 1-2 fix the vocabulary and principles that later product standards build on. Manufacturers preparing for the main CRA obligations on 11 December 2027 can now align their risk assessments and technical documentation with the agreed terms. Vulnerability and incident reporting through ENISA's Single Reporting Platform has applied since 11 September 2026.

What to do

  • Buy EN 40000-1-1 and -1-2 from your national standards body once published and align your CRA risk assessment wording with them.
  • Track EN 40000-1-3: it will shape secure-development and vulnerability-handling evidence.
  • Confirm your team can report an actively exploited vulnerability through the ENISA Single Reporting Platform within 24 hours.

Background: EU Cyber Resilience Act explained

NIS2 · FranceLaw & transpositionMedium impact

France's NIS2 bill reaches the National Assembly, two years late

Assembly debate from 9 Nov 2026

What changed

The National Assembly began examining the projet de loi résilience on 9 November 2026. The bill transposes NIS2 and the Critical Entities Resilience directive and adapts French law to DORA. On 10 November deputies voted 69 to 37 to delete article 16 bis, a Senate addition that would have barred authorities from forcing encryption providers to weaken their security. The government backed the deletion, calling the article too broad and unrelated to the bill. France missed the October 2024 transposition deadline and has been referred to the EU Court of Justice.

How it affects you

France is one of the largest NIS2 markets still without national rules. Once the bill passes and ANSSI publishes the implementing measures, essential and important entities, and their suppliers, will face registration, security measures and incident reporting. Suppliers selling into French essential entities should expect NIS2 questionnaires in 2027 contracts.

What to do

  • If you operate in France, check whether your sector and size put you in scope of NIS2.
  • Prepare Article 21 evidence now: it is the same list of measures in every member state.
  • Watch for the final vote and the ANSSI implementing decrees that set the actual deadlines.

Background: NIS2 / GDPR / HIPAA explained

NIS2 · GermanyEnforcementHigh impact

BSI to chase unregistered NIS2 entities this quarter

Q4 2026

What changed

Germany's NIS2 implementation act required essential and important entities to register with the BSI by 6 March 2026. Registrations remain well below the roughly 29,500 entities the government expects, although published counts vary widely between sources. A BSI department head told Tagesspiegel Background that the agency will write to entities that obviously should have registered during the fourth quarter of 2026, starting with a hearing. Failing to register is an administrative offence under § 65 BSIG with fines of up to €500,000. Law firms report no published fine decisions so far.

How it affects you

Registration is the cheapest NIS2 duty to meet and the easiest one for the BSI to check, so it is where enforcement starts. Registering late ends the ongoing violation but does not undo the missed deadline. Once registered, an entity also owes the BSI incident reports and must implement the § 30 BSIG risk-management measures.

What to do

  • Run a scope check for every German legal entity in your group, not only the parent.
  • Register in the BSI portal now if you are in scope, and document why if you concluded you are not.
  • Make sure your incident reporting runbook names who files the 24-hour early warning with the BSI.

Background: NIS2 / GDPR / HIPAA explained

NIS2 · ItalyDeadlineMedium impact

Italy's deadline for ACN security measures passed on 31 October

Deadline 31 Oct 2026

What changed

Under Legislative Decree 138/2024, essential and important entities notified by Italy's national cybersecurity agency (ACN) had until 31 October 2026 to adopt the baseline security measures ACN defined for them. Italian trade press reports that ACN will start its programme of checks and inspections from November 2026, with periodic, planned verification for essential entities. Fines reach €10 million or 2% of worldwide turnover for essential entities and €7 million or 1.4% for important entities.

How it affects you

Italy is one of the first member states where NIS2 has moved from paperwork to supervision. Obligations there run from the individual ACN notification, not from the law, so each entity has its own clock. Suppliers to Italian essential entities should expect their customers to push measures down the supply chain.

What to do

  • If you received an ACN notification, keep evidence for each baseline measure ready for an inspection.
  • Note the annual windows: registration from 1 January to 28 February, activity and service updates from 1 May to 30 June.
  • Check ACN's official notices for the inspection schedule; dates in trade press are not yet confirmed by ACN.

Background: NIS2 / GDPR / HIPAA explained

Checked, nothing new

ISO 27001No new edition. ISO/IEC 27001:2022 with Amendment 1:2024 (climate action) is current, the 2013 transition ended on 31 October 2025, and no revision of 27001 or 27002 is underway. Pages promising an "ISO 27001:2026" are wrong.
NIST CSF & SP 800-53We found no new NIST CSF or SP 800-53 release in the period. CSF 2.0 and SP 800-53 Rev. 5.2.0 remain the current versions.

Dates to watch

  1. 17 Nov 2026 · EU CRA

    Scheduled publication of EN 40000-1-1 and EN 40000-1-2, the first horizontal CRA standards.

  2. 2 Dec 2026 · EU AI Act

    Date set by the Digital Omnibus on AI for the Article 50(2) duty to mark AI-generated content.

  3. 1 Jan 2027 · TISAX

    TISAX assessments ordered from this date run against the VDA ISA2027 catalogue.

  4. 15 Jan 2027 · SOC 2

    Comment period on the proposed 2027 Trust Services Criteria closes.

  5. 2 Dec 2027 · EU AI Act

    High-risk obligations for Annex III AI systems apply, delayed from August 2026.

  6. 11 Dec 2027 · EU CRA

    Main Cyber Resilience Act obligations apply to products with digital elements placed on the EU market.

Know which of these changes hit your controls.

WardBee checks your AWS, GitHub and GitLab evidence against ISO 27001, SOC 2, NIST, CIS and the EU CRA, and shows what is verified, failing or still manual.

Framework Watch summarises public sources in our own words and links to them. It is not legal advice; check the primary text before you act on a date or requirement.

What's new · v1.0.0

ScanComb and WardBee 1.0: compliance checks, TISAX and SOC 2 readiness, and a new public site

This is the first release of ScanComb and WardBee. WardBee brings automated compliance checks, framework workspaces, reports and task tracking for engineering, security and compliance teams. scancomb.com adds free checks and a TISAX readiness check, plus guides and news.

Highlights

  • TISAX readiness check Answer a public questionnaire and get a free readiness score by email. A paid report adds findings, an action plan for each chapter, a roadmap and a PDF. You can import the gaps into a WardBee workspace as tasks.
  • Dedicated TISAX section in WardBee Manage TISAX in one place. Set the scope, keep a self-assessment register, follow an action plan with tasks, track audits and labels, and manage suppliers and exports.
  • SOC 2 readiness Work through a readiness questionnaire, criterion guidance, a policy pack and reviews. Criteria are explained in plain words and questions can be answered in the side drawer. You can download a SOC 2 readiness report as a PDF.
  • Sovereignty Profile free check Run the free Sovereignty Profile check and get a report. The scores are explained in plain words.
  • Projects with a shared scan pool Run several projects or clients in separate workspaces that share one pool of scans. A For consultants page explains the setup.

Improvements

  • Resource inventory See an inventory of your resources with filters, saved views and notifications.
  • EU Cyber Resilience Act support Prepare for the EU Cyber Resilience Act with product classification and a continuous technical file.
  • NIS2 Supplier Check Assess suppliers against NIS2 with the NIS2 Supplier Check.
  • Free AI security check and AI Shield playbooks Take a free AI security check and read practical playbooks on AI agent permissions, prompt injection, shadow AI and more.
  • Manual control verification Verify controls that cannot be checked automatically, using a clearer drawer for manual controls.
  • Clearer controls and findings Findings and resource names are easier to read, you can filter to checks-only scans, and you can compare one scan with the previous one.
  • Faster control and dashboard pages Controls, the dashboard and risks load faster. App pages show a loading state right away.
  • Better start for new workspaces New workspaces start with ISO 27001 and SOC 2, with an explanation of what scans do. If no frameworks are chosen, a Choose frameworks step guides you.
  • Support tickets, announcements and notification bell Open support tickets inside WardBee and get email updates. Announcements appear in a header bell.
  • New site design, menu and guides scancomb.com has a new look and a grouped menu with News, Free checks and Guides. WardBee uses the same visual style, and the in-app docs are task-focused guides.
  • What's New and Framework Watch A What's New dialog shows release notes on scancomb.com. A weekly Framework Watch news issue is also published.
  • Team invitations and two-factor sign-in Invite teammates by email with consistent role names. Two-factor setup includes a QR code.

Fixes

  • Security improvements to sign-up and sign-in Sign-up and sign-in are now better protected.
  • More accurate AWS multi-factor authentication checks All MFA device types are now recognized, and users who only use programmatic access are no longer flagged.
  • Confirmed failures are shown correctly A confirmed failure now outranks an error in a control's status.
  • One critical-control email per scan You now get a single critical-control email per control for each scan.
  • Smoother onboarding and failed checks Workspaces without frameworks are sent to setup. Checks that fail are refunded, and queued checks show as Queued.
  • Correct access errors Signed-out or unauthorized requests now get a proper access error instead of a server error.