StigData/Archive/Windows.Firewall/U_Windows_Firewall_STIG_V1R6_Manual-xccdf.xml

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
<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type='text/xsl' href='STIG_unclass.xsl'?><Benchmark xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:cpe="http://cpe.mitre.org/language/2.0" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:dc="http://purl.org/dc/elements/1.1/" id="Windows_Firewall" xml:lang="en" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/schema/xccdf-1.1.4.xsd http://cpe.mitre.org/dictionary/2.0 http://cpe.mitre.org/files/cpe-dictionary_2.1.xsd" xmlns="http://checklists.nist.gov/xccdf/1.1"><status date="2017-01-30">accepted</status><title>Windows Firewall with Advanced Security Security Technical Implementation Guide</title><description>The Windows Firewall with Advanced Security Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DoD) information systems. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.
</description><notice id="terms-of-use" xml:lang="en">Developed_by_DISA_for_the_DoD</notice><reference href="http://iase.disa.mil"><dc:publisher>DISA</dc:publisher><dc:source>STIG.DOD.MIL</dc:source></reference><plain-text id="release-info">Release: 6 Benchmark Date: 28 Apr 2017</plain-text><version>1</version><Profile id="MAC-1_Classified"><title>I - Mission Critical Classified</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-1_Public"><title>I - Mission Critical Public</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-1_Sensitive"><title>I - Mission Critical Sensitive</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-2_Classified"><title>II - Mission Support Classified</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-2_Public"><title>II - Mission Support Public</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-2_Sensitive"><title>II - Mission Support Sensitive</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-3_Classified"><title>III - Administrative Classified</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-3_Public"><title>III - Administrative Public</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-3_Sensitive"><title>III - Administrative Sensitive</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Group id="V-17415"><title>Windows Firewall Domain - Enable Firewall</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54833r2_rule" severity="medium" weight="10.0"><version>WNFWA-000001</version><title>The Windows Firewall with Advanced Security must be enabled when connected to a domain.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. This setting enables the firewall when connected to the domain.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63429r3_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Domain Profile Tab -&gt; State, "Firewall state" to "On (recommended)".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set domainprofile state on".
Or
"Netsh advfirewall set allprofiles state on".</fixtext><fix id="F-63429r3_fix" /><check system="C-58965r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, the Domain Profile requirements can be marked NA.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\DomainProfile\
 
Value Name: EnableFirewall
 
Type: REG_DWORD
Value: 0x00000001 (1)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\
 
Value Name: EnableFirewall
 
Type: REG_DWORD
Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17416"><title>Windows Firewall Private - Enable Firewall</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54849r2_rule" severity="medium" weight="10.0"><version>WNFWA-000002</version><title>The Windows Firewall with Advanced Security must be enabled when connected to a private network.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. This setting enables the firewall when connected to a private network.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63481r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Private Profile Tab -&gt; State, "Firewall state" to "On (recommended)".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile state on".
Or
"Netsh advfirewall set allprofiles state on".</fixtext><fix id="F-63481r1_fix" /><check system="C-58991r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PrivateProfile\
 
Value Name: EnableFirewall
 
Type: REG_DWORD
Value: 0x00000001 (1)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\
 
Value Name: EnableFirewall
 
Type: REG_DWORD
Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17417"><title>Windows Firewall Public - Enable Firewall</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54855r2_rule" severity="medium" weight="10.0"><version>WNFWA-000003</version><title>The Windows Firewall with Advanced Security must be enabled when connected to a public network.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. This setting enables the firewall when connected to a public network.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63483r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Public Profile Tab -&gt; State, "Firewall state" to "On (recommended)".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set publicprofile state on".
Or
"Netsh advfirewall set allprofiles state on".</fixtext><fix id="F-63483r1_fix" /><check system="C-58993r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PublicProfile\
 
Value Name: EnableFirewall
 
Type: REG_DWORD
Value: 0x00000001 (1)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile\
 
Value Name: EnableFirewall
 
Type: REG_DWORD
Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17418"><title>Windows Firewall Domain - Inbound</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54859r3_rule" severity="high" weight="10.0"><version>WNFWA-000004</version><title>The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a domain.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unsolicited inbound connections may be malicious attempts to gain access to a system. Unsolicited inbound connections, for which there is no rule allowing the connection, will be blocked in the domain.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63485r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Domain Profile Tab -&gt; State, "Inbound connections" to "Block (default)".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set domainprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.</fixtext><fix id="F-63485r1_fix" /><check system="C-61085r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, the Domain Profile requirements can be marked NA.
 
If the system is a member of a domain and the firewall's Domain Profile is not enabled (see V-17415), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\DomainProfile\
 
Value Name: DefaultInboundAction
 
Type: REG_DWORD
Value: 0x00000001 (1)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\
 
Value Name: DefaultInboundAction
 
Type: REG_DWORD
Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17419"><title>Windows Firewall Domain - Outbound</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54863r3_rule" severity="medium" weight="10.0"><version>WNFWA-000005</version><title>The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a domain.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Outbound connections are allowed in the domain, unless a rule explicitly blocks the connection. This allows normal outbound communication, which could be restricted as necessary with additional rules.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63487r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Domain Profile Tab -&gt; State, "Outbound connections" to "Allow (default)".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set domainprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.</fixtext><fix id="F-63487r1_fix" /><check system="C-61087r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, the Domain Profile requirements can be marked NA.
 
If the system is a member of a domain and the firewall's Domain Profile is not enabled (see V-17415), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\DomainProfile\
 
Value Name: DefaultOutboundAction
 
Type: REG_DWORD
Value: 0x00000000 (0)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\
 
Value Name: DefaultOutboundAction
 
Type: REG_DWORD
Value: 0x00000000 (0)</check-content></check></Rule></Group><Group id="V-17425"><title>Windows Firewall Domain - Log Size</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54874r3_rule" severity="low" weight="10.0"><version>WNFWA-000009</version><title>The Windows Firewall with Advanced Security log size must be configured for domain connections.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The firewall log file size for a domain connection will be set to ensure enough capacity is allocated for audit data.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63495r3_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Domain Profile Tab -&gt; Logging (select Customize), "Size limit (KB):" to "16,384" or greater.
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh command may also be used to configure this setting:
"Netsh advfirewall set domainprofile logging maxfilesize 16384" or greater.</fixtext><fix id="F-63495r3_fix" /><check system="C-61095r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, the Domain Profile requirements can be marked NA.
 
If the system is a member of a domain and the firewall's Domain Profile is not enabled (see V-17415), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\DomainProfile\Logging\
 
Value Name: LogFileSize
 
Type: REG_DWORD
Value: 0x00004000 (16384) (or greater)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\Logging\
 
Value Name: LogFileSize
 
Type: REG_DWORD
Value: 0x00004000 (16384) (or greater)</check-content></check></Rule></Group><Group id="V-17426"><title>Windows Firewall Domain - Log Dropped Packets</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54877r3_rule" severity="low" weight="10.0"><version>WNFWA-000010</version><title>The Windows Firewall with Advanced Security must log dropped packets when connected to a domain.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of dropped packets for a domain connection will be enabled to maintain an audit trail of potential issues.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63497r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Domain Profile Tab -&gt; Logging (select Customize), "Log dropped packets" to "Yes".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set domainprofile logging droppedconnections enable".
Or
"Netsh advfirewall set allprofiles logging droppedconnections enable".</fixtext><fix id="F-63497r1_fix" /><check system="C-61097r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, the Domain Profile requirements can be marked NA.
 
If the system is a member of a domain and the firewall's Domain Profile is not enabled (see V-17415), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\DomainProfile\Logging\
 
Value Name: LogDroppedPackets
 
Type: REG_DWORD
Value: 0x00000001 (1)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\Logging\
 
Value Name: LogDroppedPackets
 
Type: REG_DWORD
Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17427"><title>Windows FW Domain - Log Successful Connections</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54878r3_rule" severity="low" weight="10.0"><version>WNFWA-000011</version><title>The Windows Firewall with Advanced Security must log successful connections when connected to a domain.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of successful connections for a domain connection will be enabled to maintain an audit trail if issues are discovered.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63917r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Domain Profile Tab -&gt; Logging (select Customize), "Log successful connections" to "Yes".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set domainprofile logging allowedconnections enable".
Or
"Netsh advfirewall set allprofiles logging allowedconnections enable".</fixtext><fix id="F-63917r1_fix" /><check system="C-61099r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, the Domain Profile requirements can be marked NA.
 
If the system is a member of a domain and the firewall's Domain Profile is not enabled (see V-17415), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\DomainProfile\Logging\
 
Value Name: LogSuccessfulConnections
 
Type: REG_DWORD
Value: 0x00000001 (1)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\Logging\
 
Value Name: LogSuccessfulConnections
 
Type: REG_DWORD
Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17428"><title>Windows Firewall Private – Inbound</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54879r3_rule" severity="high" weight="10.0"><version>WNFWA-000012</version><title>The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a private network.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unsolicited inbound connections may be malicious attempts to gain access to a system. Unsolicited inbound connections, for which there is no rule allowing the connection, will be blocked on a private network.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63499r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Private Profile Tab -&gt; State, "Inbound connections" to "Block (default)".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.</fixtext><fix id="F-63499r1_fix" /><check system="C-61101r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PrivateProfile\
 
Value Name: DefaultInboundAction
 
Type: REG_DWORD
Value: 0x00000001 (1)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\
 
Value Name: DefaultInboundAction
 
Type: REG_DWORD
Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17429"><title>Windows Firewall Private - Outbound</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54890r3_rule" severity="medium" weight="10.0"><version>WNFWA-000013</version><title>The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a private network.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Outbound connections are allowed on a private network, unless a rule explicitly blocks the connection. This allows normal outbound communication, which could be restricted as necessary with additional rules.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63501r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Private Profile Tab -&gt; State, "Outbound connections" to "Allow (default)".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.</fixtext><fix id="F-63501r1_fix" /><check system="C-61103r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PrivateProfile\
 
Value Name: DefaultOutboundAction
 
Type: REG_DWORD
Value: 0x00000000 (0)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\
 
Value Name: DefaultOutboundAction
 
Type: REG_DWORD
Value: 0x00000000 (0)</check-content></check></Rule></Group><Group id="V-17435"><title>Windows Firewall Private - Log Size</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54903r3_rule" severity="low" weight="10.0"><version>WNFWA-000017</version><title>The Windows Firewall with Advanced Security log size must be configured for private network connections.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The firewall log file size for a private connection will be set to ensure enough capacity is allocated for audit data.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63509r3_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Private Profile Tab -&gt; Logging (select Customize), "Size limit (KB)" to "16,384" or greater.
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh command may also be used to configure this setting:
"Netsh advfirewall set privateprofile logging maxfilesize 16384" or greater.</fixtext><fix id="F-63509r3_fix" /><check system="C-61111r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PrivateProfile\Logging\
 
Value Name: LogFileSize
 
Type: REG_DWORD
Value: 0x00004000 (16384) (or greater)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\Logging\
 
Value Name: LogFileSize
 
Type: REG_DWORD
Value: 0x00004000 (16384) (or greater)</check-content></check></Rule></Group><Group id="V-17436"><title>Windows Firewall Private - Log Dropped Packets</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54904r3_rule" severity="low" weight="10.0"><version>WNFWA-000018</version><title>The Windows Firewall with Advanced Security must log dropped packets when connected to a private network.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of dropped packets for a private network connection will be enabled to maintain an audit trail of potential issues.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63511r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Private Profile Tab -&gt; Logging (select Customize), "Log dropped packets" to "Yes".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile logging droppedconnections enable".
Or
"Netsh advfirewall set allprofiles logging droppedconnections enable".</fixtext><fix id="F-63511r1_fix" /><check system="C-61113r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PrivateProfile\Logging\
 
Value Name: LogDroppedPackets
 
Type: REG_DWORD
Value: 0x00000001 (1)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\Logging\
 
Value Name: LogDroppedPackets
 
Type: REG_DWORD
Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17437"><title>Windows FW Private - Log Successful Connections</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54905r3_rule" severity="low" weight="10.0"><version>WNFWA-000019</version><title>The Windows Firewall with Advanced Security must log successful connections when connected to a private network.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of successful connections for a private network connection will be enabled to maintain an audit trail if issues are discovered.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63513r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Private Profile Tab -&gt; Logging (select Customize), "Logged successful connections" to "Yes".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile logging allowedconnections enable".
Or
"Netsh advfirewall set allprofiles logging allowedconnections enable".</fixtext><fix id="F-63513r1_fix" /><check system="C-61115r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PrivateProfile\Logging\
 
Value Name: LogSuccessfulConnections
 
Type: REG_DWORD
Value: 0x00000001 (1)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\Logging\
 
Value Name: LogSuccessfulConnections
 
Type: REG_DWORD
Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17438"><title>Windows Firewall Public – Inbound </title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54906r3_rule" severity="high" weight="10.0"><version>WNFWA-000020</version><title>The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a public network.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unsolicited inbound connections may be malicious attempts to gain access to a system. Unsolicited inbound connections, for which there is no rule allowing the connection, will be blocked on a public network.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63515r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Public Profile Tab -&gt; State, "Inbound connections" to "Block (default)".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set publicprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.</fixtext><fix id="F-63515r1_fix" /><check system="C-61117r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PublicProfile\
 
Value Name: DefaultInboundAction
 
Type: REG_DWORD
Value: 0x00000001 (1)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile\
 
Value Name: DefaultInboundAction
 
Type: REG_DWORD
Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17439"><title>Windows Firewall Public - Outbound </title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54908r3_rule" severity="medium" weight="10.0"><version>WNFWA-000021</version><title>The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a public network.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Outbound connections are allowed on a public network, unless a rule explicitly blocks the connection. This allows normal outbound communication, which could be restricted as necessary with additional rules.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63517r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Public Profile Tab -&gt; State, "Outbound connections" to "Allow (default)".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set publicprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.</fixtext><fix id="F-63517r1_fix" /><check system="C-61121r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PublicProfile\
 
Value Name: DefaultOutboundAction
 
Type: REG_DWORD
Value: 0x00000000 (0)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile\
 
Value Name: DefaultOutboundAction
 
Type: REG_DWORD
Value: 0x00000000 (0)</check-content></check></Rule></Group><Group id="V-17442"><title>Windows Firewall Public - Local Firewall Rules</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54917r3_rule" severity="medium" weight="10.0"><version>WNFWA-000024</version><title>The Windows Firewall with Advanced Security local firewall rules must not be merged with Group Policy settings when connected to a public network.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Local firewall rules will not be merged with Group Policy settings on a public network to prevent Group Policy settings from being changed.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63523r1_fix">If the system is not a member of a domain, this is NA.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Public Profile Tab -&gt; Settings (select Customize) -&gt; Rule merging, "Apply local firewall rules:" to "No".</fixtext><fix id="F-63523r1_fix" /><check system="C-61129r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, this is NA.
 
If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.
 
Verify the registry value below.
 
If this registry value does not exist or is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PublicProfile\
 
Value Name: AllowLocalPolicyMerge
 
Type: REG_DWORD
Value: 0x00000000 (0)</check-content></check></Rule></Group><Group id="V-17443"><title>Windows Firewall Public - Local Connection Rules</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54918r3_rule" severity="medium" weight="10.0"><version>WNFWA-000025</version><title>The Windows Firewall with Advanced Security local connection rules must not be merged with Group Policy settings when connected to a public network.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Local connection rules will not be merged with Group Policy settings on a public network to prevent Group Policy settings from being changed.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63525r1_fix">If the system is not a member of a domain, this is NA.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Public Profile Tab -&gt; Settings (select Customize) -&gt; Rule merging, "Apply local connection security rules:" to "No".</fixtext><fix id="F-63525r1_fix" /><check system="C-61133r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, this is NA.
 
If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.
 
Verify the registry value below.
 
If this registry value does not exist or is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PublicProfile\
 
Value Name: AllowLocalIPsecPolicyMerge
 
Type: REG_DWORD
Value: 0x00000000 (0)</check-content></check></Rule></Group><Group id="V-17445"><title>Windows Firewall Public - Log Size</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54921r3_rule" severity="low" weight="10.0"><version>WNFWA-000027</version><title>The Windows Firewall with Advanced Security log size must be configured for public network connections.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The firewall log file size for a public network connection will be set to ensure enough capacity is allocated for audit data.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63529r2_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Public Profile Tab -&gt; Logging (select Customize), "Size limit (KB)" to "16,384" or greater.
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh command may also be used to configure this setting:
"Netsh advfirewall set publicprofile logging maxfilesize 16384" or greater.</fixtext><fix id="F-63529r2_fix" /><check system="C-61137r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PublicProfile\Logging\
 
Value Name: LogFileSize
 
Type: REG_DWORD
Value: 0x00004000 (16384) (or greater)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile\Logging\
 
Value Name: LogFileSize
 
Type: REG_DWORD
Value: 0x00004000 (16384) (or greater)</check-content></check></Rule></Group><Group id="V-17446"><title>Windows Firewall Public - Log Dropped Packets</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54922r3_rule" severity="low" weight="10.0"><version>WNFWA-000028</version><title>The Windows Firewall with Advanced Security must log dropped packets when connected to a public network.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of dropped packets for a public network connection will be enabled to maintain an audit trail of potential issues.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63531r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Public Profile Tab -&gt; Logging (select Customize), "Log dropped packets" to "Yes".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set publicprofile logging droppedconnections enable".
Or
"Netsh advfirewall set allprofiles logging droppedconnections enable".</fixtext><fix id="F-63531r1_fix" /><check system="C-61141r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PublicProfile\Logging\
 
Value Name: LogDroppedPackets
 
Type: REG_DWORD
Value: 0x00000001 (1)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile\Logging\
 
Value Name: LogDroppedPackets
 
Type: REG_DWORD
Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17447"><title>Windows FW Public - Log Successful Connections</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-54923r3_rule" severity="low" weight="10.0"><version>WNFWA-000029</version><title>The Windows Firewall with Advanced Security must log successful connections when connected to a public network.</title><description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of successful connections for a public network connection will be enabled to maintain an audit trail if issues are discovered.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63533r1_fix">The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
 
Configure the policy value for Computer Configuration -&gt; Windows Settings -&gt; Security Settings -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall with Advanced Security -&gt; Windows Firewall Properties (this link will be in the right pane) -&gt; Public Profile Tab -&gt; Logging (select Customize), "Logged successful connections" to "Yes".
 
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
 
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set publicprofile logging allowedconnections enable".
Or
"Netsh advfirewall set allprofiles logging allowedconnections enable".</fixtext><fix id="F-63533r1_fix" /><check system="C-61143r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.
 
If the following policy-based registry value exists and is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PublicProfile\Logging\
 
Value Name: LogSuccessfulConnections
 
Type: REG_DWORD
Value: 0x00000001 (1)
 
If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile\Logging\
 
Value Name: LogSuccessfulConnections
 
Type: REG_DWORD
Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-36440"><title>Inbound Firewall Exception for Administration</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-55086r1_rule" severity="medium" weight="10.0"><version>WNFWA-000100</version><title>Inbound exceptions to the firewall on domain workstations must only allow authorized remote management hosts.</title><description>&lt;VulnDiscussion&gt;Allowing inbound access to domain workstations from other systems may allow lateral movement across systems if credentials are compromised. Limiting inbound connections only from authorized remote management systems will help limit this exposure.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><ident system="http://iase.disa.mil/cci">CCI-000366</ident><fixtext fixref="F-47957r2_fix">Ensure firewall exceptions to inbound connections on domain workstations only allow authorized management systems and remote management hosts.
 
Firewall rules can be complex and should be thoroughly tested before applying in a production environment.
 
One method for restricting inbound connections is to only allow exceptions for a specific scope of remote IP addresses. For any inbound rules that allow connections from other systems, configure the Scope for Remote IP addresses to those of authorized management systems and remote management hosts. This may be defined as an IP address, subnet, or range. Apply the rule to all firewall profiles.</fixtext><fix id="F-47957r2_fix" /><check system="C-48768r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>This requirement is NA for servers and non domain workstations.
 
Verify firewall exceptions for inbound connections on domain workstations only allow authorized management systems and remote management hosts.
 
Review inbound firewall exception rules in Windows Firewall with Advanced Security. Firewall rules can be complex and should be reviewed with the firewall administrator.
 
One method for restricting inbound connections is to only allow exceptions for a specific scope of remote IP addresses.
 
If allowed inbound exceptions are not limited to authorized management systems and remote management hosts, this is a finding.</check-content></check></Rule></Group></Benchmark>