-
Notifications
You must be signed in to change notification settings - Fork 281
/
Copy pathowasp-asvs-4.0.3.yaml
3628 lines (3628 loc) · 145 KB
/
owasp-asvs-4.0.3.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:owasp-asvs-4.0.3
locale: en
ref_id: OWASP-ASVS-4.0.3
name: OWASP ASVS 4.0.3
description: OWASP Application Security Verification Standard. https://owasp.org/www-project-application-security-verification-standard/
copyright: CC BY-SA 3.0 - The OWASP Foundation
version: 2
provider: OWASP
packager: intuitem
objects:
framework:
urn: urn:intuitem:risk:framework:owasp-asvs-4.0.3
ref_id: OWASP-ASVS-4.0.3
name: OWASP ASVS 4.0.3
description: 'OWASP Application Security Verification Standard '
implementation_groups_definition:
- ref_id: L1
name: Level 1
description: First steps, automated, or whole of portfolio view
- ref_id: L2
name: Level 2
description: Most applications
- ref_id: L3
name: Level 3
description: High value, high assurance, or high safety
requirement_nodes:
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
assessable: false
depth: 1
ref_id: V1
name: Architecture, Design and Threat Modeling
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
ref_id: V1.1
name: Secure Software Development Lifecycle
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1
ref_id: V1.1.1
description: Verify the use of a secure software development lifecycle that
addresses security in all stages of development. ([C1](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1
ref_id: V1.1.2
description: Verify the use of threat modeling for every design change or sprint
planning to identify threats, plan for countermeasures, facilitate appropriate
risk responses, and guide security testing.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1
ref_id: V1.1.3
description: Verify that all user stories and features contain functional security
constraints, such as "As a user, I should be able to view and edit my profile.
I should not be able to view or edit anyone else's profile"
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1
ref_id: V1.1.4
description: Verify documentation and justification of all the application's
trust boundaries, components, and significant data flows.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1.5
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1
ref_id: V1.1.5
description: Verify definition and security analysis of the application's high-level
architecture and all connected remote services. ([C1](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1.6
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1
ref_id: V1.1.6
description: Verify implementation of centralized, simple (economy of design),
vetted, secure, and reusable security controls to avoid duplicate, missing,
ineffective, or insecure controls. ([C10](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1.7
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.1
ref_id: V1.1.7
description: Verify availability of a secure coding checklist, security requirements,
guideline, or policy to all developers and testers.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.2
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
ref_id: V1.2
name: Authentication Architecture
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.2.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.2
ref_id: V1.2.1
description: Verify the use of unique or special low-privilege operating system
accounts for all application components, services, and servers. ([C3](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.2.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.2
ref_id: V1.2.2
description: Verify that communications between application components, including
APIs, middleware and data layers, are authenticated. Components should have
the least necessary privileges needed. ([C3](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.2.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.2
ref_id: V1.2.3
description: Verify that the application uses a single vetted authentication
mechanism that is known to be secure, can be extended to include strong authentication,
and has sufficient logging and monitoring to detect account abuse or breaches.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.2.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.2
ref_id: V1.2.4
description: Verify that all authentication pathways and identity management
APIs implement consistent authentication security control strength, such that
there are no weaker alternatives per the risk of the application.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.4
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
ref_id: V1.4
name: Access Control Architecture
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.4.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.4
ref_id: V1.4.1
description: Verify that trusted enforcement points, such as access control
gateways, servers, and serverless functions, enforce access controls. Never
enforce access controls on the client.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.4.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.4
ref_id: V1.4.4
description: Verify the application uses a single and well-vetted access control
mechanism for accessing protected data and resources. All requests must pass
through this single mechanism to avoid copy and paste or insecure alternative
paths. ([C7](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.4.5
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.4
ref_id: V1.4.5
description: Verify that attribute or feature-based access control is used whereby
the code checks the user's authorization for a feature/data item rather than
just their role. Permissions should still be allocated using roles. ([C7](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.5
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
ref_id: V1.5
name: Input and Output Architecture
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.5.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.5
ref_id: V1.5.1
description: Verify that input and output requirements clearly define how to
handle and process data based on type, content, and applicable laws, regulations,
and other policy compliance.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.5.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.5
ref_id: V1.5.2
description: Verify that serialization is not used when communicating with untrusted
clients. If this is not possible, ensure that adequate integrity controls
(and possibly encryption if sensitive data is sent) are enforced to prevent
deserialization attacks including object injection.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.5.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.5
ref_id: V1.5.3
description: Verify that input validation is enforced on a trusted service layer.
([C5](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.5.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.5
ref_id: V1.5.4
description: Verify that output encoding occurs close to or by the interpreter
for which it is intended. ([C4](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.6
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
ref_id: V1.6
name: Cryptographic Architecture
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.6.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.6
ref_id: V1.6.1
description: Verify that there is an explicit policy for management of cryptographic
keys and that a cryptographic key lifecycle follows a key management standard
such as NIST SP 800-57.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.6.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.6
ref_id: V1.6.2
description: Verify that consumers of cryptographic services protect key material
and other secrets by using key vaults or API based alternatives.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.6.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.6
ref_id: V1.6.3
description: Verify that all keys and passwords are replaceable and are part
of a well-defined process to re-encrypt sensitive data.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.6.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.6
ref_id: V1.6.4
description: Verify that the architecture treats client-side secrets--such as
symmetric keys, passwords, or API tokens--as insecure and never uses them
to protect or access sensitive data.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.7
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
ref_id: V1.7
name: Errors, Logging and Auditing Architecture
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.7.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.7
ref_id: V1.7.1
description: Verify that a common logging format and approach is used across
the system. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.7.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.7
ref_id: V1.7.2
description: Verify that logs are securely transmitted to a preferably remote
system for analysis, detection, alerting, and escalation. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.8
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
ref_id: V1.8
name: Data Protection and Privacy Architecture
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.8.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.8
ref_id: V1.8.1
description: Verify that all sensitive data is identified and classified into
protection levels.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.8.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.8
ref_id: V1.8.2
description: Verify that all protection levels have an associated set of protection
requirements, such as encryption requirements, integrity requirements, retention,
privacy and other confidentiality requirements, and that these are applied
in the architecture.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.9
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
ref_id: V1.9
name: Communications Architecture
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.9.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.9
ref_id: V1.9.1
description: Verify the application encrypts communications between components,
particularly when these components are in different containers, systems, sites,
or cloud providers. ([C3](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.9.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.9
ref_id: V1.9.2
description: Verify that application components verify the authenticity of each
side in a communication link to prevent person-in-the-middle attacks. For
example, application components should validate TLS certificates and chains.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.10
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
ref_id: V1.10
name: Malicious Software Architecture
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.10.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.10
ref_id: V1.10.1
description: Verify that a source code control system is in use, with procedures
to ensure that check-ins are accompanied by issues or change tickets. The
source code control system should have access control and identifiable users
to allow traceability of any changes.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.11
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
ref_id: V1.11
name: Business Logic Architecture
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.11.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.11
ref_id: V1.11.1
description: Verify the definition and documentation of all application components
in terms of the business or security functions they provide.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.11.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.11
ref_id: V1.11.2
description: Verify that all high-value business logic flows, including authentication,
session management and access control, do not share unsynchronized state.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.11.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.11
ref_id: V1.11.3
description: Verify that all high-value business logic flows, including authentication,
session management and access control are thread safe and resistant to time-of-check
and time-of-use race conditions.
implementation_groups:
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.12
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
ref_id: V1.12
name: Secure File Upload Architecture
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.12.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.12
ref_id: V1.12.2
description: Verify that user-uploaded files - if required to be displayed or
downloaded from the application - are served by either octet stream downloads,
or from an unrelated domain, such as a cloud file storage bucket. Implement
a suitable Content Security Policy (CSP) to reduce the risk from XSS vectors
or other attacks from the uploaded file.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1
ref_id: V1.14
name: Configuration Architecture
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14
ref_id: V1.14.1
description: Verify the segregation of components of differing trust levels
through well-defined security controls, firewall rules, API gateways, reverse
proxies, cloud-based security groups, or similar mechanisms.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14
ref_id: V1.14.2
description: Verify that binary signatures, trusted connections, and verified
endpoints are used to deploy binaries to remote devices.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14
ref_id: V1.14.3
description: Verify that the build pipeline warns of out-of-date or insecure
components and takes appropriate actions.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14
ref_id: V1.14.4
description: Verify that the build pipeline contains a build step to automatically
build and verify the secure deployment of the application, particularly if
the application infrastructure is software defined, such as cloud environment
build scripts.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14.5
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14
ref_id: V1.14.5
description: Verify that application deployments adequately sandbox, containerize
and/or isolate at the network level to delay and deter attackers from attacking
other applications, especially when they are performing sensitive or dangerous
actions such as deserialization. ([C5](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14.6
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v1.14
ref_id: V1.14.6
description: Verify the application does not use unsupported, insecure, or deprecated
client-side technologies such as NSAPI plugins, Flash, Shockwave, ActiveX,
Silverlight, NACL, or client-side Java applets.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2
assessable: false
depth: 1
ref_id: V2
name: Authentication
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2
ref_id: V2.1
name: Password Security
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
ref_id: V2.1.1
description: Verify that user set passwords are at least 12 characters in length
(after multiple spaces are combined). ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
ref_id: V2.1.2
description: Verify that passwords of at least 64 characters are permitted,
and that passwords of more than 128 characters are denied. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
ref_id: V2.1.3
description: Verify that password truncation is not performed. However, consecutive
multiple spaces may be replaced by a single space. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
ref_id: V2.1.4
description: Verify that any printable Unicode character, including language
neutral characters such as spaces and Emojis are permitted in passwords.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1.5
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
ref_id: V2.1.5
description: Verify users can change their password.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1.6
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
ref_id: V2.1.6
description: Verify that password change functionality requires the user's current
and new password.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1.7
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
ref_id: V2.1.7
description: Verify that passwords submitted during account registration, login,
and password change are checked against a set of breached passwords either
locally (such as the top 1,000 or 10,000 most common passwords which match
the system's password policy) or using an external API. If using an API a
zero knowledge proof or other mechanism should be used to ensure that the
plain text password is not sent or used in verifying the breach status of
the password. If the password is breached, the application must require the
user to set a new non-breached password. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1.8
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
ref_id: V2.1.8
description: Verify that a password strength meter is provided to help users
set a stronger password.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1.9
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
ref_id: V2.1.9
description: Verify that there are no password composition rules limiting the
type of characters permitted. There should be no requirement for upper or
lower case or numbers or special characters. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1.10
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
ref_id: V2.1.10
description: Verify that there are no periodic credential rotation or password
history requirements.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1.11
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
ref_id: V2.1.11
description: Verify that "paste" functionality, browser password helpers, and
external password managers are permitted.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1.12
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.1
ref_id: V2.1.12
description: Verify that the user can choose to either temporarily view the
entire masked password, or temporarily view the last typed character of the
password on platforms that do not have this as built-in functionality.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2
ref_id: V2.2
name: General Authenticator Security
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2
ref_id: V2.2.1
description: Verify that anti-automation controls are effective at mitigating
breached credential testing, brute force, and account lockout attacks. Such
controls include blocking the most common breached passwords, soft lockouts,
rate limiting, CAPTCHA, ever increasing delays between attempts, IP address
restrictions, or risk-based restrictions such as location, first login on
a device, recent attempts to unlock the account, or similar. Verify that no
more than 100 failed attempts per hour is possible on a single account.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2
ref_id: V2.2.2
description: Verify that the use of weak authenticators (such as SMS and email)
is limited to secondary verification and transaction approval and not as a
replacement for more secure authentication methods. Verify that stronger methods
are offered before weak methods, users are aware of the risks, or that proper
measures are in place to limit the risks of account compromise.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2
ref_id: V2.2.3
description: Verify that secure notifications are sent to users after updates
to authentication details, such as credential resets, email or address changes,
logging in from unknown or risky locations. The use of push notifications
- rather than SMS or email - is preferred, but in the absence of push notifications,
SMS or email is acceptable as long as no sensitive information is disclosed
in the notification.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2
ref_id: V2.2.4
description: Verify impersonation resistance against phishing, such as the use
of multi-factor authentication, cryptographic devices with intent (such as
connected keys with a push to authenticate), or at higher AAL levels, client-side
certificates.
implementation_groups:
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2.5
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2
ref_id: V2.2.5
description: Verify that where a Credential Service Provider (CSP) and the application
verifying authentication are separated, mutually authenticated TLS is in place
between the two endpoints.
implementation_groups:
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2.6
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2
ref_id: V2.2.6
description: Verify replay resistance through the mandated use of One-time Passwords
(OTP) devices, cryptographic authenticators, or lookup codes.
implementation_groups:
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2.7
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.2
ref_id: V2.2.7
description: Verify intent to authenticate by requiring the entry of an OTP
token or user-initiated action such as a button press on a FIDO hardware key.
implementation_groups:
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.3
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2
ref_id: V2.3
name: Authenticator Lifecycle
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.3.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.3
ref_id: V2.3.1
description: Verify system generated initial passwords or activation codes SHOULD
be securely randomly generated, SHOULD be at least 6 characters long, and
MAY contain letters and numbers, and expire after a short period of time.
These initial secrets must not be permitted to become the long term password.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.3.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.3
ref_id: V2.3.2
description: Verify that enrollment and use of user-provided authentication
devices are supported, such as a U2F or FIDO tokens.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.3.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.3
ref_id: V2.3.3
description: Verify that renewal instructions are sent with sufficient time
to renew time bound authenticators.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.4
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2
ref_id: V2.4
name: Credential Storage
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.4.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.4
ref_id: V2.4.1
description: Verify that passwords are stored in a form that is resistant to
offline attacks. Passwords SHALL be salted and hashed using an approved one-way
key derivation or password hashing function. Key derivation and password hashing
functions take a password, a salt, and a cost factor as inputs when generating
a password hash. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.4.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.4
ref_id: V2.4.2
description: Verify that the salt is at least 32 bits in length and be chosen
arbitrarily to minimize salt value collisions among stored hashes. For each
credential, a unique salt value and the resulting hash SHALL be stored. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.4.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.4
ref_id: V2.4.3
description: Verify that if PBKDF2 is used, the iteration count SHOULD be as
large as verification server performance will allow, typically at least 100,000
iterations. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.4.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.4
ref_id: V2.4.4
description: Verify that if bcrypt is used, the work factor SHOULD be as large
as verification server performance will allow, with a minimum of 10. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.4.5
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.4
ref_id: V2.4.5
description: Verify that an additional iteration of a key derivation function
is performed, using a salt value that is secret and known only to the verifier.
Generate the salt value using an approved random bit generator [SP 800-90Ar1]
and provide at least the minimum security strength specified in the latest
revision of SP 800-131A. The secret salt value SHALL be stored separately
from the hashed passwords (e.g., in a specialized device like a hardware security
module).
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2
ref_id: V2.5
name: Credential Recovery
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5
ref_id: V2.5.1
description: Verify that a system generated initial activation or recovery secret
is not sent in clear text to the user. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5
ref_id: V2.5.2
description: Verify password hints or knowledge-based authentication (so-called
"secret questions") are not present.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5
ref_id: V2.5.3
description: Verify password credential recovery does not reveal the current
password in any way. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5.4
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5
ref_id: V2.5.4
description: Verify shared or default accounts are not present (e.g. "root",
"admin", or "sa").
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5.5
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5
ref_id: V2.5.5
description: Verify that if an authentication factor is changed or replaced,
that the user is notified of this event.
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5.6
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5
ref_id: V2.5.6
description: Verify forgotten password, and other recovery paths use a secure
recovery mechanism, such as time-based OTP (TOTP) or other soft token, mobile
push, or another offline recovery mechanism. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
implementation_groups:
- L1
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5.7
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.5
ref_id: V2.5.7
description: Verify that if OTP or multi-factor authentication factors are lost,
that evidence of identity proofing is performed at the same level as during
enrollment.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.6
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2
ref_id: V2.6
name: Look-up Secret Verifier
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.6.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.6
ref_id: V2.6.1
description: Verify that lookup secrets can be used only once.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.6.2
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.6
ref_id: V2.6.2
description: Verify that lookup secrets have sufficient randomness (112 bits
of entropy), or if less than 112 bits of entropy, salted with a unique and
random 32-bit salt and hashed with an approved one-way hash.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.6.3
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.6
ref_id: V2.6.3
description: Verify that lookup secrets are resistant to offline attacks, such
as predictable values.
implementation_groups:
- L2
- L3
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.7
assessable: false
depth: 2
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2
ref_id: V2.7
name: Out of Band Verifier
- urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.7.1
assessable: true
depth: 3
parent_urn: urn:intuitem:risk:req_node:owasp-asvs-4.0.3:v2.7
ref_id: V2.7.1
description: Verify that clear text out of band (NIST "restricted") authenticators,