This Annex covers the aspects specific to the NWDAF network product class.

As part of the NWDAF network product, it is expected that the NWDAF to contain NWDAF application (for data analysis), a set of running processes (typically more than one) executing the software package for the NWDAF functions and OAM functions that is specific to the NWDAF network product model. Functionalities specific to the NWDAF network product introduce additional threats and/or critical assets as described below. Related security requirements and test cases have been captured in TS 33.521.

In addition to the critical assets of a GNP described in clause 5.2 of the present document, the critical assets specific to the NWDAF to be protected are:

• NWDAF Application;
• Collected Data from NFs: e.g. part of mobility management data as depicted in clause K.2.1 collected from AMF, part of Session related data, user plane data as depicted in clause J.2.1 collected from SMF, part of user subscription data as depicted in clause E.2.1 collected from UDM, part of NF and User Data as depicted in clause I.2.1 collected from NEF, data collectd from NRF, PCF, AF and OAM, etc.
• The interfaces of NWDAF to be protected and which are within SECAM scope:
  • Service based interface, Nnwdaf, for providing services to AMF, SMF, NEF, PCF, NSSF, OAM and AF.
  • Service based interface for consuming services from AMF, SMF, UDM, PCF, NRF, NEF and AF.
  • Console interface, for local access: local interface on NWDAF
  • OAM interface, for remote access and data collection: interface between NWDAF and OAM system
• NWDAF Software: binary code or executable code