Commit 83d5e57b authored by Valerie Aurora (Bow Shock)'s avatar Valerie Aurora (Bow Shock)
Browse files

Fix typos in table and renumber last section

parent c52a38b5

EN-304-625.md

+5 −4
Original line number Diff line number Diff line
@@ -54,6 +54,7 @@ Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation 




## Trademarks



The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.



**DECT™** , **PLUGTESTS™** , **UMTS™** and the ETSI logo are trademarks of ETSI registered for the benefit of its Members. **3GPP™** , **LTE™** and **5G ™** logo are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. **oneM2M™** logo is a trademark of ETSI registered for the benefit of its Members and of the oneM2M Partners. **GSM** ® and the GSM logo are trademarks registered and owned by the GSM Association.
@@ -526,11 +527,11 @@ _Describe the expected support period and its impact on security risks. Generall 


The support period of an operating system should generally be at least 10 years.



# 6 Requirements specifications

# 5 Requirements specifications



## 6.1 General

## 5.1 General



## 6.2 Technical security requirements specifications

## 5.2 Technical security requirements specifications



_List technical security requirements for the product. Each requirement should be objectively verifiable on an instance of a product. Each should include an implementable method of verifying the requirement is met. Each should include a way to determine if the requirement is applicable to the product. Ideally each will include at least one concrete example of an implementation that satisfies the requirement and a test that verifies it. If the requirement allows the manufacturer to specify their own solution to the technical requirement, the requirement should include a specific way to measure the effectiveness of the risk mitigation and set a minimum level._
@@ -551,7 +552,7 @@ _List any related ETSI standards and how they interact with the present document 
_Table mapping technical security requirements from Section 5 of the present document to essential cybersecurity requirements in Annex I of the CRA. The purpose of this is to help identify missing technical security requirements._



| CRA requirement                                 | Technical security requirements(s) |

|-------------------------------------------------|-------------------------------- ---|

|-------------------------------------------------|------------------------------------|

| No known exploitable vulnerabilities            | |

| Secure design, development, production          | |

| Secure by default configuration                 | |