Skip to content

Draft — not approved. A working draft by UASK. It may change without notice.

References

Status
Draft
Version
0.1.0
Authority
UASK standard
Applies to
operating-system
Markdown source

Version: 0.1 · texts read 2026-11-21

This document is informative. It holds the dated statements about law and about standards that the rules of the Construction Constitution and of Vulnerability management rest on, so that a rule stays jurisdiction-neutral and never has to change when a date does. No sentence here creates an obligation (SCF-CHG-002): what a product has to satisfy is in the Constitution and the profiles. Terms are defined in the glossary.

The legal notice of the overview applies to every row. The rows summarise published texts to make obligations verifiable in engineering; they are not legal advice, and a product placed on a regulated market needs qualified counsel on the regime that applies to it.

1. How to read the claims

The rows of sections 3 and 4 are claims of the class Regulatory of the knowledge base, section 4: the published text, the provision, and the date from which it applies. Each row also names the rules it informs. Sections 2 and 5 are patterns: they read from the rows and cite them by id.

  • Two regimes. The document holds the regime of the European Union and the regime of the United Kingdom, the two for which SCF 1.0 gives dated claims (decision D5 of the plan to version 1.0, 2026-11-21). A product placed on any other market names its regime in its product record (SCF-GOV-008); the absence of a regime here says nothing about whether it exists.
  • Rules cite, rows state. A rule of the Constitution may name a provision in its Source line; the line stays with the rule. What the provision says, and from when, is stated once, here. Provisions cited only in a rule’s Source line and not needed by the rules named in this document are not repeated.
  • Paraphrase. A row paraphrases; words in quotation marks are the text’s own. “Applies from” is the date on which the provision takes effect, not the date of publication.
  • Texts read. Section 3: Regulation (EU) 2024/2847 as published in the Official Journal (L series, 20.11.2024), opened on 2026-11-21 from the Publications Office of the European Union. Section 4: the Act as enacted and the Regulations as made, opened on 2026-11-21 from legislation.gov.uk. Later corrigenda, consolidated and revised versions, and acts adopted under either instrument (delegated and implementing acts, commencement orders, amending regulations) were not compared; reading them belongs to the review before related work (SCF-CHG-017).
  • Ids. Three letters name the subject (CRA, UKR, STD), two digits the claim and a letter a part of it, as in CRA-10a. A published row id keeps its fact through a refresh and is not reused for another fact; a withdrawn row leaves its id unused.
  • Refresh. A row is refreshed by reading its source again. A changed fact is a PATCH change of this document (SCF-CHG-006); a changed provision that alters what a rule has to say is a change of that rule, classed by the Change policy. The document is reviewed every six months.

2. From a declared market to a regime

A product declares the markets it is placed on (SCF-GOV-008); the declaration decides which regime the pipeline reflects (SCF-LGL-006). Both read from the rows of sections 3 and 4.

Declared market Regime What puts a product inside Rows
European Union Regulation (EU) 2024/2847, the Cyber Resilience Act a product with digital elements made available on the Union market whose intended purpose or foreseeable use includes a data connection to a device or network; the place of the manufacturer is not a condition CRA-01 to CRA-03
United Kingdom Product Security and Telecommunications Infrastructure Act 2022, Part 1, with the Security Requirements Regulations 2023 a relevant connectable product made available to consumers in the United Kingdom; desktop and laptop computers, and tablet computers without a cellular capability, are excepted UKR-01 to UKR-03, UKR-06

A product declared for both markets is inside both regimes unless one excepts it. An exception under one regime, such as the United Kingdom exception for desktop and laptop computers (UKR-06), says nothing about the other. That exception names computers; whether a system distributed apart from the computer it runs on is inside it is a question of the text and of counsel (the legal notice of the overview), and the regimes that follow from a declared market are named in the product record (SCF-GOV-008).

3. European Union: Regulation (EU) 2024/2847

Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024 on horizontal cybersecurity requirements for products with digital elements (the Cyber Resilience Act), OJ L, 20.11.2024: https://eur-lex.europa.eu/eli/reg/2024/2847/oj/eng.

Id Claim Provision Applies from Informs
CRA-01 The Regulation applies to products with digital elements made available on the market whose intended purpose or reasonably foreseeable use includes “a direct or indirect logical or physical data connection to a device or network”. “Making available on the market” is the supply of a product for distribution or use on the Union market in the course of a commercial activity, for payment or free of charge Art. 2(1); Art. 3(22) 11 December 2027 SCF-GOV-008
CRA-02 The Regulation entered into force on the twentieth day after its publication on 20 November 2024, that is on 10 December 2024. It applies from 11 December 2027, except that Article 14 applies from 11 September 2026 and Chapter IV (Articles 35 to 51, notification of conformity assessment bodies) from 11 June 2026 Art. 71(1), (2) see claim SCF-GOV-008, SCF-VUL-006, SCF-LGL-006
CRA-03 A product placed on the market before 11 December 2027 is subject to the requirements only if it is substantially modified from that date. The obligations of Article 14 apply to every product in scope placed on the market before 11 December 2027 Art. 69(2), (3) 11 September 2026 for Art. 14 SCF-VUL-006
CRA-04 A manufacturer notifies an actively exploited vulnerability in its product, at the same time to the CSIRT designated as coordinator and to ENISA, through the single reporting platform: an early warning “within 24 hours of the manufacturer becoming aware”, a notification within 72 hours, and a final report “no later than 14 days after a corrective or mitigating measure is available”. An actively exploited vulnerability is one for which “there is reliable evidence that a malicious actor has exploited it in a system without permission of the system owner” Art. 14(1), (2); Art. 3(42); Art. 16 11 September 2026 SCF-VUL-006, SCF-VMG-014 to SCF-VMG-017
CRA-05 A manufacturer notifies a severe incident having an impact on the security of its product through the same channels: an early warning within 24 hours of becoming aware, an incident notification within 72 hours, and a final report within one month after the incident notification. An incident is severe where it negatively affects or is capable of negatively affecting the ability of the product to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or has led or is capable of leading to the introduction or execution of malicious code in the product or in the network and information systems of a user Art. 14(3), (4), (5) 11 September 2026 SCF-VUL-006, SCF-VMG-014, SCF-VMG-015
CRA-06 The notification goes to the electronic end-point of the CSIRT designated as coordinator in the Member State of the manufacturer’s main establishment in the Union, the Member State where decisions related to the cybersecurity of its products are predominantly taken. A manufacturer with no main establishment in the Union uses, in this order, the Member State in which its authorised representative for the most of its products is established, then that of the importer placing the most of them, then that of the distributor making the most of them available, then the one in which the most users are located Art. 14(7); Art. 18 11 September 2026 SCF-VUL-006, SCF-GOV-008
CRA-07 After becoming aware of an actively exploited vulnerability or a severe incident, the manufacturer informs the impacted users, and where appropriate all users, of it and, where necessary, of “any risk mitigation and corrective measures that the users can deploy”, where appropriate in a structured, machine-readable format Art. 14(8) 11 September 2026 SCF-VMG-016
CRA-08 The manufacturer determines a support period that reflects the length of time the product is expected to be in use. The support period is at least five years; where the product is expected to be in use for less than five years it corresponds to the expected use time. The information taken into account goes into the technical documentation. The end date of the support period, “including at least the month and the year”, is specified at the time of purchase, and where technically feasible a notification tells users that the end of the support period has been reached Art. 13(8), (19); Annex II point 7 11 December 2027 SCF-LGL-006
CRA-09 Each security update made available during the support period remains available after it has been issued “for a minimum of 10 years or for the remainder of the support period, whichever is longer” Art. 13(9) 11 December 2027 SCF-LGL-006
CRA-10a Vulnerability handling, point (1): identify and document vulnerabilities and components contained in the product, including by drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies Annex I Part II (1); Art. 3(39) 11 December 2027 SCF-LGL-006, SCF-VMG-004
CRA-10b Point (2): address and remediate vulnerabilities without delay, including by providing security updates; where technically feasible, new security updates are provided separately from functionality updates Annex I Part II (2) 11 December 2027 SCF-LGL-006
CRA-10c Point (3): apply effective and regular tests and reviews of the security of the product Annex I Part II (3) 11 December 2027 SCF-VMG-007
CRA-10d Point (4): once a security update is available, share and publicly disclose information about fixed vulnerabilities (a description, information to identify the affected product, the impacts, the severity and information helping users remediate); in duly justified cases the publication may be delayed until users have had the possibility to apply the patch Annex I Part II (4) 11 December 2027 SCF-VUL-005, SCF-VMG-013
CRA-10e Point (5): put in place and enforce a policy on coordinated vulnerability disclosure Annex I Part II (5); Art. 13(8) 11 December 2027 SCF-VUL-007, SCF-LGL-006, SCF-VMG-011
CRA-10f Point (6): take measures to facilitate the sharing of information about potential vulnerabilities in the product and in third-party components, including by providing a contact address for reporting Annex I Part II (6); Art. 13(17) 11 December 2027 SCF-VUL-001, SCF-LGL-006
CRA-10g Point (7): provide mechanisms to securely distribute updates so that vulnerabilities are fixed or mitigated in a timely manner and, where applicable for security updates, automatically Annex I Part II (7) 11 December 2027 SCF-LGL-006
CRA-10h Point (8): where security updates are available, disseminate them without delay and, unless otherwise agreed for a tailor-made product, free of charge, “accompanied by advisory messages providing users with the relevant information, including on potential action to be taken” Annex I Part II (8) 11 December 2027 SCF-VUL-005, SCF-LGL-006
CRA-11 The technical documentation is drawn up before the product is placed on the market and is continuously updated, where appropriate, at least during the support period; its content is listed in Annex VII. The manufacturer keeps the technical documentation and the EU declaration of conformity at the disposal of the market surveillance authorities “for at least 10 years after the product with digital elements has been placed on the market or for the support period, whichever is longer” Art. 13(12), (13); Art. 31(2); Annex VII 11 December 2027 SCF-LGL-006
CRA-12 The product is accompanied by the information and instructions of Annex II, among them the single point of contact where vulnerabilities can be reported and where the coordinated disclosure policy can be found (point 2) and the type of technical security support and the end date of the support period (point 7). The manufacturer keeps them at the disposal of users and authorities for the same period as the technical documentation Art. 13(17), (18); Annex II points 2, 7 11 December 2027 SCF-VUL-001, SCF-LGL-006

4. United Kingdom: Product Security and Telecommunications Infrastructure Act 2022, Part 1

The Product Security and Telecommunications Infrastructure Act 2022 (c. 46), Part 1, as enacted: https://www.legislation.gov.uk/ukpga/2022/46/part/1/enacted. The Product Security and Telecommunications Infrastructure (Security Requirements for Relevant Connectable Products) Regulations 2023 (SI 2023/1007), as made: https://www.legislation.gov.uk/uksi/2023/1007/made.

Id Claim Provision Applies from Informs
UKR-01 A “relevant connectable product” is an internet-connectable or a network-connectable product that is not an excepted product. A “UK consumer connectable product” is a relevant connectable product made available to consumers in the United Kingdom (or, where identical products meet that condition, to other customers there) that no relevant person had supplied to a customer before Act ss. 4, 5, 6, 54 see UKR-03 SCF-GOV-008
UKR-02 The Secretary of State may specify security requirements for relevant connectable products made available to consumers in the United Kingdom. A manufacturer must comply with the relevant requirements where it intends the product to be a UK consumer connectable product or ought to be aware that it will be one; the product may not be made available in the United Kingdom without a statement of compliance, or a summary of it; a record of investigations and compliance failures is kept for 10 years Act ss. 1, 8, 9, 12 see UKR-03 SCF-GOV-008, SCF-LGL-006
UKR-03 The Regulations were made on 14 September 2023, come into force on 29 April 2024 and extend to England and Wales, Scotland and Northern Ireland. They specify the security requirements (Schedule 1), the conditions for deemed compliance (Schedule 2), the excepted products (Schedule 3) and the content of the statement of compliance (Schedule 4) SI 2023/1007 reg. 1(2), reg. 3 to 7 29 April 2024 SCF-GOV-008
UKR-04 Schedule 1 states three requirements. Passwords are unique per product or defined by the user, and a unique password is not based on an incremental counter, on public information or on a product identifier (unless by an accepted cryptographic method), and is not otherwise guessable (paragraph 1). At least one point of contact for reporting security issues is published, with when the reporter receives an acknowledgement and status updates until resolution (paragraph 2). The defined support period is published; a support period shortened after publication does not meet the requirement (paragraph 3). The information of paragraphs 2 and 3 is made available without a prior request, in English, free of charge and without requesting the reader’s personal information SI 2023/1007 Sch. 1 paras 1, 2, 3 29 April 2024 SCF-GOV-004, SCF-GOV-008, SCF-VUL-001, SCF-VUL-007, SCF-VMG-003, SCF-LGL-006
UKR-05 A manufacturer is treated as complying with paragraph 1 by complying with provision 5.1-1 and, where relevant, 5.1-2 of ETSI EN 303 645 V2.1.1; with paragraph 2 by complying with provision 5.2-1 of that standard, or with paragraphs 6.2.2, 6.2.5 and 6.5 of ISO/IEC 29147:2018 and publishing the information they ask for; and with paragraph 3 by complying with provision 5.3-13 of that standard SI 2023/1007 Sch. 2 paras 1, 2, 3 29 April 2024 SCF-VUL-001, SCF-VUL-007
UKR-06 Excepted products include products to which relevant legislation applies that are made available for supply in Northern Ireland, electric vehicle charge points, medical devices, smart meter products and “desktop computers”, “laptop computers” and “tablet computers which do not have the capability to connect to cellular networks”, except those designed exclusively for children under 14 SI 2023/1007 Sch. 3 paras 1 to 5 29 April 2024 SCF-GOV-008
UKR-07 The statement of compliance carries at least the product type or batch, the manufacturer’s name and address, the declaration of compliance with Schedule 1 or with the deemed compliance conditions, the defined support period that was correct when the product was first supplied, the signatory and the place and date of issue. The manufacturer keeps a copy for “whichever is the longer of” 10 years from the date of issue and the defined support period SI 2023/1007 reg. 7, 8; Sch. 4 29 April 2024 SCF-LGL-006

The Act’s own commencement orders were not read. The date given for UKR-01 and UKR-02 is the date from which the Regulations that give the duty its content apply.

SCF-LGL-006 names seven items that a product placed on a market with product-security regulation reflects in its pipeline. The table says which rows state each item in each regime. “None” means that no provision of the instrument read states the item: for the United Kingdom, that Schedule 1 of the Regulations states no requirement on it.

Item European Union United Kingdom
Bill of materials CRA-10a none
Support period CRA-08 UKR-04, UKR-07
Update policy CRA-09, CRA-10b, CRA-10g, CRA-10h the published support period only (UKR-04)
Disclosure policy CRA-10e, CRA-10f, CRA-12 UKR-04, UKR-05
Reporting capability CRA-04 to CRA-07 none
Technical documentation CRA-11 the statement of compliance, which is not technical documentation (UKR-07)
Retention CRA-11, CRA-12 UKR-02, UKR-07

6. Standards and specifications

The standards and specifications that the vulnerability rules cite. They are references in the sense of the source policy of the knowledge base, section 3, not claims of the class Regulatory, except where a row says that a regulation names the standard. Each was opened on 2026-11-21.

Id Source Version or date What it states, for the rules that use it Used by
STD-01 RFC 9116, A File Format to Aid in Security Vulnerability Disclosure April 2022 a security.txt file under /.well-known/ of a domain; the Contact and Expires fields are always present SCF-VMG-001
STD-02 ETSI EN 303 645, Cyber Security for Consumer Internet of Things: Baseline Requirements V2.1.1 (2020-06) provision 5.2-1: a published vulnerability disclosure policy with contact information and timelines for the initial acknowledgement and for status updates; provision 5.3-13: the defined support period is published. The standard is named by UKR-05 SCF-VMG-003, SCF-VMG-011
STD-03 ISO/IEC 29147, Information technology, Security techniques, Vulnerability disclosure 2018, 2nd edition named by UKR-05 (paragraphs 6.2.2, 6.2.5, 6.5) as a route to deemed compliance. The text of the standard was not read none
STD-04 NIST SP 800-218, Secure Software Development Framework (SSDF) Version 1.1, February 2022 practices RV.1.1 (gather information on potential vulnerabilities, including by monitoring vulnerability databases), RV.2.2 (plan and implement risk responses) and RV.3.1, RV.3.3, RV.3.4 (root cause, similar vulnerabilities, the process) SCF-VMG-007, SCF-VMG-008, SCF-VMG-010
STD-05 CISA, Known Exploited Vulnerabilities Catalog no version; the catalogue changes continuously, page read 2026-11-21 CISA “maintains the authoritative source of vulnerabilities that have been exploited in the wild” SCF-VUL-003, SCF-VMG-015
STD-06 OpenVEX specification v0.2.0 the status labels not_affected, affected, fixed and under_investigation; a not_affected statement carries a status justification or an impact statement SCF-VUL-004, SCF-VMG-005
STD-07 FIRST, Common Vulnerability Scoring System v4.0, specification document document version 1.2 the Base score assumes the reasonable worst case across deployed environments; the Threat and Environmental metrics refine it for a specific environment SCF-VMG-006
STD-08 The Linux kernel documentation, Security bugs page read 2026-11-21 publication of a fix may be postponed at the request of the reporter or an affected party for up to 7 calendar days from the start of the release process, exceptionally 14; coordination with operating system vendors runs through separate channels SCF-VMG-011, SCF-VMG-012