The most important quality of a cybersecurity requirement is that it should ideally be objectively testable on an instance of the product. If it can't be tested on the product itself, it is a documentation requirement, in which the manufacturer documents the steps they took to implement the requirement (such as configuration files or written policies used by employees).
The alternative is "check-box" requirements, which only require that the vendor says that they did a thing ("Did you have every commit code-reviewed by a second person? [x] Yes [ ] No"). These are not acceptable and should be converted into testable requirements if possible and documentation requirements otherwise.
The CRA requires the manufacturer to keep all the documentation necessary to show that the tests were conducted. In addition, the CRA explicitly grants the MSA the following rights in Article 13 Rec. 22:
> \"Manufacturers shall, upon a reasoned request from a market surveillance authority, provide that authority, in a language which can be easily understood by that authority, with all the information and documentation, in paper or electronic form, necessary to demonstrate the conformity of the product with digital elements and of the processes put in place by the manufacturer with the essential cybersecurity requirements set out in Annex I. Manufacturers shall cooperate with that authority, at its request, on any measures taken to eliminate the cybersecurity risks posed by the product with digital elements which they have placed on the market.\"
