@@ -93,8 +93,6 @@ The Technical Body should advise the ETSI Secretariat if the above default natio
The following non-technical requirements shall be implemented by all products with digital elements evaluated with the present document.
-**[REQ-GEN-0]:** The product shall have technical documentation with what [Risk factors](#45-risk-factors) the product shall be evaluated.
-**[REQ-GEN-1]:** The product shall have technical documentation a detailed enough systems architecture design description, that enables national bodies like MSA to evaluate and test the product design.
-**[REQ-GEN-2]:** The product dependencies to Operating System essential security capabilities are documented.
-**[REQ-GEN-3]:** The products technical documentation shall describe the external services and systems that are required for the product operation like mentioned in [4.10.1 External security functions, not in scope of the present document].
-**[REQ-GEN-4]:** Traffic related to the product operation, including but not limited to configuration, metrics and API access, is addressed as Application level traffic as per RFC 1122 in the technical documentation.
@@ -535,41 +533,6 @@ There are three different types of assessments used in this document.
## 6.1 General requirements assessments
### 6.1.0.0 REQ-GEN-0
**Requirement:** The product shall have technical documentation with what [Risk factors](#45-risk-factors) the product shall be evaluated.
**Objective:** The product is fit for the targeted market what is considered to be foreseeable use of the product.<br/>
**Preparation:** None<br/>
**Activities:**
1. Study the technical documentation.
**Verdict:**
1. Pass if all risk factors are included
2. and the reasoning why a given level was selected is presented.
3. Fail otherwise.
**Supporting Evidence:**
1. References to to documentation sections.
### 6.1.0.1 REQ-GEN-1
**Requirement:** The product shall have technical documentation a detailed enough systems architecture design description, that enables national bodies like MSA to evaluate and test the product design.
**Objective:** MSA and other related parties can examine the product without installing it into a test or production environment.<br/>
**Preparation:** None<br/>
**Activities:**
1. Study the technical documentation.
**Verdict:**
1. Pass documentation has a detailed enough systems architecture design description.
2. Fail otherwise.
**Supporting Evidence:**
1. References to to documentation sections.
### 6.1.0.2 REQ-GEN-2
**Requirement:** The product dependencies to Operating System essential security capabilities are documented.
