Xxxxxxxx Capabilities. As presented in D3.1, the standard design for the SCs is defined in figure 2.1-1. This corresponds to the final design since the internal structure of the Network Service (NS) is maintained from the previous deliverable. Summarising the SC architecture: the NS encompasses the Security Element Manager (SEM) and the Container and Virtual Network Function (xNF), being the SEM the input/output point with respect to the xNF internally deployed. The SEM exposes two external interfaces to interact with the xNF: (i) the VeNf-Vnfm and (ii) the Message Broker (here, Xxxxx [1]). The former allows the SO to apply day0, day1 and day2 actions, which reconfigure the xNF lifecycle. The latter implements the collection of internal data generated in such xNF. Besides, the SC has another interface with the Network Function Virtualisation Infrastructure (NFVI) component, which exposes some relevant information for the SC deployment and lifecycle.
Xxxxxxxx Capabilities. This section presents the implementation details of the SCs identified in the PALANTIR context, as well as the main changes since D3.1. As commented in section 2.1.1, the IDS SC (combining IDS and DPI SCs), the FW SC, the NDS SC (introduced as NNS SC in D3.1), and the WTA SC are types of SCs still being delivered. However, four new types of SCs have been developed: SIEM and VPN, SCR and vTAP SCs, whose specific development and deployment details are explained below.
Xxxxxxxx Capabilities. Regarding the SCs, the consortium settled on a standardised structure aligned with the requirements in section 3.1, and finally partially implemented in section 4.1. The standard design or internal structure for the SCs is introduced first. This aligns with the requirements and implementation details defined in the upcoming sections. Each SC features two main modules: the Security Element Manager (SEM) and the Virtual Network Function (VNF). The former provides well-defined and standard interoperability interfaces to enable the dynamic deployment and configuration of the latter. Apart from the two main modules, which will be described thoroughly later on in this section, Figure 1 presents the general architecture of any SC, including inter-component communications and interfaces, internal networking, functionalities to be offered, and level of designated security policy to be used. Figure 1: SC detailed architecture. The rest of this section is organised to cover the multiple aspects included in Figure 1.
