-
Notifications
You must be signed in to change notification settings - Fork 281
/
Copy pathpcidss-4_0.yaml
3829 lines (3417 loc) · 167 KB
/
pcidss-4_0.yaml
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
urn: urn:intuitem:risk:library:pcidss-4_0
locale: en
ref_id: PCI DSS 4.0
name: Payment Card Industry Data Security Standard
description: 'Payment Card Industry Data Security Standard: Requirements and Testing
Procedures, v4.0 '
copyright: "\xA92006 - 2022 PCI Security Standards Council, LLC. All Rights Reserved. "
version: 1
provider: PCI Security Standards Council
packager: intuitem
objects:
framework:
urn: urn:intuitem:risk:framework:pcidss-4_0
ref_id: PCI DSS 4.0
name: Payment Card Industry Data Security Standard
description: 'Payment Card Industry Data Security Standard: Requirements and Testing
Procedures, v4.0 '
requirement_nodes:
- urn: urn:intuitem:risk:req_node:pcidss-4_0:build-and-maintain-a-secure-network-and-systems
assessable: false
depth: 1
name: Build and Maintain a Secure Network and Systems
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:build-and-maintain-a-secure-network-and-systems
ref_id: '1'
name: Requirement 1
description: Install and Maintain Network Security Controls
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1
ref_id: '1.1'
description: Processes and mechanisms for installing and maintaining network
security controls are defined and understood.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.1.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.1
ref_id: 1.1.1
description: 'All security policies and operational procedures that are identified
in Requirement 1 are:
- Documented.
- Kept up to date.
- In use.
- Known to all affected parties.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.1.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.1
ref_id: 1.1.2
description: 'Roles and responsibilities for performing activities in Requirement
1 are documented, assigned, and understood. '
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1
ref_id: '1.2'
description: Network security controls (NSCs) are configured and maintained.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2
ref_id: 1.2.1
description: 'Configuration standards for NSC rulesets are
- Defined.
- Implemented
- Maintained.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2
ref_id: 1.2.2
description: 'All changes to network connections and to configurations of NSCs
are approved and managed in accordance with the change control process defined
at Requirement 6.5.1. '
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2.3
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2
ref_id: 1.2.3
description: 'An accurate network diagram(s) is maintained that shows all connections
between the CDE and other networks, including any wireless networks. '
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2.4
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2
ref_id: 1.2.4
description: 'An accurate data-flow diagram(s) is maintained that meets the
following:
- Shows all account data flows across systems and networks.
- Updated as needed upon changes to the environment.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2.5
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2
ref_id: 1.2.5
description: All services, protocols, and ports allowed are identified, approved,
and have a defined business need.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2.6
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2
ref_id: 1.2.6
description: Security features are defined and implemented for all services,
protocols, and ports that are in use and considered to be insecure, such that
the risk is mitigated.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2.7
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2
ref_id: 1.2.7
description: Configurations of NSCs are reviewed at least once every six months
to confirm they are relevant and effective.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2.8
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.2
ref_id: 1.2.8
description: 'Configuration files for NSCs are:
- Secured from unauthorized access.
- Kept consistent with active network configurations.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1
ref_id: '1.3'
description: Network access to and from the cardholder data environment is restricted.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.3.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.3
ref_id: 1.3.1
description: "Inbound traffic to the CDE is restricted as follows: \n- To only\
\ traffic that is necessary. \n- All other traffic is specifically denied. "
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.3.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.3
ref_id: 1.3.2
description: 'Outbound traffic from the CDE is restricted as follows:
- To only traffic that is necessary.
- All other traffic is specifically denied.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.3.3
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.3
ref_id: 1.3.3
description: "NSCs are installed between all wireless networks and the CDE,\
\ regardless of whether the wireless network is a CDE, such that: \n- All\
\ wireless traffic from wireless networks into the CDE is denied by default.\n\
- Only wireless traffic with an authorized business purpose is allowed into\
\ the CDE."
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1
ref_id: '1.4'
description: Network connections between trusted and untrusted networks are
controlled.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.4.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.4
ref_id: 1.4.1
description: NSCs are implemented between trusted and untrusted networks.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.4.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.4
ref_id: 1.4.2
description: 'Inbound traffic from untrusted networks to trusted networks is
restricted to:
- Communications with system components that are authorized to provide publicly
accessible services, protocols, and ports.
- Stateful responses to communications initiated by system components in a
trusted network.
- All other traffic is denied.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.4.3
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.4
ref_id: 1.4.3
description: 'Anti-spoofing measures are implemented to detect and block forged
source IP addresses from entering the trusted network. '
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.4.4
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.4
ref_id: 1.4.4
description: 'System components that store cardholder data are not directly
accessible from untrusted networks. '
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.4.5
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.4
ref_id: 1.4.5
description: The disclosure of internal IP addresses and routing information
is limited to only authorized parties.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.5
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1
ref_id: '1.5'
description: Risks to the CDE from computing devices that are able to connect
to both untrusted networks and the CDE are mitigated.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:1.5.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:1.5
ref_id: 1.5.1
description: "Security controls are implemented on any computing devices, including\
\ company- and employee-owned devices, that connect to both untrusted networks\
\ (including the Internet) and the CDE as follows:\n- Specific configuration\
\ settings are defined to prevent threats being introduced into the entity\u2019\
s network.\n- Security controls are actively running.\n- Security controls\
\ are not alterable by users of the computing devices unless specifically\
\ documented and authorized by Management on a case-by-case basis for a limited\
\ period."
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:build-and-maintain-a-secure-network-and-systems
ref_id: '2'
name: Requirement 2
description: Apply Secure Configurations to All System Components
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2
ref_id: '2.1'
description: Processes and mechanisms for applying secure configurations to
all system components are defined and understood.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.1.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2.1
ref_id: 2.1.1
description: 'All security policies and operational procedures that are identified
in Requirement 2 are:
- Documented.
- Kept up to date.
- In use.
- Known to all affected parties. '
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.1.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2.1
ref_id: 2.1.2
description: 'Roles and responsibilities for performing activities in Requirement
2 are documented, assigned, and understood. '
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2
ref_id: '2.2'
description: System components are configured and managed securely.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2
ref_id: 2.2.1
description: 'Configuration standards are developed, implemented, and maintained
to:
- Cover all system components.
- Be consistent with industry-accepted system hardening standards or vendor
hardening recommendations.
- Be updated as new vulnerability issues are identified, as defined in Requirement
6.3.1.
- Be applied when new systems are configured and verified as in place before
or immediately after a system component is connected to a production environment.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2
ref_id: 2.2.2
description: 'Vendor default accounts are managed as follows:
- If the vendor default account(s) will be used, the default password is changed
per Requirement 8.3.6.
- If the vendor default account(s) will not be used, the account is removed
or disabled.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2.3
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2
ref_id: 2.2.3
description: "Primary functions requiring different security levels are managed\
\ as follows: \n- Only one primary function exists on a system component.\n\
OR \n- Primary functions with differing security levels that exist on the\
\ same system component are isolated from each other.\nOR\n- Primary functions\
\ with differing security levels on the same system component are all secured\
\ to the level required by the function with the highest security need."
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2.4
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2
ref_id: 2.2.4
description: Only necessary services, protocols, daemons, and functions are
enabled, and all unnecessary functionality is removed or disabled.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2.5
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2
ref_id: 2.2.5
description: 'If any insecure services, protocols, or daemons are present:
- business justification is documented.
- additional security features are documented and implemented that reduce
the risk of using insecure services, protocols, or daemons.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2.6
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2
ref_id: 2.2.6
description: System security parameters are configured to prevent misuse.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2.7
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2.2
ref_id: 2.2.7
description: All non-console administrative access is encrypted using strong
cryptography.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2
ref_id: '2.3'
description: Wireless environments are configured and managed securely.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.3.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2.3
ref_id: 2.3.1
description: "For wireless environments connected to the CDE or transmitting\
\ account data, all wireless vendor defaults are changed at installation or\
\ are confirmed to be secure, including but not limited to: \_\n- Default\
\ wireless encryption keys.\n- Default wireless encryption keys.\n- Passwords\
\ on wireless access points.\n- SNMP defaults.\n- Any other security-related\
\ wireless vendor defaults."
- urn: urn:intuitem:risk:req_node:pcidss-4_0:2.3.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:2.3
ref_id: 2.3.2
description: 'For wireless environments connected to the CDE or transmitting
account data, wireless encryption keys are changed as follows:
- Whenever personnel with knowledge of the key leave the company or the role
for which the knowledge was necessary.
- Whenever a key is suspected of or known to be compromised.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:protect-account-data
assessable: false
depth: 1
name: Protect Account Data
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:protect-account-data
ref_id: '3'
name: Requirement 3
description: Protect Stored Account Data
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3
ref_id: '3.1'
description: Processes and mechanisms for protecting stored account data are
defined and understood.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.1.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.1
ref_id: 3.1.1
description: 'All security policies and operational procedures that are identified
in Requirement 3 are:
- Documented.
- Kept up to date.
- In use.
- Known to all affected parties.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.1.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.1
ref_id: 3.1.2
description: 'Roles and responsibilities for performing activities in Requirement
3 are documented, assigned, and understood. '
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3
ref_id: '3.2'
description: Storage of account data is kept to a minimum.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.2.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.2
ref_id: 3.2.1
description: 'Account data storage is kept to a minimum through implementation
of data retention and disposal policies, procedures, and processes that include
at least the following:
- Coverage for all locations of stored account data.
- Coverage for any sensitive authentication data (SAD) stored prior to completion
of authorization. This bullet is a best practice until its effective date;
refer to Applicability Notes below for details.
- Limiting data storage amount and retention time to that which is required
for legal or regulatory, and/or business requirements.
- Specific retention requirements for stored account data that defines length
of retention period and includes a documented business justification.
- Processes for secure deletion or rendering account data unrecoverable when
no longer
needed per the retention policy.
- A process for verifying, at least once every three months, that stored account
data exceeding the defined retention period has been securely deleted or rendered
unrecoverable.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3
ref_id: '3.3'
description: Sensitive authentication data (SAD) is not stored after authorization.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3
ref_id: 3.3.1
description: ' SAD is not retained after authorization, even if encrypted. All
sensitive authentication data received is rendered unrecoverable upon completion
of the authorization process.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3.1.1
assessable: true
depth: 5
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3.1
ref_id: 3.3.1.1
description: The full contents of any track are not retained upon completion
of the authorization process.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3.1.2
assessable: true
depth: 5
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3.1
ref_id: 3.3.1.2
description: The card verification code is not retained upon completion of the
authorization process.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3.1.3
assessable: true
depth: 5
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3.1
ref_id: 3.3.1.3
description: The personal identification number (PIN) and the PIN block are
not retained upon completion of the authorization process
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3
ref_id: 3.3.2
description: 'SAD that is stored electronically prior to completion of authorization
is encrypted using
strong cryptography.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3.3
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.3
ref_id: 3.3.3
description: 'Additional requirement for issuers and companies that support
issuing services and store sensitive authentication data: Any storage of sensitive
authentication data is:
- Limited to that which is needed for a legitimate issuing business need and
is secured.
- Encrypted using strong cryptography. This bullet is a best practice until
its effective date.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3
ref_id: '3.4'
description: Access to displays of full PAN and ability to copy cardholder data
are restricted.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.4.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.4
ref_id: 3.4.1
description: 'PAN is masked when displayed (the BIN and last four digits are
the maximum number of digits
to be displayed), such that only personnel with a legitimate business need
can see more than the BIN and last four digits of the PAN.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.4.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.4
ref_id: 3.4.2
description: 'When using remote-access technologies, technical controls prevent
copy and/or relocation of
PAN for all personnel, except for those with documented, explicit authorization
and a legitimate, defined business need.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.5
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3
ref_id: '3.5'
description: Primary account number (PAN) is secured wherever it is stored.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.5.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.5
ref_id: 3.5.1
description: "PAN is rendered unreadable anywhere it is stored by using any\
\ of the following approaches:\n- One-way hashes based on strong cryptography\
\ of the entire PAN.\n- Truncation (hashing cannot be used to replace the\
\ truncated segment of PAN).\n\u2013 If hashed and truncated versions of the\
\ same PAN, or different truncation formats of the same PAN, are present in\
\ an environment, additional controls are in place such that the different\
\ versions cannot be correlated to reconstruct the original PAN.\n- Index\
\ tokens.\n- Strong cryptography with associated key-management processes\
\ and procedures."
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.5.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.5
ref_id: 3.5.2
description: Hashes used to render PAN unreadable (per the first bullet of Requirement
3.5.1) are keyed cryptographic hashes of the entire PAN, with associated key-management
processes and procedures in accordance with Requirements 3.6 and 3.7.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.5.3
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.5
ref_id: 3.5.3
description: 'If disk-level or partition-level encryption rather than file-,
column-, or field-level database encryption) is used to render PAN unreadable,
it is implemented only as follows:
- On removable electronic media.
OR
- If used for non-removable electronic media, PAN is also rendered unreadable
via another mechanism that meets Requirement 3.5.1.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.5.4
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.5
ref_id: 3.5.4
description: 'If disk-level or partition-level encryption is used (rather than
file-, column-, or field--level database encryption) to render PAN unreadable,
it is managed as follows:
- Logical access is managed separately and independently of native operating
system authentication and access control mechanisms.
- Decryption keys are not associated with user accounts.
- Authentication factors (passwords, passphrases, or cryptographic keys) that
allow access to - nencrypted data are stored securely.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.6
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3
ref_id: '3.6'
description: Cryptographic keys used to protect stored account data are secured.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.6.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.6
ref_id: 3.6.1
description: 'Procedures are defined and implemented to protect cryptographic
keys used to protect stored account data against disclosure and misuse that
include:
- Access to keys is restricted to the fewest number of custodians necessary.
- Key-encrypting keys are at least as strong as the data-encrypting keys they
protect.
- Key-encrypting keys are stored separately from data-encrypting keys.
- Keys are stored securely in the fewest possible locations and forms.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.6.1.1
assessable: true
depth: 5
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.6.1
ref_id: 3.6.1.1
description: 'Additional requirement for service providers only: A documented
description of the cryptographic architecture is maintained that includes:
- Details of all algorithms, protocols, and keys used for the protection of
stored account data, including key strength and expiry date.
- Preventing the use of the same cryptographic keys in production and test
environments. This bullet is a best practice until its effective date.
- Description of the key usage for each key.
- Inventory of any hardware security modules (HSMs), key management systems
(KMS), and other secure cryptographic devices (SCDs) used for key management,
including type and location of devices, as outlined in Requirement 12.3.4.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.6.1.2
assessable: true
depth: 5
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.6.1
ref_id: 3.6.1.2
description: 'Secret and private keys used to encrypt/decrypt stored account
data are stored in one (or more) of the following forms at all times:
- Encrypted with a key-encrypting key that is at least as strong as the data-encrypting
key, and that is stored separately from the data-encrypting key.
- Within a secure cryptographic device (SCD), such as a hardware security
module (HSM) or PTS-approved point-of-interaction device.
- As at least two full-length key components or key shares, in accordance
with an industry-accepted method'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.6.1.3
assessable: true
depth: 5
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.6.1
ref_id: 3.6.1.3
description: Access to cleartext cryptographic key components is restricted
to the fewest number of custodians necessary.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.6.1.4
assessable: true
depth: 5
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.6.1
ref_id: 3.6.1.4
description: Cryptographic keys are stored in the fewest possible location.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3
ref_id: '3.7'
description: Where cryptography is used to protect stored account data, key
management processes and procedures covering all aspects of the key
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7
ref_id: 3.7.1
description: Key-management policies and procedures are implemented to include
generation of strong cryptographic keys used to protect stored account data.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7
ref_id: 3.7.2
description: Key-management policies and procedures are implemented to include
secure distribution of cryptographic keys used to protect stored account data.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7.3
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7
ref_id: 3.7.3
description: Key-management policies and procedures are implemented to include
secure storage of cryptographic keys used to protect stored account data.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7.4
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7
ref_id: 3.7.4
description: 'Key management policies and procedures are implemented for cryptographic
key changes for keys that have reached the end of their cryptoperiod, as defined
by the associated application vendor or key owner, and based on industry best
practices and guidelines, including the following:
- A defined cryptoperiod for each key type in use.
- A process for key changes at the end of the defined cryptoperiod.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7.5
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7
ref_id: 3.7.5
description: 'Key management policies procedures are implemented to include
the retirement, replacement, or destruction of keys used to protect stored
account data, as deemed necessary when:
- The key has reached the end of its defined cryptoperiod.
- The integrity of the key has been weakened, including when personnel with
knowledge of a cleartext key component leaves the company, or the role for
which the key component was known.
- The key is suspected of or known to be compromised.
- Retired or replaced keys are not used for encryption operations.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7.6
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7
ref_id: 3.7.6
description: Where manual cleartext cryptographic key-management operations
are performed by personnel, key-management policies and procedures are implemented
include managing these operations using split knowledge and dual control.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7.7
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7
ref_id: 3.7.7
description: Key management policies and procedures are implemented to include
the prevention of unauthorized substitution of cryptographic keys.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7.8
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7
ref_id: 3.7.8
description: Key management policies and procedures are implemented to include
that cryptographic key custodians formally acknowledge (in writing or electronically)
that they understand and accept their key-custodian responsibilities.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7.9
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:3.7
ref_id: 3.7.9
description: "Additional testing procedure for service provider assessments\
\ only: If the service provider shares cryptographic keys with its customers\
\ for transmission or storage of account data, examine the documentation that\
\ the service provider provides to its customers to verify it includes guidance\
\ on how to securely transmit, store, and update customers\u2019 keys in accordance\
\ with all elements specified in Requirements 3.7.1 through 3.7.8 above."
- urn: urn:intuitem:risk:req_node:pcidss-4_0:4
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:protect-account-data
ref_id: '4'
name: Requirement 4
description: Protect Cardholder Data with Strong Cryptography During Transmission
Over Open, Public Networks
- urn: urn:intuitem:risk:req_node:pcidss-4_0:4.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:4
ref_id: '4.1'
description: Processes and mechanisms for protecting cardholder data with strong
cryptography during transmission over open, public networks are defined and
documented.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:4.1.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:4.1
ref_id: 4.1.1
description: 'All security policies and operational procedures that are identified
in Requirement 4 are:
- Documented.
- Kept up to date.
- In use.
- Known to all affected parties'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:4.1.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:4.1
ref_id: 4.1.2
- urn: urn:intuitem:risk:req_node:pcidss-4_0:4.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:4
ref_id: '4.2'
description: PAN is protected with strong cryptography during transmission.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:4.2.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:4.2
ref_id: 4.2.1
description: 'Strong cryptography and security protocols are implemented as
follows to safeguard PAN during transmission over open, public networks:
- Only trusted keys and certificates are accepted.
- Certificates used to safeguard PAN during transmission over open, public
networks are confirmed as valid and are not expired or revoked. This bullet
is a best practice until its effective date; refer to applicability notes
below for details.
- The protocol in use supports only secure versions or configurations and
does not support fallback to, or use of insecure versions, algorithms, key
sizes, or implementations.
- The encryption strength is appropriate for the encryption methodology in
use.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:4.2.1.1
assessable: true
depth: 5
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:4.2.1
ref_id: 4.2.1.1
description: "An inventory of the entity\u2019s trusted keys and certificates\
\ used to protect PAN during transmission is maintained."
- urn: urn:intuitem:risk:req_node:pcidss-4_0:4.2.1.2
assessable: true
depth: 5
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:4.2.1
ref_id: 4.2.1.2
description: Wireless networks transmitting PAN or connected to the CDE use
industry best practices to implement strong cryptography for authentication
and transmission.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:4.2.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:4.2
ref_id: 4.2.2
description: PAN is secured with strong cryptography whenever it is sent via
end-user messaging technologies.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:maintain-a-vulnerability-management-program
assessable: false
depth: 1
name: Maintain a Vulnerability Management Program
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:maintain-a-vulnerability-management-program
ref_id: '5'
name: Requirement 5
description: Protect All Systems and Networks from Malicious Software
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5
ref_id: '5.1'
description: Processes and mechanisms for protecting all systems and networks
from malicious software are defined and understood.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.1.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5.1
ref_id: 5.1.1
description: 'All security policies and operational procedures that are identified
in Requirement 5 are:
- Documented.
- Kept up to date.
- In use.
- Known to all affected parties.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.1.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5.1
ref_id: 5.1.2
description: Roles and responsibilities for performing activities in Requirement
5 are documented, assigned, and understood.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5
ref_id: '5.2'
description: Malicious software (malware) is prevented, or detected and addressed.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.2.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5.2
ref_id: 5.2.1
description: An anti-malware solution(s) is deployed on all system components,
except for those system components identified in periodic evaluations per
Requirement 5.2.3 that concludes the system components are not at risk from
malware.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.2.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5.2
ref_id: 5.2.2
description: 'The deployed anti-malware solution(s):
- Detects all known types of malware.
- Removes, blocks, or contains all known types of malware.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.2.3
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5.2
ref_id: 5.2.3
description: 'Any system components that are not at risk for malware are evaluated
periodically to include the following:
- A documented list of all system components not at risk for malware.
- Identification and evaluation of evolving malware threats for those system
components.
- Confirmation whether such system components continue to not require anti-malware
protection.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.2.3.1
assessable: true
depth: 5
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5.2.3
ref_id: 5.2.3.1
description: "The frequency of periodic evaluations of system components identified\
\ as not at risk for malware is defined in the entity\u2019s targeted risk\
\ analysis, which is performed according to all elements specified in Requirement\
\ 12.3.1."
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5
ref_id: '5.3'
description: Anti-malware mechanisms and processes are active, maintained, and
monitored.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3.1
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3
ref_id: 5.3.1
description: The anti-malware solution(s) is kept current via automatic updates.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3.2
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3
ref_id: 5.3.2
description: "The anti-malware solution(s):\n- Performs periodic scans and active\
\ or real-time scans. \nOR\n- Performs continuous behavioral analysis of systems\
\ or processes."
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3.2.1
assessable: true
depth: 5
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3.2
ref_id: 5.3.2.1
description: "If periodic malware scans are performed to meet Requirement 5.3.2,\
\ the frequency of scans is defined in the entity\u2019s targeted risk analysis,\
\ which is performed according to all elements specified in Requirement 12.3.1."
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3.3
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3
ref_id: 5.3.3
description: 'For removable electronic media, the anti-malware solution(s):
- Performs automatic scans of when the media is inserted, connected, or logically
mounted,
OR
- Performs continuous behavioral analysis of systems or processes when the
media is inserted, connected, or logically mounted.'
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3.4
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3
ref_id: 5.3.4
description: Audit logs for the anti-malware solution(s) are enabled and retained
in accordance with Requirement 10.5.1.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3.5
assessable: true
depth: 4
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5.3
ref_id: 5.3.5
description: Anti-malware mechanisms cannot be disabled or altered by users,
unless specifically documented, and authorized by management on a case-by-case
basis for a limited time period.
- urn: urn:intuitem:risk:req_node:pcidss-4_0:5.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:pcidss-4_0:5
ref_id: '5.4'
description: Anti-phishing mechanisms protect users against phishing attacks.