name: TRE
full_form: Trusted Environment
context: That TRE should verify that commands and responses between such MCIMs are origin-authenticated. 3. A TRE should be able to support and enforce the security controls of MCIMs. 4. On behalf of a M2ME subscriber, a TRE should store, monitor and enforce such MCIM management security controls as may be specifiable by the M2ME subscriber. 5. Interfaces to a TRE should be usable without compromising the Confidentiality, Integrity and Availability of the MCIMs or of that TRE. 6. A TRE should assure the security of the transition of MCIMs through their various lifecycle stages. 7. A TRE should maintain a registry of the MCIMs that it manages, including information about their current lifecycle and security status. 8. The executable code of a MCIM should be integrity checked by a TRE at boot time and whenever a TRE is reset and optionally at the start of each session with that MCIM. The integrity of the file system may also be checked. Detection of anomalies should result in the MCIM entering
description: A Trusted Environment (TRE) is a secure environment that provides a set of security controls and services to manage and protect Machine-Type Communication (MTC) devices, also known as Machine-to-Machine (M2M) devices. It verifies the origin authentication of commands and responses between MTC devices, enforces security controls, stores and monitors management security controls, and assures the security of the transition of MTC devices through their lifecycle stages.
explanation: TRE is classified as a Network Function based on its role in managing and securing MTC devices within the network. The context highlights its responsibilities in verifying origin authentication, enforcing security controls, and maintaining a registry of managed MTC devices.
section_title: 6.1.2.3	Threat analysis of Alternative 1: Non UICC based solution with remote subscription provisioning and change
biotag_Context: O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O
biotag_Description: O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O