Part 1
요약·해설
이 평가는 ETSI EN 303 645 전체 product certification을 선언하는 문서가 아닙니다. IoT product component인 Zephyr RTOS가 각 provision을 지원하는지 보여 주며, product maker가 책임져야 하는 항목은 N/A로 구분합니다.
32 defined terms
67 provisions
Zephyr feature links
Part 2
접을 수 있는 영어 원문 전체
영어 원문 전체 펼치기
8AAC77250AB38126B4B464D7C68B654B1F6981D4EB08FD7E65BEF5FC105865CB
.. _etsi_303645:
ETSI 303-645
############
`ETSI EN 303 645`, also known as "Cyber Security for Consumer Internet
of Things: Baseline Requirements," is a standard developed by the
European Telecommunications Standards Institute (ETSI).
The standard includes provisions for secure software updates, data
protection, secure communication, and the minimization of exposed
attack surfaces, among other things. It is part of a broader effort to
address the challenges and risks associated with IoT devices.
Full version of the standard can be found `here <https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf>`_.
Terminology
***********
.. list-table:: ETSI 303645 terminology
:widths: 17 43
* - administrator
- user who has the highest-privilege level possible for a user of the device,
which can mean they are able to change any configuration related to the intended
functionality.
* - associated services
- digital services that, together with the device, are part of the overall consumer
IoT product and that are typically required to provide the product's intended
functionality.
* - authentication mechanism
- method used to prove the authenticity of an entity.
* - authentication value
- individual value of an attribute used by an authentication mechanism.
* - best practice cryptography
- cryptography that is suitable for the corresponding use case and has no
indications of a feasible attack with current readily available techniques.
* - constrained device
- device which has physical limitations in either the ability to process data, the
ability to communicate data, the ability to store data or the ability to interact
with the user, due to restrictions that arise from its intended use.
* - consumer
- natural person who is acting for purposes that are outside her/his trade,
business, craft or profession.
* - consumer IoT device
- network-connected (and network-connectable) device that has relationships to
associated services and are used by the consumer typically in the home or as
electronic wearables.
* - critical security parameter
- security-related secret information whose disclosure or modification can compromise
the security of a security module.
* - debug interface
- physical interface used by the manufacturer to communicate with the device during
development or to perform triage of issues with the device and that is not used as part
of the consumer-facing functionality
* - defined support period
- minimum length of time, expressed as a period or by an end-date, for which a
manufacturer will provide security updates.
* - device manufacturer
- entity that creates an assembled final consumer IoT product, which is likely to contain
the products and components of many other suppliers.
* - factory default
- state of the device after factory reset or after final production/assembly.
* - initialization
- process that activates the network connectivity of the device for operation and
optionally sets authentication features for a user or for network access.
* - initialized state
- state of the device after initialization.
* - IoT product
- consumer IoT device and its associated services.
* - isolable
- able to be removed from the network it is connected to, where any functionality loss
caused is related only to that connectivity and not to its main function; alternatively,
able to be placed in a self-contained environment with other devices if and only if the
integrity of devices within that environment can be ensured
* - logical interface
- software implementation that utilizes a network interface to communicate over the network
via channels or ports.
* - manufacturer
- relevant economic operator in the supply chain (including the device manufacturer).
* - network interface
- physical interface that can be used to access the functionality of consumer IoT via a network.
* - owner
- user who owns or who purchased the device.
* - personal data
- Any information relating to an identified or identifiable natural person.
* - physical interface
- physical port or air interface (such as radio, audio or optical) used to communicate with the
device at the physical layer.
* - public security parameter
- security related public information whose modification can compromise the security of a
security module.
* - remotely accessible
- intended to be accessible from outside the local network.
* - security module
- set of hardware, software, and/or firmware that implements security functions.
* - security update
- software update that addresses security vulnerabilities either discovered by or reported
to the manufacturer.
* - sensitive security parameters
- critical security parameters and public security parameters.
* - software service
- software component of a device that is used to support functionality.
* - telemetry
- data from a device that can provide information to help the manufacturer identify issues
or information related to device usage.
* - unique per device
- unique for each individual device of a given product class or type.
* - user
- natural person or organization.
Provisions Assessment
*********************
The following table is a self-assessment using Table B.1 from ETSI EN
303 645, specifically focusing on the Zephyr RTOS as a component
within IoT products.
According with ETSI 303 645, table B.1 provides a mechanism to give information
about the implementation of the provisions presented in the standard. Zephyr has
adopted the following notations used in the standard:
.. list-table:: ETSI 303645 Table B.1 notations
:widths: 17 43
* - M
- the provision is a mandatory requirement
* - R
- the provision is a recommendation
* - M C
- the provision is a mandatory requirement and conditional
* - R C
- the provision is a recommendation and conditional
* - Y
- The provision is supported by Zephyr
* - N
- The provision is not supported by Zephyr
* - N/A
- The provision is not applicable to Zephyr or it is product makers responsibility
.. raw:: latex
\begin{landscape}
.. list-table:: ETSI 303645 provisions assessment using table B.1
:header-rows: 1
:widths: 25 80 15 15 60
* - Provision
- Description
- Status
- Support
- Detail
.. _ETSI_Provision_5_1_1:
* - Provision 5.1-1
- Where passwords are used and in any state other than the
factory default, all consumer IoT device passwords shall be
unique per device or defined by the user.
- M C
- N/A
-
.. _ETSI_Provision_5_1_2:
* - Provision 5.1-2
- Where pre-installed unique per device passwords are used,
these shall be generated with a mechanism that reduces the
risk of automated attacks against a class or type of device.
- M C
- N/A
-
.. _ETSI_Provision_5_1_3:
* - Provision 5.1-3
- Authentication mechanisms used to authenticate users against a
device shall use best practice cryptography, appropriate to
the properties of the technology, risk and usage.
- M
- N/A
-
.. _ETSI_Provision_5_1_4:
* - Provision 5.1-4
- Where a user can authenticate against a device, the device
shall provide to the user or an administrator a simple
mechanism to change the authentication value used.
- M C
- N/A
-
.. _ETSI_Provision_5_1_5:
* - Provision 5.1-5
- When the device is not a constrained device, it shall have a
mechanism available which makes brute-force attacks on
authentication mechanisms via network interfaces
impracticable.
- M C
- N
- **TODO**
.. _ETSI_Provision_5_2_1:
* - Provision 5.2-1
- The manufacture shall make a vulnerability disclosure policy publicly
available.
- M
- Y
- :ref:`Vulnerability Management <reporting>`
.. _ETSI_Provision_5_2_2:
* - Provision 5.2-2
- Disclosed vulnerabilities should be acted on in a timely manner.
- R
- Y
- :ref:`Vulnerability Timeline <vulnerability_timeline>`
.. _ETSI_Provision_5_2_3:
* - Provision 5.2-3
- Manufacturers should continually monitor for, identify and rectify security
vulnerabilities within products and services they sell, produce, have produced
and services they operate during the defined support period.
- R
- Y
- `Modules <https://github.com/zephyrproject-rtos/>`_ are covered
.. _ETSI_Provision_5_3_1:
* - Provision 5.3-1
- All software components in consumer IoT devices should be securely updatable.
- R
- Y
- :ref:`Device firwmware upgrade <dfu>`
.. _ETSI_Provision_5_3_2:
* - Provision 5.3-2
- When the device is not a constrained device, it shall have an update mechanism
for the secure installation of updates.
- M C
- Y
- :ref:`Device firwmware upgrade <dfu>`
.. _ETSI_Provision_5_3_3:
* - Provision 5.3-3
- An update shall be simple for the user to apply.
- M C
- N/A
-
.. _ETSI_Provision_5_3_4:
* - Provision 5.3-4
- Automatic mechanisms should be used for software updates.
- R C
- N/A
-
.. _ETSI_Provision_5_3_5:
* - Provision 5.3-5
- The device should check after initialization, and then periodically, whether
security updates are available.
- R C
- N/A
-
.. _ETSI_Provision_5_3_6:
* - Provision 5.3-6
- If the device supports automatic updates and/or update notifications, these
should be enabled in the initialized state and configurable so that the user
can enable, disable, or postpone installation of security updates and/or
update notifications.
- R C
- N/A
-
.. _ETSI_Provision_5_3_7:
* - Provision 5.3-7
- The device shall use best practice cryptography to facilitate secure update mechanisms.
- M C
- Y
- :ref:`West Sign <west-sign>`
.. _ETSI_Provision_5_3_8:
* - Provision 5.3-8
- Security updates shall be timely.
- M C
- N/A
-
.. _ETSI_Provision_5_3_9:
* - Provision 5.3-9
- The device should verify the authenticity and integrity of software updates.
- R C
- Y
- Functionality provided by `MCUboot <https://github.com/zephyrproject-rtos/mcuboot>`. Also see :ref:`Device Firwmware Upgrade <dfu>`
.. _ETSI_Provision_5_3_10:
* - Provision 5.3-10
- Where updates are delivered over a network interface, the device shall verify
the authenticity and integrity of each update via a trust relationship.
- M
- N/A
-
.. _ETSI_Provision_5_3_11:
* - Provision 5.3-11
- The manufacturer should inform the user in a recognizable and apparent manner
that a security update is required together with information on the risks
mitigated by that update.
- R C
- N/A
-
.. _ETSI_Provision_5_3_12:
* - Provision 5.3-12
- The device should notify the user when the application of a software update
will disrupt the basic functioning of the device.
- R C
- N/A
- Zephyr provides this information for its updates. Anyone using Zephyr in their products must check if they are affected
.. _ETSI_Provision_5_3_13:
* - Provision 5.3-13
- The manufacturer shall publish, in an accessible way that is clear and
transparent to the user, the defined support period.
- M
- Y
- :ref:`Release Life Cycle and Maintenance <zephyr_release_cycle>`
.. _ETSI_Provision_5_3_14:
* - Provision 5.3-14
- For constrained devices that cannot have their software updated, the rationale
for the absence of software updates, the period and method of hardware replacement
support and a defined support period should be published by the manufacturer in an
accessible way that is clear and transparent to the user.
- R C
- N/A
-
.. _ETSI_Provision_5_3_15:
* - Provision 5.3-15
- For constrained devices that cannot have their software updated, the product
should be isolable and the hardware replaceable.
- R C
- N/A
-
.. _ETSI_Provision_5_3_16:
* - Provision 5.3-16
- The model designation of the consumer IoT device shall be clearly recognizable,
either by labelling on the device or via a physical interface.
- M
- N/A
-
.. _ETSI_Provision_5_4_1:
* - Provision 5.4-1
- Sensitive security parameters in persistent storage shall be stored securely by the device.
- M
- N
- There is not secure storage within Zephyr
.. _ETSI_Provision_5_4_2:
* - Provision 5.4-2
- Where a hard-coded unique per device identity is used in a device for security purposes,
it shall be implemented in such a way that it resists tampering by means such as physical,
electrical or software.
- M C
- N/A
-
.. _ETSI_Provision_5_4_3:
* - Provision 5.4-3
- Hard-coded critical security parameters in device software source code shall not be used.
- M
- Y
- :ref:`Hardening Tool <hardening>`
.. _ETSI_Provision_5_4_4:
* - Provision 5.4-4
- Any critical security parameters used for integrity and authenticity checks of software
updates and for protection of communication with associated services in device software
shall be unique per device and shall be produced with a mechanism that reduces the risk
of automated attacks against classes of devices.
- M
- N/A
-
.. _ETSI_Provision_5_5_1:
* - Provision 5.5-1
- The consumer IoT device shall use best practice cryptography to communicate securely.
- M
- Y
-
.. _ETSI_Provision_5_5_2:
* - Provision 5.5-2
- The consumer IoT device should use reviewed or evaluated implementations to deliver
network and security functionalities, particularly in the field of cryptography.
- R
- Y
-
.. _ETSI_Provision_5_5_3:
* - Provision 5.5-3
- Cryptographic algorithms and primitives should be updatable.
- R
- N
- The whole image must be updated
.. _ETSI_Provision_5_5_4:
* - Provision 5.5-4
- Access to device functionality via a network interface in the initialized state should
only be possible after authentication on that interface.
- R
- N/A
-
.. _ETSI_Provision_5_5_5:
* - Provision 5.5-5
- Device functionality that allows security-relevant changes in configuration via a
network interface shall only be accessible after authentication. The exception is for
network service protocols that are relied upon by the device and where the manufacturer
cannot guarantee what configuration will be required for the device to operate.
- M
- N/A
-
.. _ETSI_Provision_5_5_6:
* - Provision 5.5-6
- Critical security parameters should be encrypted in transit, with such encryption
appropriate to the properties of the technology, risk and usage.
- R
- Y
-
.. _ETSI_Provision_5_5_7:
* - Provision 5.5-7
- The consumer IoT device shall protect the confidentiality of critical security
parameters that are communicated via remotely accessible network interfaces.
- M
- Y
-
.. _ETSI_Provision_5_5_8:
* - Provision 5.5-8
- The manufacturer shall follow secure management processes for critical security
parameters that relate to the device.
- M
- N/A
-
.. _ETSI_Provision_5_6_1:
* - Provision 5.6-1
- All unused network and logical interfaces shall be disabled.
- M
- Y
- :ref:`Kconfig <kconfig>`
.. _ETSI_Provision_5_6_2:
* - Provision 5.6-2
- In the initialized state, the network interfaces of the device shall minimize the
unauthenticated disclosure of security-relevant information.
- M
- Y
-
.. _ETSI_Provision_5_6_3:
* - Provision 5.6-3
- Device hardware should not unnecessarily expose physical interfaces to attack.
- R
- Y
- :ref:`Kconfig <kconfig>` and :ref:`Hardening Tool <hardening>`
.. _ETSI_Provision_5_6_4:
* - Provision 5.6-4
- Where a debug interface is physically accessible, it shall be disabled in software.
- M C
- Y
- :ref:`Hardening Tool <hardening>`
.. _ETSI_Provision_5_6_5:
* - Provision 5.6-5
- The manufacturer should only enable software services that are used or required for
the intended use or operation of the device.
- R
- Y
- :ref:`Kconfig <kconfig>` and :ref:`Hardening Tool <hardening>`
.. _ETSI_Provision_5_6_6:
* - Provision 5.6-6
- Code should be minimized to the functionality necessary for the service/device to operate.
- R
- Y
- :ref:`Kconfig <kconfig>`
.. _ETSI_Provision_5_6_7:
* - Provision 5.6-7
- Software should run with least necessary privileges, taking account of both security
and functionality.
- R
- Y
- :ref:`Security Overview <security-overview>`
.. _ETSI_Provision_5_6_8:
* - Provision 5.6-8
- The device should include a hardware-level access control mechanism for memory.
- R
- Y
- :ref:`Memory protection <memory_domain>`
.. _ETSI_Provision_5_6_9:
* - Provision 5.6-9
- The manufacturer should follow secure development processes for software deployed on
the device.
- R
- Y
- :ref:`Security Overview <security-overview>` and :ref:`Coding guidelines <coding_guidelines>`
.. _ETSI_Provision_5_7_1:
* - Provision 5.7-1
- The consumer IoT device should verify its software using secure boot mechanisms.
- R
- Y
- Functionality provided by `MCUboot <https://github.com/zephyrproject-rtos/mcuboot>`. Also see :ref:`Security Overview <west-sign>`
.. _ETSI_Provision_5_7_2:
* - Provision 5.7-2
- If an unauthorized change is detected to the software, the device should alert the
user and/or administrator to the issue and should not connect to wider networks than
those necessary to perform the alerting function.
- R
- N
- Zephyr does not provide runtime detection / notification.
.. _ETSI_Provision_5_8_1:
* - Provision 5.8-1
- The confidentiality of personal data transiting between a device and a service,
especially associated services, should be protected, with best practice cryptography.
- R
- Y
-
.. _ETSI_Provision_5_8_2:
* - Provision 5.8-2
- The confidentiality of sensitive personal data communicated between the device and
associated services shall be protected, with cryptography appropriate to the
properties of the technology and usage.
- M
- Y
-
.. _ETSI_Provision_5_8_3:
* - Provision 5.8-3
- All external sensing capabilities of the device shall be documented in an accessible
way that is clear and transparent for the user.
- M
- Y
- :ref:`sensing`
.. _ETSI_Provision_5_9_1:
* - Provision 5.9-1
- Resilience should be built in to consumer IoT devices and services, taking into
account the possibility of outages of data networks and power.
- R
- Y
-
.. _ETSI_Provision_5_9_2:
* - Provision 5.9-2
- Consumer IoT devices should remain operating and locally functional in the case of a
loss of network access and should recover cleanly in the case of restoration of a
loss of power.
- R
- Y
-
.. _ETSI_Provision_5_9_3:
* - Provision 5.9-3
- The consumer IoT device should connect to networks in an expected, operational and
stable state and in an orderly fashion, taking the capability of the infrastructure
into consideration.
- R
- Y
-
.. _ETSI_Provision_5_10_1:
* - Provision 5.10-1
- If telemetry data is collected from consumer IoT devices and services, such as usage
and measurement data, it should be examined for security anomalies.
- R C
- N/A
-
.. _ETSI_Provision_5_11_1:
* - Provision 5.11-1
- The user shall be provided with functionality such that user data can be erased from
the device in a simple manner.
- M
- N/A
-
.. _ETSI_Provision_5_11_2:
* - Provision 5.11-2
- The consumer should be provided with functionality on the device such that personal
data can be removed from associated services in a simple manner.
- R
- N/A
-
.. _ETSI_Provision_5_11_3:
* - Provision 5.11-3
- Users should be given clear instructions on how to delete their personal data.
- R
- N/A
-
.. _ETSI_Provision_5_11_4:
* - Provision 5.11-4
- Users should be provided with clear confirmation that personal data has been deleted
from services, devices and applications.
- R
- N/A
-
.. _ETSI_Provision_5_12_1:
* - Provision 5.12-1
- Installation and maintenance of consumer IoT should involve minimal decisions by the
user and should follow security best practice on usability.
- R
- N/A
-
.. _ETSI_Provision_5_12_2:
* - Provision 5.12-2
- The manufacturer should provide users with guidance on how to securely set up their device.
- R
- N/A
-
.. _ETSI_Provision_5_12_3:
* - Provision 5.12-3
- The manufacturer should provide users with guidance on how to check whether their
device is securely set up.
- R
- N/A
-
.. _ETSI_Provision_5_13_1:
* - Provision 5.13-1
- The consumer IoT device software shall validate data input via user interfaces or
transferred via Application Programming Interfaces (APIs) or between networks in
services and devices.
- M
- Y
- :ref:`Syscall verification <syscall_verification>` and :ref:`Coding guidelines <coding_guidelines>`
.. _ETSI_Provision_6_1_1:
* - Provision 6.1-1
- The manufacturer shall provide consumers with clear and transparent information about
what personal data is processed, how it is being used, by whom, and for what purposes,
for each device and service. This also applies to third parties that can be involved,
including advertisers.
- M
- N/A
-
.. _ETSI_Provision_6_1_2:
* - Provision 6.1-2
- Where personal data is processed on the basis of consumers' consent, this consent
shall be obtained in a valid way.
- M C
- N/A
-
.. _ETSI_Provision_6_1_3:
* - Provision 6.1-3
- Consumers who gave consent for the processing of their personal data shall have
the capability to withdraw it at any time.
- M
- N/A
-
.. _ETSI_Provision_6_1_4:
* - Provision 6.1-4
- If telemetry data is collected from consumer IoT devices and services, the
processing of personal data should be kept to the minimum necessary for the
intended functionality.
- R C
- N/A
-
.. _ETSI_Provision_6_1_5:
* - Provision 6.1-5
- If telemetry data is collected from consumer IoT devices and services, consumers
shall be provided with information on what telemetry data is collected, how it is
being used, by whom, and for what purposes.
- M C
- N/A
-
.. raw:: latex
\end{landscape}
Part 3
한국어 전문 번역
ETSI EN 303 645는 ‘Cyber Security for Consumer Internet of Things: Baseline Requirements’라고도 하며 European Telecommunications Standards Institute(ETSI)가 개발한 표준입니다.
이 표준은 secure software update, data protection, secure communication, 외부에 노출되는 attack surface 최소화 등을 규정합니다. IoT device와 관련된 challenge와 risk를 해결하려는 더 큰 활동의 일부입니다.
용어
| administrator | Device user에게 허용되는 가장 높은 privilege level을 가진 user입니다. Intended functionality와 관련된 모든 configuration을 바꿀 수 있음을 뜻할 수 있습니다. |
| associated services | Device와 함께 전체 consumer IoT product를 구성하며, product의 intended functionality 제공에 일반적으로 필요한 digital service입니다. |
| authentication mechanism | Entity가 진짜임을 증명하는 데 사용하는 방법입니다. |
| authentication value | Authentication mechanism이 사용하는 attribute의 개별 값입니다. |
| best practice cryptography | 해당 use case에 적합하며 현재 쉽게 구할 수 있는 technique으로 실현 가능한 attack 징후가 없는 cryptography입니다. |
| constrained device | Intended use에서 생기는 제약 때문에 data processing, communication, storage 또는 user interaction capability에 물리적 한계가 있는 device입니다. |
| consumer | Trade, business, craft 또는 profession 밖의 목적으로 행동하는 자연인입니다. |
| consumer IoT device | Associated service와 관계가 있고, consumer가 보통 가정이나 electronic wearable로 사용하는 network-connected 또는 network-connectable device입니다. |
| critical security parameter | 노출되거나 수정되면 security module의 security를 훼손할 수 있는 security 관련 secret information입니다. |
| debug interface | Manufacturer가 개발 중 device와 통신하거나 device issue를 triage하는 데 사용하는 physical interface로, consumer-facing functionality에는 쓰이지 않습니다. |
| defined support period | Manufacturer가 security update를 제공하는 최소 기간으로, 기간 또는 end date로 표현합니다. |
| device manufacturer | 여러 supplier의 product와 component를 포함할 가능성이 큰 완성된 consumer IoT product를 조립·제작하는 entity입니다. |
| factory default | Factory reset 이후 또는 최종 생산·조립 이후의 device 상태입니다. |
| initialization | Device의 network connectivity를 활성화해 operation 가능하게 하고, 선택적으로 user 또는 network access용 authentication feature를 설정하는 process입니다. |
| initialized state | Initialization 이후의 device 상태입니다. |
| IoT product | Consumer IoT device와 associated service를 합한 것입니다. |
| isolable | Main function에는 영향을 주지 않고 connectivity 관련 functionality loss만 감수해 현재 network에서 제거할 수 있는 상태입니다. 또는 environment 안 device의 integrity를 보장할 때에만 다른 device와 self-contained environment에 둘 수 있는 상태입니다. |
| logical interface | Network interface를 사용해 channel이나 port를 거쳐 network로 통신하는 software implementation입니다. |
| manufacturer | Device manufacturer를 포함한 supply chain의 관련 economic operator입니다. |
| network interface | Network를 통해 consumer IoT functionality에 접근하는 데 사용할 수 있는 physical interface입니다. |
| owner | Device를 소유하거나 구매한 user입니다. |
| personal data | 식별됐거나 식별 가능한 자연인과 관련된 모든 정보입니다. |
| physical interface | Physical layer에서 device와 통신하는 physical port 또는 radio·audio·optical 같은 air interface입니다. |
| public security parameter | 수정되면 security module의 security를 훼손할 수 있는 security 관련 public information입니다. |
| remotely accessible | Local network 밖에서 접근할 수 있도록 의도된 상태입니다. |
| security module | Security function을 구현하는 hardware, software 또는 firmware의 집합입니다. |
| security update | Manufacturer가 발견했거나 보고받은 security vulnerability를 해결하는 software update입니다. |
| sensitive security parameters | Critical security parameter와 public security parameter를 합한 것입니다. |
| software service | Functionality 지원에 사용하는 device의 software component입니다. |
| telemetry | Manufacturer가 issue나 device usage 관련 정보를 식별하는 데 도움을 주는 device data입니다. |
| unique per device | 주어진 product class 또는 type의 각 개별 device마다 고유한 상태입니다. |
| user | 자연인 또는 organization입니다. |
Provision 평가
다음 표는 IoT product의 component로 사용되는 Zephyr RTOS에 초점을 맞춰 ETSI EN 303 645 표 B.1로 수행한 self-assessment입니다.
ETSI 303 645의 표 B.1은 표준 provision의 구현 상태를 설명하는 mechanism을 제공합니다. Zephyr 문서는 다음 notation을 사용합니다.
| M | Mandatory requirement |
| R | Recommendation |
| M C | Conditional mandatory requirement |
| R C | Conditional recommendation |
| Y | Zephyr가 provision을 지원함 |
| N | Zephyr가 provision을 지원하지 않음 |
| N/A | Zephyr에 적용되지 않거나 product maker 책임임 |
| Provision | 설명 | 구분 | Zephyr 지원 | 근거·세부 사항 |
|---|---|---|---|---|
5.1-1 | Password를 사용하며 factory default가 아닌 모든 상태에서는 consumer IoT device의 모든 password가 device마다 고유하거나 user가 정의한 값이어야 합니다. | M C | N/A | — |
5.1-2 | 미리 설치된 device별 고유 password를 사용한다면, 같은 class나 type의 device에 대한 automated attack 위험을 낮추는 mechanism으로 생성해야 합니다. | M C | N/A | — |
5.1-3 | Device에 user를 authenticate하는 mechanism은 technology 특성, risk와 usage에 맞는 best practice cryptography를 사용해야 합니다. | M | N/A | — |
5.1-4 | User가 device에 authenticate할 수 있다면 device는 user 또는 administrator가 authentication value를 바꾸는 단순한 mechanism을 제공해야 합니다. | M C | N/A | — |
5.1-5 | Constrained device가 아니라면 network interface의 authentication mechanism에 대한 brute-force attack을 실질적으로 불가능하게 하는 mechanism이 있어야 합니다. | M C | N | Zephyr 원문 assessment의 세부 항목은 TODO입니다. |
5.2-1 | Manufacturer는 vulnerability disclosure policy를 공개해야 합니다. | M | Y | Vulnerability Management |
5.2-2 | 공개된 vulnerability에는 적시에 조치해야 합니다. | R | Y | Vulnerability timeline |
5.2-3 | Manufacturer는 defined support period 동안 판매·생산한 product와 운영 service의 security vulnerability를 계속 monitor하고 식별·수정해야 합니다. | R | Y | Zephyr module repository가 대상입니다. |
5.3-1 | Consumer IoT device의 모든 software component는 secure update가 가능해야 합니다. | R | Y | Device Firmware Upgrade |
5.3-2 | Constrained device가 아니라면 update를 안전하게 install하는 update mechanism을 가져야 합니다. | M C | Y | Device Firmware Upgrade |
5.3-3 | User가 update를 쉽게 적용할 수 있어야 합니다. | M C | N/A | — |
5.3-4 | Software update에 automatic mechanism을 사용하는 것이 좋습니다. | R C | N/A | — |
5.3-5 | Device는 initialization 이후와 그 뒤 주기적으로 security update가 있는지 확인하는 것이 좋습니다. | R C | N/A | — |
5.3-6 | Automatic update 또는 update notification을 지원하면 initialized state에서 enable하는 것이 좋습니다. User가 security update나 notification을 enable·disable하거나 installation을 연기할 수 있게 configuration해야 합니다. | R C | N/A | — |
5.3-7 | Device는 secure update mechanism을 위해 best practice cryptography를 사용해야 합니다. | M C | Y | west sign |
5.3-8 | Security update는 적시에 제공해야 합니다. | M C | N/A | — |
5.3-9 | Device는 software update의 authenticity와 integrity를 검증하는 것이 좋습니다. | R C | Y | 기능은 MCUboot가 제공합니다. Device Firmware Upgrade도 참고합니다. |
5.3-10 | Network interface로 update를 전달하면 device는 trust relationship을 통해 각 update의 authenticity와 integrity를 검증해야 합니다. | M | N/A | — |
5.3-11 | Manufacturer는 security update가 필요하다는 사실과 그 update가 완화하는 risk를 user가 알아보기 쉬운 명확한 방식으로 알리는 것이 좋습니다. | R C | N/A | — |
5.3-12 | Software update 적용이 device의 기본 동작을 중단시킬 경우 device는 user에게 알리는 것이 좋습니다. | R C | N/A | Zephyr는 자체 update에 관한 정보를 제공합니다. Zephyr를 product에 사용하는 주체는 영향 여부를 확인해야 합니다. |
5.3-13 | Manufacturer는 defined support period를 user가 이해할 수 있도록 명확하고 투명하며 접근 가능한 방식으로 공개해야 합니다. | M | Y | Release lifecycle and maintenance |
5.3-14 | Software update가 불가능한 constrained device는 update가 없는 이유, hardware replacement 지원 기간과 방법, defined support period를 접근 가능하고 명확하게 공개하는 것이 좋습니다. | R C | N/A | — |
5.3-15 | Software update가 불가능한 constrained device product는 network에서 isolate할 수 있고 hardware를 교체할 수 있는 것이 좋습니다. | R C | N/A | — |
5.3-16 | Consumer IoT device model designation은 device label 또는 physical interface로 명확하게 식별할 수 있어야 합니다. | M | N/A | — |
5.4-1 | Persistent storage의 sensitive security parameter는 device가 안전하게 저장해야 합니다. | M | N | Zephyr 자체에는 secure storage가 없습니다. |
5.4-2 | Security 목적으로 hard-coded device별 고유 identity를 사용한다면 physical, electrical 또는 software tampering에 견디도록 구현해야 합니다. | M C | N/A | — |
5.4-3 | Device software source code에 hard-coded critical security parameter를 사용하면 안 됩니다. | M | Y | Hardening Tool |
5.4-4 | Software update integrity·authenticity 검사와 associated service 통신 보호에 사용하는 critical security parameter는 device마다 고유해야 하며, device class에 대한 automated attack 위험을 줄이는 mechanism으로 생성해야 합니다. | M | N/A | — |
5.5-1 | Consumer IoT device는 secure communication에 best practice cryptography를 사용해야 합니다. | M | Y | — |
5.5-2 | Consumer IoT device는 network와 security functionality, 특히 cryptography를 제공할 때 review 또는 evaluation된 implementation을 사용하는 것이 좋습니다. | R | Y | — |
5.5-3 | Cryptographic algorithm과 primitive는 update할 수 있는 것이 좋습니다. | R | N | 전체 image를 update해야 합니다. |
5.5-4 | Initialized state에서 network interface를 통한 device functionality 접근은 해당 interface에서 authentication한 뒤에만 허용하는 것이 좋습니다. | R | N/A | — |
5.5-5 | Network interface를 통해 security 관련 configuration change를 허용하는 functionality는 authentication 후에만 접근할 수 있어야 합니다. Device가 의존하지만 manufacturer가 필요한 configuration을 보장할 수 없는 network service protocol은 예외입니다. | M | N/A | — |
5.5-6 | Critical security parameter는 transit 중 encryption하는 것이 좋으며, encryption은 technology 특성, risk와 usage에 적합해야 합니다. | R | Y | — |
5.5-7 | Consumer IoT device는 remotely accessible network interface로 전달되는 critical security parameter의 confidentiality를 보호해야 합니다. | M | Y | — |
5.5-8 | Manufacturer는 device 관련 critical security parameter에 secure management process를 적용해야 합니다. | M | N/A | — |
5.6-1 | 사용하지 않는 모든 network interface와 logical interface를 disable해야 합니다. | M | Y | Kconfig |
5.6-2 | Initialized state에서 device network interface는 authentication 없이 security 관련 information이 노출되는 양을 최소화해야 합니다. | M | Y | — |
5.6-3 | Device hardware는 attack에 불필요한 physical interface를 노출하지 않는 것이 좋습니다. | R | Y | Kconfig과 Hardening Tool |
5.6-4 | Debug interface에 물리적으로 접근할 수 있다면 software에서 disable해야 합니다. | M C | Y | Hardening Tool |
5.6-5 | Manufacturer는 device intended use나 operation에 사용하는 또는 필요한 software service만 enable하는 것이 좋습니다. | R | Y | Kconfig과 Hardening Tool |
5.6-6 | Code는 service나 device 동작에 필요한 functionality로 최소화하는 것이 좋습니다. | R | Y | Kconfig |
5.6-7 | Security와 functionality를 모두 고려해 software는 꼭 필요한 최소 privilege로 실행하는 것이 좋습니다. | R | Y | Security Overview |
5.6-8 | Device는 memory를 위한 hardware-level access-control mechanism을 포함하는 것이 좋습니다. | R | Y | Memory protection |
5.6-9 | Manufacturer는 device에 배포하는 software에 secure development process를 적용하는 것이 좋습니다. | R | Y | Security Overview와 Coding guideline |
5.7-1 | Consumer IoT device는 secure boot mechanism으로 software를 검증하는 것이 좋습니다. | R | Y | 기능은 MCUboot가 제공합니다. west sign도 참고합니다. |
5.7-2 | Software의 unauthorized change를 감지하면 device는 user 또는 administrator에게 알리고, alert 기능에 필요한 범위보다 넓은 network에는 연결하지 않는 것이 좋습니다. | R | N | Zephyr는 runtime detection 또는 notification을 제공하지 않습니다. |
5.8-1 | Device와 service, 특히 associated service 사이를 이동하는 personal data의 confidentiality는 best practice cryptography로 보호하는 것이 좋습니다. | R | Y | — |
5.8-2 | Device와 associated service 사이에서 통신하는 sensitive personal data의 confidentiality는 technology와 usage 특성에 적합한 cryptography로 보호해야 합니다. | M | Y | — |
5.8-3 | Device의 모든 external sensing capability를 user가 이해할 수 있도록 명확하고 투명하며 접근 가능한 방식으로 문서화해야 합니다. | M | Y | Sensing subsystem |
5.9-1 | Data network와 power outage 가능성을 고려해 consumer IoT device와 service에 resilience를 내장하는 것이 좋습니다. | R | Y | — |
5.9-2 | Network access를 잃어도 consumer IoT device는 계속 동작하고 local functionality를 유지하는 것이 좋으며, power가 복구되면 정상적으로 recover해야 합니다. | R | Y | — |
5.9-3 | Consumer IoT device는 infrastructure capability를 고려해 예상 가능하고 operational하며 stable한 상태에서 질서 있게 network에 연결하는 것이 좋습니다. | R | Y | — |
5.10-1 | Usage·measurement data 같은 telemetry를 consumer IoT device와 service에서 수집한다면 security anomaly를 검사하는 것이 좋습니다. | R C | N/A | — |
5.11-1 | User가 device의 user data를 간단히 erase할 수 있는 functionality를 제공해야 합니다. | M | N/A | — |
5.11-2 | Consumer가 associated service에서 personal data를 간단히 제거할 수 있는 device functionality를 제공하는 것이 좋습니다. | R | N/A | — |
5.11-3 | User에게 personal data 삭제 방법을 명확하게 안내하는 것이 좋습니다. | R | N/A | — |
5.11-4 | Service, device와 application에서 personal data가 삭제됐다는 명확한 confirmation을 user에게 제공하는 것이 좋습니다. | R | N/A | — |
5.12-1 | Consumer IoT installation과 maintenance에서 user가 내려야 하는 decision을 최소화하고 usability security best practice를 따르는 것이 좋습니다. | R | N/A | — |
5.12-2 | Manufacturer는 device를 안전하게 setup하는 방법을 user에게 안내하는 것이 좋습니다. | R | N/A | — |
5.12-3 | Manufacturer는 device가 안전하게 setup됐는지 확인하는 방법을 user에게 안내하는 것이 좋습니다. | R | N/A | — |
5.13-1 | Consumer IoT device software는 user interface로 받은 data, API로 전달된 data, service와 device의 network 사이에서 전달된 data를 validate해야 합니다. | M | Y | Syscall verification과 Coding guideline |
6.1-1 | Manufacturer는 각 device와 service가 어떤 personal data를 처리하는지, 어떻게·누가·무슨 목적으로 사용하는지 consumer에게 명확하고 투명하게 알려야 합니다. Advertiser를 포함한 관련 third party에도 적용됩니다. | M | N/A | — |
6.1-2 | Consumer consent를 근거로 personal data를 처리한다면 consent를 유효한 방식으로 얻어야 합니다. | M C | N/A | — |
6.1-3 | Personal data processing에 consent한 consumer는 언제든 consent를 withdraw할 수 있어야 합니다. | M | N/A | — |
6.1-4 | Consumer IoT device와 service에서 telemetry를 수집한다면 personal data processing을 intended functionality에 필요한 최소 범위로 유지하는 것이 좋습니다. | R C | N/A | — |
6.1-5 | Consumer IoT device와 service에서 telemetry를 수집한다면 어떤 telemetry를 수집하고 어떻게·누가·무슨 목적으로 사용하는지 consumer에게 알려야 합니다. | M C | N/A | — |
Source
출처
영어 원문에는 문단, 문서 지시문, 표, 코드, 코드 심벌, 경로를 그대로 보존했습니다.