Use four branches to decide scope. First, determine whether the product is a . Second, identify the physical device and the associated services typically required for its intended functionality. Third, test each provision's mandatory, recommended, conditional, or feature-dependent status against the product facts. Fourth, record the Device Under Test, support decision, evidence, and reassessment triggers before making a claim.
1
Section 1
What is in scope of ETSI EN 303 645?
ETSI EN 303 645 applies to consumer IoT devices connected to network infrastructure, such as the Internet or a home network, and to their interactions with associated services. The standard gives examples such as connected children's toys and baby monitors, smoke detectors, door locks, window sensors, gateways, smart cameras, smart TVs, speakers, wearable health trackers, home automation and alarm systems, connected appliances, and smart home assistants.
Decide whether the product is a , which associated services are part of the overall IoT product, and whether any security claim depends on companion apps, cloud services, application programming interfaces (APIs), telemetry services, gateways, hubs, or support processes. Having software alone does not put a product in scope.
Branch 1 - consumer product: continue when the network-connected or network-connectable device is typically used by consumers in the home or as an electronic wearable. Retail sale, professional installation, or business deployment does not by itself move an otherwise consumer device out of scope.
Branch 2 - primary industrial purpose: stop the EN 303 645 scope analysis when the device is primarily intended for manufacturing, healthcare, or another industrial application. Record the intended-purpose evidence and check the separate law, contract, or sector standard that prompted the review.
Record the device and required associated services together, but keep the boundary explicit: the EN provisions apply to the device and its interactions with associated services, and V3.1.3 defines those services as part of the overall consumer IoT product.
Do not claim that EN 303 645 covers every security issue: the standard describes a baseline and says it is not intended to solve all consumer IoT security challenges.
Defines the EN 303 645 scope for consumer IoT devices, interactions with associated services, examples of covered products, constrained devices, and out-of-scope industrial categories.
connected to network infrastructure
2
Section 2
How should associated services be handled?
EN 303 645 defines associated services as digital services that, together with the device, form part of the overall consumer IoT product and are typically required for intended functionality. Examples include mobile applications, cloud computing or storage, third-party APIs, and a manufacturer-chosen telemetry service.
EN 303 645 V3.1.3 defines associated services as part of the overall consumer IoT product and applies its provisions to the device and its interactions with those services. For practical evidence work, this means a team should not ignore a service that is required for authentication, updates, telemetry, remote access, deletion, user information, or vulnerability handling.
List every associated service needed for the intended product functionality.
Classify a manufacturer-selected telemetry service, required mobile application, cloud storage endpoint, or third-party API as an associated service when it forms part of the product and is typically required for intended functionality.
Keep a user-chosen news website, streaming service, video-sharing service, or optional app outside the associated-service boundary when the manufacturer does not include it as part of the product's intended functionality.
State which security provisions rely on a companion app, cloud endpoint, gateway, hub, API, or telemetry flow.
Keep a separate note for external services that are visible to the user but not required for the consumer IoT product's intended functionality.
Review the boundary whenever firmware, apps, cloud behavior, APIs, or support processes materially change.
Defines associated services as services that form part of the overall consumer IoT product and are typically required for intended functionality.
part of the overall consumer IoT product
3
Section 3
When can a provision be marked not applicable?
EN 303 645 recognizes that applicability depends on the device. Provision 5.0-1 requires a recorded justification for each recommendation considered not applicable or not fulfilled. Annex B separately limits an N/A support entry to a conditional provision whose condition is not satisfied or a provision tied to a feature, capability, or mechanism that does not exist.
The standard gives examples such as resource constraints, a missing function, or an additional industry or regulatory requirement that precludes a provision. A statement such as "not relevant to our architecture" is not enough: identify the condition or feature, the product facts, and the supporting evidence.
For a mandatory provision without an applicable conditional (C) or feature-dependent (F) status, do not use N/A. Record support or non-support and let the applicable assessment or scheme determine the consequence.
Record a justification for every recommendation treated as not applicable or not fulfilled.
Tie each resource-constraint claim to the use case, the product facts, and the exact provision it affects. Do not use a product-wide constrained-device label as a substitute for provision-by-provision analysis.
Tie each N/A claim to an unmet Annex B condition or the absence of the relevant feature, capability, or mechanism.
Keep N/A justifications reviewable by assurance assessors, supply-chain stakeholders, security researchers, or retailers.
Supports recommendation justifications through Provision 5.0-1 and defines Annex B's separate C and F conditions for using N/A.
A justification shall be recorded
4
Section 4
What evidence should be ready for TS 103 701 assessment?
ETSI TS 103 701 is a conformance assessment methodology for consumer IoT devices, their relation to associated services, and corresponding relevant processes against ETSI EN 303 645. It can be used in first-, second-, or third-party assessment and within certification or conformance-declaration schemes, but it does not define a scheme.
For scope work, the key assessment artifacts are the Device Under Test identification, the Implementation Conformance Statement, and the Implementation eXtra Information for Testing. TS 103 701 says the supplier organization provides ICS and IXIT to the test laboratory, and the test laboratory uses them to derive a test plan.
Complete the DUT identification for the specific and software version being assessed.
Complete the ICS in a way that makes conditional and feature-based N/A claims consistent with implemented functionality.
Complete the IXIT for provisions claimed as Yes, including information needed for conceptual and functional test activities.
Provide enough product, service, process, and user-documentation evidence for the test laboratory to check completeness, consistency, and soundness.
Use external evidence only where the assessment scheme and TS 103 701 method allow it.
Defines the conformance assessment methodology, DUT, Supplier Organization, Test Laboratory, ICS, IXIT, assessment phases, conceptual tests, functional tests, and use of external evidence.
The TL uses these documents to derive a test plan.
Recommended next step
Assign the scope and assessment evidence
This ETSI EN 303 645 guidance helps turn scope, associated-service boundaries, provision-specific resource constraints, ICS, and IXIT evidence into assigned review work.
Practical scope checklist before publishing a claim
Before a public page, procurement response, or assessment package says that a product follows ETSI EN 303 645, make the scope statement specific enough to test. The standard is a baseline for consumer IoT, while TS 103 701 test cases are generic and expect competent bodies to derive a suitable test plan.
The scope record should stand alone: a reviewer should be able to identify the device, associated services, relevant processes, provisions claimed Yes or N/A, and the evidence location without relying on tribal knowledge.
Name the specific consumer IoT product and the software or firmware version used for the claim.
List required associated services and the provisions that depend on them.
Separate baseline EN 303 645 claims from additional internal policy, customer, legal, or procurement requirements.
Record constrained-device reasoning and every recommendation treated as not applicable or not fulfilled.
Reassess after a change to intended use, target market, device model, firmware, companion app, cloud endpoint, API, telemetry provider, update route, authentication feature, support process, or public claim.
Avoid broad compliance wording unless the boundary, assessment method, evidence set, and version are stated.
Primary source for EN 303 645 scope, consumer IoT examples, associated-service definitions, provision-specific resource constraints, baseline limitations, and Provision 5.0-1 justification records.
Defines the EN 303 645 scope for consumer IoT devices, interactions with associated services, examples of covered products, constrained devices, and out-of-scope industrial categories.
Defines associated services as services that form part of the overall consumer IoT product and are typically required for intended functionality.
Show 2 more
Supports recommendation justifications through Provision 5.0-1 and defines Annex B's separate C and F conditions for using N/A.
Assessment source for DUT identification, Supplier Organization and Test Laboratory roles, ICS, IXIT, conceptual and functional tests, and use of external evidence.
Defines the conformance assessment methodology, DUT, Supplier Organization, Test Laboratory, ICS, IXIT, assessment phases, conceptual tests, functional tests, and use of external evidence.
Supports assessment-boundary language by explaining that TSOs are generic and that competent bodies derive a suitable test plan.
"The TL uses these documents to derive a test plan."