name: HMEE
full_form: Hardware Mediated Execution Environment
context: This solution proposes to equip the NFVI with one or more HMEEs, where an HMEE can be deployed for a single VNF or a group of VNFs. If the HMEE is shared, it needs to provide isolation from collocated VNFs. The HMEE is to be used for executing sensitive functions within the VNF, such as information elements marked as private (e.g. the SIDF de-concealing the SUPI from the SUCI). Other operations should use the existing security measures for NFV deployment. When deploying an HMEE on a NFV environment, the following are required: - The NFVI needs to be deployed using hardware resources that have an HMEE enabled. - The NFVI is designated an appropriate trust domain for VNF deployment based on its HMEE capability. HMEE enabled hosts provide security guarantees that reduce security risks and therefore belongs to higher trust domains. NOTE: Establishment of trust domains is based on solutions for key issue #1 - Data-in-use are inaccessible by either other VNFs or the virtualisation layer
description: The Hardware Mediated Execution Environment (HMEE) is a network function that provides a secure environment for executing sensitive functions within Virtual Network Functions (VNFs). It ensures isolation from collocated VNFs and reduces security risks, enabling the deployment of VNFs in higher trust domains.
explanation: The context explicitly describes HMEE as an entity that can be deployed for a single VNF or a group of VNFs, providing isolation and security guarantees. This role is characteristic of a Network Function, which is responsible for managing and controlling network operations.
section_title: 6.5.2	Solution details
biotag_Context: O,O,O,O,O,O,B-Technology,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,O,B-Network Function,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,B-Network Function,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,B-Network Function,O,O,B-Technology,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Technology,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,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,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O