VNF Security Requirements (from ONAP)

R-118669 

Login access (e.g., shell access) to the operating system layer, whether interactive or as part of an automated process, MUST be through an encrypted protocol such as SSH or TLS.

Y

N

All login access (e.g., shell access) to any service, whether interactive or as part of an automated process, must be through an encrypted protocol such as SSH or TLS 1.2 or higher.

R-19082 

The VNF MUST not contain undocumented functionality.

R-19768 

The VNF SHOULD support the separation of (1) signaling and payload traffic (i.e., customer facing traffic), (2) operations, administration and management traffic, and (3) internal VNF traffic (i.e., east-west traffic such as storage access) using technologies such as VPN and VLAN.

R-21819 

VNFs that are subject to regulatory requirements MUST provide functionality that enables the Operator to comply with ETSI TC LI requirements, and, optionally, other relevant national equivalents.

R-23740 

The VNF MUST implement and enforce the principle of least privilege on all protected interfaces.

Y

Y

RA-1 2.3.8.2 Platform and Access

sec.sys.007

The Platform must implement controls enforcing separation of duties and privileges, least privilege use and least common mechanism (Role-Based Access Control)

R-240760 

The VNF MUST NOT contain any backdoors.

R-256267 

If SNMP is utilized, the VNF MUST support at least SNMPv3 with message authentication.

R-258686 

The VNF application processes SHOULD NOT run as root. If a VNF application process must run as root, the technical reason must be documented.

R-353637 

Containerized components of VNFs SHOULD follow the recommendations for Container Base Images and Build File Configuration in the latest available version of the CIS Docker Community Edition Benchmarks to ensure that containerized VNFs are secure. All non-compliances with the benchmarks MUST be documented.

R-381623 

Containerized components of VNFs SHOULD execute in a Docker run-time environment that follows the Container Runtime Configuration in the latest available version of the CIS Docker Community Edition Benchmarks to ensure that containerized VNFs are secure. All non-compliances with the benchmarks MUST be documented.

R-46986 

The VNF provider MUST follow GSMA vendor practices and SEI CERT Coding Standards when developing the VNF in order to minimize the risk of vulnerabilities. See GSMA NESAS Network Equipment Security Assurance Scheme – Development and Lifecycle Security Requirements Version 1.0 (https://www.gsma.com/ security/wp-content/uploads/2019/11/FS.16-NESAS-Development-and-Lifecycle-Security- Requirements-v1.0.pdf) and SEI CERT Coding Standards (https://wiki.sei.cmu.edu/ confluence/display/seccode/SEI+CERT+Coding+Standards).

R-56904 

The VNF MUST interoperate with the ONAP (SDN) Controller so that it can dynamically modify the firewall rules, ACL rules, QoS rules, virtual routing and forwarding rules. This does not preclude the VNF providing other interfaces for modifying rules.

R-61354 

The VNF MUST provide a mechanism (e.g., access control list) to permit and/or restrict access to services on the VNF by source, destination, protocol, and/or port.

R-62498 

The VNF MUST support only encrypted access protocols, e.g., TLS, SSH, SFTP.

Y

Y

RA-1 2.3.8.2 Platform and Access

sec.sys.003 (doesn't mention technologies)

The Platform must support Secure and encrypted communications, and confidentiality and integrity of network traffic

The Platform must support Secure and encrypted communications, and confidentiality and integrity of network traffic, utilising encrypted access protocols such as TLS 1.2 or higher, SSH, SFTP.

R-638682 

The VNF MUST log any security event required by the VNF Requirements to Syslog using LOG_AUTHPRIV for any event that would contain sensitive information and LOG_AUTH for all other relevant events.

R-69649 

The VNF Provider MUST have patches available for vulnerabilities in the VNF as soon as possible. Patching shall be controlled via change control process with vulnerabilities disclosed along with mitigation recommendations.

RA-1 includes requirements for the platform

R-756950 

The VNF MUST be operable without the use of Network File System (NFS).

R-80335 

For all GUI and command-line interfaces, the VNF MUST provide the ability to present a warning notice that is set by the Operator. A warning notice is a formal statement of resource intent presented to everyone who accesses the system.

R-842258 

The VNF MUST include a configuration (e.g. a heat template or CSAR package) that specifies the targeted parameters (e.g. a limited set of ports) over which the VNF will communicate; including internal, external and management communication.

R-86261 

The VNF MUST be able to authenticate and authorize all remote access.

R-872986 

The VNF MUST store Authentication Credentials used to authenticate to other systems encrypted except where there is a technical need to store the password unencrypted in which case it must be protected using other security techniques that include the use of file and directory permissions. Ideally, credentials SHOULD rely on a HW Root of Trust, such as a TPM or HSM.

Y

Y

RA-1 2.3.8.1 System Hardening

sec.gen.003

All servers part of Cloud Infrastructure must support a root of trust and secure boot

modify to add, "such as TPM or HSM" as in:

All servers part of Cloud Infrastructure must support a root of trust, such as TPM or HSM, and secure boot

R-92207 

The VNF SHOULD provide a mechanism that enables the operators to perform automated system configuration auditing at configurable time intervals.

Y

N

The platform must perform automated system configuration auditing at configurable time intervals.

R-99771 

The VNF MUST have all code (e.g., QCOW2) and configuration files (e.g., HEAT template, Ansible playbook, script) hardened, or with documented recommended configurations for hardening and interfaces that allow the Operator to harden the VNF. Actions taken to harden a system include disabling all unnecessary services, and changing default values such as default credentials and community strings.

R-23135 

The VNF MUST, if not integrated with the Operator’s identity and access management system, authenticate all access to protected resources.

R-231402 

The VNF MUST provide a means to explicitly logout, thus ending that session.

Y

N

The Platform must provide a means to explicitly logout from an interactive session, thus ending that session.

The Platform must provide a means to automatically logout, thus ending that session, of any interactive session after a configurable period of inactivity.

R-251639 

The VNF MUST provide explicit confirmation of a session termination such as a message, new page, or rerouting to a login page.

R-358699 

The VNF MUST support at least the following roles: system administrator, application administrator, network function O&M.

R-373737 

The VNF MUST, if not integrated with the operator’s IAM system, provide a mechanism for assigning roles and/or permissions to an identity.

R-39562 

The VNF MUST disable unnecessary or vulnerable cgi-bin programs.

R-42874 

The VNF MUST allow the Operator to restrict access to protected resources based on the assigned permissions associated with an ID in order to support Least Privilege (no more privilege than required to perform job functions).

R-45719 

The VNF MUST, if not integrated with the Operator’s Identity and Access Management system, enforce a configurable “terminate idle sessions” policy by terminating the session after a configurable period of inactivity.

R-46908 

The VNF MUST, if not integrated with the Operator’s Identity and Access Management system, comply with “password complexity” policy. When passwords are used, they shall be complex and shall at least meet the following password construction requirements: (1) be a minimum configurable number of characters in length, (2) include 3 of the 4 following types of characters: upper-case alphabetic, lower-case alphabetic, numeric, and special, (3) not be the same as the UserID with which they are associated or other common strings as specified by the environment, (4) not contain repeating or sequential characters or numbers, (5) not to use special characters that may have command functions, and (6) new passwords must not contain sequences of three or more characters from the previous password.

Y

N

Requirement exists in discussions but not in consolidated requirements

The Platform must ensure compliance with password complexity policy.  When passwords are created, they shall be complex and shall at least meet the following password construction requirements: (1) be a minimum configurable number of characters in length, (2) include 3 of the 4 following types of characters: upper-case alphabetic, lower-case alphabetic, numeric, and special, (3) not be the same as the UserID with which they are associated or other common strings as specified by the environment, (4) not contain repeating or sequential characters or numbers, and (5) not be the same as a password used previously during a configurable period.

The Platform must ensure compliance with password expiry policy. Passwords expire after a configurable period of time. Passwords expire for non-use after a configurable period of time. 

R-479386 

The VNF MUST provide the capability of setting a configurable message to be displayed after successful login. It MAY provide a list of supported character sets.

R-581188 

The VNF MUST NOT identify the reason for a failed authentication, only that the authentication failed.

Y

N

The Platform must not identify the reason for a failed authentication, only that the authentication failed.

The Platform must limit the number of failed authentication attempts to a configurable number. When the number of failed attempts is reached, the platform must disable the user account; user account can be enabled by an administrator.

R-59391 

The VNF MUST NOT allow the assumption of the permissions of another account to mask individual accountability. For example, use SUDO when a user requires elevated permissions such as root or admin.

R-75041 

The VNF MUST, if not integrated with the Operator’s Identity and Access Management system, support configurable password expiration.

R-78010 

The VNF MUST support LDAP in order to integrate with an external identity and access manage system. It MAY support other identity and access management protocols.

Y

N

The Platform must support LDAP in order to integrate with an external identity and access manage system. It MAY support other identity and access management protocols.

R-79107 

The VNF MUST, if not integrated with the Operator’s Identity and Access Management system, support the ability to lock out the userID after a configurable number of consecutive unsuccessful authentication attempts using the same userID. The locking mechanism must be reversible by an administrator and should be reversible after a configurable time period.

R-81147 

The VNF MUST, if not integrated with the Operator’s Identity and Access Management system, support multifactor authentication on all protected interfaces exposed by the VNF for use by human users.

R-814377 

The VNF MUST have the capability of allowing the Operator to create, manage, and automatically provision user accounts using one of the protocols specified in Chapter 7.

R-844011 

The VNF MUST not store authentication credentials to itself in clear text or any reversible form and must use salting.