@@ -3295,14 +3295,22 @@ A cryptographic algorithm, scheme or protocol that is not CRY-SOTA under items i
- NOTE 3: A cryptographic mechanism composed of more than one cryptographic primitive (for example a hybrid key-encapsulation mechanism or a hybrid signature scheme) inherits the most restrictive classification of its constituent primitives. A hybrid construction including a Legacy or Deprecated component is therefore classified as Legacy or Deprecated, regardless of the classification of the other components.
- NOTE 4: In item iv), an external specification or external requirement means a specification or requirement that is imposed on the product and that requires the use of a specific cryptographic algorithm, scheme or protocol for the product to interoperate with an identified system, platform or operational context. An external requirement can be, for instance, a regulatory requirement, an operational constraint, a technical interoperability constraint, or a platform compatibility requirement.
- NOTE 5: The routes in items i) to iv) correspond to the ACM-listed, ACM-extended and interoperability-based cryptographic mechanism routes of the cross-vertical Annex K framework. Items i) to iii) correspond to the ACM-listed and ACM-extended routes; item iv) corresponds to the interoperability-based route, the conditions of which are specified for the present document in clause K.2.4 (2).
## K.2 Assessment criteria for compliance with cryptographic requirements
### K.2.1 Assessment objective
The purpose of this assessment case is to verify that, for every cryptographic algorithm, scheme or protocol used by a security mechanism of the product, appropriate evidence is provided demonstrating classification as CRY-SOTA in accordance with clause K.1, by reference to one of paths i), ii) or iii) of that clause.
### K.2.2 Assessment preparation
Preconditions for the assessment:
- • where the product has a default configuration, that default configuration shall be used for the assessment;
- • otherwise, the delivery-state configuration shall be used (i.e. the configuration of the product as made available on the market in accordance with Annex I, Part I, point (2)(b) of Regulation (EU) 2024/2847 [i.1]);
- • the manufacturer shall make available a list identifying every security mechanism of the product, the cryptographic algorithm, scheme or protocol used by that mechanism, the parameters in use, and whether the algorithm forms part of the default or delivery-state configuration.
### K.2.3 Assessment activities
For every security mechanism identified under the preceding clause, the assessor shall:
- 1) review the documentation provided and confirm that, for each algorithm in use, the manufacturer has identified the path of clause K.1 (i, ii, or iii) by which the algorithm is classified as CRY-SOTA, and the corresponding catalogue entry or clause reference;
@@ -3331,95 +3339,18 @@ For every security mechanism identified under the preceding clause, the assessor
The product shall, by default, use State-of-the-Art cryptography algorithms listed in (CRY-SOTA), to be used for the supported security mechanism of the product where applicable.
- RATIONALE: Cryptographic mechanisms are the foundation of trust, integrity, and authenticity in digital systems. Using state-of-the-art cryptographic algorithms and protocols ensures protection against known vulnerabilities and cryptographic attacks. Failure to conform to CRY-SOTA risks compromising the integrity of signed content, enabling spoofing, tampering, or repudiation attacks, and undermining the overall security posture of the system.
> NOTE 1: The use of security mechanism e.g. authentication, access control, secure communication, secure storage and secure update are described in the main text of this standard.
> NOTE 2: Cryptographic algorithm primitives (in short, algorithms e.g. public- and private-key encryption algorithms, hash functions, authentication codes, digital signatures) are classified as CRY-SOTA if they are listed in the [\[i.9\]](#_ref_i.9) document and are suitable for the implementation of supported security mechanisms of the product.
> NOTE 3 Supporting evidence options that an algorithm, which is not included in CRY-SOTA, is applicable and suitable for the respective use case, are listed in the related assessment criteria ( K.1.2.1) clause.
### K.1.2 Assessment criteria
#### K.1.2.1 Assessment objective:
The purpose of this assessment case is (the conceptual assessment) whether the implemented algorithms are identified as CRY-SOTA.
#### K.1.2.2 Assessment preparation:
- Preconditions for the test: If applicable, the product is in the default- configuration. Otherwise, the product is in the delivery state, where it is available on the market in accordance with CRA Annex I part 1(2) (b).
#### K.1.2.3 Assessment activities:
- For every security mechanism the list of used algorithms, which are reachable over an external interface and identified as CRY- SOTA shall be documented.
#### K.1.2.4 Supporting Evidence:
- description of the performed test
- all test records of the performed test
#### K.1.2.5 Assignment of verdict:
- The verdict PASS shall be assigned if evidence has been provided.
- The verdict FAIL shall be assigned otherwise
If the verdict in K.1.2.1 has been assigned FAIL, the following assessment has to be performed additionally:
##### K.1.2.5.1 Assessment objective:
If for a certain security mechanism and use case no CRY-SOTA algorithm is applicable, evidence shall be
provided in the documentation that a suitable algorithm has been implemented for this evidence instead.
##### K.1.2.5.2 Assessment preparation:
- Preconditions for the test: If applicable, the product is in the default configuration state. Otherwise, the product is in the delivery state, where it is available on the market in accordance with CRA Annex I part 1(2) (b).
##### K.1.2.5.3 Assessment activities:
For every security mechanism and for every used algorithm, which is reachable over an interface of the product and identified as not included in CRY- SOTA, the documentation shall provide evidence:
- that this algorithm is applicable and suitable for the respective use case
- that no CRY-SOTA algorithm is applicable
##### K.1.2.5.4 Supporting Evidence:
- 1. Identification of the certain algorithm by reference in further algorithm catalogues as national cryptographic catalogues 2 or vertical use case specific cryptographic algorithm catalogues
- 2. No entry of known exploitable vulnerabilities provided in ENISA “European Vulnerability Database.
- Description of the performed test
- all test records of the performed test
##### K.1.2.5.5 Assignment of verdict:
- The verdict PASS shall be assigned if respective evidence has been provided,
- The verdict FAIL shall be assigned otherwise.
> NOTE 3: Functional correctness and completeness assessment criteria of the documentation are to be specified in accordance with the capabilities set in the specific vertical Standards.
## K.2. Requirement (“crypto agility”)
Where applicable the product shall by default be prepared to update cryptographic algorithm used for the supported security mechanism of the product to maintain when there are indications that the used cryptographic
algorithm will not stay SOTA anymore within the intended lifetime of the product.
> NOTE 4: To maintain SOTA for cryptographic algorithm within the intended lifetime of the product concepts to consider are crypto agility additional to the capability of updating cryptographic algorithms on the product in accordance to Secure Update and Secure Communication mechanism.
> NOTE 5: Formal verification can use mathematical proofs and /or rigorous methods to prove an algorithm's correctness, ensuring it meets its formal specification for all valid inputs, unlike testing which only samples cases. This process involves creating formal models, using techniques like theorem proving or model checking, and is crucial for critical systems like cryptography finding hard-to-spot bugs and guaranteeing security/reliability.
> NOTE 6: The _ref_i.9 listing has two classes of SOTA algorithms; Legacy mechanisms with an expiry date as defined in ACM, and Recommended mechanisms with no set expiry date.
> NOTE 7: For products or components of products that cannot have their cryptographic algorithms updated for example if the implementation or part uses a hardware-based root of trust, it is important that the intended lifetime of the equipment does not exceed the recommended usage lifetime of the cryptographic algorithms used by the product. Thereby the implementation of an algorithm can include the specific implementation of their parameters
> NOTE 8: If a component storing the algorithm or corresponding parameters of a main product is replaced
by a new component, the product is considered as a new product according to the New Legislative Framework
Blue Guide4, if the replacement provides a substantial modification to the main product
### K.2.1 Assessment criteria
#### K.2.1.1 Assessment objective:
The purpose of this assessment case is (the conceptual assessment) whether the product is prepared to update
cryptographic algorithms for the supported security mechanism.
#### K.2.1.2 Assessment preparation:
- Preconditions for the test: If applicable, the product is in the default- configuration. Otherwise, the
product is in the delivery state, where it is available on the market in accordance with CRA Annex I
part 1(2) (b).
#### K.2.1.3 Assessment activities:
- For every used SOTA algorithm, which is reachable over an interface, the life span of the algorithm is
documented, as well its property, if the algorithm is considered as legacy or recommended algorithm.
- If the life span of the product exceeds the life span of a legacy algorithm, the algorithm is marked as
updatable by a recommended algorithm in the documentation.
- If an algorithm is identified as SOTA recommended, no further action is required.
#### K.2.1.4 Supporting Evidence:
- Description /documentation of the performed test.
- All test records of the performed test.
#### K.2.1.5 Assignment of verdict:
- The verdict PASS shall be assigned if respective evidence has been provided,
