Fix table 4.5.2 margins

The Technical Body may propose different dates to the default ones (3, 6, 18). Technical Bodies who wish to propose different dates are advised to indicate this clearly in the approved committee draft.

| Proposed national transposition dates                          |                                 |

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

|:-|:-|

| Date of latest announcement of this EN (doa):                  | 3 months after ETSI publication |

| Date of latest publication of new National Standard            |                                 |

| or endorsement of this EN (dop/e):                             | 6 months after doa              |

For the purposes of the present document, the following abbreviations apply:

| Abbreviation | Description                                       |

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

| CRA          | Cyber Reciliensy Act                              |

| OS           | Operating System                                  |

| IDP          | Identity Provider                                 |

| VPN          | Virtual Private Network                           |

| SIEM         | Security Information and Event Management systems |

| NMS          | Network Management System                         |

| 2FA          | Two Factor Authentication                         |

| CSP          | Communication System Provider                     |

| SDN          | Software Defined Networks                         |

| GUI          | Graphical User Interface                          |

| NE           | One or more connected Network Elements            |

| MDM          | Mobile Device Management system                   |

`CRA    Cyber Reciliensy Act`

`OS     Operating System`

`IDP    Identity Provider`

`VPN    Virtual Private Network`

`SIEM   Security Information and Event Management systems`

`NMS    Network Management System`

`2FA    Two Factor Authentication`

`CSP    Communication System Provider`

`SDN    Software Defined Networks`

`GUI    Graphical User Interface`

`NE     One or more connected Network Elements`

`MDM    Mobile Device Management system`

# 4 Product context

    -   **[ACC-L-2]** Private network with multiple connections to public networks filtered by firewalls, no internal segmentation

    -   **[ACC-L-3]** Everything else

### 4.5.1 Mapping of use cases to risk factors and security profiles

### 4.5.2 Mapping of use cases to risk factors and security profiles

The table below is an example, how the example use cases could be mapped to different risk factors.

If there is no clear use case to be referred, the manufacturer shall take the presented dimensions, Service Requesting Users, Complexity and Expectations, into consideraton and document what factors apply.

In case of overlap in the requirements, a stronger and more secure option shall be selected.

| Use case                                              | SRU     | COM     | EXP     | ACL     |

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

|:-|:-|:-|:-|:-|

| [4.4.1.1 IoT network with monitoring data collection] | SRU-L-0 | COM-L-0 | EXP-L-0 | ACC-L-1 |

| [4.4.1.2 Home network deployment]                     | SRU-L-0 | COM-L-1 | EXP-L-0 | ACL-L-2 |

| [4.4.2.1 Office network]                              | SRU-L-1 | COM-L-2 | EXP-L-0 | ACL-L-2 |