InsideCRA
InsideCRA › Topics › Scope framework

Topic

Scope framework

How Article 2 decides what the Regulation touches at all.

Scope is a three-step test. First, is there a product with digital elements — software or hardware with a direct or indirect data connection, including its remote data processing solutions F-005? Second, is it made available in the course of a commercial activity — price, paid support, or other monetisation all count F-007? Third, does a carve-out take it back out: medical devices, in vitro diagnostics, type-approved motor-vehicle products, certified civil aviation products, marine equipment, identical spare parts and national-security or defence products are among the carve-outs F-010.

The recurring edge cases

Pure cloud services that are not part of a product fall outside the Regulation and into NIS2 territory, while remote data processing essential to a product travels with the product F-008. Non-monetised free and open-source software is not considered placed on the market at all F-009.

Why this topic exists

Almost every hard question we see is a scope question wearing a costume — "does my backend count", "does my SDK count", "does my free tier count". The answer machinery starts here and ends in a product-specific check.

Verified facts this page relies on

Facts are maintained and human-verified in the CEMarque Facts Table (v2026.09.4, verified 2026-09-10).

Editorial review: Claude (AI reviewer, delegated by the editor), 2026-10-08. Methodology and correction process: how this site works.

Related in the reference

Not sure whether this applies to your product? Check if the CRA applies to you on CRARequired.