summaryrefslogtreecommitdiffstats
path: root/docs/Chapter4/Security.rst
blob: 9b4f5f76fa635233f2b85ab89a5a30b7d76a590e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
.. Modifications Copyright © 2017-2018 AT&T Intellectual Property.

.. Licensed under the Creative Commons License, Attribution 4.0 Intl.
   (the "License"); you may not use this documentation except in compliance
   with the License. You may obtain a copy of the License at

.. https://creativecommons.org/licenses/by/4.0/

.. Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.


VNF Security
----------------------

The objective of this section is to provide the key security
requirements that need to be met by VNFs. The security requirements are
grouped into five areas as listed below. Other security areas will be
addressed in future updates. These security requirements are applicable
to all VNFs. Additional security requirements for specific types of VNFs
will be applicable and are outside the scope of these general
requirements.

Section 4.3 Security in *VNF Guidelines* outlines
the five broad security areas for VNFs that are detailed in the
following sections:

-  **VNF General Security**: This section addresses general security
   requirements for the VNFs that the VNF provider will need to address.

-  **VNF Identity and Access Management**: This section addresses
   security requirements with respect to Identity and Access Management
   as these pertain to generic VNFs.

-  **VNF API Security**: This section addresses the generic security
   requirements associated with APIs. These requirements are applicable
   to those VNFs that use standard APIs for communication and data
   exchange.

-  **VNF Security Analytics**: This section addresses the security
   requirements associated with analytics for VNFs that deal with
   monitoring, data collection and analysis.

-  **VNF Data Protection**: This section addresses the security
   requirements associated with data protection.

VNF General Security Requirements
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This section provides details on the VNF general security requirements
on various security areas such as user access control, network security,
ACLs, infrastructure security, and vulnerability management. These
requirements cover topics associated with compliance, security patching,
logging/accounting, authentication, encryption, role-based access
control, least privilege access/authorization. The following security
requirements need to be met by the solution in a virtual environment:

General Security Requirements

Integration and operation within a robust security environment is necessary
and expected. The security architecture will include one or more of the
following: IDAM (Identity and Access Management) for all system and
applications access, Code scanning, network vulnerability scans, OS,
Database and application patching, malware detection and cleaning,
DDOS prevention, network security gateways (internal and external)
operating at various layers, host and application based tools for
security compliance validation, aggressive security patch application,
tightly controlled software distribution and change control processes
and other state of the art security solutions. The VNF is expected to
function reliably within such an environment and the developer is
expected to understand and accommodate such controls and can expected
to supply responsive interoperability support and testing throughout
the product’s lifecycle.


.. req::
    :id: R-23740
    :target: VNF
    :keyword: MUST
    :updated: casablanca

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

.. req::
    :id: R-61354
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    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.

.. req::
    :id: R-92207
    :target: VNF
    :keyword: SHOULD
    :updated: casablanca

    The VNF **SHOULD** provide a mechanism for performing automated
    system configuration auditing at configurable time intervals.

.. req::
    :id: R-23882
    :target: VNF
    :keyword: SHOULD
    :updated: casablanca

    The VNF **SHOULD** provide the capability for the Operator to run security
    vulnerability scans of the operating system and all application layers.

.. req::
    :id: R-46986
    :target: VNF
    :keyword: SHOULD

    The VNF **SHOULD** have source code scanned using scanning
    tools (e.g., Fortify) and provide reports.

.. req::
    :id: R-99771
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    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.

.. req::
    :id: R-19768
    :target: VNF
    :keyword: SHOULD
    :updated: casablanca

    The VNF **SHOULD** support Layer 3 VPNs that enable segregation of
    traffic by application (i.e., AVPN, IPSec VPN for Internet routes).

.. req::
    :id: R-40813
    :target: VNF
    :keyword: SHOULD
    :updated: casablanca

    The VNF **SHOULD** support the use of virtual trusted platform
    module.

.. req::
    :id: R-56904
    :target: VNF
    :keyword: MUST

    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.

.. req::
    :id: R-69649
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    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.

.. req::
    :id: R-78010
    :target: VNF
    :keyword: MUST

    The VNF **MUST** use the NCSP's IDAM API for Identification,
    authentication and access control of customer or VNF application users.

.. req::
    :id: R-62498
    :target: VNF
    :keyword: MUST
    :updated: casablanca

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

.. req::
    :id: R-35144
    :target: VNF
    :keyword: MUST

    The VNF **MUST**, if not using the NCSP's IDAM API, comply
    with the NCSP's credential management policy.

.. req::
    :id: R-41994
    :target: VNF
    :keyword: MUST

    The VNF **MUST**, if not using the NCSP's IDAM API, comply
    with "No Self-Signed Certificates" policy. Self-signed certificates
    must be used for encryption only, using specified and approved
    encryption protocols such as TLS 1.2 or higher or equivalent security
    protocols such as IPSec, AES.

.. req::
    :id: R-80335
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    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.

.. req::
    :id: R-19082
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** allow the Operator to disable or remove any security
    testing tools or programs included in the VNF, e.g., password cracker,
    port scanner.

.. req::
    :id: R-21819
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** provide functionality that enables the Operator to comply
    with requests for information from law enforcement and government agencies.

.. req::
    :id: R-86261
    :target: VNF
    :keyword: MUST NOT
    :updated: casablanca

    The VNF **MUST NOT** allow vendor access to VNFs remotely.

.. req::
   :id: R-638682
   :target: VNF
   :keyword: MUST
   :introduced: casablanca
   :validation_mode: in_service

   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.

VNF Identity and Access Management Requirements
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The following security requirements for logging, identity, and access
management need to be met by the solution in a virtual environment:


Identity and Access Management Requirements

.. req::
    :id: R-99174
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** allow the creation of multiple IDs so that
    individual accountability can be supported.

.. req::
    :id: R-42874
    :target: VNF
    :keyword: MUST
    :updated: casablanca

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

.. req::
    :id: R-71787
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    Each layer of the VNF **MUST** support access restriction
    independently of all other layers so that Segregation of Duties
    can be implemented.

.. req::
    :id: R-59391
    :target: VNF
    :keyword: MUST NOT
    :updated: casablanca

    The VNF **MUST NOT** not allow the assumption of the permissions of
    another account to mask individual accountability.

.. req::
    :id: R-64503
    :target: VNF
    :keyword: MUST

    The VNF **MUST** provide minimum privileges for initial
    and default settings for new user accounts.

.. req::
    :id: R-86835
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** set the default settings for user access
    to deny authorization, except for a super user type of account.
    When a VNF is added to the network, nothing should be able to use
    it until the super user configures the VNF to allow other users
    (human and application)  have access.

.. req::
    :id: R-81147
    :target: VNF
    :keyword: MUST

    The VNF **MUST** have greater restrictions for access and
    execution, such as up to 3 factors of authentication and restricted
    authorization, for commands affecting network services, such as
    commands relating to VNFs.

.. req::
    :id: R-39562
    :target: VNF
    :keyword: MUST

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

.. req::
    :id: R-15671
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** provide access controls that allow the Operator
    to restrict access to VNF functions and data to authorized entities.

.. req::
    :id: R-85419
    :target: VNF
    :keyword: SHOULD
    :updated: casablanca

    The VNF **SHOULD** support OAuth 2.0 authorization using an external
    Authorization Server.

.. req::
    :id: R-75041
    :target: VNF
    :keyword: MUST
    :updated: casablanca

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

.. req::
    :id: R-98391
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST**, if not integrated with the Operator's Identity and
    Access Management system, support Role-Based Access Control to enforce
    least privilege.

.. req::
    :id: R-46908
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    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.

.. req::
    :id: R-79107
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST**, if not integrated with the Operator's Identity
    and Access Management system, support the ability to disable the
    userID after a configurable number of consecutive unsuccessful
    authentication attempts using the same userID.

.. req::
    :id: R-23135
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** authenticate all access to protected GUIs, CLIs,
    and APIs.


VNF API Security Requirements
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This section covers API security requirements when these are used by the
VNFs. Key security areas covered in API security are Access Control,
Authentication, Passwords, PKI Authentication Alarming, Anomaly
Detection, Lawful Intercept, Monitoring and Logging, Input Validation,
Cryptography, Business continuity, Biometric Authentication,
Identification, Confidentiality and Integrity, and Denial of Service.

The solution in a virtual environment needs to meet the following API
security requirements:


API Requirements

.. req::
    :id: R-43884
    :target: VNF
    :keyword: SHOULD
    :updated: casablanca

    The VNF **SHOULD** integrate with the Operator's authentication and
    authorization services (e.g., IDAM).

.. req::
    :id: R-21652
    :target: VNF
    :keyword: MUST

    The VNF **MUST** implement the following input validation
    control: Check the size (length) of all input. Do not permit an amount
    of input so great that it would cause the VNF to fail. Where the input
    may be a file, the VNF API must enforce a size limit.

.. req::
    :id: R-54930
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** implement the following input validation controls:
    Do not permit input that contains content or characters inappropriate
    to the input expected by the design. Inappropriate input, such as
    SQL expressions, may cause the system to execute undesirable and
    unauthorized transactions against the database or allow other
    inappropriate access to the internal network (injection attacks).

.. req::
    :id: R-21210
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** implement the following input validation control
    on APIs: Validate that any input file has a correct and valid
    Multipurpose Internet Mail Extensions (MIME) type. Input files
    should be tested for spoofed MIME types.

VNF Security Analytics Requirements
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This section covers VNF security analytics requirements that are mostly
applicable to security monitoring. The VNF Security Analytics cover the
collection and analysis of data following key areas of security
monitoring:

-  Anti-virus software

-  Logging

-  Data capture

-  Tasking

-  DPI

-  API based monitoring

-  Detection and notification

-  Resource exhaustion detection

-  Proactive and scalable monitoring

-  Mobility and guest VNF monitoring

-  Closed loop monitoring

-  Interfaces to management and orchestration

-  Malformed packet detections

-  Service chaining

-  Dynamic security control

-  Dynamic load balancing

-  Connection attempts to inactive ports (malicious port scanning)

The following requirements of security monitoring need to be met by the
solution in a virtual environment.

Security Analytics Requirements


.. req::
    :id: R-48470
    :target: VNF
    :keyword: MUST

    The VNF **MUST** support Real-time detection and
    notification of security events.

.. req::
    :id: R-22286
    :target: VNF
    :keyword: MUST

    The VNF **MUST** support Integration functionality via
    API/Syslog/SNMP to other functional modules in the network (e.g.,
    PCRF, PCEF) that enable dynamic security control by blocking the
    malicious traffic or malicious end users.

.. req::
    :id: R-32636
    :target: VNF
    :keyword: MUST

    The VNF **MUST** support API-based monitoring to take care of
    the scenarios where the control interfaces are not exposed, or are
    optimized and proprietary in nature.

.. req::
    :id: R-22367
    :target: VNF
    :keyword: MUST

    The VNF **MUST** support detection of malformed packets due to
    software misconfiguration or software vulnerability.

.. req::
    :id: R-73223
    :target: VNF
    :keyword: MUST

    The VNF **MUST** support proactive monitoring to detect and
    report the attacks on resources so that the VNFs and associated VMs can
    be isolated, such as detection techniques for resource exhaustion, namely
    OS resource attacks, CPU attacks, consumption of kernel memory, local
    storage attacks.

.. req::
    :id: R-58370
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** operate with anti-virus software which produces
    alarms every time a virus is detected.

.. req::
    :id: R-56920
    :target: VNF
    :keyword: MUST

    The VNF **MUST** protect all security audit logs (including
    API, OS and application-generated logs), security audit software, data,
    and associated documentation from modification, or unauthorized viewing,
    by standard OS access control mechanisms, by sending to a remote system,
    or by encryption.

.. req::
    :id: R-54520
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** log successful and unsuccessful authentication
    attempts, e.g., authentication associated with a transaction,
    authentication to create a session, authentication to assume elevated
    privilege.

.. req::
    :id: R-55478
    :target: VNF
    :keyword: MUST

    The VNF **MUST** log logoffs.

.. req::
    :id: R-13344
    :target: VNF
    :keyword: MUST

    The VNF **MUST** log starting and stopping of security
    logging.

.. req::
    :id: R-07617
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** log success and unsuccessful creation, removal, or
    change to the inherent privilege level of users.

.. req::
    :id: R-94525
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** log connections to the network listeners of the
    resource.

.. req::
    :id: R-31614
    :target: VNF
    :keyword: MUST

    The VNF **MUST** log the field "event type" in the security audit
    logs.

.. req::
    :id: R-97445
    :target: VNF
    :keyword: MUST

    The VNF **MUST** log the field "date/time" in the security audit
    logs.

.. req::
    :id: R-25547
    :target: VNF
    :keyword: MUST

    The VNF **MUST** log the field "protocol" in the security audit logs.

.. req::
    :id: R-06413
    :target: VNF
    :keyword: MUST

    The VNF **MUST** log the field "service or program used for access"
    in the security audit logs.

.. req::
    :id: R-15325
    :target: VNF
    :keyword: MUST

    The VNF **MUST** log the field "success/failure" in the
    security audit logs.

.. req::
    :id: R-89474
    :target: VNF
    :keyword: MUST

    The VNF **MUST** log the field "Login ID" in the security audit logs.

.. req::
    :id: R-04982
    :target: VNF
    :keyword: MUST NOT

    The VNF **MUST NOT** include an authentication credential,
    e.g., password, in the security audit logs, even if encrypted.

.. req::
    :id: R-63330
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** detect when its security audit log storage
    medium is approaching capacity (configurable) and issue an alarm.

.. req::
    :id: R-41252
    :target: VNF
    :keyword: MUST

    The VNF **MUST** support the capability of online storage of
    security audit logs.

.. req::
    :id: R-41825
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** activate security alarms automatically when
    a configurable number of consecutive unsuccessful login attempts
    is reached.

.. req::
    :id: R-43332
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** activate security alarms automatically when
    it detects the successful modification of a critical system or
    application file.

.. req::
    :id: R-74958
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** activate security alarms automatically when
    it detects an unsuccessful attempt to gain permissions
    or assume the identity of another user.

.. req::
    :id: R-15884
    :target: VNF
    :keyword: MUST

    The VNF **MUST** include the field "date" in the Security alarms
    (where applicable and technically feasible).

.. req::
    :id: R-23957
    :target: VNF
    :keyword: MUST

    The VNF **MUST** include the field "time" in the Security alarms
    (where applicable and technically feasible).

.. req::
    :id: R-71842
    :target: VNF
    :keyword: MUST

    The VNF **MUST** include the field "service or program used for
    access" in the Security alarms (where applicable and technically feasible).

.. req::
    :id: R-57617
    :target: VNF
    :keyword: MUST

    The VNF **MUST** include the field "success/failure" in the
    Security alarms (where applicable and technically feasible).

.. req::
    :id: R-99730
    :target: VNF
    :keyword: MUST

    The VNF **MUST** include the field "Login ID" in the Security
    alarms (where applicable and technically feasible).

.. req::
    :id: R-29705
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** restrict changing the criticality level of a
    system security alarm to users with administrative privileges.

.. req::
    :id: R-13627
    :target: VNF
    :keyword: MUST

    The VNF **MUST** monitor API invocation patterns to detect
    anomalous access patterns that may represent fraudulent access or other
    types of attacks, or integrate with tools that implement anomaly and
    abuse detection.

.. req::
    :id: R-04492
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** generate security audit logs that can be sent
    to Security Analytics Tools for analysis.

.. req::
    :id: R-30932
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** log successful and unsuccessful access to VNF
    resources, including data.

.. req::
    :id: R-54816
    :target: VNF
    :keyword: MUST

    The VNF **MUST** support the storage of security audit logs
    for agreed period of time for forensic analysis.

.. req::
    :id: R-84160
    :target: VNF
    :keyword: MUST

    The VNF **MUST** have security logging for VNFs and their
    OSs be active from initialization. Audit logging includes automatic
    routines to maintain activity records and cleanup programs to ensure
    the integrity of the audit/logging systems.

.. req::
    :id: R-34552
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** be implemented so that it is not vulnerable to OWASP
    Top 10 web application security risks.

.. req::
    :id: R-33488
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** protect against all denial of service
    attacks, both volumetric and non-volumetric, or integrate with external
    denial of service protection tools.

VNF Data Protection Requirements
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This section covers VNF data protection requirements that are mostly
applicable to security monitoring.


Data Protection Requirements

.. req::
    :id: R-58964
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** provide the capability to restrict read
    and write access to data handled by the VNF.

.. req::
    :id: R-83227
    :target: VNF
    :keyword: MUST

    The VNF **MUST** Provide the capability to encrypt data in
    transit on a physical or virtual network.

.. req::
    :id: R-32641
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** provide the capability to encrypt data on
    non-volatile memory.Non-volative memory is storage that is
    capable of retaining data without electrical power, e.g.
    Complementary metal–oxide–semiconductor (CMOS) or hard drives.

.. req::
    :id: R-13151
    :target: VNF
    :keyword: SHOULD

    The VNF **SHOULD** disable the paging of the data requiring
    encryption, if possible, where the encryption of non-transient data is
    required on a device for which the operating system performs paging to
    virtual memory. If not possible to disable the paging of the data
    requiring encryption, the virtual memory should be encrypted.

.. req::
    :id: R-73067
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** use NIST and industry standard cryptographic
    algorithms and standard modes of operations when implementing
    cryptography.

.. req::
    :id: R-12467
    :target: VNF
    :keyword: MUST NOT
    :updated: casablanca

    The VNF **MUST NOT** use compromised encryption algorithms.
    For example, SHA, DSS, MD5, SHA-1 and Skipjack algorithms.
    Acceptable algorithms can be found in the NIST FIPS publications
    (https://csrc.nist.gov/publications/fips) and in the
    NIST Special Publications (https://csrc.nist.gov/publications/sp).

.. req::
    :id: R-02170
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** use, whenever possible, standard implementations
    of security applications, protocols, and formats, e.g., S/MIME, TLS, SSH,
    IPSec, X.509 digital certificates for cryptographic implementations.
    These implementations must be purchased from reputable vendors or obtained
    from reputable open source communities and must not be developed in-house.

.. req::
    :id: R-70933
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** provide the ability to migrate to newer
    versions of cryptographic algorithms and protocols with minimal impact.

.. req::
    :id: R-95864
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** support digital certificates that comply with X.509
    standards.

.. req::
    :id: R-12110
    :target: VNF
    :keyword: MUST NOT

    The VNF **MUST NOT** use keys generated or derived from
    predictable functions or values, e.g., values considered predictable
    include user identity information, time of day, stored/transmitted data.

.. req::
    :id: R-69610
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** provide the capability of using X.509 certificates
    issued by an external Certificate Authority.

.. req::
    :id: R-47204
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** be capable of protecting the confidentiality and integrity
    of data at rest and in transit from unauthorized access and modification.


VNF Cryptography Requirements
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This section covers VNF cryptography requirements that are mostly
applicable to encryption or protocol meethods.

.. req::
    :id: R-48080
    :target: VNF
    :keyword: SHOULD
    :updated: casablanca

    The VNF **SHOULD** support an automated certificate management protocol
    such as CMPv2, Simple Certificate Enrollment Protocol (SCEP) or
    Automated Certificate Management Environment (ACME).

.. req::
    :id: R-93860
    :target: VNF
    :keyword: SHOULD
    :updated: casablanca

    The VNF **SHOULD** provide the capability to integrate with an
    external encryption service.

.. req::
    :id: R-44723
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** use symmetric keys of at least 112 bits in length.

.. req::
    :id: R-25401
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** use asymmetric keys of at least 2048 bits in length.

.. req::
    :id: R-52060
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** provide the capability to configure encryption
    algorithms or devices so that they comply with the laws of the jurisdiction
    in which there are plans to use data encryption.

.. req::
    :id: R-83500
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** provide the capability of allowing certificate
    renewal and revocation.

.. req::
    :id: R-29977
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** provide the capability of testing the validity
    of a digital certificate by validating the CA signature on the certificate.

.. req::
    :id: R-24359
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** provide the capability of testing the validity
    of a digital certificate by validating the date the certificate is being
    used is within the validity period for the certificate.

.. req::
    :id: R-39604
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** provide the capability of testing the
    validity of a digital certificate by checking the Certificate Revocation
    List (CRL) for the certificates of that type to ensure that the
    certificate has not been revoked.

.. req::
    :id: R-75343
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** provide the capability of testing the
    validity of a digital certificate by recognizing the identity represented
    by the certificate - the "distinguished name".

.. req::
    :id: R-49109
    :target: VNF
    :keyword: MUST
    :updated: casablanca

    The VNF **MUST** support HTTP/S using TLS v1.2 or higher
    with strong cryptographic ciphers.