As part of the AAnF network product, it is expected that the AAnF to contain AAnF application, a set of running processes (typically more than one) executing the software package for the AAnF functions and OAM functions that is specific to the AAnF network product model. Functionalities specific to the AAnF network product introduce additional threats and/or critical assets as described below. Related security requirements and test cases have been captured in TS 33.537.
In addition to the critical assets of a GNP described in clause 5.2 of the present document, the critical assets specific to the AAnF to be protected are:
AAnF Application;
AKMA context Data: i.e. subscriber's identities (SUPI), AKMA Anchor Key (KAKMA) and AKMA Key IDentifier (A-KID).
The interfaces of AAnF to be protected and which are within SECAM scope:
Service based interface, Naanf, for providing services for AUSF, NEF, AF
Service based interface for consuming services from AUSF, NEF, AF, and NRF
Console interface, for local access: local interface on AAnF
OAM interface, for remote access: interface between AAnF and OAM system
Threat name: Control plane data protection with AUSF.
Threat Category: Tampering, Information Disclosure, Denial of Service.
Threat Description: Control plane traffic is transported between the AAnF and the AUSF via SBA interface. If the control plane data transported over the interface is not confidentiality protected, it can be subject to eavesdropping. Information is leaked to unauthorized parties. If the control plane traffic is not integrity protected, attackers can tamper with user traffic at will. If the control plane traffic is not replay protected, attackers can insert historical legitimate values into the AAnF or to the AUSF. This can lead to denial of service to legitimate users.
If the protection implemented for the control plane transported over the SBA interface uses the wrong security profile, which may contain weak security algorithms or protocol versions known to be vulnerable, the level of the security of the user plane data may be degraded and fail to fulfil the required security.
Threat name: Control plane data protection with AF/NEF.
Threat Category: Tampering, Information Disclosure, Denial of Service.
Threat Description: Control plane traffic is transported between the AAnF and the AF/NEF via SBA interface. If the control plane data transported over the interface is not confidentiality protected, it can be subject to eavesdropping. Information is leaked to unauthorized parties. If the control plane traffic is not integrity protected, attackers can tamper with user traffic at will. If the control plane traffic is not replay protected, attackers can insert historical legitimate values into the AAnF or to the AF/NEF. This can lead to denial of service to legitimate users.
If the protection implemented for the control plane transported over the SBA interface uses the wrong security profile, which may contain weak security algorithms or protocol versions known to be vulnerable, the level of the security of the user plane data may be degraded and fail to fulfil the required security.