From 7128be82aa67354dbedbab7001676d0a5ec10755 Mon Sep 17 00:00:00 2001 From: Adam Haynes Date: Tue, 12 Mar 2019 00:07:07 +0100 Subject: [PATCH] Release Merge release into master --- CHANGELOG.md | 11 +- .../Resources/windows.ProcessMitigation.ps1 | 2 +- .../Resources/windows.Script.skip.ps1 | 2 +- .../Resources/windows.xSslSettings.ps1 | 16 +- .../Resources/windows.xWebConfigProperty.ps1 | 18 +- .../WindowsDnsServer.schema.psm1 | 4 +- DSCResources/helper.psm1 | 5 +- FILEHASH.md | 166 +- Module/Rule.Skip/Skip.psm1 | 8 +- Module/Rule/Rule.psm1 | 11 +- Module/STIG/STIG.psm1 | 4 +- PowerStig.psd1 | 44 +- StigData/Processed/IIS-8-5-Site-1.5.xml | 1508 ----------------- StigData/Processed/IIS-8-5-Site-1.6.xml | 1465 ---------------- StigData/Processed/IISSite-8.5-1.5.xml | 56 +- StigData/Processed/IISSite-8.5-1.6.xml | 58 +- ...dowsDnsServer-2012R2-1.10.org.default.xml} | 0 ...0.xml => WindowsDnsServer-2012R2-1.10.xml} | 0 ...dowsDnsServer-2012R2-1.11.org.default.xml} | 0 ...1.xml => WindowsDnsServer-2012R2-1.11.xml} | 78 +- ...ndowsDnsServer-2012R2-1.9.org.default.xml} | 0 ....9.xml => WindowsDnsServer-2012R2-1.9.xml} | 0 StigData/Schema/PowerStig.xsd | 23 + .../DSCResources/.tests.header.ps1 | 1 + .../DSCResources/Common.integration.ps1 | 207 +-- .../DotNetFramework.integration.tests.ps1 | 57 +- .../DSCResources/Firefox.config.ps1 | 77 +- .../Firefox.integration.tests.ps1 | 18 +- .../DSCResources/IisServer.config.ps1 | 76 +- .../IisServer.integration.tests.ps1 | 26 +- .../DSCResources/IisSite.config.ps1 | 73 +- .../IisSite.integration.tests.ps1 | 33 +- .../DSCResources/InternetExplorer.config.ps1 | 81 +- .../InternetExplorer.integration.tests.ps1 | 18 +- .../DSCResources/Office.config.ps1 | 82 +- .../DSCResources/Office.integration.tests.ps1 | 18 +- .../DSCResources/OracleJRE.config.ps1 | 73 +- .../OracleJRE.integration.tests.ps1 | 26 +- .../DSCResources/SqlServer.config.ps1 | 164 +- .../SqlServer.integration.tests.ps1 | 18 +- .../DSCResources/WindowsClient.config.ps1 | 75 +- .../WindowsClient.integration.tests.ps1 | 27 +- .../DSCResources/WindowsDnsServer.config.ps1 | 75 +- .../WindowsDnsServer.integration.tests.ps1 | 26 +- .../DSCResources/WindowsFirewall.config.ps1 | 79 +- .../WindowsFirewall.integration.tests.ps1 | 19 +- .../DSCResources/WindowsServer.config.ps1 | 77 +- .../WindowsServer.integration.tests.ps1 | 41 +- Tests/Integration/DSCResources/helper.psm1 | 48 +- appveyor.yml | 2 +- 50 files changed, 700 insertions(+), 4296 deletions(-) delete mode 100644 StigData/Processed/IIS-8-5-Site-1.5.xml delete mode 100644 StigData/Processed/IIS-8-5-Site-1.6.xml rename StigData/Processed/{WindowsServer-2012R2-DNS-1.10.org.default.xml => WindowsDnsServer-2012R2-1.10.org.default.xml} (100%) rename StigData/Processed/{WindowsServer-2012R2-DNS-1.10.xml => WindowsDnsServer-2012R2-1.10.xml} (100%) rename StigData/Processed/{WindowsServer-2012R2-DNS-1.11.org.default.xml => WindowsDnsServer-2012R2-1.11.org.default.xml} (100%) rename StigData/Processed/{WindowsServer-2012R2-DNS-1.11.xml => WindowsDnsServer-2012R2-1.11.xml} (99%) rename StigData/Processed/{WindowsServer-2012R2-DNS-1.9.org.default.xml => WindowsDnsServer-2012R2-1.9.org.default.xml} (100%) rename StigData/Processed/{WindowsServer-2012R2-DNS-1.9.xml => WindowsDnsServer-2012R2-1.9.xml} (100%) diff --git a/CHANGELOG.md b/CHANGELOG.md index fb2b2e57d..4dd94a472 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,8 +1,15 @@ # Versions -## 3.0.0 +## Unreleased + +## 3.0.1 + +UPDATES + +* Fixed [#350](https://github.com/Microsoft/PowerStig/issues/350): Updates to fix Skip rules not working correctly +* Fixed [#348](https://github.com/Microsoft/PowerStig/issues/348): Update to DnsServer Schema to correct typo. -NEW +## 3.0.0 * Introduces class support for each rule type * The STIG class now contains an array of rule objects vs xml elements diff --git a/DSCResources/Resources/windows.ProcessMitigation.ps1 b/DSCResources/Resources/windows.ProcessMitigation.ps1 index bfc6b8f21..f7020e484 100644 --- a/DSCResources/Resources/windows.ProcessMitigation.ps1 +++ b/DSCResources/Resources/windows.ProcessMitigation.ps1 @@ -6,7 +6,7 @@ $mitigationTargets = $rules.MitigationTarget | Select-Object -Unique foreach ($target in $mitigationTargets) { - $targetrules = $rules | where {$_.MitigationTarget -eq "$target"} + $targetrules = $rules | Where-Object {$_.MitigationTarget -eq "$target"} $enableValue = @() $disableValue = @() $idValue = @() diff --git a/DSCResources/Resources/windows.Script.skip.ps1 b/DSCResources/Resources/windows.Script.skip.ps1 index 75a51f2e0..2ed58a3f5 100644 --- a/DSCResources/Resources/windows.Script.skip.ps1 +++ b/DSCResources/Resources/windows.Script.skip.ps1 @@ -1,7 +1,7 @@ # Copyright (c) Microsoft Corporation. All rights reserved. # Licensed under the MIT License. -$rules = $stig.RuleList | Select-Rule -Type SkipRule +$rules = $stig.RuleList | Select-Rule -Type SkippedRule foreach ( $rule in $rules ) { diff --git a/DSCResources/Resources/windows.xSslSettings.ps1 b/DSCResources/Resources/windows.xSslSettings.ps1 index 594892389..15ad0565f 100644 --- a/DSCResources/Resources/windows.xSslSettings.ps1 +++ b/DSCResources/Resources/windows.xSslSettings.ps1 @@ -1,16 +1,16 @@ # Copyright (c) Microsoft Corporation. All rights reserved. # Licensed under the MIT License. -# Header + $rules = $stig.RuleList | Select-Rule -Type SslSettingsRule -foreach ($website in $WebsiteName) +if ($rules) { - $value = Get-UniqueStringArray -InputObject $rules.Value -AsString - [array] $value = $value.Split(',') -replace "'",'' - - xSslSettings "$(Get-ResourceTitle -Rule $rule -Instance $website)" + foreach ($website in $WebsiteName) { - Name = "IIS:\Sites\$website" - Bindings = $value + xSslSettings "[$($rules.id -join ' ')]$website" + { + Name = "IIS:\Sites\$website" + Bindings = (Get-UniqueStringArray -InputObject $rules.Value) + } } } diff --git a/DSCResources/Resources/windows.xWebConfigProperty.ps1 b/DSCResources/Resources/windows.xWebConfigProperty.ps1 index 44690cb89..9c27551a3 100644 --- a/DSCResources/Resources/windows.xWebConfigProperty.ps1 +++ b/DSCResources/Resources/windows.xWebConfigProperty.ps1 @@ -1,6 +1,6 @@ # Copyright (c) Microsoft Corporation. All rights reserved. # Licensed under the MIT License. -#region Header + $rules = $stig.RuleList | Select-Rule -Type WebConfigurationPropertyRule if ($WebsiteName) @@ -11,10 +11,10 @@ if ($WebsiteName) { xWebConfigProperty "$(Get-ResourceTitle -Rule $rule -Instance $website)" { - WebsitePath = "IIS:\Sites\$website" - Filter = $rule.ConfigSection - PropertyName = $rule.Key - Value = $rule.Value + WebsitePath = "IIS:\Sites\$website" + Filter = $rule.ConfigSection + PropertyName = $rule.Key + Value = $rule.Value } } } @@ -34,10 +34,10 @@ else xWebConfigProperty "$(Get-ResourceTitle -Rule $rule)" { - WebsitePath = $psPath - Filter = $rule.ConfigSection - PropertyName = $rule.Key - Value = $rule.Value + WebsitePath = $psPath + Filter = $rule.ConfigSection + PropertyName = $rule.Key + Value = $rule.Value } } } diff --git a/DSCResources/WindowsDnsServer/WindowsDnsServer.schema.psm1 b/DSCResources/WindowsDnsServer/WindowsDnsServer.schema.psm1 index ced890495..31df09482 100644 --- a/DSCResources/WindowsDnsServer/WindowsDnsServer.schema.psm1 +++ b/DSCResources/WindowsDnsServer/WindowsDnsServer.schema.psm1 @@ -58,7 +58,7 @@ Configuration WindowsDnsServer [Parameter()] [ValidateNotNullOrEmpty()] - [sashtable] + [hashtable] $Exception, [Parameter()] @@ -78,7 +78,7 @@ Configuration WindowsDnsServer ) ##### BEGIN DO NOT MODIFY ##### - $stig = [STIG]::New('WindowsServer', $OsVersion, 'Dns' , $StigVersion) + $stig = [STIG]::New('WindowsDnsServer', $OsVersion, $StigVersion) $stig.LoadRules($OrgSettings, $Exception, $SkipRule, $SkipRuleType) # $resourcePath is exported from the helper module in the header diff --git a/DSCResources/helper.psm1 b/DSCResources/helper.psm1 index b6bfc2528..424c7e9b4 100644 --- a/DSCResources/helper.psm1 +++ b/DSCResources/helper.psm1 @@ -61,7 +61,10 @@ function Select-Rule process { - return $RuleList.Where( {$_.GetType().ToString() -eq $Type}) + return $RuleList.Where({ + $_.GetType().ToString() -eq $Type -and + [string]::IsNullOrEmpty($_.DuplicateOf) + }) } } diff --git a/FILEHASH.md b/FILEHASH.md index d3a2e2eec..c7188e2ef 100644 --- a/FILEHASH.md +++ b/FILEHASH.md @@ -1,88 +1,108 @@ -# PowerSTIG File Hashes : Module Version 2.4.0.0 +# PowerSTIG File Hashes : Module Version 3.0.1 Hashes for **PowerSTIG** files are listed in the following table: | File | SHA256 Hash | Size (bytes) | | :---- | ---- | ---: | -| Mozilla-All-FireFox-4.23.org.default.xml | D8E45DC6E83499FF22CA90D417CD477A0DF4450F091117E766A57418BABA2CED | 302 | -| Mozilla-All-FireFox-4.23.xml | A71E114C43CCD9C173EB0FBF3C3011971E11B99860826FB110027F2CE6D97C80 | 21652 | -| Mozilla-All-FireFox-4.24.org.default.xml | 6BFB0DC668F689F81FD1D05A2F4EDCC1552FD37A765301AA6367F208108DC9D7 | 306 | -| Mozilla-All-FireFox-4.24.xml | 44FB05D6F6FA5ED4CC986C333882C72F81E1BD9F19E8722D21215809CCA815A1 | 20730 | +| ActiveDirectory-All-Domain-2.10.org.default.xml | C3335957BAB1A9F23E1495DAC49BCFF3F690F7EAD020EB456B8BEB375E9B5615 | 302 | +| ActiveDirectory-All-Domain-2.10.xml | D05147ED1FBC13B6933BE5049BA7FC0C249B13389FC00B37432003AB329EF5D2 | 37878 | +| ActiveDirectory-All-Domain-2.11.org.default.xml | 395459A673BC80006E2F4B03E8FE84E89C36AAAF729B7A476623D3C4C8E3D7E3 | 302 | +| ActiveDirectory-All-Domain-2.11.xml | F90FFC7C5AD02FB25F3FBFC258929635212AE8AB0E62D519250BED3CF2786835 | 38337 | +| ActiveDirectory-All-Domain-2.12.org.default.xml | 973C2D3FC456F6979ACCC147CF772E3020EADFFC24070191517E2F703084CD30 | 306 | +| ActiveDirectory-All-Domain-2.12.xml | 9AB03AB34705C64064A3061ABD24465ED0A46E1ADC7F2D94D63784DB62542B5D | 38562 | +| ActiveDirectory-All-Forest-2.7.org.default.xml | 4C807A55F82C206FACFB7031F2F8989EF2C50845E913C4A598E3F6277B61B5E2 | 304 | +| ActiveDirectory-All-Forest-2.7.xml | 7306BBFC38778E0CE1A514F06DBE61333113A536F7142DD5CB811F5F18B733CA | 7649 | +| ActiveDirectory-All-Forest-2.8.org.default.xml | 4F9515E446D0ACF2A545820C8A16973BD5B888D4F8E979AF0B941E16931BB8F9 | 301 | +| ActiveDirectory-All-Forest-2.8.xml | F8513063D964F3795A6CF3FE4AD0194792E79B6A16CECE90DA4F269B7D2FCC43 | 8200 | +| DotNetFramework-4-1.4.org.default.xml | FABD84CFEB2BC0659B72A8836F744EDA3F30CCC9DEB414380A16E98D82AC9F3D | 301 | +| DotNetFramework-4-1.4.xml | 8A55BFE40DC9044FA28B4BC02F1166BC46819C2EADD38FCBAF05C0E6BCAD8FED | 22005 | +| DotNetFramework-4-1.6.org.default.xml | AA83FB9224208C2546DD1DBE1555972A96A8BA4B916ECA6F0DF4BECBBD2E3FD8 | 301 | +| DotNetFramework-4-1.6.xml | D07EB054E3C084D23939F6503A167BCB10C050197A5582074F969F561CEF9422 | 23167 | +| FireFox-All-4.21.org.default.xml | BC4E093A07E77444F03866016AA3F8D62F1D460DCB499DEBC618618C34BA78FF | 302 | +| FireFox-All-4.21.xml | 5D1F1CAE9F056D8429B12EB7AE8C64277C3EE8D50480319F2BCF2822B8D91D2A | 22599 | +| FireFox-All-4.23.org.default.xml | D8E45DC6E83499FF22CA90D417CD477A0DF4450F091117E766A57418BABA2CED | 302 | +| FireFox-All-4.23.xml | A71E114C43CCD9C173EB0FBF3C3011971E11B99860826FB110027F2CE6D97C80 | 21652 | +| FireFox-All-4.24.org.default.xml | 6BFB0DC668F689F81FD1D05A2F4EDCC1552FD37A765301AA6367F208108DC9D7 | 306 | +| FireFox-All-4.24.xml | 44FB05D6F6FA5ED4CC986C333882C72F81E1BD9F19E8722D21215809CCA815A1 | 20730 | +| IIS-8-5-Site-1.5.xml | 497EC6A01815FE092AA7D643FE0D633454B9F34F71E11434FD31C7BC43E17400 | 130351 | +| IIS-8-5-Site-1.6.xml | 30F22CA38344568226C3AB4AF55B77B3EDFCDA74D8784D64ABFE00D9F5C1EFA3 | 130652 | +| IISServer-8.5-1.5.org.default.xml | 510653F2D005187518FBD5F8D5E7E9E0A6C02BDE4C23D52C9575389BA43C8C6A | 438 | +| IISServer-8.5-1.5.xml | 6904AB497EC7E3B32BCDF213EFB9B1D8E4BF7B796CF14FB619FEF2BD589C5E34 | 112981 | +| IISServer-8.5-1.6.org.default.xml | 9572C936FEBDF4F630E2A2A17CCB6CFCDFABEA3DCD92C9BEAC979F137A42D7F1 | 438 | +| IISServer-8.5-1.6.xml | B078F30133F8BC97E647392B0346363A809FCC19CB8D622EAEFE44C2C01ACB90 | 114711 | +| IISSite-8.5-1.5.org.default.xml | 2FA88EF0A08A668A8A9F6FC37B3A6671101A0C7CA62BB00309D525CEEA34EC06 | 1067 | +| IISSite-8.5-1.5.xml | 9C8551DBD54CB48E015352C410B45A3C8D7B3EDD020E8EFD3AA233E777760D7C | 130344 | +| IISSite-8.5-1.6.org.default.xml | D72DA4DAA07C93D7ED2C957C0DB3C33B3D5E04E5A92424AA4EA2F1537CFFE62D | 1067 | +| IISSite-8.5-1.6.xml | 52656F4B5FC417AFCED0801563EB088ED170FE8B1A02195FE3CA838E61031815 | 130643 | +| InternetExplorer-11-1.15.org.default.xml | D00EE7C7D3D06AA18A803F0F9AD985FD0B87D5B4CCFDB5975C2E34403860CA8D | 306 | +| InternetExplorer-11-1.15.xml | 594447C10312F9CC66708DC80C9A45479BD87E0B667F82584D771D6603D1EC71 | 332787 | +| InternetExplorer-11-1.16.org.default.xml | BDC028F6D224DD78E77CB81658BDF4A63C17C7095B1637A25701834A22344694 | 306 | +| InternetExplorer-11-1.16.xml | A08FF78951C46567C1D0BE99DC4A5E5A81FB8348C033981300A421FEB1854EDF | 332828 | +| Office-Excel2013-1.7.org.default.xml | E263E5B184D2DE284E8E96CB333EF11EC8E92F49869DB072BCFD83FCD3662265 | 430 | +| Office-Excel2013-1.7.xml | 53B1485542CE27DCA6ADC12C5BD5420A58D6B0A999EFC07492E0D11A7B04AE29 | 51672 | +| Office-Outlook2013-1.12.org.default.xml | 369D5DE682FD78D37466EC2B36D43D844A76959829B81129C5033306602D4FD1 | 430 | +| Office-Outlook2013-1.12.xml | 3B8CB23E585C659B47A3EEE4B75B8DF94998CD8D95F96C7868485E4CA7E38872 | 88658 | +| Office-Outlook2013-1.13.org.default.xml | 14AC0A5769C8D7E3478E14065F301C74335A221CE21D1EAB99BFF687BE79A418 | 449 | +| Office-Outlook2013-1.13.xml | 98B85178E26523B05C192939739E0D704FDE5EE73B9F851FB02003522859C7A1 | 88540 | +| Office-PowerPoint2013-1.6.org.default.xml | AA83FB9224208C2546DD1DBE1555972A96A8BA4B916ECA6F0DF4BECBBD2E3FD8 | 301 | +| Office-PowerPoint2013-1.6.xml | CAFF4CCE68F80F9D61B6E33D0ACE487ADE8DC4A84472B00416BC479E10105612 | 44520 | +| Office-Word2013-1.6.org.default.xml | AA83FB9224208C2546DD1DBE1555972A96A8BA4B916ECA6F0DF4BECBBD2E3FD8 | 301 | +| Office-Word2013-1.6.xml | D784B8111CA2DE947FFFB47D88E263237B026332433EDB6AAD8227247C07AFFF | 38530 | +| OracleJRE-8-1.5.org.default.xml | 05F665F8005E85FFA8568580F32472709F922FC06175AAAFFCED26EAC857FDA2 | 301 | +| OracleJRE-8-1.5.xml | 0B6D4C2DCB9522BE5EA8C4213474FDE70B1F59076C2E56D6A7195D39EAFE7BF1 | 15237 | | SqlServer-2012-Database-1.17.org.default.xml | 57AA572AF80DE95D4BC5B8B9079AED3CA6BE63718B726D4FFEF631F017D23D9E | 305 | | SqlServer-2012-Database-1.17.xml | 7260BFEDE8FC3947B1A36F8A4AE1AA8CC4AF160D4C67CF7223C159CA5C2A5E99 | 37718 | | SqlServer-2012-Database-1.18.org.default.xml | 1095CEEAD18CBBAD9068326B97D520F7F76F1F71331618F17B2138DC8FE55ED4 | 306 | | SqlServer-2012-Database-1.18.xml | 18391A6F6314DCD36AE992319699A2AC16890E11A9B62944B44DE1C3DF9D5E79 | 38236 | +| SqlServer-2012-Instance-1.15.org.default.xml | 4BDA2DC398D1CDFD8FD8C58A1ADF47AC7F072FC4CAD082B4168B6D801BB1EDF2 | 302 | +| SqlServer-2012-Instance-1.15.xml | 095F93906426561A3ADAD9C9F3A39341809D091AE4764B21370866758D1EE5E7 | 355728 | | SqlServer-2012-Instance-1.16.org.default.xml | 0603777B3C8A380A7CC47766FF7A995E22F7988FCA56AA8EAB202CBE89C090CB | 302 | | SqlServer-2012-Instance-1.16.xml | 0B058581795678751D94D0C1E33290C8525318B7B32C7C07979F72D9D578C6EA | 355822 | | SqlServer-2012-Instance-1.17.org.default.xml | E7C6F909F78CA3BD5B77E417FBBDABBB1F5125A9D95939623AD720B7DA281BBB | 302 | | SqlServer-2012-Instance-1.17.xml | E8A66131927FA1879672FAC1BB4E2811F1393E1F50B4C5B7159A2C092AED6185 | 358721 | | SqlServer-2016-Instance-1.3.org.default.xml | 5C992B2F864BBA7A975A9F4FEC3535309BD2EC6CE10D6BD159C127B4AA4E24FE | 301 | | SqlServer-2016-Instance-1.3.xml | D8BB9463E4ADC6C19DC40BD1F10A4E844A728605EA231DAC8617A47795BB8844 | 177660 | -| Windows-10-Client-1.15.org.default.xml | 85EE6D3F64483A1D77B1270839202A5EDDEF77A6B9462A9386E21806B6CD42B4 | 3237 | -| Windows-10-Client-1.15.xml | BCF14643941EE133CAAF5A92C232F1E13B5E50B195810BA7746DAC41FF95A392 | 564883 | -| Windows-10-Client-1.16.org.default.xml | FF2BB1BD364C1AC9AC5F51BC4AA1A48648C5F9C2B3C1B690A28E1280D59B7D7C | 3240 | -| Windows-10-Client-1.16.xml | B671F8D497AEA16CC60DE09E7EF00324362092773010ECA85260D9EE0C1109C9 | 311595 | -| Windows-2012R2-DC-2.14.org.default.xml | FC2D849C9645CDEDDB8810DBA7167C5CC3C396FA3B29B365CE5994AF60801396 | 3915 | -| Windows-2012R2-DC-2.14.xml | 2D84F5A7F4A641FCAB30C44C6276EF15CB4D98D20E656BEF9C8859AB33E62205 | 417362 | -| Windows-2012R2-DC-2.15.org.default.xml | 8CB79727392F0E0A26C61EC43E010702F8F8B2838F9AAC162FBDFD18EF7555ED | 3959 | -| Windows-2012R2-DC-2.15.xml | AAD3535A2F3F85C01397EB0286C5B75E3F0315DFB92DC0797E7EE4D05B6882D0 | 418611 | -| Windows-2012R2-DNS-1.10.org.default.xml | D7B3A3B7FCF8F0DBD5E70FFEA0E54B770C0E2CF228B6F13FCB692D14A6D6E013 | 302 | -| Windows-2012R2-DNS-1.10.xml | B406CBF518FD7A704223F28EA3CCBC65918E78F548543B1FE4B8E3ABD9FA3A43 | 126089 | -| Windows-2012R2-DNS-1.11.org.default.xml | 74831D43FD2564947D69D7EF8EECCC5F192FCA17DED3BA463341EDD20ED3BA58 | 306 | -| Windows-2012R2-DNS-1.11.xml | 90C222999667B5FC1C861DBDA7A2BB300ED088027596C2906C14252251CF3093 | 126954 | -| Windows-2012R2-IISServer-1.5.org.default.xml | 61F54F59B315DDD3EF5AD689B6AEC4F20BE3A83A4CE5DF70D33BCF9C9A0F1933 | 434 | -| Windows-2012R2-IISServer-1.5.xml | 5DEC43CFE778A66EDE61BBEED906E60327C427F2E19607A466834E1F67D876B2 | 110033 | -| Windows-2012R2-IISServer-1.6.org.default.xml | E1B3202DAA7135486885705F2C8C5648A13E8BF5BB7D9C23DA61790A81D9050B | 434 | -| Windows-2012R2-IISServer-1.6.xml | 39E9ABD73A6A5998910DCA01C73CC49BEB0AA64CC9F4A985FDE290A16E748B4A | 111756 | -| Windows-2012R2-IISSite-1.2.org.default.xml | E864D16D047B9586C8B2F82AA8746BBDE14442CC9AF10FFC17D4866A925320C4 | 1184 | -| Windows-2012R2-IISSite-1.2.xml | E0867A97182E13959815590793DF2F27994B361E54EBACDDE75BB1A7521A0C1E | 61196 | -| Windows-2012R2-IISSite-1.5.org.default.xml | 614DB2B38B949C78C0F56E0785BC1004516D19259F7BA3925E4622F833234B5A | 1083 | -| Windows-2012R2-IISSite-1.5.xml | 268BCDDBB3F3996752713ADE2B6CE2D5665BB8CACC037797D0BB93A04ADFDEBA | 56252 | -| Windows-2012R2-MS-2.13.org.default.xml | 8203C6EA1C481656CA08C3CC3008780E9ECF6079D2938ECD0347A1CFCE9A4A16 | 3639 | -| Windows-2012R2-MS-2.13.xml | 0D028C7C40AEC102BBEB88A26C284216E69FE6054962B6D28E48C50203EE2EEC | 356243 | -| Windows-2012R2-MS-2.14.org.default.xml | E8C8B34E88EBDE53A15B2567010E5328759CBD28981C43F115544A5A83657CA5 | 3199 | -| Windows-2012R2-MS-2.14.xml | 764E9C41761E19BC94CCD2090B3CF4CC5D85E21EEEEC4C6A99611C26C30F0E95 | 355961 | -| Windows-2016-DC-1.6.org.default.xml | CDD8F03A1520B07D6B0ECB1835BC2629D768EE48A36D86F550020922220AB9EC | 3999 | -| Windows-2016-DC-1.6.xml | 7AC75FE3589B1078EA16684B1746A659E597990B51BAE8A1CD30965E23B10F3B | 542588 | -| Windows-2016-DC-1.7.org.default.xml | 06BD9988D96E95B24DED9D6F4FBABD2ED617461C903E078810E2899128A9C777 | 3812 | -| Windows-2016-DC-1.7.xml | 572DB4E88B89B3DC2F540825CA20AD3AE6A7C6D476B059783805415E48A133F1 | 542459 | -| Windows-2016-MS-1.6.org.default.xml | CC13EBD7A4F8B89DBC4BD91BA52817B59692399EAD2B3F0F166FFEBD08C6477D | 3956 | -| Windows-2016-MS-1.6.xml | 41C957C38E4A87C5BE70399C0D39F7BACE3FDA51865FA379B6BC67081413E6AC | 474892 | -| Windows-2016-MS-1.7.org.default.xml | 94D88702D4D1A41278F39E21C3E322D15A5AE5861F74F5A82B5CE69E8515B4E2 | 3767 | -| Windows-2016-MS-1.7.xml | A80D853F02EE3223C1B34FD9C075E9889A701212F3ACCAC32AE904143F824F00 | 474763 | -| Windows-All-ADDomain-2.10.org.default.xml | C3335957BAB1A9F23E1495DAC49BCFF3F690F7EAD020EB456B8BEB375E9B5615 | 302 | -| Windows-All-ADDomain-2.10.xml | D05147ED1FBC13B6933BE5049BA7FC0C249B13389FC00B37432003AB329EF5D2 | 37878 | -| Windows-All-ADDomain-2.9.org.default.xml | 16A0AD798E655678FF4340ABEE31BE6BCC6A4C680E65263491E2E73D76183281 | 304 | -| Windows-All-ADDomain-2.9.xml | 5E90ADD91336A93CCF8F0467AC8F6220013E78D32E3815E09C423E2E3AEB118C | 42174 | -| Windows-All-ADForest-2.7.org.default.xml | 4C807A55F82C206FACFB7031F2F8989EF2C50845E913C4A598E3F6277B61B5E2 | 304 | -| Windows-All-ADForest-2.7.xml | 7306BBFC38778E0CE1A514F06DBE61333113A536F7142DD5CB811F5F18B733CA | 7649 | -| Windows-All-ADForest-2.8.org.default.xml | 4F9515E446D0ACF2A545820C8A16973BD5B888D4F8E979AF0B941E16931BB8F9 | 301 | -| Windows-All-ADForest-2.8.xml | F8513063D964F3795A6CF3FE4AD0194792E79B6A16CECE90DA4F269B7D2FCC43 | 8200 | -| Windows-All-Domain-2.11.org.default.xml | 395459A673BC80006E2F4B03E8FE84E89C36AAAF729B7A476623D3C4C8E3D7E3 | 302 | -| Windows-All-Domain-2.11.xml | F90FFC7C5AD02FB25F3FBFC258929635212AE8AB0E62D519250BED3CF2786835 | 38337 | -| Windows-All-Domain-2.12.org.default.xml | 973C2D3FC456F6979ACCC147CF772E3020EADFFC24070191517E2F703084CD30 | 306 | -| Windows-All-Domain-2.12.xml | 9AB03AB34705C64064A3061ABD24465ED0A46E1ADC7F2D94D63784DB62542B5D | 38562 | -| Windows-All-DotNet4-1.4.org.default.xml | FABD84CFEB2BC0659B72A8836F744EDA3F30CCC9DEB414380A16E98D82AC9F3D | 301 | -| Windows-All-DotNet4-1.4.xml | 8A55BFE40DC9044FA28B4BC02F1166BC46819C2EADD38FCBAF05C0E6BCAD8FED | 22005 | -| Windows-All-DotNet4-1.6.org.default.xml | AA83FB9224208C2546DD1DBE1555972A96A8BA4B916ECA6F0DF4BECBBD2E3FD8 | 301 | -| Windows-All-DotNet4-1.6.xml | D07EB054E3C084D23939F6503A167BCB10C050197A5582074F969F561CEF9422 | 23167 | -| Windows-All-Excel2013-1.7.org.default.xml | E263E5B184D2DE284E8E96CB333EF11EC8E92F49869DB072BCFD83FCD3662265 | 430 | -| Windows-All-Excel2013-1.7.xml | 53B1485542CE27DCA6ADC12C5BD5420A58D6B0A999EFC07492E0D11A7B04AE29 | 51672 | -| Windows-All-FW-1.6.org.default.xml | 38EE83A72D4A36D022853EAB9052CC129759C32692FBFC31E39A42FE2CCFA267 | 979 | -| Windows-All-FW-1.6.xml | A9D4568FE2C91C71442442DCCF661BE63469E2A5E44203F85261255446713600 | 32506 | -| Windows-All-IE11-1.15.org.default.xml | 4BDA2DC398D1CDFD8FD8C58A1ADF47AC7F072FC4CAD082B4168B6D801BB1EDF2 | 302 | -| Windows-All-IE11-1.15.xml | 7F1EA8A198B9D8A32FACBFBAB9E165A5DDD8780B06FD135AAB9BCDCC0DF3D581 | 157289 | -| Windows-All-IE11-1.16.org.default.xml | 0603777B3C8A380A7CC47766FF7A995E22F7988FCA56AA8EAB202CBE89C090CB | 302 | -| Windows-All-IE11-1.16.xml | A532935FDAB976A95AA8814C718F15CF201763BD84415F882574C9ADE31A2C5C | 157330 | -| Windows-All-OracleJRE8-1.5.org.default.xml | 05F665F8005E85FFA8568580F32472709F922FC06175AAAFFCED26EAC857FDA2 | 301 | -| Windows-All-OracleJRE8-1.5.xml | 0B6D4C2DCB9522BE5EA8C4213474FDE70B1F59076C2E56D6A7195D39EAFE7BF1 | 15237 | -| Windows-All-Outlook2013-1.12.org.default.xml | 369D5DE682FD78D37466EC2B36D43D844A76959829B81129C5033306602D4FD1 | 430 | -| Windows-All-Outlook2013-1.12.xml | 3B8CB23E585C659B47A3EEE4B75B8DF94998CD8D95F96C7868485E4CA7E38872 | 88658 | -| Windows-All-Outlook2013-1.13.org.default.xml | 14AC0A5769C8D7E3478E14065F301C74335A221CE21D1EAB99BFF687BE79A418 | 449 | -| Windows-All-Outlook2013-1.13.xml | 98B85178E26523B05C192939739E0D704FDE5EE73B9F851FB02003522859C7A1 | 88540 | -| Windows-All-PowerPoint2013-1.6.org.default.xml | AA83FB9224208C2546DD1DBE1555972A96A8BA4B916ECA6F0DF4BECBBD2E3FD8 | 301 | -| Windows-All-PowerPoint2013-1.6.xml | CAFF4CCE68F80F9D61B6E33D0ACE487ADE8DC4A84472B00416BC479E10105612 | 44520 | -| Windows-All-Word2013-1.6.org.default.xml | AA83FB9224208C2546DD1DBE1555972A96A8BA4B916ECA6F0DF4BECBBD2E3FD8 | 301 | -| Windows-All-Word2013-1.6.xml | D784B8111CA2DE947FFFB47D88E263237B026332433EDB6AAD8227247C07AFFF | 38530 | -| Windows-Defender-Antivirus-1.4.org.default.xml | 7B29E729DBAD5D0AA20904664916575A5E7A7444EFD630C3A49704AAF4A9C926 | 1037 | -| Windows-Defender-Antivirus-1.4.xml | 6E36B8909B13CA21DE33D92ACC8A9053CEA165E33A26FECDA230C5040D87DBE2 | 49928 | +| WindowsClient-10-1.14.org.default.xml | EBA18D2A351823A884D3F7EAEE16D4565352E4EC510C19AA96C069C363C459EB | 3213 | +| WindowsClient-10-1.14.xml | C32A26EA83F797E2847A45567C38AA2D49B8C6F55AF56878B25E0F871115CC3C | 316709 | +| WindowsClient-10-1.15.org.default.xml | 85EE6D3F64483A1D77B1270839202A5EDDEF77A6B9462A9386E21806B6CD42B4 | 3237 | +| WindowsClient-10-1.15.xml | FAB314BE6E3C97D65BA536872803DBD0D2D8D9EACE58DE910ADFAB7FC965A992 | 318370 | +| WindowsClient-10-1.16.org.default.xml | FF2BB1BD364C1AC9AC5F51BC4AA1A48648C5F9C2B3C1B690A28E1280D59B7D7C | 3240 | +| WindowsClient-10-1.16.xml | B62E548A78F7F929689173F02FAC6D2FC5B3EE6468CB84710BD006E5949F45A7 | 318355 | +| WindowsDefender-All-1.4.org.default.xml | 7B29E729DBAD5D0AA20904664916575A5E7A7444EFD630C3A49704AAF4A9C926 | 1037 | +| WindowsDefender-All-1.4.xml | 6E36B8909B13CA21DE33D92ACC8A9053CEA165E33A26FECDA230C5040D87DBE2 | 49928 | +| WindowsDnsServer-2012R2-1.10.org.default.xml | D7B3A3B7FCF8F0DBD5E70FFEA0E54B770C0E2CF228B6F13FCB692D14A6D6E013 | 302 | +| WindowsDnsServer-2012R2-1.10.xml | B406CBF518FD7A704223F28EA3CCBC65918E78F548543B1FE4B8E3ABD9FA3A43 | 126089 | +| WindowsDnsServer-2012R2-1.11.org.default.xml | 74831D43FD2564947D69D7EF8EECCC5F192FCA17DED3BA463341EDD20ED3BA58 | 306 | +| WindowsDnsServer-2012R2-1.11.xml | 1543DB28DF255232AFC5B60CB0909DA6A3EDC3A91CE6636084A428C1C8E1A627 | 126914 | +| WindowsDnsServer-2012R2-1.9.org.default.xml | FB7B3CBC2E0F47EADD3F183B77916805F21AF049FC8019EE21ED389F52955704 | 304 | +| WindowsDnsServer-2012R2-1.9.xml | C1B02518966248A701AD40090E1C3C64CE3F1BD55C7C6E4633DFB32DB398DF7D | 125398 | +| WindowsFirewall-All-1.6.org.default.xml | 38EE83A72D4A36D022853EAB9052CC129759C32692FBFC31E39A42FE2CCFA267 | 979 | +| WindowsFirewall-All-1.6.xml | A9D4568FE2C91C71442442DCCF661BE63469E2A5E44203F85261255446713600 | 32506 | +| WindowsFirewall-All-1.7.org.default.xml | 3EC920564BE2746EE9C1D35484CCCBD24BAB3F6B53CB10861DE865EB3D427D42 | 942 | +| WindowsFirewall-All-1.7.xml | B4E3C584E01317DADA6B6E0DBA64F9849F338EA776D6722E041A0F30351F3A24 | 65570 | +| WindowsServer-2012R2-DC-2.13.org.default.xml | B47692D5F4C5F09E19320583A0E3093F7D4B794585C4153887E52F764C111524 | 4138 | +| WindowsServer-2012R2-DC-2.13.xml | 22560AEC50E50E9BBA4A75C4E96994075B9731D987576518EF5267892399E06D | 417821 | +| WindowsServer-2012R2-DC-2.14.org.default.xml | FC2D849C9645CDEDDB8810DBA7167C5CC3C396FA3B29B365CE5994AF60801396 | 3915 | +| WindowsServer-2012R2-DC-2.14.xml | 2D84F5A7F4A641FCAB30C44C6276EF15CB4D98D20E656BEF9C8859AB33E62205 | 417362 | +| WindowsServer-2012R2-DC-2.15.org.default.xml | 8CB79727392F0E0A26C61EC43E010702F8F8B2838F9AAC162FBDFD18EF7555ED | 3959 | +| WindowsServer-2012R2-DC-2.15.xml | AAD3535A2F3F85C01397EB0286C5B75E3F0315DFB92DC0797E7EE4D05B6882D0 | 418611 | +| WindowsServer-2012R2-DNS-1.10.org.default.xml | D7B3A3B7FCF8F0DBD5E70FFEA0E54B770C0E2CF228B6F13FCB692D14A6D6E013 | 302 | +| WindowsServer-2012R2-DNS-1.10.xml | B406CBF518FD7A704223F28EA3CCBC65918E78F548543B1FE4B8E3ABD9FA3A43 | 126089 | +| WindowsServer-2012R2-DNS-1.11.org.default.xml | 74831D43FD2564947D69D7EF8EECCC5F192FCA17DED3BA463341EDD20ED3BA58 | 306 | +| WindowsServer-2012R2-DNS-1.11.xml | 1543DB28DF255232AFC5B60CB0909DA6A3EDC3A91CE6636084A428C1C8E1A627 | 126914 | +| WindowsServer-2012R2-DNS-1.9.org.default.xml | FB7B3CBC2E0F47EADD3F183B77916805F21AF049FC8019EE21ED389F52955704 | 304 | +| WindowsServer-2012R2-DNS-1.9.xml | C1B02518966248A701AD40090E1C3C64CE3F1BD55C7C6E4633DFB32DB398DF7D | 125398 | +| WindowsServer-2012R2-MS-2.12.org.default.xml | 285DDD496F43BD98F85CE9C11D0EEF573C6E0AEA306B872C03149A8F5751A7E3 | 3425 | +| WindowsServer-2012R2-MS-2.12.xml | C5DFF98F679BAD3C0D466CB51CF47FF0B487754291ACC00C2C99822272870A80 | 351991 | +| WindowsServer-2012R2-MS-2.13.org.default.xml | 8203C6EA1C481656CA08C3CC3008780E9ECF6079D2938ECD0347A1CFCE9A4A16 | 3639 | +| WindowsServer-2012R2-MS-2.13.xml | 0D028C7C40AEC102BBEB88A26C284216E69FE6054962B6D28E48C50203EE2EEC | 356243 | +| WindowsServer-2012R2-MS-2.14.org.default.xml | E8C8B34E88EBDE53A15B2567010E5328759CBD28981C43F115544A5A83657CA5 | 3199 | +| WindowsServer-2012R2-MS-2.14.xml | 764E9C41761E19BC94CCD2090B3CF4CC5D85E21EEEEC4C6A99611C26C30F0E95 | 355961 | +| WindowsServer-2016-DC-1.6.org.default.xml | CDD8F03A1520B07D6B0ECB1835BC2629D768EE48A36D86F550020922220AB9EC | 3999 | +| WindowsServer-2016-DC-1.6.xml | 0B4A3855E978BF8FCDD948E405FFEAB0424021DF2340BF570CC9CEC029747D2A | 573755 | +| WindowsServer-2016-DC-1.7.org.default.xml | 06BD9988D96E95B24DED9D6F4FBABD2ED617461C903E078810E2899128A9C777 | 3812 | +| WindowsServer-2016-DC-1.7.xml | CDA5DA66BF8DDD62616E23953BC3A74F7BC31D63FD0884FB551ACF72B67B52FE | 573603 | +| WindowsServer-2016-MS-1.6.org.default.xml | CC13EBD7A4F8B89DBC4BD91BA52817B59692399EAD2B3F0F166FFEBD08C6477D | 3956 | +| WindowsServer-2016-MS-1.6.xml | 613AF9EC5D0DA78F2366AF924EC21B1C4938FE42768DDCD823AEC6BD9C3B6B95 | 481201 | +| WindowsServer-2016-MS-1.7.org.default.xml | 94D88702D4D1A41278F39E21C3E322D15A5AE5861F74F5A82B5CE69E8515B4E2 | 3767 | +| WindowsServer-2016-MS-1.7.xml | A80D853F02EE3223C1B34FD9C075E9889A701212F3ACCAC32AE904143F824F00 | 474763 | diff --git a/Module/Rule.Skip/Skip.psm1 b/Module/Rule.Skip/Skip.psm1 index 3e97fcb9d..a0a21f980 100644 --- a/Module/Rule.Skip/Skip.psm1 +++ b/Module/Rule.Skip/Skip.psm1 @@ -39,12 +39,12 @@ Class SkippedRule : Rule .DESCRIPTION A constructor for SkippedRule. Returns a ready to use instance of SkippedRule. - .PARAMETER StigRuleId - The Id of an individual Stig Rule + .PARAMETER Rule + The Stig Rule #> - SkippedRule ([string] $Id) + SkippedRule ([xml.xmlelement] $Rule) : Base ($Rule) { - $this.Id = $Id + $this.UpdateRuleTitle('Skip') } #endregion diff --git a/Module/Rule/Rule.psm1 b/Module/Rule/Rule.psm1 index de08d92de..56bf3b803 100644 --- a/Module/Rule/Rule.psm1 +++ b/Module/Rule/Rule.psm1 @@ -172,10 +172,19 @@ Class Rule : ICloneable #> [void] AddExceptionToPolicy ([string] $Value) { - $this.Title = "[Exception] " + $this.title + $this.UpdateRuleTitle('Exception') $this.($this.GetOverrideValue()) = $Value } + <# + .SYNOPSIS + Applies a uniform title update format + #> + [void] UpdateRuleTitle ([string] $Value) + { + $this.Title = "[$Value] " + $this.Title + } + <# .SYNOPSIS Creates a shallow copy of the current object diff --git a/Module/STIG/STIG.psm1 b/Module/STIG/STIG.psm1 index 66ccbe80c..db79167b2 100644 --- a/Module/STIG/STIG.psm1 +++ b/Module/STIG/STIG.psm1 @@ -220,9 +220,9 @@ Class STIG { foreach ($rule in $type.Rule) { - if ( @($SkipRules) -contains $rule.Id -or $type.Name -eq $SkipRuleType ) + if (@($SkipRules) -contains $rule.Id -or @($SkipRuleType) -contains $type.Name) { - $importRule = [SkippedRule]::new($rule.Id) + $importRule = [SkippedRule]::new($rule) } else { diff --git a/PowerStig.psd1 b/PowerStig.psd1 index 01a404145..001f3e05f 100644 --- a/PowerStig.psd1 +++ b/PowerStig.psd1 @@ -6,7 +6,7 @@ RootModule = 'PowerStig.psm1' # Version number of this module. -ModuleVersion = '3.0.0' +ModuleVersion = '3.0.1' # ID used to uniquely identify this module GUID = 'a132f6a5-8f96-4942-be25-b213ee7e4af3' @@ -96,44 +96,10 @@ PrivateData = @{ ProjectUri = 'https://github.com/Microsoft/PowerStig' # ReleaseNotes of this module - ReleaseNotes = 'NEW - - * Introduces class support for each rule type - * The STIG class now contains an array of rule objects vs xml elements - * Orgsettings, Exceptions, and Rule skips are all supported by the Rule base class - * Rule help is provided for any loaded rule. - * See the [wiki](https://github.com/Microsoft/PowerStig/wiki/GettingRuleHelp) for more information. - * Major code refactor to simplify maintenance and usage - * [Breaking Change] The STIG class constructor no longer accepts Orgsettings, Exceptions, or Rule skips - * That functionality has move to the load rule method - * DSC composite resource parameter validation for version numbers has been removed - * The STIG class validates all input and will throw an error if invalid data is provided. - * The Get-StigList has be updated and renamed to Get-Stig to return the STIG class - - UPDATES - - * Fixed [#241](https://github.com/Microsoft/PowerStig/issues/241): [WindowsFeatureRule] PsDesiredStateConfiguration\WindowsOptionalFeature doesn''t properly handle features that return $null - * Fixed [#258](https://github.com/Microsoft/PowerStig/issues/258): New-StigChecklist will not accept a path without an explicit filename - * Fixed [#243](https://github.com/Microsoft/PowerStig/issues/243): [V-46515] Windows-All-IE11-1.15 Rawstring typo - * Fixed [#289](https://github.com/Microsoft/PowerStig/issues/289): Updated DocumentRule and DocumentRuleConvert Classes to parse correctly. - * Fixed [#284](https://github.com/Microsoft/PowerStig/issues/284): [V-74415] [V-74413] Windows 10 STIG rule V-74415 and V-74413 should not contain white space in key - * Fixed [290](https://github.com/Microsoft/PowerStig/issues/290): [V-76731] IIS Server STIG V-76731 fails to properly set STIG guidance because rule is not split. - * Fixed [314](https://github.com/Microsoft/PowerStig/issues/314): Update PowerSTIG to Utilize LogTargetW3C parameter in xWebAdministration 2.5.0.0. - * Fixed [334](https://github.com/Microsoft/PowerStig/issues/334): Update PowerStig to utilize AccessControlDsc 1.3.0.0 - * Fixed [331](https://github.com/Microsoft/PowerStig/issues/331): 2012/R2 [V-39325] 2016 [V-73373], [V-73389] PermissionRule.Convert CheckContent Match Parser Update - * Fixed [320](https://github.com/Microsoft/PowerStig/issues/320): IIS Site STIG doesn''t correctly convert STIGS that contain "SSL Settings" in raw string - - * Added the following STIGs - * IIS Site 8.5 V1R6 [#276](https://github.com/Microsoft/PowerStig/issues/276) - * Windows Firewall STIG V1R7 [#319](https://github.com/Microsoft/PowerStig/issues/319) - - * Removed the following STIGs - * Windows Server 2012 R2 DC 2.12 - * Windows Server 2012 R2 DSN 1.7 - * Active Directory Domain 2.9 - * IIS Server 8.5 1.3 - * IIS Site 8.5 1.2 - * Removed: Internet Explorer 1.13' + ReleaseNotes = 'UPDATES + +* Fixed [#350](https://github.com/Microsoft/PowerStig/issues/350): Updates to fix Skip rules not working correctly +* Fixed [#348](https://github.com/Microsoft/PowerStig/issues/348): Update to DnsServer Schema to correct typo.' } # End of PSData hashtable } # End of PrivateData hashtable } diff --git a/StigData/Processed/IIS-8-5-Site-1.5.xml b/StigData/Processed/IIS-8-5-Site-1.5.xml deleted file mode 100644 index cc02d93a0..000000000 --- a/StigData/Processed/IIS-8-5-Site-1.5.xml +++ /dev/null @@ -1,1508 +0,0 @@ - - - - <VulnDiscussion>IIS 8.5 will either allow or deny script execution based on file extension. The ability to control script execution is controlled through two features with IIS 8.5, Request Filtering and "Handler Mappings". - -For "Handler Mappings", the ISSO must document and approve all allowable file extensions the website allows (white list) and denies (black list) by the website. The white list and black list will be compared to the "Handler Mappings" in IIS 8. "Handler Mappings" at the site level take precedence over "Handler Mappings" at the server level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - For "Handler Mappings", the ISSO must document and approve all allowable scripts the website allows (white list) and denies (black list) by the website. The white list and black list will be compared to the "Handler Mappings" in IIS 8.5. "Handler Mappings" at the site level take precedence over "Handler Mappings" at the server level. - -Open the IIS 8.5 Manager. - -Click the site name under review. - -Double-click "Handler Mappings". - -If any script file extensions from the black list are enabled, this is a finding. - - - <VulnDiscussion>Resource mapping is the process of tying a particular file type to a process in the web server that can serve that type of file to a requesting client and to identify which file types are not to be delivered to a client. - -By not specifying which files can and which files cannot be served to a user, the web server could deliver to a user web server configuration files, log files, password files, etc. - -The web server must only allow hosted application file types to be served to a user and all other types must be disabled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - For "Handler Mappings", the ISSO must document and approve all allowable file extensions the website allows (white list) and denies (black list) by the website. The white list and black list will be compared to the "Handler Mappings" in IIS 8.5. "Handler Mappings" at the site level take precedence over "Handler Mappings" at the server level. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Double-click "Request Filtering". - -If any file name extensions from the black list have "Allowed" set to "True", this is a finding. - - - <VulnDiscussion>By setting limits on web requests, it ensures availability of web services and mitigates the risk of buffer overflow type attacks. The maxAllowedContentLength Request Filter limits the number of bytes the server will accept in a request.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click on the site name. - -Double-click the "Request Filtering" icon. - -Click “Edit Feature Settings” in the "Actions" pane. - -If the "maxAllowedContentLength" value is not explicitly set to "30000000" or less or a length documented and approved by the ISSO, this is a finding. - - - - <VulnDiscussion>The goal is to control the web users experience in navigating any portion of the web document root directories. Ensuring all web content directories have at least the equivalent of an index.html file is a significant factor to accomplish this end. Also, enumeration techniques, such as URL parameter manipulation, rely upon being able to obtain information about the web server’s directory structure by locating directories with default pages. This practice helps ensure the anonymous web user will not obtain directory browsing information or an error message revealing the server type and version.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: This requirement is only for each site's root directory. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Click the site name under review. - -Double-click "Default Document". - -In the "Actions" pane, verify the "Default Document" feature is enabled. - -If an "Enable" option is listed under the "Actions" pane, the "Default Document" feature is not enabled and this is a finding. - -If "Default Document" is "Enabled, review the document types. - -Click the "Content View" tab, click on each listed "Default Document" and click on "Explore" under the "Actions" pane. Verify there is a document of that type in the directory. - -If "Default Document" is "Enabled" but no listed document types are present in the "Content View", this is a finding. - - - <VulnDiscussion>During an attack on the web server or any of the hosted applications, the system administrator may need to disconnect or disable access by users to stop the attack. - -The web server must provide a capability to disconnect users to a hosted application without compromising other hosted applications unless deemed necessary to stop the attack. Methods to disconnect or disable connections are to stop the application service for a specified hosted application, stop the web server, or block all connections through web server access list. - -The web server capabilities used to disconnect or disable users from connecting to hosted applications and the web server must be documented to make certain that, during an attack, the proper action is taken to conserve connectivity to any other hosted application if possible and to make certain log data is conserved for later forensic analysis.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Interview the System Administrator and Web Manager. - -Ask for documentation for the IIS 8.5 web server administration. - -Verify there are documented procedures for shutting down an IIS 8.5 website in the event of an attack. The procedure should, at a minimum, provide the following steps: - -Determine the respective website for the application at risk of an attack. - -Access the IIS 8.5 web server IIS 8.5 Manager. - -Select the respective website. - -In the "Actions" pane, under "Manage Website", click on "Stop". - -If necessary, stop all websites. - -If necessary, stop the IIS 8.5 web server by selecting the web server in the IIS 8.5 Manager. - -In the "Actions" pane, under "Manage Server", click on "Stop". - -If there are not documented procedures with, at a minimum, the mentioned steps for stopping a website, this is a finding. - - - <VulnDiscussion>In order to make certain that the logging mechanism used by the web server has sufficient storage capacity in which to write the logs, the logging mechanism needs to be able to allocate log record storage capacity. - -The task of allocating log record storage capacity is usually performed during initial installation of the logging mechanism. The system administrator will usually coordinate the allocation of physical drive space with the web server administrator along with the physical location of the partition and disk. Refer to NIST SP 800-92 for specific requirements on log rotation and storage dependent on the impact of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Access the IIS 8.5 web server IIS 8.5 Manager. - -Under "IIS" double-click on the "Logging" icon. - -In the "Logging" configuration box, determine the "Directory:" to which the "W3C" logging is being written. - -Confirm with the System Administrator that the designated log path is of sufficient size to maintain the logging. - -Under "Log File Rollover", verify the "Do not create new log files" is not selected. - -Verify a schedule is configured to rollover log files on a regular basis. - -Consult with the System Administrator to determine if there is a documented process for moving the log files off of the IIS 8.5 web server to another logging device. - -If the designated logging path device is not of sufficient space to maintain all log files and there is not a schedule to rollover files on a regular basis, this is a finding. - - - <VulnDiscussion>Web servers provide numerous processes, features, and functionalities that utilize TCP/IP ports. Some of these processes may be deemed unnecessary or too unsecure to run on a production system. - -The web server must provide the capability to disable or deactivate network-related services that are deemed to be non-essential to the server mission, are too unsecure, or are prohibited by the PPSM CAL and vulnerability assessments. - -Failure to comply with DoD ports, protocols, and services (PPS) requirements can result in compromise of enclave boundary protections and/or functionality of the AIS. - -The ISSM will ensure web servers are configured to use only authorized PPS in accordance with the Network Infrastructure STIG, DoD Instruction 8551.1, Ports, Protocols, and Services Management (PPSM), and the associated Ports, Protocols, and Services (PPS) Assurance Category Assignments List.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Review the website to determine if HTTP and HTTPs (e.g., 80 and 443) are used in accordance with those ports and services registered and approved for use by the DoD PPSM. Any variation in PPS will be documented, registered, and approved by the PPSM. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name under review. - -In the “Action” Pane, click “Bindings”. - -Review the ports and protocols. If unknown ports or protocols are used, then this is a finding. - - - <VulnDiscussion>IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: Recycling Application Pools can create an unstable environment in a 64-bit SharePoint environment. If operational issues arise, with supporting documentation from the ISSO, this check can be downgraded to a Cat III. - -Open the IIS 8.5 Manager. - -Perform for each Application Pool. - -Click the “Application Pools”. - -Highlight an Application Pool and click "Advanced Settings" in the “Action” Pane. - -Scroll down to the "Recycling section" and verify the value for "Request Limit" is set to a value other than "0". - -If the "Request Limit" is set to a value of "0", this is a finding. - - - <VulnDiscussion>IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: Recycling Application Pools can create an unstable environment in a 64-bit SharePoint environment. If operational issues arise, mitigation steps can be set, to include setting the “Fixed number or requests”, “Specific time”, and “Private memory usage” in the recycling conditions lieu of the “Virtual memory” setting. If mitigation is used in lieu of this requirement, with supporting documentation from the ISSO, this check can be downgraded to a Cat III. - -Open the IIS 8.5 Manager. - -Perform for each Application Pool. - -Click on “Application Pools”. - -Highlight an Application Pool and click "Advanced Settings" in the Action Pane. - -In the "Advanced Settings" dialog box scroll down to the "Recycling" section and verify the value for "Virtual Memory Limit" is not set to 0. - -If the value for "Virtual Memory Limit" is set to 0, this is a finding. - - - - <VulnDiscussion>IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: Recycling Application Pools can create an unstable environment in a 64-bit SharePoint environment. If operational issues arise, with supporting documentation from the ISSO this check can be downgraded to a Cat III. - -Open the IIS 8.5 Manager. - -Perform for each Application Pool. - -Click the “Application Pools”. - -Highlight an Application Pool and click "Advanced Settings" in the “Action” Pane. - -Scroll down to the "Recycling" section and verify the value for "Private Memory Limit" is set to a value other than "0". - -If the "Private Memory Limit" is set to a value of "0", this is a finding. - - - <VulnDiscussion>Application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: Recycling Application Pools can create an unstable environment in a 64-bit SharePoint environment. If operational issues arise, with supporting documentation from the ISSO this check can be downgraded to a Cat III. - -Open the IIS 8.5 Manager. - -Perform for each Application Pool. - -Click the “Application Pools”. - -Highlight an Application Pool and click "Advanced Settings" in the “Action” Pane. - -Scroll down to the "Recycling" section and expand the "Generate Recycle Event Log Entry" section. - -Verify both the "Regular time interval" and "Specific time" options are set to "True". - -If both the "Regular time interval" and "Specific time" options are not set to "True", this is a finding. - - - - - <VulnDiscussion>Log files are a critical component to the successful management of an IS used within the DoD. By generating log files with useful information web administrators can leverage them in the event of a disaster, malicious attack, or other site-specific needs. - -Ascertaining the correct order of the events that occurred is important during forensic analysis. Events that appear harmless by themselves might be flagged as a potential threat when properly viewed in sequence. By also establishing the event date and time, an event can be properly viewed with an enterprise tool to fully see a possible threat in its entirety. - -Without sufficient information establishing when the log event occurred, investigation into the cause of event is severely hindered. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked. - -Satisfies: SRG-APP-000092-WSR-000055, SRG-APP-000093-WSR-000053</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - - Date,Time,ClientIP,UserName,Method,UriQuery,ProtocolVersion,Referer - - - - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Click the "Logging" icon. - -Under Format select "W3C". - -Click “Select Fields”, verify at a minimum the following fields are checked: Date, Time, Client IP Address, User Name, Method, URI Query, Protocol Status, and Referrer. - -If the "W3C" is not selected as the logging format OR any of the required fields are not selected, this is a finding. - - - <VulnDiscussion>Internet Information Services (IIS) on Windows Server 2012 provides basic logging capabilities. However, because IIS takes some time to flush logs to disk, administrators do not have access to logging information in real-time. In addition, text-based log files can be difficult and time-consuming to process. - -In IIS 8.5, the administrator has the option of sending logging information to Event Tracing for Windows (ETW). This option gives the administrator the ability to use standard query tools, or create custom tools, for viewing real-time logging information in ETW. This provides a significant advantage over parsing text-based log files that are not updated in real time. - -Satisfies: SRG-APP-000092-WSR-000055, SRG-APP-000108-WSR-000166</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - - - - - File,ETW - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Click the "Logging" icon. - -Under Log Event Destination, verify the "Both log file and ETW event" radio button is selected. - -If the "Both log file and ETW event" radio button is not selected, this is a finding. - - - <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. - -Ascertaining the success or failure of an event is important during forensic analysis. Correctly determining the outcome will add information to the overall reconstruction of the logable event. By determining the success or failure of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the event occurred in other areas within the enterprise. - -Without sufficient information establishing the success or failure of the logged event, investigation into the cause of event is severely hindered. The success or failure also provides a means to measure the impact of an event and help authorized personnel to determine the appropriate response. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - - - RequestHeader - Connection - - - RequestHeader - Warning - - - ServerVariable - HTTP_CONNECTION - - - - W3C - - - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Select the website being reviewed. - -Under "IIS", double-click the "Logging" icon. - -Verify the "Format:" under "Log File" is configured to "W3C". - -Select the "Fields" button. - -Under "Custom Fields", verify the following fields are selected: - -Request Header >> Connection - -Request Header >> Warning - -Server Variable >> HTTP_CONNECTION - -If any of the above fields are not selected, this is a finding. - - - <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. - -Determining user accounts, processes running on behalf of the user, and running process identifiers also enable a better understanding of the overall event. User tool identification is also helpful to determine if events are related to overall user access or specific client tools. - -Log record content that may be necessary to satisfy the requirement of this control includes: time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - - - ServerVariable - HTTP_USER_AGENT - - - RequestHeader - User-Agent - - - RequestHeader - Authorization - - - ResponseHeader - Content-Type - - - UserAgent,UserName,Referer - W3C - - - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Access the IIS 8.5 web server IIS 8.5 Manager. - -Under "IIS", double-click the "Logging" icon. - -Verify the "Format:" under "Log File" is configured to "W3C". - -Select the "Fields" button. - -Under "Standard Fields", verify "User Agent", "User Name" and "Referrer" are selected. - -Under "Custom Fields", verify the following fields have been configured: - -Server Variable >> HTTP_USER_AGENT - -Request Header >> User-Agent - -Request Header >> Authorization - -Response Header >> Content-Type - -If any of the above fields are not selected, this is a finding. - - - - - <VulnDiscussion>Resource exhaustion can occur when an unlimited number of concurrent requests are allowed on a website, facilitating a Denial of Service attack. Mitigating this kind of attack will include limiting the number of concurrent HTTP/HTTPS requests per IP address and may include, where feasible, limiting parameter values associated with keepalive (i.e., a parameter used to limit the amount of time a connection may be inactive).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Access the IIS 8.5 IIS Manager. - -Click the IIS 8.5 server. - -Select "Configuration Editor" under the "Management" section. - -From the "Section:" drop-down list at the top of the configuration editor, locate "system.applicationHost/sites". - -Expand "siteDefaults". -Expand "limits". - -Review the results and verify the value is greater than zero for the "maxconnections" parameter. - -If the maxconnections parameter is set to zero, this is a finding. - - - <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. - -Ascertaining the correct source, e.g. source IP, of the events is important during forensic analysis. Correctly determining the source of events will add information to the overall reconstruction of the logable event. By determining the source of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the source occurred in other areas within the enterprise. - -A web server behind a load balancer or proxy server, when not configured correctly, will record the load balancer or proxy server as the source of every logable event. When looking at the information forensically, this information is not helpful in the investigation of events. The web server must record with each event the client source of the event.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Interview the System Administrator to review the configuration of the IIS 8.5 architecture and determine if inbound web traffic is passed through a proxy. - -If the IIS 8.5 is receiving inbound web traffic through a proxy, the audit logs must be reviewed to determine if correct source information is being passed through by the proxy server. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Click the "Logging" icon. - -Click on "View log file" button. - -When log file is displaced, review source IP information in log entries and verify entries do not reflect the IP address of the proxy server. - -If the log entries in the log file(s) reflect the IP address of the proxy server as the source, this is a finding. -If the website is not behind a load balancer or proxy server, this is Not Applicable. - - - <VulnDiscussion>A major tool in exploring the website use, attempted use, unusual conditions, and problems are the access and error logs. In the event of a security incident, these logs can provide the SA and the web manager with valuable information. Failure to protect log files could enable an attacker to modify the log file data or falsify events to mask an attacker's activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Click the "Logging" icon. - -Click "Browse" and navigate to the directory where the log files are stored. - -Right-click the log file name to review and click “Properties”. - -Click the “Security” tab; verify only authorized groups are listed, if others are listed, this is a finding. - -Note: The log file should be restricted as follows: - -SYSTEM, Auditors group: Full -SA, web managers: Read - - - - - <VulnDiscussion>The web server must be configured to listen on a specified IP address and port. Without specifying an IP address and port for the web server to utilize, the web server will listen on all IP addresses available to the hosting server. If the web server has multiple IP addresses, i.e., a management IP address, the web server will also accept connections on the management IP address. - -Accessing the hosted application through an IP address normally used for non-application functions opens the possibility of user access to resources, utilities, files, ports, and protocols that are protected on the desired application IP address.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Right-click on the site name under review. - -Select “Edit Bindings”. - -Verify there are hostname entries and unique IP addresses assigned to port 80 for HTTP and port 443 for HTTPS. - -If both hostname entries and unique IP addresses are not configure to port 80 for HTTP and port 443 for HTTPS, this is a finding. - - - <VulnDiscussion>Many of the security problems that occur are not the result of a user gaining access to files or data for which the user does not have permissions, but rather users are assigned incorrect permissions to unauthorized data. The files, directories, and data that are stored on the web server need to be evaluated and a determination made concerning authorized access to information and programs on the server. Only authorized users and administrative accounts will be allowed on the host server in order to maintain the web server, applications, and review the server operations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Check the account used for anonymous access to the website. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. - -Double-click "Authentication" in the IIS section of the website’s Home Pane. - -If Anonymous access is disabled, this is Not a Finding. - -If Anonymous access is enabled, click “Anonymous Authentication”. - -Click “Edit” in the "Actions" pane. - -If the “Specific user” radio button is enabled and an ID is specified in the adjacent control box, this is the ID being used for anonymous access. Note: account name. - -Check privileged groups that may allow the anonymous account inappropriate membership: -Open “Server Manager” on the machine. - -Expand Configuration. - -Expand Local Users and Groups. - -Click “Groups”. - -Review members of any of the following privileged groups: - -Administrators -Backup Operators -Certificate Services (of any designation) -Distributed COM Users -Event Log Readers -Network Configuration Operators -Performance Log Users -Performance Monitor Users -Power Users -Print Operators -Remote Desktop Users -Replicator -Users - -Double-click each group and review its members. - -If the IUSR account or any account noted above used for anonymous access is a member of any group with privileged access, this is a finding. - - - <VulnDiscussion>The web document (home) directory is accessed by multiple anonymous users when the web server is in production. By locating the web document (home) directory on the same partition as the web server system file the risk for unauthorized access to these protected files is increased. Additionally, having the web document (home) directory path on the same drive as the system folders also increases the potential for a drive space exhaustion attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name under review. - -Click the "Advanced Settings" from the "Actions" pane. - -Review the Physical Path. - -If the Path is on the same partition as the OS, this is a finding. - - - <VulnDiscussion>The use of a DoD PKI certificate ensures clients the private website they are connecting to is legitimate, and is an essential part of the DoD defense-in-depth strategy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name under review. - -Click “Bindings” in the “Action” Pane. - -Click the “HTTPS type” from the box. - -Click “Edit”. - -Click “View” and then review and verify the certificate path. - -If the list of CAs in the trust hierarchy does not lead to the DoD PKI Root CA, DoD-approved external certificate authority (ECA), or DoD-approved external partner, this is a finding. - -If HTTPS is not an available type under site bindings, this is a finding. - - - <VulnDiscussion>Application pools isolate sites and applications to address reliability, availability, and security issues. Sites and applications may be grouped according to configurations, although each site will be associated with a unique application pool.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Open the IIS 8.5 Manager. - -Click "Application Pools". - -In the list of Application Pools, review the "Applications" column and verify unique application pools for each website. - -If any Application Pools are being used for more than one website, this is a finding. - - - - <VulnDiscussion>CGI and ASP scripts represent one of the most common and exploitable means of compromising a web server. All CGI and ASP program files must be segregated into their own unique folder to simplify the protection of these files. ASP scripts must be placed into a unique folder only containing other ASP scripts. JAVA and other technology-specific scripts must also be placed into their own unique folders. The placement of CGI, ASP, or equivalent scripts to special folders gives the Web Manager or the SA control over what goes into those folders and to facilitate access control at the folder level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Determine whether scripts are used on the web server for the target website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. - -All interactive programs must be placed in unique designated folders based on CGI or ASP script type. - -Open the IIS 8.5 Manager. - -Right-click the IIS 8.5 web site name and select Explore. - -Search for the listed script extensions. Each script type must be in its unique designated folder. - -If scripts are not segregated from web content and in their own unique folders, then this is a finding. - - - <VulnDiscussion>CGI is a programming standard for interfacing external applications with information servers, such as HTTP or web servers. CGI, represented by all upper case letters, should not be confused with the .cgi file extension. The .cgi file extension does represent a CGI script, but CGI scripts may be written in a number of programming languages (e.g., PERL, C, PHP, and JavaScript), each having their own unique file extension. - -The use of CGI scripts represent one of the most common and exploitable means of compromising a web server. By definition, CGI scripts are executable by the operating system of the host server. While access control is provided via the web service, the execution of CGI programs is not limited unless the SA or the Web Manager takes specific measures. CGI programs can access and alter data files, launch other programs, and use the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Determine whether scripts are used on the web server for the subject website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. - -If the website does not utilize CGI, this finding is Not Applicable. - -All interactive programs must have restrictive permissions. - -Open the IIS 8.5 Manager. - -Right-click the IIS 8.5 web site name and select “Explore”. - -Search for the listed script extensions. - -Review the permissions to the CGI scripts and verify only the permissions listed, or more restrictive permissions are assigned. - -Administrators: FULL -TrustedInstaller: FULL -ALL APPLICATION PACKAGES: Read -SYSTEM: FULL -ApplicationPoolId: READ -Custom Service Account: READ -Users: READ - -If the permissions are less restrictive than listed above, this is a finding. - - - <VulnDiscussion>Copies of backup files will not execute on the server, but they can be read by the anonymous user if special precautions are not taken. Such backup copies contain the same sensitive information as the actual script being executed and, as such, are useful to malicious users. Techniques and systems exist today to search web servers for such files and are able to exploit the information contained in them.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Determine whether scripts are used on the web server for the subject website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. - -If the website does not utilize CGI, this finding is Not Applicable. - -Open the IIS 8.5 Manager. - -Right-click the IIS 8.5 web site name and select “Explore”. - -Search for the listed script extensions - -Search for the following files: *.bak, *.old, *.temp, *.tmp, *.backup, or “copy of...”. - -If files with these extensions are found, this is a finding. - - - <VulnDiscussion>A consent banner will be in place to make prospective entrants aware that the website they are about to enter is a DoD web site and their activity is subject to monitoring. The document, DoDI 8500.01, establishes the policy on the use of DoD information systems. It requires the use of a standard Notice and Consent Banner and standard text to be included in user agreements. The requirement for the banner is for websites with security and access controls. These are restricted and not publicly accessible. If the website does not require authentication/authorization for use, then the banner does not need to be present. A manual check of the document root directory for a banner page file (such as banner.html) or navigation to the website via a browser can be used to confirm the information provided from interviewing the web staff.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: This requirement is only applicable for private DoD websites. - -If a banner is required, the following banner page must be in place: - -“You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. - -By using this IS (which includes any device attached to this IS), you consent to the following conditions: - --The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. - -- At any time, the USG may inspect and seize data stored on this IS. - -- Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. - -- This IS includes security measures (e.g., authentication and access controls) to protect USG interests—not for your personal benefit or privacy. - -- Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.” - -OR - -If your system cannot meet the character limits to store this amount of text in the banner, the following is another option for the warning banner: - -"I've read & consent to terms in IS user agreem't." - -NOTE: While DoDI 8500.01 does not contain a copy of the banner to be used, it does point to the RMF Knowledge Service for a copy of the required text. It is also noted that the banner is to be displayed only once when the individual enters the site and not for each page. - -If the access-controlled website does not display this banner page before entry, this is a finding. - - - - - <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. - -A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. - -A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Absent - .exe - False - application/octet-stream - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Click on the IIS 8.5 site. -Under IIS, double-click the “MIME Types” icon. -From the "Group by:" drop-down list, select "Content Type". -From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: -If any OS shell MIME types are configured, this is a finding. -.exe - - - <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. - -A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. - -A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Absent - .dll - False - application/x-msdownload - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Click on the IIS 8.5 site. -Under IIS, double-click the “MIME Types” icon. -From the "Group by:" drop-down list, select "Content Type". -From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: -If any OS shell MIME types are configured, this is a finding. -.dll - - - <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. - -A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. - -A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Absent - .com - False - application/octet-stream - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Click on the IIS 8.5 site. -Under IIS, double-click the “MIME Types” icon. -From the "Group by:" drop-down list, select "Content Type". -From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: -If any OS shell MIME types are configured, this is a finding. -.com - - - <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. - -A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. - -A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Absent - .bat - False - application/x-bat - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Click on the IIS 8.5 site. -Under IIS, double-click the “MIME Types” icon. -From the "Group by:" drop-down list, select "Content Type". -From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: -If any OS shell MIME types are configured, this is a finding. -.bat - - - <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. - -A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. - -A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Absent - .csh - False - application/x-csh - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Click on the IIS 8.5 site. -Under IIS, double-click the “MIME Types” icon. -From the "Group by:" drop-down list, select "Content Type". -From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: -If any OS shell MIME types are configured, this is a finding. -.csh - - - - - <VulnDiscussion>Transport Layer Security (TLS) encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. - -FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: If the server being reviewed is a public IIS 8.5 web server, this is Not Applicable. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Double-click the "SSL Settings" icon. - -Verify "Require SSL" check box is selected. - -If the "Require SSL" check box is not selected, this is a finding. - Ssl - - - <VulnDiscussion>Transport Layer Security (TLS) encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. - -FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: If the server being reviewed is a private IIS 8.5 web server, this is Not Applicable. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Double-click the "SSL Settings" icon. - -Verify "Require SSL" check box is selected. - -If the "Require SSL" check box is not selected, this is a finding. - Ssl - - - <VulnDiscussion>A DoD private website must utilize PKI as an authentication mechanism for web users. Information systems residing behind web servers requiring authorization based on individual identity must use the identity provided by certificate-based authentication to support access control decisions. Not using client certificates allows an attacker unauthenticated access to private websites. - -Satisfies: SRG-APP-000172-WSR-000104, SRG-APP-000224-WSR-000135, SRG-APP-000427-WSR-000186</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: If the server being reviewed is a public IIS 8.5 web server, this is Not Applicable. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Double-click the "SSL Settings" icon. - -Verify the "Clients Certificate Required" check box is selected. - -If the "Clients Certificate Required" check box is not selected, this is a finding. - SslRequireCert - - - <VulnDiscussion>When data is written to digital media, such as hard drives, mobile computers, external/removable hard drives, personal digital assistants, flash/thumb drives, etc., there is risk of data loss and data compromise. User identities and passwords stored on the hard drive of the hosting hardware must be encrypted to protect the data from easily being discovered and used by an unauthorized user to access the hosted applications. The cryptographic libraries and functionality used to store and retrieve the user identifiers and passwords must be part of the web server. - -Preventing the disclosure of transmitted information requires that the web server take measures to employ some form of cryptographic mechanism in order to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS). - -Transmission of data can take place between the web server and a large number of devices/applications external to the web server. Examples are a web client used by a user, a backend database, an audit server, or other web servers in a web cluster. - -If data is transmitted unencrypted, the data then becomes vulnerable to disclosure. The disclosure may reveal user identifier/password combinations, website code revealing business logic, or other user personal information. - -Also satisfies: SRG-APP-000439-WSR-000151</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Double-click the "SSL Settings" icon under the "IIS" section. - -Verify "Require SSL" is checked. - -Verify "Client Certificates Required" is selected. - -Click the site under review. - -Select "Configuration Editor" under the "Management" section. - -From the "Section:" drop-down list at the top of the configuration editor, locate “system.webServer/security/access”. - -The value for "sslFlags" set must include "ssl128". - -If the "Require SSL" is not selected, this is a finding. - -If the "Client Certificates Required" is not selected, this is a finding. - -If the "sslFlags" is not set to "ssl128", this is a finding. - Ssl,SslNegotiateCert,SslRequireCert,Ssl128 - - - <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. - -An example of this would be an SMTP queue. This queue may be added to a web server through an SMTP module to enhance error reporting or to allow developers to add SMTP functionality to their applications. - -Any modules used by the web server that queue data before transmission must maintain the confidentiality and integrity of the information before the data is transmitted. - -Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. - -Protecting the confidentiality and integrity of received information requires that application servers take measures to employ approved cryptography in order to protect the information during transmission over the network. This is usually achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPsec tunnel. - -The web server must utilize approved encryption when receiving transmitted data. - -Also satisfies: SRG-APP-000442-WSR-000182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Double-click the "SSL Settings" icon under the "IIS" section. - -Verify "Require SSL" is checked. - -Verify "Client Certificates Required" is selected. - -Click the site under review. - -Select "Configuration Editor" under the "Management" section. - -From the "Section:" drop-down list at the top of the configuration editor, locate “system.webServer/security/access”. - -The value for "sslFlags" should be ssl128. - -If the "Require SSL" is not selected, this is a finding. - -If the "Client Certificates Required" is not selected, this is a finding. - -If the "sslFlags" is not set to "ssl128", this is a finding. - Ssl,SslNegotiateCert,SslRequireCert,Ssl128 - - - - - <VulnDiscussion>The idle time-out attribute controls the amount of time a worker process will remain idle before it shuts down. A worker process is idle if it is not processing requests and no new requests are received. - -The purpose of this attribute is to conserve system resources; the default value for idle time-out is 20 minutes. - -By default, the World Wide Web (WWW) service establishes an overlapped recycle, in which the worker process to be shut down is kept running until after a new worker process is started.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - idleTimeout - True - [TimeSpan]{0} -le [TimeSpan]'00:20:00' - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the Application Pools. - -Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. - -Scroll down to the "Process Model" section and verify the value for "Idle Time-out" is set to "20". - -If the "Idle Time-out" is not set to "20" or less, this is a finding. - - - - - <VulnDiscussion>In order to determine the possible causes of client connection errors and to conserve system resources, it is important to both log errors and manage those settings controlling requests to the application pool.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - queueLength - True - {0} -le 1000 - Open the IIS 8.5 Manager. - -Perform for each Application Pool. - -Click the “Application Pools”. - -Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. - -Scroll down to the "General" section and verify the value for "Queue Length" is set to 1000. - -If the "Queue Length" is set to "1000" or less, this is not a finding. - - - - - <VulnDiscussion>Windows Process Activation Service (WAS) manages application pool configurations and may flag a worker process as unhealthy and shut it down. An application pool’s pinging monitor must be enabled to confirm worker processes are functional. A lack of response from the worker process might mean the worker process does not have a thread to respond to the ping request, or it is hanging for some other reason. The ping interval and ping response time may need adjustment to gain access to timely information about application pool health without triggering false, unhealthy conditions; for example, instability caused by an application.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - pingingEnabled - False - - Open the Internet Information Services (IIS) Manager. - -Click the “Application Pools”. - -Perform for each Application Pool. - -Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. - -Scroll down to the "Process Model" section and verify the value for "Ping Enabled" is set to "True". - -If the value for "Ping Enabled" is not set to "True", this is a finding. - $true - - - <VulnDiscussion>Rapid fail protection is a feature that interrogates the health of worker processes associated with websites and web applications. It can be configured to perform a number of actions such as shutting down and restarting worker processes that have reached failure thresholds. By not setting rapid fail protection the web server could become unstable in the event of a worker process crash potentially leaving the web server unusable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - rapidFailProtection - False - - Open the IIS 8.5 Manager. - -Click the “Application Pools”. - -Perform for each Application Pool. - -Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. - -Scroll down to the "Rapid Fail Protection" section and verify the value for "Enabled" is set to "True". - -If the "Rapid Fail Protection:Enabled" is not set to "True", this is a finding. - $true - - - <VulnDiscussion>Windows Process Activation Service (WAS) manages application pool configuration and may flag a worker process as unhealthy and shut it down. The rapid fail protection must be set to a suitable value. A lack of response from the worker process might mean the worker process does not have a thread to respond to the ping request, or that it is hanging for some other reason. The ping interval and ping response time may need adjustment to gain access to timely information about application pool health without triggering false, unhealthy conditions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - rapidFailProtectionInterval - True - [TimeSpan]{0} -le [TimeSpan]'00:05:00' - Open the IIS 8.5 Manager. - -Click the “Application Pools”. - -Perform for each Application Pool. - -Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. - -Scroll down to the "Rapid Fail Protection" section and verify the value for "Failure Interval" is set to "5". - -If the "Failure Interval" is not set to "5" or less, this is a finding. - - - - - - - /system.web/sessionState - <VulnDiscussion>When the session information is stored on the client, the session ID, along with the user authorization and identity information, is sent along with each client request and is stored in either a cookie, embedded in the uniform resource locator (URL), or placed in a hidden field on the displayed form. Each of these offers advantages and disadvantages. The biggest disadvantage to all three is the hijacking of a session along with all of the user's credentials. - -When the user authorization and identity information is stored on the server in a protected and encrypted database, the communication between the client and web server will only send the session identifier, and the server can then retrieve user credentials for the session when needed. If, during transmission, the session were to be hijacked, the user's credentials would not be compromised. - -ASP.NET provides a session state, which is available as the HttpSessionState class, as a method of storing session-specific information that is visible only within the session. ASP.NET session state identifies requests from the same browser during a limited time window as a session, and provides the ability to persist variable values for the duration of that session.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - mode - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Under the "ASP.NET" section, select "Session State". - -Under "Session State Mode Settings", verify the "In Process" mode is selected. - -If the "Session State Mode Settings" is set to "In Process", this is not a finding. - -Alternative method: - -Click the site name. - -Select "Configuration Editor" under the "Management" section. - -From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". - -Verify the "mode" reflects "InProc". - -If the "mode" is not set to "InProc", this is a finding. - InProc - - - /system.web/sessionState - <VulnDiscussion>When the session information is stored on the client, the session ID, along with the user authorization and identity information, is sent along with each client request and is stored in either a cookie, embedded in the uniform resource locator (URL), or placed in a hidden field on the displayed form. Each of these offers advantages and disadvantages. The biggest disadvantage to all three is the hijacking of a session along with all of the user's credentials. - -When the user authorization and identity information is stored on the server in a protected and encrypted database, the communication between the client and website will only send the session identifier, and the server can then retrieve user credentials for the session when needed. If, during transmission, the session were to be hijacked, the user's credentials would not be compromised. - -ASP.NET provides a session state, which is available as the HttpSessionState class, as a method of storing session-specific information that is visible only within the session. ASP.NET session state identifies requests from the same browser during a limited time window as a session, and provides the ability to persist variable values for the duration of that session. - -Cookies associate session information with client information for the duration of a user’s connection to a website. Using cookies is a more efficient way to track session state than any of the methods that do not use cookies because cookies do not require any redirection. -</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - cookieless - False - - From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". -Verify the "cookieless" is set to "UseCookies". - UseCookies - - - /system.web/trust - <VulnDiscussion>A web server may host too many applications. Each application will need certain system resources and privileged operations to operate correctly. An application's trust level determines the permissions granted by the ASP.NET Code Access Security (CAS) policy. An application with full trust permissions may access all resource types on a server and perform privileged operations, while applications running with partial trust have varying levels of operating permissions and access to resources. The CAS determines the permissions granted to the application on the server. Setting a level of trust compatible with the applications will limit the potential harm a compromised application could cause to a system. The web server must be configured to contain and control the applications and protect the system resources and privileged operations from those not needed by the application for operation. - -Limiting the application will confine the potential harm a compromised application could cause to a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - level - True - '{0}' -cmatch '^(Full|High)$' - Note: If the server being reviewed is a non-production website, this is Not Applicable. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name under review. - -Double-click the ".NET Trust Level" icon. - -If the ".NET Trust Level" is not set to Full or less, this is a finding. - - - - - - /system.web/sessionState - <VulnDiscussion>Communication between a client and the web server is done using the HTTP protocol, but HTTP is a stateless protocol. In order to maintain a connection or session, a web server will generate a session identifier (ID) for each client session when the session is initiated. The session ID allows the web server to track a user session and, in many cases, the user, if the user previously logged into a hosted application. - -By being able to guess session IDs, an attacker can easily perform a man-in-the-middle attack. To truly generate random session identifiers that cannot be reproduced, the web server session ID generator, when used twice with the same input criteria, must generate an unrelated random ID. - -The session ID generator also needs to be a FIPS 140-2-approved generator.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - mode - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Under the "ASP.NET" section, select "Session State". - -Under "Session State" Mode Settings, verify the "In Process" mode is selected. - -If the "In Process" mode is selected, this is not a finding. - -Alternative method: - -Click the site name. - -Select "Configuration Editor" under the "Management" section. - -From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". - -Verify the "mode" reflects "InProc". - -If the "mode" is not set to "InProc", this is a finding. - InProc - - - /system.webServer/security/requestFiltering/requestlimits - <VulnDiscussion>Request filtering replaces URLScan in IIS, enabling administrators to create a more granular rule set with which to allow or reject inbound web content. By setting limits on web requests, it helps to ensure availability of web services and may also help mitigate the risk of buffer overflow type attacks. The MaxURL Request Filter limits the number of bytes the server will accept in a URL.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - maxUrl - True - {0} -le 4096 - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click on the site name. - -Double-click the "Request Filtering" icon. - -Click “Edit Feature Settings” in the "Actions" pane. - -If the "maxUrl" value is not set to "4096" or less, this is a finding. - - - - - /system.webServer/security/requestFiltering/requestlimits - <VulnDiscussion>By setting limits on web requests, it helps to ensure availability of web services and may also help mitigate the risk of buffer overflow type attacks. The Maximum Query String Request Filter describes the upper limit on allowable query string lengths. Upon exceeding the configured value, IIS will generate a Status Code 404.15.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - maxQueryString - True - {0} -le 2048 - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click on the site name. - -Double-click the "Request Filtering" icon. - -Click “Edit Feature Settings” in the "Actions" pane. - -If the "Maximum Query String" value is not set to "2048" or less, this is a finding. - - - - - /system.webServer/security/requestFiltering - <VulnDiscussion>By setting limits on web requests, it ensures availability of web services and mitigates the risk of buffer overflow type attacks. The allow high-bit characters Request Filter enables rejection of requests containing non-ASCII characters.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - allowHighBitCharacters - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click on the site name. - -Double-click the "Request Filtering" icon. - -Click “Edit Feature Settings” in the "Actions" pane. - -If the "Allow high-bit characters" check box is checked, this is a finding. - false - - - /system.webServer/security/requestFiltering - <VulnDiscussion>Request filtering enables administrators to create a more granular rule set with which to allow or reject inbound web content. By setting limits on web requests, it ensures availability of web services and mitigates the risk of buffer overflow type attacks. When the “Allow double escaping” option is disabled it prevents attacks that rely on double-encoded requests.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - allowDoubleEscaping - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click on the site name. - -Double-click the "Request Filtering" icon. - -Click “Edit Feature Settings” in the "Actions" pane. - -If the "Allow double escaping" check box is checked, this is a finding. - false - - - /system.webServer/security/requestFiltering/fileExtensions - <VulnDiscussion>Request filtering enables administrators to create a more granular rule set to allow or reject inbound web content. By setting limits on web requests it helps to ensure availability of web services and may also help mitigate the risk of buffer overflow type attacks. The allow unlisted property of the “File Extensions Request” filter enables rejection of requests containing specific file extensions not defined in the “File Extensions” filter. Tripping this filter will cause IIS to generate a Status Code 404.7.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - allowUnlisted - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click on the site name. - -Double-click the "Request Filtering" icon. - -Click “Edit Feature Settings” in the "Actions" pane. - -If "Allow unlisted file name extensions" check box is checked, this is a finding. - false - - - /system.webServer/directoryBrowse - <VulnDiscussion>Directory browsing allows the contents of a directory to be displayed upon request from a web client. If directory browsing is enabled for a directory in IIS, users could receive a web page listing the contents of the directory. If directory browsing is enabled the risk of inadvertently disclosing sensitive content is increased.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - enabled - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Click the Site. - -Double-click the "Directory Browsing" icon. - -If the "Directory Browsing" is not installed, this is Not Applicable. - -Under the "Actions" pane verify "Directory Browsing" is "Disabled". - -If "Directory Browsing" is not "Disabled", this is a finding. - false - - - /system.webServer/httpErrors - <VulnDiscussion>HTTP error pages contain information that could enable an attacker to gain access to an information system. Failure to prevent the sending of HTTP error pages with full information to remote requesters exposes internal configuration information to potential attackers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - errormode - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name under review. - -Double-click the "Error Pages" icon. - -Click each error message and click "Edit Feature" setting from the "Actions" pane. - -If any error message is not set to “Detailed errors for local requests and custom error pages for remote requests”, this is a finding. - DetailedLocalOnly - - - /system.web/compilation - <VulnDiscussion>Setting compilation debug to false ensures detailed error information does not inadvertently display during live application usage, mitigating the risk of application information being displayed to users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - debug - False - - Note: If the ".NET feature" is not installed, this check is Not Applicable. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name under review. - -Double-click ".NET Compilation". - -Scroll down to the "Behavior" section and verify the value for "Debug" is set to "False". - -If the "Debug" value is not set to "False", this is a finding. - false - - - /system.web/sessionState - <VulnDiscussion>Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted application as the previously authenticated user. By closing sessions after a set period of inactivity, the web server can make certain that those sessions that are not closed through the user logging out of an application are eventually closed. - -Acceptable values are 5 minutes for high-value applications, 10 minutes for medium-value applications, and 20 minutes for low-value applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - timeout - True - '{0}' -le '00:20:00' - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Select "Configuration Editor" under the "Management" section. - -From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". - -Verify the "timeout" is set to "00:20:00 or less”, using the lowest value possible depending upon the application. -Acceptable values are 5 minutes for high-value applications, 10 minutes for medium-value applications, and 20 minutes for low-value applications. - -If "timeout" is not set to "00:20:00 or less”, this is a finding. - - - - - - - /system.webServer/asp/session - <VulnDiscussion>The HTTP protocol is a stateless protocol. To maintain a session, a session identifier is used. The session identifier is a piece of data that is used to identify a session and a user. If the session identifier is compromised by an attacker, the session can be hijacked. By encrypting the session identifier, the identifier becomes more difficult for an attacker to hijack, decrypt, and use before the session has expired.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - keepSessionIdSecure - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Access the IIS 8.5 Manager. - -Select the website being reviewed. - -Under "Management" section, double-click the "Configuration Editor" icon. - -From the "Section:" drop-down list, select “system.webServer/asp". - -Expand the "session" section. - -Verify the "keepSessionIdSecure" is set to "True". - -If the "keepSessionIdSecure" is not set to "True", this is a finding. - True - - - /system.web/httpCookies - <VulnDiscussion>A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie must be encrypted. - -When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). - -Cookies shared between the web server and the client when encrypted should not also be compressed. - -A cookie can be read by client-side scripts easily if cookie properties are not set properly. By allowing cookies to be read by the client-side scripts, information such as session identifiers could be compromised and used by an attacker who intercepts the cookie. Setting cookie properties (i.e. HttpOnly property) to disallow client-side scripts from reading cookies better protects the information inside the cookie. - - - -Satisfies: SRG-APP-000439-WSR-000154, SRG-APP-000439-SSR-000155, SRG-APP-000439-WSR-000153</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - requireSSL - False - - From the "Section:" drop-down list, select "system.web/httpCookies". -Verify the "require SSL" is set to "True". - True - - - /system.web/sessionState - <VulnDiscussion>A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie must be encrypted. - -When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). - -Cookies shared between the web server and the client when encrypted should not also be compressed. - -A cookie can be read by client-side scripts easily if cookie properties are not set properly. By allowing cookies to be read by the client-side scripts, information such as session identifiers could be compromised and used by an attacker who intercepts the cookie. Setting cookie properties (i.e. HttpOnly property) to disallow client-side scripts from reading cookies better protects the information inside the cookie. - - - -Satisfies: SRG-APP-000439-WSR-000154, SRG-APP-000439-SSR-000155, SRG-APP-000439-WSR-000153</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - compressionEnabled - False - - From the "Section:" drop-down list, select "system.web/sessionState". -Verify the "compressionEnabled" is set to "False". - False - - - - - <VulnDiscussion>A web server can be installed with functionality that, just by its nature, is not secure. Web Distributed Authoring (WebDAV) is an extension to the HTTP protocol that, when developed, was meant to allow users to create, change, and move documents on a server, typically a web server or web share. Allowing this functionality, development, and deployment is much easier for web authors. - -WebDAV is not widely used and has serious security concerns because it may allow clients to modify unauthorized files on the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Web-DAV-Publishing - Absent - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Select the IIS 8.5 website. - -Review the features listed under the "IIS" section. - -If the "WebDAV Authoring Rules" icon exists, this is a finding. - - - diff --git a/StigData/Processed/IIS-8-5-Site-1.6.xml b/StigData/Processed/IIS-8-5-Site-1.6.xml deleted file mode 100644 index cffae4a49..000000000 --- a/StigData/Processed/IIS-8-5-Site-1.6.xml +++ /dev/null @@ -1,1465 +0,0 @@ - - - - <VulnDiscussion>IIS 8.5 will either allow or deny script execution based on file extension. The ability to control script execution is controlled through two features with IIS 8.5, Request Filtering and "Handler Mappings". - -For "Handler Mappings", the ISSO must document and approve all allowable file extensions the website allows (white list) and denies (black list) by the website. The white list and black list will be compared to the "Handler Mappings" in IIS 8. "Handler Mappings" at the site level take precedence over "Handler Mappings" at the server level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - For "Handler Mappings", the ISSO must document and approve all allowable scripts the website allows (white list) and denies (black list) by the website. The white list and black list will be compared to the "Handler Mappings" in IIS 8.5. "Handler Mappings" at the site level take precedence over "Handler Mappings" at the server level. - -Open the IIS 8.5 Manager. - -Click the site name under review. - -Double-click "Handler Mappings". - -If any script file extensions from the black list are enabled, this is a finding. - - - <VulnDiscussion>Resource mapping is the process of tying a particular file type to a process in the web server that can serve that type of file to a requesting client and to identify which file types are not to be delivered to a client. - -By not specifying which files can and which files cannot be served to a user, the web server could deliver to a user web server configuration files, log files, password files, etc. - -The web server must only allow hosted application file types to be served to a user and all other types must be disabled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - For "Handler Mappings", the ISSO must document and approve all allowable file extensions the website allows (white list) and denies (black list) by the website. The white list and black list will be compared to the "Handler Mappings" in IIS 8.5. "Handler Mappings" at the site level take precedence over "Handler Mappings" at the server level. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Double-click "Request Filtering". - -If any file name extensions from the black list have "Allowed" set to "True", this is a finding. - - - <VulnDiscussion>By setting limits on web requests, it ensures availability of web services and mitigates the risk of buffer overflow type attacks. The maxAllowedContentLength Request Filter limits the number of bytes the server will accept in a request.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click on the site name. - -Double-click the "Request Filtering" icon. - -Click “Edit Feature Settings” in the "Actions" pane. - -If the "maxAllowedContentLength" value is not explicitly set to "30000000" or less or a length documented and approved by the ISSO, this is a finding. - - - - <VulnDiscussion>The goal is to control the web users experience in navigating any portion of the web document root directories. Ensuring all web content directories have at least the equivalent of an index.html file is a significant factor to accomplish this end. Also, enumeration techniques, such as URL parameter manipulation, rely upon being able to obtain information about the web server’s directory structure by locating directories with default pages. This practice helps ensure the anonymous web user will not obtain directory browsing information or an error message revealing the server type and version.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: This requirement is only for each site's root directory. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Click the site name under review. - -Double-click "Default Document". - -In the "Actions" pane, verify the "Default Document" feature is enabled. - -If an "Enable" option is listed under the "Actions" pane, the "Default Document" feature is not enabled and this is a finding. - -If "Default Document" is "Enabled, review the document types. - -Click the "Content View" tab, click on each listed "Default Document" and click on "Explore" under the "Actions" pane. Verify there is a document of that type in the directory. - -If "Default Document" is "Enabled" but no listed document types are present in the "Content View", this is a finding. - - - <VulnDiscussion>During an attack on the web server or any of the hosted applications, the system administrator may need to disconnect or disable access by users to stop the attack. - -The web server must provide a capability to disconnect users to a hosted application without compromising other hosted applications unless deemed necessary to stop the attack. Methods to disconnect or disable connections are to stop the application service for a specified hosted application, stop the web server, or block all connections through web server access list. - -The web server capabilities used to disconnect or disable users from connecting to hosted applications and the web server must be documented to make certain that, during an attack, the proper action is taken to conserve connectivity to any other hosted application if possible and to make certain log data is conserved for later forensic analysis.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Interview the System Administrator and Web Manager. - -Ask for documentation for the IIS 8.5 web server administration. - -Verify there are documented procedures for shutting down an IIS 8.5 website in the event of an attack. The procedure should, at a minimum, provide the following steps: - -Determine the respective website for the application at risk of an attack. - -Access the IIS 8.5 web server IIS 8.5 Manager. - -Select the respective website. - -In the "Actions" pane, under "Manage Website", click on "Stop". - -If necessary, stop all websites. - -If necessary, stop the IIS 8.5 web server by selecting the web server in the IIS 8.5 Manager. - -In the "Actions" pane, under "Manage Server", click on "Stop". - -If there are not documented procedures with, at a minimum, the mentioned steps for stopping a website, this is a finding. - - - <VulnDiscussion>In order to make certain that the logging mechanism used by the web server has sufficient storage capacity in which to write the logs, the logging mechanism needs to be able to allocate log record storage capacity. - -The task of allocating log record storage capacity is usually performed during initial installation of the logging mechanism. The system administrator will usually coordinate the allocation of physical drive space with the web server administrator along with the physical location of the partition and disk. Refer to NIST SP 800-92 for specific requirements on log rotation and storage dependent on the impact of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Access the IIS 8.5 web server IIS 8.5 Manager. - -Under "IIS" double-click on the "Logging" icon. - -In the "Logging" configuration box, determine the "Directory:" to which the "W3C" logging is being written. - -Confirm with the System Administrator that the designated log path is of sufficient size to maintain the logging. - -Under "Log File Rollover", verify the "Do not create new log files" is not selected. - -Verify a schedule is configured to rollover log files on a regular basis. - -Consult with the System Administrator to determine if there is a documented process for moving the log files off of the IIS 8.5 web server to another logging device. - -If the designated logging path device is not of sufficient space to maintain all log files and there is not a schedule to rollover files on a regular basis, this is a finding. - - - <VulnDiscussion>Web servers provide numerous processes, features, and functionalities that utilize TCP/IP ports. Some of these processes may be deemed unnecessary or too unsecure to run on a production system. - -The web server must provide the capability to disable or deactivate network-related services that are deemed to be non-essential to the server mission, are too unsecure, or are prohibited by the PPSM CAL and vulnerability assessments. - -Failure to comply with DoD ports, protocols, and services (PPS) requirements can result in compromise of enclave boundary protections and/or functionality of the AIS. - -The ISSM will ensure web servers are configured to use only authorized PPS in accordance with the Network Infrastructure STIG, DoD Instruction 8551.1, Ports, Protocols, and Services Management (PPSM), and the associated Ports, Protocols, and Services (PPS) Assurance Category Assignments List.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Review the website to determine if HTTP and HTTPs (e.g., 80 and 443) are used in accordance with those ports and services registered and approved for use by the DoD PPSM. Any variation in PPS will be documented, registered, and approved by the PPSM. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name under review. - -In the “Action” Pane, click “Bindings”. - -Review the ports and protocols. If unknown ports or protocols are used, then this is a finding. - - - <VulnDiscussion>IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: Recycling Application Pools can create an unstable environment in a 64-bit SharePoint environment. If operational issues arise, with supporting documentation from the ISSO, this check can be downgraded to a Cat III. - -Open the IIS 8.5 Manager. - -Perform for each Application Pool. - -Click the “Application Pools”. - -Highlight an Application Pool and click "Advanced Settings" in the “Action” Pane. - -Scroll down to the "Recycling section" and verify the value for "Request Limit" is set to a value other than "0". - -If the "Request Limit" is set to a value of "0", this is a finding. - - - <VulnDiscussion>IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: Recycling Application Pools can create an unstable environment in a 64-bit SharePoint environment. If operational issues arise, mitigation steps can be set, to include setting the “Fixed number or requests”, “Specific time”, and “Private memory usage” in the recycling conditions lieu of the “Virtual memory” setting. If mitigation is used in lieu of this requirement, with supporting documentation from the ISSO, this check can be downgraded to a Cat III. - -Open the IIS 8.5 Manager. - -Perform for each Application Pool. - -Click on “Application Pools”. - -Highlight an Application Pool and click "Advanced Settings" in the Action Pane. - -In the "Advanced Settings" dialog box scroll down to the "Recycling" section and verify the value for "Virtual Memory Limit" is not set to 0. - -If the value for "Virtual Memory Limit" is set to 0, this is a finding. - - - - <VulnDiscussion>IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: Recycling Application Pools can create an unstable environment in a 64-bit SharePoint environment. If operational issues arise, with supporting documentation from the ISSO this check can be downgraded to a Cat III. - -Open the IIS 8.5 Manager. - -Perform for each Application Pool. - -Click the “Application Pools”. - -Highlight an Application Pool and click "Advanced Settings" in the “Action” Pane. - -Scroll down to the "Recycling" section and verify the value for "Private Memory Limit" is set to a value other than "0". - -If the "Private Memory Limit" is set to a value of "0", this is a finding. - - - <VulnDiscussion>Application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: Recycling Application Pools can create an unstable environment in a 64-bit SharePoint environment. If operational issues arise, with supporting documentation from the ISSO this check can be downgraded to a Cat III. - -Open the IIS 8.5 Manager. - -Perform for each Application Pool. - -Click the “Application Pools”. - -Highlight an Application Pool and click "Advanced Settings" in the “Action” Pane. - -Scroll down to the "Recycling" section and expand the "Generate Recycle Event Log Entry" section. - -Verify both the "Regular time interval" and "Specific time" options are set to "True". - -If both the "Regular time interval" and "Specific time" options are not set to "True", this is a finding. - - - - - <VulnDiscussion>Log files are a critical component to the successful management of an IS used within the DoD. By generating log files with useful information web administrators can leverage them in the event of a disaster, malicious attack, or other site-specific needs. - -Ascertaining the correct order of the events that occurred is important during forensic analysis. Events that appear harmless by themselves might be flagged as a potential threat when properly viewed in sequence. By also establishing the event date and time, an event can be properly viewed with an enterprise tool to fully see a possible threat in its entirety. - -Without sufficient information establishing when the log event occurred, investigation into the cause of event is severely hindered. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked. - -Satisfies: SRG-APP-000092-WSR-000055, SRG-APP-000093-WSR-000053</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - - Date,Time,ClientIP,UserName,Method,UriQuery,ProtocolVersion,Referer - - - - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Click the "Logging" icon. - -Under Format select "W3C". - -Click “Select Fields”, verify at a minimum the following fields are checked: Date, Time, Client IP Address, User Name, Method, URI Query, Protocol Status, and Referrer. - -If the "W3C" is not selected as the logging format OR any of the required fields are not selected, this is a finding. - - - <VulnDiscussion>Internet Information Services (IIS) on Windows Server 2012 provides basic logging capabilities. However, because IIS takes some time to flush logs to disk, administrators do not have access to logging information in real-time. In addition, text-based log files can be difficult and time-consuming to process. - -In IIS 8.5, the administrator has the option of sending logging information to Event Tracing for Windows (ETW). This option gives the administrator the ability to use standard query tools, or create custom tools, for viewing real-time logging information in ETW. This provides a significant advantage over parsing text-based log files that are not updated in real time. - -Satisfies: SRG-APP-000092-WSR-000055, SRG-APP-000108-WSR-000166</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - - - - - File,ETW - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Click the "Logging" icon. - -Under Log Event Destination, verify the "Both log file and ETW event" radio button is selected. - -If the "Both log file and ETW event" radio button is not selected, this is a finding. - - - <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. - -Ascertaining the success or failure of an event is important during forensic analysis. Correctly determining the outcome will add information to the overall reconstruction of the logable event. By determining the success or failure of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the event occurred in other areas within the enterprise. - -Without sufficient information establishing the success or failure of the logged event, investigation into the cause of event is severely hindered. The success or failure also provides a means to measure the impact of an event and help authorized personnel to determine the appropriate response. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - - - RequestHeader - Connection - - - RequestHeader - Warning - - - - W3C - - - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Select the website being reviewed. - -Under "IIS", double-click the "Logging" icon. - -Verify the "Format:" under "Log File" is configured to "W3C". - -Select the "Fields" button. - -Under "Custom Fields", verify the following fields are selected: - -Request Header >> Connection - -Request Header >> Warning - -If any of the above fields are not selected, this is a finding. - - - <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. - -Determining user accounts, processes running on behalf of the user, and running process identifiers also enable a better understanding of the overall event. User tool identification is also helpful to determine if events are related to overall user access or specific client tools. - -Log record content that may be necessary to satisfy the requirement of this control includes: time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - - - ServerVariable - HTTP_USER_AGENT - - - RequestHeader - Authorization - - - ResponseHeader - Content-Type - - - UserAgent,UserName,Referer - W3C - - - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Access the IIS 8.5 web server IIS 8.5 Manager. - -Under "IIS", double-click the "Logging" icon. - -Verify the "Format:" under "Log File" is configured to "W3C". - -Select the "Fields" button. - -Under "Standard Fields", verify "User Agent", "User Name" and "Referrer" are selected. - -Under "Custom Fields", verify the following fields have been configured: - -Server Variable >> HTTP_USER_AGENT - -Request Header >> Authorization - -Response Header >> Content-Type - -If any of the above fields are not selected, this is a finding. - - - - - <VulnDiscussion>Resource exhaustion can occur when an unlimited number of concurrent requests are allowed on a website, facilitating a Denial of Service attack. Mitigating this kind of attack will include limiting the number of concurrent HTTP/HTTPS requests per IP address and may include, where feasible, limiting parameter values associated with keepalive (i.e., a parameter used to limit the amount of time a connection may be inactive).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Access the IIS 8.5 IIS Manager. - -Click the IIS 8.5 server. - -Select "Configuration Editor" under the "Management" section. - -From the "Section:" drop-down list at the top of the configuration editor, locate "system.applicationHost/sites". - -Expand "siteDefaults". -Expand "limits". - -Review the results and verify the value is greater than zero for the "maxconnections" parameter. - -If the maxconnections parameter is set to zero, this is a finding. - - - <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. - -Ascertaining the correct source, e.g. source IP, of the events is important during forensic analysis. Correctly determining the source of events will add information to the overall reconstruction of the logable event. By determining the source of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the source occurred in other areas within the enterprise. - -A web server behind a load balancer or proxy server, when not configured correctly, will record the load balancer or proxy server as the source of every logable event. When looking at the information forensically, this information is not helpful in the investigation of events. The web server must record with each event the client source of the event.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Interview the System Administrator to review the configuration of the IIS 8.5 architecture and determine if inbound web traffic is passed through a proxy. - -If the IIS 8.5 is receiving inbound web traffic through a proxy, the audit logs must be reviewed to determine if correct source information is being passed through by the proxy server. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Click the "Logging" icon. - -Click on "View log file" button. - -When log file is displaced, review source IP information in log entries and verify entries do not reflect the IP address of the proxy server. - -If the log entries in the log file(s) reflect the IP address of the proxy server as the source, this is a finding. -If the website is not behind a load balancer or proxy server, this is Not Applicable. - - - <VulnDiscussion>A major tool in exploring the website use, attempted use, unusual conditions, and problems are the access and error logs. In the event of a security incident, these logs can provide the SA and the web manager with valuable information. Failure to protect log files could enable an attacker to modify the log file data or falsify events to mask an attacker's activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Click the site name. -Click the "Logging" icon. -Click "Browse" and navigate to the directory where the log files are stored. -Right-click the log file name to review and click “Properties”. -Click the “Security” tab. -Verify only authorized groups are listed, if others are listed, this is a finding. -Note: The log file should be restricted as follows: -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control -Web Managers - Read - - - <VulnDiscussion>The web server must be configured to listen on a specified IP address and port. Without specifying an IP address and port for the web server to utilize, the web server will listen on all IP addresses available to the hosting server. If the web server has multiple IP addresses, i.e., a management IP address, the web server will also accept connections on the management IP address. - -Accessing the hosted application through an IP address normally used for non-application functions opens the possibility of user access to resources, utilities, files, ports, and protocols that are protected on the desired application IP address.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Right-click on the site name under review. - -Select “Edit Bindings”. - -Verify there are hostname entries and unique IP addresses assigned to port 80 for HTTP and port 443 for HTTPS. - -If both hostname entries and unique IP addresses are not configure to port 80 for HTTP and port 443 for HTTPS, this is a finding. - - - <VulnDiscussion>Many of the security problems that occur are not the result of a user gaining access to files or data for which the user does not have permissions, but rather users are assigned incorrect permissions to unauthorized data. The files, directories, and data that are stored on the web server need to be evaluated and a determination made concerning authorized access to information and programs on the server. Only authorized users and administrative accounts will be allowed on the host server in order to maintain the web server, applications, and review the server operations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Check the account used for anonymous access to the website. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. - -Double-click "Authentication" in the IIS section of the website’s Home Pane. - -If Anonymous access is disabled, this is Not a Finding. - -If Anonymous access is enabled, click “Anonymous Authentication”. - -Click “Edit” in the "Actions" pane. - -If the “Specific user” radio button is enabled and an ID is specified in the adjacent control box, this is the ID being used for anonymous access. Note: account name. - -Check privileged groups that may allow the anonymous account inappropriate membership: -Open “Server Manager” on the machine. - -Expand Configuration. - -Expand Local Users and Groups. - -Click “Groups”. - -Review members of any of the following privileged groups: - -Administrators -Backup Operators -Certificate Services (of any designation) -Distributed COM Users -Event Log Readers -Network Configuration Operators -Performance Log Users -Performance Monitor Users -Power Users -Print Operators -Remote Desktop Users -Replicator -Users - -Double-click each group and review its members. - -If the IUSR account or any account noted above used for anonymous access is a member of any group with privileged access, this is a finding. - - - <VulnDiscussion>The web document (home) directory is accessed by multiple anonymous users when the web server is in production. By locating the web document (home) directory on the same partition as the web server system file the risk for unauthorized access to these protected files is increased. Additionally, having the web document (home) directory path on the same drive as the system folders also increases the potential for a drive space exhaustion attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name under review. - -Click the "Advanced Settings" from the "Actions" pane. - -Review the Physical Path. - -If the Path is on the same partition as the OS, this is a finding. - - - <VulnDiscussion>The use of a DoD PKI certificate ensures clients the private website they are connecting to is legitimate, and is an essential part of the DoD defense-in-depth strategy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name under review. - -Click “Bindings” in the “Action” Pane. - -Click the “HTTPS type” from the box. - -Click “Edit”. - -Click “View” and then review and verify the certificate path. - -If the list of CAs in the trust hierarchy does not lead to the DoD PKI Root CA, DoD-approved external certificate authority (ECA), or DoD-approved external partner, this is a finding. - -If HTTPS is not an available type under site bindings, this is a finding. - - - <VulnDiscussion>Application pools isolate sites and applications to address reliability, availability, and security issues. Sites and applications may be grouped according to configurations, although each site will be associated with a unique application pool.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Open the IIS 8.5 Manager. - -Click "Application Pools". - -In the list of Application Pools, review the "Applications" column and verify unique application pools for each website. - -If any Application Pools are being used for more than one website, this is a finding. - - - - <VulnDiscussion>CGI and ASP scripts represent one of the most common and exploitable means of compromising a web server. All CGI and ASP program files must be segregated into their own unique folder to simplify the protection of these files. ASP scripts must be placed into a unique folder only containing other ASP scripts. JAVA and other technology-specific scripts must also be placed into their own unique folders. The placement of CGI, ASP, or equivalent scripts to special folders gives the Web Manager or the SA control over what goes into those folders and to facilitate access control at the folder level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Determine whether scripts are used on the web server for the target website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. - -All interactive programs must be placed in unique designated folders based on CGI or ASP script type. - -Open the IIS 8.5 Manager. - -Right-click the IIS 8.5 web site name and select Explore. - -Search for the listed script extensions. Each script type must be in its unique designated folder. - -If scripts are not segregated from web content and in their own unique folders, then this is a finding. - - - <VulnDiscussion>CGI is a programming standard for interfacing external applications with information servers, such as HTTP or web servers. CGI, represented by all upper case letters, should not be confused with the .cgi file extension. The .cgi file extension does represent a CGI script, but CGI scripts may be written in a number of programming languages (e.g., PERL, C, PHP, and JavaScript), each having their own unique file extension. - -The use of CGI scripts represent one of the most common and exploitable means of compromising a web server. By definition, CGI scripts are executable by the operating system of the host server. While access control is provided via the web service, the execution of CGI programs is not limited unless the SA or the Web Manager takes specific measures. CGI programs can access and alter data files, launch other programs, and use the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Determine whether scripts are used on the web server for the subject website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. - -If the website does not utilize CGI, this finding is Not Applicable. - -All interactive programs must have restrictive permissions. - -Open the IIS 8.5 Manager. - -Right-click the IIS 8.5 web site name and select “Explore”. - -Search for the listed script extensions. - -Review the permissions to the CGI scripts and verify only the permissions listed, or more restrictive permissions are assigned. - -Administrators: FULL -TrustedInstaller: FULL -ALL APPLICATION PACKAGES: Read -SYSTEM: FULL -ApplicationPoolId: READ -Custom Service Account: READ -Users: READ - -If the permissions are less restrictive than listed above, this is a finding. - - - <VulnDiscussion>Copies of backup files will not execute on the server, but they can be read by the anonymous user if special precautions are not taken. Such backup copies contain the same sensitive information as the actual script being executed and, as such, are useful to malicious users. Techniques and systems exist today to search web servers for such files and are able to exploit the information contained in them.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Determine whether scripts are used on the web server for the subject website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. - -If the website does not utilize CGI, this finding is Not Applicable. - -Open the IIS 8.5 Manager. - -Right-click the IIS 8.5 web site name and select “Explore”. - -Search for the listed script extensions - -Search for the following files: *.bak, *.old, *.temp, *.tmp, *.backup, or “copy of...”. - -If files with these extensions are found, this is a finding. - - - <VulnDiscussion>A consent banner will be in place to make prospective entrants aware that the website they are about to enter is a DoD web site and their activity is subject to monitoring. The document, DoDI 8500.01, establishes the policy on the use of DoD information systems. It requires the use of a standard Notice and Consent Banner and standard text to be included in user agreements. The requirement for the banner is for websites with security and access controls. These are restricted and not publicly accessible. If the website does not require authentication/authorization for use, then the banner does not need to be present. A manual check of the document root directory for a banner page file (such as banner.html) or navigation to the website via a browser can be used to confirm the information provided from interviewing the web staff.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: This requirement is only applicable for private DoD websites. - -If a banner is required, the following banner page must be in place: - -“You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. - -By using this IS (which includes any device attached to this IS), you consent to the following conditions: - --The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. - -- At any time, the USG may inspect and seize data stored on this IS. - -- Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. - -- This IS includes security measures (e.g., authentication and access controls) to protect USG interests—not for your personal benefit or privacy. - -- Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.” - -OR - -If your system cannot meet the character limits to store this amount of text in the banner, the following is another option for the warning banner: - -"I've read & consent to terms in IS user agreem't." - -NOTE: While DoDI 8500.01 does not contain a copy of the banner to be used, it does point to the RMF Knowledge Service for a copy of the required text. It is also noted that the banner is to be displayed only once when the individual enters the site and not for each page. - -If the access-controlled website does not display this banner page before entry, this is a finding. - - - - - <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. - -A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. - -A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Absent - .exe - False - application/octet-stream - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Click on the IIS 8.5 site. -Under IIS, double-click the “MIME Types” icon. -From the "Group by:" drop-down list, select "Content Type". -From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: -If any OS shell MIME types are configured, this is a finding. -.exe - - - <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. - -A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. - -A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Absent - .dll - False - application/x-msdownload - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Click on the IIS 8.5 site. -Under IIS, double-click the “MIME Types” icon. -From the "Group by:" drop-down list, select "Content Type". -From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: -If any OS shell MIME types are configured, this is a finding. -.dll - - - <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. - -A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. - -A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Absent - .com - False - application/octet-stream - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Click on the IIS 8.5 site. -Under IIS, double-click the “MIME Types” icon. -From the "Group by:" drop-down list, select "Content Type". -From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: -If any OS shell MIME types are configured, this is a finding. -.com - - - <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. - -A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. - -A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Absent - .bat - False - application/x-bat - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Click on the IIS 8.5 site. -Under IIS, double-click the “MIME Types” icon. -From the "Group by:" drop-down list, select "Content Type". -From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: -If any OS shell MIME types are configured, this is a finding. -.bat - - - <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. - -A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. - -A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Absent - .csh - False - application/x-csh - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Click on the IIS 8.5 site. -Under IIS, double-click the “MIME Types” icon. -From the "Group by:" drop-down list, select "Content Type". -From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: -If any OS shell MIME types are configured, this is a finding. -.csh - - - - - <VulnDiscussion>Transport Layer Security (TLS) encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. - -FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: If the server being reviewed is a public IIS 8.5 web server, this is Not Applicable. -Note: If SSL is installed on load balancer through which traffic is routed to the IIS 8.5 server, and the IIS 8.5 server ONLY receives traffic from the load balancer, the SSL requirement must be met on the load balancer. -Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Click the site name. -Double-click the "SSL Settings" icon. -Verify "Require SSL" check box is selected. -If the "Require SSL" check box is not selected, this is a finding. - Ssl - - - <VulnDiscussion>Transport Layer Security (TLS) encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. - -FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: If the server being reviewed is a private IIS 8.5 web server, this is Not Applicable. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Double-click the "SSL Settings" icon. - -Verify "Require SSL" check box is selected. - -If the "Require SSL" check box is not selected, this is a finding. - Ssl - - - <VulnDiscussion>A DoD private website must utilize PKI as an authentication mechanism for web users. Information systems residing behind web servers requiring authorization based on individual identity must use the identity provided by certificate-based authentication to support access control decisions. Not using client certificates allows an attacker unauthenticated access to private websites. - -Satisfies: SRG-APP-000172-WSR-000104, SRG-APP-000224-WSR-000135, SRG-APP-000427-WSR-000186</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: If the server being reviewed is a public IIS 8.5 web server, this is Not Applicable. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Double-click the "SSL Settings" icon. - -Verify the "Clients Certificate Required" check box is selected. - -If the "Clients Certificate Required" check box is not selected, this is a finding. - SslRequireCert - - - <VulnDiscussion>When data is written to digital media, such as hard drives, mobile computers, external/removable hard drives, personal digital assistants, flash/thumb drives, etc., there is risk of data loss and data compromise. User identities and passwords stored on the hard drive of the hosting hardware must be encrypted to protect the data from easily being discovered and used by an unauthorized user to access the hosted applications. The cryptographic libraries and functionality used to store and retrieve the user identifiers and passwords must be part of the web server. - -Preventing the disclosure of transmitted information requires that the web server take measures to employ some form of cryptographic mechanism in order to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS). - -Transmission of data can take place between the web server and a large number of devices/applications external to the web server. Examples are a web client used by a user, a backend database, an audit server, or other web servers in a web cluster. - -If data is transmitted unencrypted, the data then becomes vulnerable to disclosure. The disclosure may reveal user identifier/password combinations, website code revealing business logic, or other user personal information. - -Also satisfies: SRG-APP-000439-WSR-000151</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Note: If SSL is installed on load balancer through which traffic is routed to the IIS 8.5 server, and the IIS 8.5 server ONLY receives traffic from the load balancer, the SSL requirement must be met on the load balancer. -Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Double-click the "SSL Settings" icon under the "IIS" section. -Verify "Require SSL" is checked. -Verify "Client Certificates Required" is selected. -Click the site under review. -Select "Configuration Editor" under the "Management" section. -From the "Section:" drop-down list at the top of the configuration editor, locate “system.webServer/security/access”. -The value for "sslFlags" set must include "ssl128". -If the "Require SSL" is not selected, this is a finding. -If the "Client Certificates Required" is not selected, this is a finding. -If the "sslFlags" is not set to "ssl128", this is a finding. - Ssl,SslNegotiateCert,SslRequireCert,Ssl128 - - - <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. - -An example of this would be an SMTP queue. This queue may be added to a web server through an SMTP module to enhance error reporting or to allow developers to add SMTP functionality to their applications. - -Any modules used by the web server that queue data before transmission must maintain the confidentiality and integrity of the information before the data is transmitted. - -Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. - -Protecting the confidentiality and integrity of received information requires that application servers take measures to employ approved cryptography in order to protect the information during transmission over the network. This is usually achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPsec tunnel. - -The web server must utilize approved encryption when receiving transmitted data. - -Also satisfies: SRG-APP-000442-WSR-000182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Check: -Note: If SSL is installed on load balancer through which traffic is routed to the IIS 8.5 server, and the IIS 8.5 server ONLY receives traffic from the load balancer, the SSL requirement must be met on the load balancer. -Follow the procedures below for each site hosted on the IIS 8.5 web server: -Open the IIS 8.5 Manager. -Double-click the "SSL Settings" icon under the "IIS" section. -Verify "Require SSL" is checked. -Verify "Client Certificates Required" is selected. -Click the site under review. -Select "Configuration Editor" under the "Management" section. -From the "Section:" drop-down list at the top of the configuration editor, locate “system.webServer/security/access”. -The value for "sslFlags" should be “ssl128”. -If the "Require SSL" is not selected, this is a finding. -If the "Client Certificates Required" is not selected, this is a finding. -If the "sslFlags" is not set to "ssl128", this is a finding. - Ssl,SslNegotiateCert,SslRequireCert,Ssl128 - - - - - <VulnDiscussion>The idle time-out attribute controls the amount of time a worker process will remain idle before it shuts down. A worker process is idle if it is not processing requests and no new requests are received. - -The purpose of this attribute is to conserve system resources; the default value for idle time-out is 20 minutes. - -By default, the World Wide Web (WWW) service establishes an overlapped recycle, in which the worker process to be shut down is kept running until after a new worker process is started.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - idleTimeout - True - [TimeSpan]{0} -le [TimeSpan]'00:20:00' - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the Application Pools. - -Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. - -Scroll down to the "Process Model" section and verify the value for "Idle Time-out" is set to "20". - -If the "Idle Time-out" is not set to "20" or less, this is a finding. - - - - - <VulnDiscussion>In order to determine the possible causes of client connection errors and to conserve system resources, it is important to both log errors and manage those settings controlling requests to the application pool.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - queueLength - True - {0} -le 1000 - Open the IIS 8.5 Manager. - -Perform for each Application Pool. - -Click the “Application Pools”. - -Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. - -Scroll down to the "General" section and verify the value for "Queue Length" is set to 1000. - -If the "Queue Length" is set to "1000" or less, this is not a finding. - - - - - <VulnDiscussion>Windows Process Activation Service (WAS) manages application pool configurations and may flag a worker process as unhealthy and shut it down. An application pool’s pinging monitor must be enabled to confirm worker processes are functional. A lack of response from the worker process might mean the worker process does not have a thread to respond to the ping request, or it is hanging for some other reason. The ping interval and ping response time may need adjustment to gain access to timely information about application pool health without triggering false, unhealthy conditions; for example, instability caused by an application.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - pingingEnabled - False - - Open the Internet Information Services (IIS) Manager. - -Click the “Application Pools”. - -Perform for each Application Pool. - -Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. - -Scroll down to the "Process Model" section and verify the value for "Ping Enabled" is set to "True". - -If the value for "Ping Enabled" is not set to "True", this is a finding. - $true - - - <VulnDiscussion>Rapid fail protection is a feature that interrogates the health of worker processes associated with websites and web applications. It can be configured to perform a number of actions such as shutting down and restarting worker processes that have reached failure thresholds. By not setting rapid fail protection the web server could become unstable in the event of a worker process crash potentially leaving the web server unusable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - rapidFailProtection - False - - Open the IIS 8.5 Manager. - -Click the “Application Pools”. - -Perform for each Application Pool. - -Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. - -Scroll down to the "Rapid Fail Protection" section and verify the value for "Enabled" is set to "True". - -If the "Rapid Fail Protection:Enabled" is not set to "True", this is a finding. - $true - - - <VulnDiscussion>Windows Process Activation Service (WAS) manages application pool configuration and may flag a worker process as unhealthy and shut it down. The rapid fail protection must be set to a suitable value. A lack of response from the worker process might mean the worker process does not have a thread to respond to the ping request, or that it is hanging for some other reason. The ping interval and ping response time may need adjustment to gain access to timely information about application pool health without triggering false, unhealthy conditions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - rapidFailProtectionInterval - True - [TimeSpan]{0} -le [TimeSpan]'00:05:00' - Open the IIS 8.5 Manager. - -Click the “Application Pools”. - -Perform for each Application Pool. - -Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. - -Scroll down to the "Rapid Fail Protection" section and verify the value for "Failure Interval" is set to "5". - -If the "Failure Interval" is not set to "5" or less, this is a finding. - - - - - - - /system.web/sessionState - <VulnDiscussion>When the session information is stored on the client, the session ID, along with the user authorization and identity information, is sent along with each client request and is stored in either a cookie, embedded in the uniform resource locator (URL), or placed in a hidden field on the displayed form. Each of these offers advantages and disadvantages. The biggest disadvantage to all three is the hijacking of a session along with all of the user's credentials. - -When the user authorization and identity information is stored on the server in a protected and encrypted database, the communication between the client and web server will only send the session identifier, and the server can then retrieve user credentials for the session when needed. If, during transmission, the session were to be hijacked, the user's credentials would not be compromised. - -ASP.NET provides a session state, which is available as the HttpSessionState class, as a method of storing session-specific information that is visible only within the session. ASP.NET session state identifies requests from the same browser during a limited time window as a session, and provides the ability to persist variable values for the duration of that session.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - mode - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Under the "ASP.NET" section, select "Session State". - -Under "Session State Mode Settings", verify the "In Process" mode is selected. - -If the "Session State Mode Settings" is set to "In Process", this is not a finding. - -Alternative method: - -Click the site name. - -Select "Configuration Editor" under the "Management" section. - -From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". - -Verify the "mode" reflects "InProc". - -If the "mode" is not set to "InProc", this is a finding. - InProc - - - /system.web/sessionState - <VulnDiscussion>When the session information is stored on the client, the session ID, along with the user authorization and identity information, is sent along with each client request and is stored in either a cookie, embedded in the uniform resource locator (URL), or placed in a hidden field on the displayed form. Each of these offers advantages and disadvantages. The biggest disadvantage to all three is the hijacking of a session along with all of the user's credentials. - -When the user authorization and identity information is stored on the server in a protected and encrypted database, the communication between the client and website will only send the session identifier, and the server can then retrieve user credentials for the session when needed. If, during transmission, the session were to be hijacked, the user's credentials would not be compromised. - -ASP.NET provides a session state, which is available as the HttpSessionState class, as a method of storing session-specific information that is visible only within the session. ASP.NET session state identifies requests from the same browser during a limited time window as a session, and provides the ability to persist variable values for the duration of that session. - -Cookies associate session information with client information for the duration of a user’s connection to a website. Using cookies is a more efficient way to track session state than any of the methods that do not use cookies because cookies do not require any redirection. -</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - cookieless - False - - From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". -Verify the "cookieless" is set to "UseCookies". - UseCookies - - - /system.web/trust - <VulnDiscussion>A web server may host too many applications. Each application will need certain system resources and privileged operations to operate correctly. An application's trust level determines the permissions granted by the ASP.NET Code Access Security (CAS) policy. An application with full trust permissions may access all resource types on a server and perform privileged operations, while applications running with partial trust have varying levels of operating permissions and access to resources. The CAS determines the permissions granted to the application on the server. Setting a level of trust compatible with the applications will limit the potential harm a compromised application could cause to a system. The web server must be configured to contain and control the applications and protect the system resources and privileged operations from those not needed by the application for operation. - -Limiting the application will confine the potential harm a compromised application could cause to a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - level - True - '{0}' -cmatch '^(Full|High)$' - Note: If the server being reviewed is a non-production website, this is Not Applicable. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name under review. - -Double-click the ".NET Trust Level" icon. - -If the ".NET Trust Level" is not set to Full or less, this is a finding. - - - - - - /system.web/sessionState - <VulnDiscussion>Communication between a client and the web server is done using the HTTP protocol, but HTTP is a stateless protocol. In order to maintain a connection or session, a web server will generate a session identifier (ID) for each client session when the session is initiated. The session ID allows the web server to track a user session and, in many cases, the user, if the user previously logged into a hosted application. - -By being able to guess session IDs, an attacker can easily perform a man-in-the-middle attack. To truly generate random session identifiers that cannot be reproduced, the web server session ID generator, when used twice with the same input criteria, must generate an unrelated random ID. - -The session ID generator also needs to be a FIPS 140-2-approved generator.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - mode - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Under the "ASP.NET" section, select "Session State". - -Under "Session State" Mode Settings, verify the "In Process" mode is selected. - -If the "In Process" mode is selected, this is not a finding. - -Alternative method: - -Click the site name. - -Select "Configuration Editor" under the "Management" section. - -From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". - -Verify the "mode" reflects "InProc". - -If the "mode" is not set to "InProc", this is a finding. - InProc - - - /system.webServer/security/requestFiltering/requestlimits - <VulnDiscussion>Request filtering replaces URLScan in IIS, enabling administrators to create a more granular rule set with which to allow or reject inbound web content. By setting limits on web requests, it helps to ensure availability of web services and may also help mitigate the risk of buffer overflow type attacks. The MaxURL Request Filter limits the number of bytes the server will accept in a URL.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - maxUrl - True - {0} -le 4096 - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click on the site name. - -Double-click the "Request Filtering" icon. - -Click “Edit Feature Settings” in the "Actions" pane. - -If the "maxUrl" value is not set to "4096" or less, this is a finding. - - - - - /system.webServer/security/requestFiltering/requestlimits - <VulnDiscussion>By setting limits on web requests, it helps to ensure availability of web services and may also help mitigate the risk of buffer overflow type attacks. The Maximum Query String Request Filter describes the upper limit on allowable query string lengths. Upon exceeding the configured value, IIS will generate a Status Code 404.15.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - maxQueryString - True - {0} -le 2048 - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click on the site name. - -Double-click the "Request Filtering" icon. - -Click “Edit Feature Settings” in the "Actions" pane. - -If the "Maximum Query String" value is not set to "2048" or less, this is a finding. - - - - - /system.webServer/security/requestFiltering - <VulnDiscussion>By setting limits on web requests, it ensures availability of web services and mitigates the risk of buffer overflow type attacks. The allow high-bit characters Request Filter enables rejection of requests containing non-ASCII characters.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - allowHighBitCharacters - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click on the site name. - -Double-click the "Request Filtering" icon. - -Click “Edit Feature Settings” in the "Actions" pane. - -If the "Allow high-bit characters" check box is checked, this is a finding. - false - - - /system.webServer/security/requestFiltering - <VulnDiscussion>Request filtering enables administrators to create a more granular rule set with which to allow or reject inbound web content. By setting limits on web requests, it ensures availability of web services and mitigates the risk of buffer overflow type attacks. When the “Allow double escaping” option is disabled it prevents attacks that rely on double-encoded requests.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - allowDoubleEscaping - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click on the site name. - -Double-click the "Request Filtering" icon. - -Click “Edit Feature Settings” in the "Actions" pane. - -If the "Allow double escaping" check box is checked, this is a finding. - false - - - /system.webServer/security/requestFiltering/fileExtensions - <VulnDiscussion>Request filtering enables administrators to create a more granular rule set to allow or reject inbound web content. By setting limits on web requests it helps to ensure availability of web services and may also help mitigate the risk of buffer overflow type attacks. The allow unlisted property of the “File Extensions Request” filter enables rejection of requests containing specific file extensions not defined in the “File Extensions” filter. Tripping this filter will cause IIS to generate a Status Code 404.7.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - allowUnlisted - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click on the site name. - -Double-click the "Request Filtering" icon. - -Click “Edit Feature Settings” in the "Actions" pane. - -If "Allow unlisted file name extensions" check box is checked, this is a finding. - false - - - /system.webServer/directoryBrowse - <VulnDiscussion>Directory browsing allows the contents of a directory to be displayed upon request from a web client. If directory browsing is enabled for a directory in IIS, users could receive a web page listing the contents of the directory. If directory browsing is enabled the risk of inadvertently disclosing sensitive content is increased.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - enabled - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Click the Site. - -Double-click the "Directory Browsing" icon. - -If the "Directory Browsing" is not installed, this is Not Applicable. - -Under the "Actions" pane verify "Directory Browsing" is "Disabled". - -If "Directory Browsing" is not "Disabled", this is a finding. - false - - - /system.webServer/httpErrors - <VulnDiscussion>HTTP error pages contain information that could enable an attacker to gain access to an information system. Failure to prevent the sending of HTTP error pages with full information to remote requesters exposes internal configuration information to potential attackers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - errormode - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name under review. - -Double-click the "Error Pages" icon. - -Click each error message and click "Edit Feature" setting from the "Actions" pane. - -If any error message is not set to “Detailed errors for local requests and custom error pages for remote requests”, this is a finding. - DetailedLocalOnly - - - /system.web/compilation - <VulnDiscussion>Setting compilation debug to false ensures detailed error information does not inadvertently display during live application usage, mitigating the risk of application information being displayed to users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - debug - False - - Note: If the ".NET feature" is not installed, this check is Not Applicable. - -Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name under review. - -Double-click ".NET Compilation". - -Scroll down to the "Behavior" section and verify the value for "Debug" is set to "False". - -If the "Debug" value is not set to "False", this is a finding. - false - - - /system.web/sessionState - <VulnDiscussion>Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted application as the previously authenticated user. By closing sessions after a set period of inactivity, the web server can make certain that those sessions that are not closed through the user logging out of an application are eventually closed. - -Acceptable values are 5 minutes for high-value applications, 10 minutes for medium-value applications, and 20 minutes for low-value applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - timeout - True - '{0}' -le '00:20:00' - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Click the site name. - -Select "Configuration Editor" under the "Management" section. - -From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". - -Verify the "timeout" is set to "00:20:00 or less”, using the lowest value possible depending upon the application. -Acceptable values are 5 minutes for high-value applications, 10 minutes for medium-value applications, and 20 minutes for low-value applications. - -If "timeout" is not set to "00:20:00 or less”, this is a finding. - - - - - - - /system.webServer/asp/session - <VulnDiscussion>The HTTP protocol is a stateless protocol. To maintain a session, a session identifier is used. The session identifier is a piece of data that is used to identify a session and a user. If the session identifier is compromised by an attacker, the session can be hijacked. By encrypting the session identifier, the identifier becomes more difficult for an attacker to hijack, decrypt, and use before the session has expired.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - keepSessionIdSecure - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Access the IIS 8.5 Manager. - -Select the website being reviewed. - -Under "Management" section, double-click the "Configuration Editor" icon. - -From the "Section:" drop-down list, select “system.webServer/asp". - -Expand the "session" section. - -Verify the "keepSessionIdSecure" is set to "True". - -If the "keepSessionIdSecure" is not set to "True", this is a finding. - True - - - /system.web/httpCookies - <VulnDiscussion>A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie must be encrypted. - -When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). - -Cookies shared between the web server and the client when encrypted should not also be compressed. - -A cookie can be read by client-side scripts easily if cookie properties are not set properly. By allowing cookies to be read by the client-side scripts, information such as session identifiers could be compromised and used by an attacker who intercepts the cookie. Setting cookie properties (i.e. HttpOnly property) to disallow client-side scripts from reading cookies better protects the information inside the cookie. - - - -Satisfies: SRG-APP-000439-WSR-000154, SRG-APP-000439-SSR-000155, SRG-APP-000439-WSR-000153</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - requireSSL - False - - From the "Section:" drop-down list, select "system.web/httpCookies". -Verify the "require SSL" is set to "True". - True - - - /system.web/sessionState - <VulnDiscussion>A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie must be encrypted. - -When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). - -Cookies shared between the web server and the client when encrypted should not also be compressed. - -A cookie can be read by client-side scripts easily if cookie properties are not set properly. By allowing cookies to be read by the client-side scripts, information such as session identifiers could be compromised and used by an attacker who intercepts the cookie. Setting cookie properties (i.e. HttpOnly property) to disallow client-side scripts from reading cookies better protects the information inside the cookie. - - - -Satisfies: SRG-APP-000439-WSR-000154, SRG-APP-000439-SSR-000155, SRG-APP-000439-WSR-000153</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - compressionEnabled - False - - From the "Section:" drop-down list, select "system.web/sessionState". -Verify the "compressionEnabled" is set to "False". - False - - - - - <VulnDiscussion>A web server can be installed with functionality that, just by its nature, is not secure. Web Distributed Authoring (WebDAV) is an extension to the HTTP protocol that, when developed, was meant to allow users to create, change, and move documents on a server, typically a web server or web share. Allowing this functionality, development, and deployment is much easier for web authors. - -WebDAV is not widely used and has serious security concerns because it may allow clients to modify unauthorized files on the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Web-DAV-Publishing - Absent - False - False - - Follow the procedures below for each site hosted on the IIS 8.5 web server: - -Open the IIS 8.5 Manager. - -Select the IIS 8.5 website. - -Review the features listed under the "IIS" section. - -If the "WebDAV Authoring Rules" icon exists, this is a finding. - - - diff --git a/StigData/Processed/IISSite-8.5-1.5.xml b/StigData/Processed/IISSite-8.5-1.5.xml index 93eba3526..98aeeb8a0 100644 --- a/StigData/Processed/IISSite-8.5-1.5.xml +++ b/StigData/Processed/IISSite-8.5-1.5.xml @@ -30,11 +30,11 @@ The web server must only allow hosted application file types to be served to a u For "Handler Mappings", the ISSO must document and approve all allowable file extensions the website allows (white list) and denies (black list) by the website. The white list and black list will be compared to the "Handler Mappings" in IIS 8.5. "Handler Mappings" at the site level take precedence over "Handler Mappings" at the server level. -Follow the procedures below for each site hosted on the IIS 8.5 web server: +Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. -Double-click "Request Filtering". +Double-click "Request Filtering". If any file name extensions from the black list have "Allowed" set to "True", this is a finding. @@ -71,7 +71,7 @@ Click the site name under review. Double-click "Default Document". -In the "Actions" pane, verify the "Default Document" feature is enabled. +In the "Actions" pane, verify the "Default Document" feature is enabled. If an "Enable" option is listed under the "Actions" pane, the "Default Document" feature is not enabled and this is a finding. @@ -398,7 +398,7 @@ Select the "Fields" button. Under "Standard Fields", verify "User Agent", "User Name" and "Referrer" are selected. -Under "Custom Fields", verify the following fields have been configured: +Under "Custom Fields", verify the following fields have been configured: Server Variable >> HTTP_USER_AGENT @@ -434,7 +434,7 @@ Review the results and verify the value is greater than zero for the "maxconnect If the maxconnections parameter is set to zero, this is a finding. - <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. Ascertaining the correct source, e.g. source IP, of the events is important during forensic analysis. Correctly determining the source of events will add information to the overall reconstruction of the logable event. By determining the source of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the source occurred in other areas within the enterprise. @@ -622,7 +622,7 @@ If any Application Pools are being used for more than one website, this is a fin False False - Determine whether scripts are used on the web server for the target website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. + Determine whether scripts are used on the web server for the target website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. All interactive programs must be placed in unique designated folders based on CGI or ASP script type. @@ -694,29 +694,29 @@ If files with these extensions are found, this is a finding. Note: This requirement is only applicable for private DoD websites. -If a banner is required, the following banner page must be in place: +If a banner is required, the following banner page must be in place: -“You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. +“You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. -By using this IS (which includes any device attached to this IS), you consent to the following conditions: +By using this IS (which includes any device attached to this IS), you consent to the following conditions: --The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -- At any time, the USG may inspect and seize data stored on this IS. +- At any time, the USG may inspect and seize data stored on this IS. -- Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. +- Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -- This IS includes security measures (e.g., authentication and access controls) to protect USG interests—not for your personal benefit or privacy. +- This IS includes security measures (e.g., authentication and access controls) to protect USG interests—not for your personal benefit or privacy. -- Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.” +- Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.” -OR +OR -If your system cannot meet the character limits to store this amount of text in the banner, the following is another option for the warning banner: +If your system cannot meet the character limits to store this amount of text in the banner, the following is another option for the warning banner: -"I've read & consent to terms in IS user agreem't." +"I've read & consent to terms in IS user agreem't." -NOTE: While DoDI 8500.01 does not contain a copy of the banner to be used, it does point to the RMF Knowledge Service for a copy of the required text. It is also noted that the banner is to be displayed only once when the individual enters the site and not for each page. +NOTE: While DoDI 8500.01 does not contain a copy of the banner to be used, it does point to the RMF Knowledge Service for a copy of the required text. It is also noted that the banner is to be displayed only once when the individual enters the site and not for each page. If the access-controlled website does not display this banner page before entry, this is a finding. @@ -904,9 +904,9 @@ If the "Clients Certificate Required" check box is not selected, this is a findi <VulnDiscussion>When data is written to digital media, such as hard drives, mobile computers, external/removable hard drives, personal digital assistants, flash/thumb drives, etc., there is risk of data loss and data compromise. User identities and passwords stored on the hard drive of the hosting hardware must be encrypted to protect the data from easily being discovered and used by an unauthorized user to access the hosted applications. The cryptographic libraries and functionality used to store and retrieve the user identifiers and passwords must be part of the web server. -Preventing the disclosure of transmitted information requires that the web server take measures to employ some form of cryptographic mechanism in order to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS). +Preventing the disclosure of transmitted information requires that the web server take measures to employ some form of cryptographic mechanism in order to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS). -Transmission of data can take place between the web server and a large number of devices/applications external to the web server. Examples are a web client used by a user, a backend database, an audit server, or other web servers in a web cluster. +Transmission of data can take place between the web server and a large number of devices/applications external to the web server. Examples are a web client used by a user, a backend database, an audit server, or other web servers in a web cluster. If data is transmitted unencrypted, the data then becomes vulnerable to disclosure. The disclosure may reveal user identifier/password combinations, website code revealing business logic, or other user personal information. @@ -943,13 +943,13 @@ If the "sslFlags" is not set to "ssl128", this is a finding. <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. -An example of this would be an SMTP queue. This queue may be added to a web server through an SMTP module to enhance error reporting or to allow developers to add SMTP functionality to their applications. +An example of this would be an SMTP queue. This queue may be added to a web server through an SMTP module to enhance error reporting or to allow developers to add SMTP functionality to their applications. Any modules used by the web server that queue data before transmission must maintain the confidentiality and integrity of the information before the data is transmitted. -Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. +Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. -Protecting the confidentiality and integrity of received information requires that application servers take measures to employ approved cryptography in order to protect the information during transmission over the network. This is usually achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPsec tunnel. +Protecting the confidentiality and integrity of received information requires that application servers take measures to employ approved cryptography in order to protect the information during transmission over the network. This is usually achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPsec tunnel. The web server must utilize approved encryption when receiving transmitted data. @@ -1182,7 +1182,7 @@ If the ".NET Trust Level" is not set to Full or less, this is a finding. By being able to guess session IDs, an attacker can easily perform a man-in-the-middle attack. To truly generate random session identifiers that cannot be reproduced, the web server session ID generator, when used twice with the same input criteria, must generate an unrelated random ID. The session ID generator also needs to be a FIPS 140-2-approved generator.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - + V-76775 False mode False @@ -1440,9 +1440,9 @@ If the "keepSessionIdSecure" is not set to "True", this is a finding. /system.web/httpCookies - <VulnDiscussion>A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie must be encrypted. + <VulnDiscussion>A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie must be encrypted. -When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). +When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). Cookies shared between the web server and the client when encrypted should not also be compressed. @@ -1462,9 +1462,9 @@ Verify the "require SSL" is set to "True". /system.web/sessionState - <VulnDiscussion>A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie must be encrypted. + <VulnDiscussion>A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie must be encrypted. -When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). +When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). Cookies shared between the web server and the client when encrypted should not also be compressed. diff --git a/StigData/Processed/IISSite-8.5-1.6.xml b/StigData/Processed/IISSite-8.5-1.6.xml index cffae4a49..f8caa79e0 100644 --- a/StigData/Processed/IISSite-8.5-1.6.xml +++ b/StigData/Processed/IISSite-8.5-1.6.xml @@ -30,11 +30,11 @@ The web server must only allow hosted application file types to be served to a u For "Handler Mappings", the ISSO must document and approve all allowable file extensions the website allows (white list) and denies (black list) by the website. The white list and black list will be compared to the "Handler Mappings" in IIS 8.5. "Handler Mappings" at the site level take precedence over "Handler Mappings" at the server level. -Follow the procedures below for each site hosted on the IIS 8.5 web server: +Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. -Double-click "Request Filtering". +Double-click "Request Filtering". If any file name extensions from the black list have "Allowed" set to "True", this is a finding. @@ -71,7 +71,7 @@ Click the site name under review. Double-click "Default Document". -In the "Actions" pane, verify the "Default Document" feature is enabled. +In the "Actions" pane, verify the "Default Document" feature is enabled. If an "Enable" option is listed under the "Actions" pane, the "Default Document" feature is not enabled and this is a finding. @@ -388,7 +388,7 @@ Select the "Fields" button. Under "Standard Fields", verify "User Agent", "User Name" and "Referrer" are selected. -Under "Custom Fields", verify the following fields have been configured: +Under "Custom Fields", verify the following fields have been configured: Server Variable >> HTTP_USER_AGENT @@ -422,7 +422,7 @@ Review the results and verify the value is greater than zero for the "maxconnect If the maxconnections parameter is set to zero, this is a finding. - <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. Ascertaining the correct source, e.g. source IP, of the events is important during forensic analysis. Correctly determining the source of events will add information to the overall reconstruction of the logable event. By determining the source of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the source occurred in other areas within the enterprise. @@ -603,7 +603,7 @@ If any Application Pools are being used for more than one website, this is a fin False False - Determine whether scripts are used on the web server for the target website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. + Determine whether scripts are used on the web server for the target website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. All interactive programs must be placed in unique designated folders based on CGI or ASP script type. @@ -675,29 +675,29 @@ If files with these extensions are found, this is a finding. Note: This requirement is only applicable for private DoD websites. -If a banner is required, the following banner page must be in place: +If a banner is required, the following banner page must be in place: -“You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. +“You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. -By using this IS (which includes any device attached to this IS), you consent to the following conditions: +By using this IS (which includes any device attached to this IS), you consent to the following conditions: --The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -- At any time, the USG may inspect and seize data stored on this IS. +- At any time, the USG may inspect and seize data stored on this IS. -- Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. +- Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -- This IS includes security measures (e.g., authentication and access controls) to protect USG interests—not for your personal benefit or privacy. +- This IS includes security measures (e.g., authentication and access controls) to protect USG interests—not for your personal benefit or privacy. -- Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.” +- Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.” -OR +OR -If your system cannot meet the character limits to store this amount of text in the banner, the following is another option for the warning banner: +If your system cannot meet the character limits to store this amount of text in the banner, the following is another option for the warning banner: -"I've read & consent to terms in IS user agreem't." +"I've read & consent to terms in IS user agreem't." -NOTE: While DoDI 8500.01 does not contain a copy of the banner to be used, it does point to the RMF Knowledge Service for a copy of the required text. It is also noted that the banner is to be displayed only once when the individual enters the site and not for each page. +NOTE: While DoDI 8500.01 does not contain a copy of the banner to be used, it does point to the RMF Knowledge Service for a copy of the required text. It is also noted that the banner is to be displayed only once when the individual enters the site and not for each page. If the access-controlled website does not display this banner page before entry, this is a finding. @@ -880,9 +880,9 @@ If the "Clients Certificate Required" check box is not selected, this is a findi <VulnDiscussion>When data is written to digital media, such as hard drives, mobile computers, external/removable hard drives, personal digital assistants, flash/thumb drives, etc., there is risk of data loss and data compromise. User identities and passwords stored on the hard drive of the hosting hardware must be encrypted to protect the data from easily being discovered and used by an unauthorized user to access the hosted applications. The cryptographic libraries and functionality used to store and retrieve the user identifiers and passwords must be part of the web server. -Preventing the disclosure of transmitted information requires that the web server take measures to employ some form of cryptographic mechanism in order to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS). +Preventing the disclosure of transmitted information requires that the web server take measures to employ some form of cryptographic mechanism in order to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS). -Transmission of data can take place between the web server and a large number of devices/applications external to the web server. Examples are a web client used by a user, a backend database, an audit server, or other web servers in a web cluster. +Transmission of data can take place between the web server and a large number of devices/applications external to the web server. Examples are a web client used by a user, a backend database, an audit server, or other web servers in a web cluster. If data is transmitted unencrypted, the data then becomes vulnerable to disclosure. The disclosure may reveal user identifier/password combinations, website code revealing business logic, or other user personal information. @@ -909,13 +909,13 @@ If the "sslFlags" is not set to "ssl128", this is a finding. <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. -An example of this would be an SMTP queue. This queue may be added to a web server through an SMTP module to enhance error reporting or to allow developers to add SMTP functionality to their applications. +An example of this would be an SMTP queue. This queue may be added to a web server through an SMTP module to enhance error reporting or to allow developers to add SMTP functionality to their applications. Any modules used by the web server that queue data before transmission must maintain the confidentiality and integrity of the information before the data is transmitted. -Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. +Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. -Protecting the confidentiality and integrity of received information requires that application servers take measures to employ approved cryptography in order to protect the information during transmission over the network. This is usually achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPsec tunnel. +Protecting the confidentiality and integrity of received information requires that application servers take measures to employ approved cryptography in order to protect the information during transmission over the network. This is usually achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPsec tunnel. The web server must utilize approved encryption when receiving transmitted data. @@ -924,7 +924,7 @@ Also satisfies: SRG-APP-000442-WSR-000182</VulnDiscussion><FalsePositiv False False - Check: + Check: Note: If SSL is installed on load balancer through which traffic is routed to the IIS 8.5 server, and the IIS 8.5 server ONLY receives traffic from the load balancer, the SSL requirement must be met on the load balancer. Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -1139,7 +1139,7 @@ If the ".NET Trust Level" is not set to Full or less, this is a finding. By being able to guess session IDs, an attacker can easily perform a man-in-the-middle attack. To truly generate random session identifiers that cannot be reproduced, the web server session ID generator, when used twice with the same input criteria, must generate an unrelated random ID. The session ID generator also needs to be a FIPS 140-2-approved generator.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - + V-76775 False mode False @@ -1397,9 +1397,9 @@ If the "keepSessionIdSecure" is not set to "True", this is a finding. /system.web/httpCookies - <VulnDiscussion>A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie must be encrypted. + <VulnDiscussion>A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie must be encrypted. -When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). +When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). Cookies shared between the web server and the client when encrypted should not also be compressed. @@ -1419,9 +1419,9 @@ Verify the "require SSL" is set to "True". /system.web/sessionState - <VulnDiscussion>A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie must be encrypted. + <VulnDiscussion>A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the client during the session. The cookie will contain the session identifier (ID) and may contain authentication data to the hosted application. To protect this data from easily being compromised, the cookie must be encrypted. -When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). +When a cookie is sent encrypted via SSL/TLS, an attacker must spend a great deal of time and resources to decrypt the cookie. If, along with encryption, the cookie is compressed, the attacker can now use a combination of plaintext injection and inadvertent information leakage through data compression to reduce the time needed to decrypt the cookie. This attack is called Compression Ratio Info-leak Made Easy (CRIME). Cookies shared between the web server and the client when encrypted should not also be compressed. diff --git a/StigData/Processed/WindowsServer-2012R2-DNS-1.10.org.default.xml b/StigData/Processed/WindowsDnsServer-2012R2-1.10.org.default.xml similarity index 100% rename from StigData/Processed/WindowsServer-2012R2-DNS-1.10.org.default.xml rename to StigData/Processed/WindowsDnsServer-2012R2-1.10.org.default.xml diff --git a/StigData/Processed/WindowsServer-2012R2-DNS-1.10.xml b/StigData/Processed/WindowsDnsServer-2012R2-1.10.xml similarity index 100% rename from StigData/Processed/WindowsServer-2012R2-DNS-1.10.xml rename to StigData/Processed/WindowsDnsServer-2012R2-1.10.xml diff --git a/StigData/Processed/WindowsServer-2012R2-DNS-1.11.org.default.xml b/StigData/Processed/WindowsDnsServer-2012R2-1.11.org.default.xml similarity index 100% rename from StigData/Processed/WindowsServer-2012R2-DNS-1.11.org.default.xml rename to StigData/Processed/WindowsDnsServer-2012R2-1.11.org.default.xml diff --git a/StigData/Processed/WindowsServer-2012R2-DNS-1.11.xml b/StigData/Processed/WindowsDnsServer-2012R2-1.11.xml similarity index 99% rename from StigData/Processed/WindowsServer-2012R2-DNS-1.11.xml rename to StigData/Processed/WindowsDnsServer-2012R2-1.11.xml index 4c35c433c..2158a71f3 100644 --- a/StigData/Processed/WindowsServer-2012R2-DNS-1.11.xml +++ b/StigData/Processed/WindowsDnsServer-2012R2-1.11.xml @@ -122,7 +122,7 @@ Verify "Errors and warnings" or "All events" is selected. If any option other than "Errors and warnings" or "All events" is selected, this is a finding. For Windows 2012 R2 DNS Server, the Enhanced DNS logging and diagnostics in Windows Server 2012 R2 must also be enabled. - + Run eventvwr.msc at an elevated command prompt. In the Event viewer, navigate to the applications and Services Logs\Microsoft\Windows\DNS Server. @@ -182,7 +182,7 @@ Verify "Errors and warnings" or "All events" is selected. If any option other than "Errors and warnings" or "All events" is selected, this is a finding. For Windows 2012 R2 DNS Server, the Enhanced DNS logging and diagnostics in Windows Server 2012 R2 must also be enabled. - + Run eventvwr.msc at an elevated command prompt. In the Event viewer, navigate to the applications and Services Logs\Microsoft\Windows\DNS Server. @@ -212,7 +212,7 @@ Verify "Errors and warnings" or "All events" is selected. If any option other than "Errors and warnings" or "All events" is selected, this is a finding. For Windows 2012 R2 DNS Server, the Enhanced DNS logging and diagnostics in Windows Server 2012 R2 must also be enabled. - + Run eventvwr.msc at an elevated command prompt. In the Event viewer, navigate to the applications and Services Logs\Microsoft\Windows\DNS Server. @@ -242,7 +242,7 @@ Verify "Errors and warnings" or "All events" is selected. If any option other than "Errors and warnings" or "All events" is selected, this is a finding. For Windows 2012 R2 DNS Server, the Enhanced DNS logging and diagnostics in Windows Server 2012 R2 must also be enabled. - + Run eventvwr.msc at an elevated command prompt. In the Event viewer, navigate to the applications and Services Logs\Microsoft\Windows\DNS Server. @@ -272,8 +272,8 @@ Verify "Errors and warnings" or "All events" is selected. If any option other than "Errors and warnings" or "All events" is selected, this is a finding. For Windows 2012 R2 DNS Server, the Enhanced DNS logging and diagnostics in Windows Server 2012 R2 must also be enabled. - -Run eventvwr.msc at an elevated command prompt. + +Run eventvwr.msc at an elevated command prompt. In the Event viewer, navigate to the applications and Services Logs\Microsoft\Windows\DNS Server. @@ -323,7 +323,7 @@ Press Windows Key + R, execute dnsmgmt.msc. On the opened DNS Manager snap-in from the left pane, expand the server name for the DNS server, and then expand Forward Lookup Zones. From the expanded list, click to select the zone. - + Confirm with the DNS administrator that the hosts defined in the zone files do not resolve to hosts in another zone with its fully qualified domain name. The exceptions are glue records supporting zone delegations, CNAME records supporting a system migration, or CNAME records that point to third-party Content Delivery Networks (CDN) or cloud computing platforms. In the case of third-party CDNs or cloud offerings, an approved mission need must be demonstrated. Additional exceptions are CNAME records in a multi-domain Active Directory environment pointing to hosts in other internal domains in the same multi-domain environment. @@ -501,10 +501,10 @@ Open an elevated Windows PowerShell prompt on a DNS server using the Domain Admi Use the “Get-DnsServerDiagnostics” cmdlet to view the status of individual diagnostic events. Verify following diagnostic events are set to "True": -Queries, Answers, Notifications, Update, QuestionTransactions, UnmatcheResponse, SendPackets, ReceivePackets, TcpPackets, UdpPackets, FullPackets, UseSystemEventLog -Also set to “True” should be: +Queries, Answers, Notifications, Update, QuestionTransactions, UnmatcheResponse, SendPackets, ReceivePackets, TcpPackets, UdpPackets, FullPackets, UseSystemEventLog +Also set to “True” should be: EnableLoggingForLocalLookupEvent -EnableLoggingForPluginDLLEvent +EnableLoggingForPluginDLLEvent EnableLoggingForRecursiveLookupEvent EnableLoggingForRemoteServerEvent EnableLoggingForRemoteServerEvent @@ -583,9 +583,9 @@ Press Windows Key + R, execute dnsmgmt.msc. On the opened DNS Manager snap-in from the left pane, expand the server name for the DNS server, and then expand Forward Lookup Zones. -From the expanded list, click to select the zone. +From the expanded list, click to select the zone. -View the validity period for the DS Resource Record. +View the validity period for the DS Resource Record. If the validity period for the DS Resource Record for the child domain is less than two days (48 hours) or more than one week (168 hours), this is a finding. @@ -593,7 +593,7 @@ If the validity period for the DS Resource Record for the child domain is less t False False - Windows 2008 DNS Servers that are Active Directory integrated must be located where required to meet the Active Directory services. + Windows 2008 DNS Servers that are Active Directory integrated must be located where required to meet the Active Directory services. If all of the Windows 2008 DNS Servers are AD integrated, this check is Not Applicable. @@ -687,9 +687,9 @@ Right-click the zone and select DNSSEC, Properties. Select the KSK Tab. -Verify the "DNSKEY signature validity period (hours):” is set to at least 48 hours and no more than 168 hours. +Verify the "DNSKEY signature validity period (hours):” is set to at least 48 hours and no more than 168 hours. -Select the ZSK Tab. +Select the ZSK Tab. Verify the "DNSKEY signature validity period (hours):" is set to at least 48 hours and no more than 168 hours. If either the KSK or ZSK Tab "DNSKEY signature validity period (hours):" values are set to less than 48 hours or more than 168 hours, this is a finding. @@ -705,7 +705,7 @@ Log on to the DNS server using the Domain Admin or Enterprise Admin account. Open an elevated Windows PowerShell prompt on a DNS server using the Domain Admin or Enterprise Admin account. -Type the following command: +Type the following command: PS C:\> Get-DnsServerResourceRecord -ZoneName example.com <enter> @@ -739,10 +739,10 @@ At a command prompt on any system, type: nslookup <enter>; -At the nslookup prompt, type: +At the nslookup prompt, type: server=###.###.###.### <enter>; -(where the ###.###.###.### is replaced by the IP of each NS record) +(where the ###.###.###.### is replaced by the IP of each NS record) Enter a FQDN for a known host record in the zone. @@ -778,7 +778,7 @@ From the expanded list, click to select the zone. Review the SOA information for the zone and obtain the Serial Number. Access each secondary name server for the same zone and review the SOA information. - + Verify the Serial Number is the same on all authoritative name servers. If the Serial Number is not the same on one or more authoritative name servers, this is a finding. @@ -796,8 +796,8 @@ Press Windows Key + R, execute dnsmgmt.msc. On the opened DNS Manager snap-in from the left pane, expand the server name for the DNS server, and then expand Forward Lookup Zones. From the expanded list, click to select each zone. - -Review the RRs for each zone and verify all of the DNSEC record types are included for the zone. + +Review the RRs for each zone and verify all of the DNSEC record types are included for the zone. NOTE: The DS (Delegation Signer)record should also exist but the requirement for it is validated under WDNS-SC-000011. @@ -819,7 +819,7 @@ Press Windows Key + R, execute dnsmgmt.msc. On the opened DNS Manager snap-in from the left pane, expand the server name for the DNS server, and then expand Forward Lookup Zones. -From the expanded list, click to select the zone. +From the expanded list, click to select the zone. Review the zone's RRs in the right window pane. @@ -1067,7 +1067,7 @@ Click “Connection Security Rules”. Confirm at least one rule is configured for TCP 53. -Double-click on each Rule to verify the following: +Double-click on each Rule to verify the following: On the “Authentication” tab, "Authentication mode:" is set to "Request authentication for inbound and outbound connections". @@ -1205,7 +1205,7 @@ If the results do not show the RRSIG and signature information, this is a findin Access Services on the Windows DNS Server and locate the DNS Server Service. -Determine the account under which the DNS Server Service is running. +Determine the account under which the DNS Server Service is running. Access Windows Explorer. @@ -1247,7 +1247,7 @@ Press Windows Key + R, execute dnsmgmt.msc. On the opened DNS Manager snap-in from the left pane, expand the server name for the DNS Server, and then expand Forward Lookup Zones. -From the expanded list, click to select the zone. +From the expanded list, click to select the zone. Review the zone's RRs in the right window pane. @@ -1527,7 +1527,7 @@ Press Windows Key + R, execute dnsmgmt.msc. On the opened DNS Manager snap-in from the left pane, expand the server name for the DNS server, and then expand Forward Lookup Zones. -From the expanded list, click to select the zone. +From the expanded list, click to select the zone. Review the records for the zone and ensure the complete RRSet of records are present: RRSIG, NSEC3, DNSKEY, indicating DNSSEC compliance. @@ -1806,7 +1806,7 @@ If the results do not show the RRSIG and signature information, this is a findin False NOTE: This requirement applies to any Windows 2012 DNS Servers which host non-AD-integrated zones (file based) even if the DNS servers host AD-integrated zones, too. - + If the Windows 2012 DNS Servers only host AD-integrated zones, this requirement is not applicable. To protect authenticity of zone transfers between Windows 2012 DNS Servers with file based zones, IPsec must be configured on each pair of name servers in a zone transfer transaction for those zones. @@ -1830,7 +1830,7 @@ If Rules exist, double-click on each Rule to verify the following: For the "Authentication:" tab, click on the "Customize..." button. On the Authentication tab, verify "Authentication mode:" is set to "Request authentication for inbound and outbound connections". - + Confirm the "Signing Algorithm" is set to "RSA (default)". Under "Method", ensure the "Advanced:" radio button is selected. @@ -1942,7 +1942,7 @@ Fix Text: Sign, or re-sign, the hosted zone(s) on the DNS server being validated In the DNS Manager console tree on the DNS server being validated, navigate to Forward Lookup Zones. -Right-click the zone (repeat for each hosted zone), point to DNSSEC, and then click Sign the Zone, either using saved parameters or custom parameters. +Right-click the zone (repeat for each hosted zone), point to DNSSEC, and then click Sign the Zone, either using saved parameters or custom parameters. @@ -1971,7 +1971,7 @@ Double-click on each Rule to verify the following: For the "Authentication:" tab, click on the "Customize..." button. On the Authentication tab, verify "Authentication mode:" is set to "Request authentication for inbound and outbound connections". - + Confirm the "Signing Algorithm" is set to "RSA (default)". Under "Method", ensure the "Advanced:" radio button is selected. Click on the "Customize" button. @@ -1990,7 +1990,7 @@ If the certificate used does not meet the requirements, this is a finding. To ensure the cryptographic keys are protected after being backed up to another medium (tape, disk, SAN, etc.), consult with the System Administrator to determine the backup policy in place for the DNS Server. -Determine how and where backed up data is being stored. +Determine how and where backed up data is being stored. Verify the protection of the backup medium is secured to the same level, or higher, as the server itself. @@ -2272,9 +2272,9 @@ If any accounts or groups other than the following are granted the "Manage audit Administrators Auditors (if the site has an Auditors group that further limits this privilege.) -If an application requires this user right, this would not be a finding. -Vendor documentation must support the requirement for having the user right. -The requirement must be documented with the ISSO. +If an application requires this user right, this would not be a finding. +Vendor documentation must support the requirement for having the user right. +The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords. Verify the permissions on the DNS logs. @@ -2352,9 +2352,9 @@ If any accounts or groups other than the following are granted the "Manage audit Administrators Auditors (if the site has an Auditors group that further limits this privilege.) -If an application requires this user right, this would not be a finding. -Vendor documentation must support the requirement for having the user right. -The requirement must be documented with the ISSO. +If an application requires this user right, this would not be a finding. +Vendor documentation must support the requirement for having the user right. +The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords. Verify the permissions on the DNS logs. @@ -2442,13 +2442,13 @@ If any option other than "Errors and warnings" or "All events" is selected, this For Windows 2012 R2 DNS Server, the Enhanced DNS logging and diagnostics in Windows Server 2012 R2 must also be enabled. -Run “eventvwr.msc” at an elevated command prompt. +Run “eventvwr.msc” at an elevated command prompt. In the Event viewer, navigate to the applications and Services Logs\Microsoft\Windows\DNS Server. Right-click on the DNS Server, point to View, and then click "Show Analytic and Debug Logs". -Right-click on Analytical and then click “Properties”. +Right-click on Analytical and then click “Properties”. Confirm the "Enable logging" check box is selected. diff --git a/StigData/Processed/WindowsServer-2012R2-DNS-1.9.org.default.xml b/StigData/Processed/WindowsDnsServer-2012R2-1.9.org.default.xml similarity index 100% rename from StigData/Processed/WindowsServer-2012R2-DNS-1.9.org.default.xml rename to StigData/Processed/WindowsDnsServer-2012R2-1.9.org.default.xml diff --git a/StigData/Processed/WindowsServer-2012R2-DNS-1.9.xml b/StigData/Processed/WindowsDnsServer-2012R2-1.9.xml similarity index 100% rename from StigData/Processed/WindowsServer-2012R2-DNS-1.9.xml rename to StigData/Processed/WindowsDnsServer-2012R2-1.9.xml diff --git a/StigData/Schema/PowerStig.xsd b/StigData/Schema/PowerStig.xsd index 019e74cb0..59ed6a929 100644 --- a/StigData/Schema/PowerStig.xsd +++ b/StigData/Schema/PowerStig.xsd @@ -323,6 +323,29 @@ + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Tests/Integration/DSCResources/.tests.header.ps1 b/Tests/Integration/DSCResources/.tests.header.ps1 index bc24e5f64..95c1760fe 100644 --- a/Tests/Integration/DSCResources/.tests.header.ps1 +++ b/Tests/Integration/DSCResources/.tests.header.ps1 @@ -11,6 +11,7 @@ if ( (-not (Test-Path -Path (Join-Path -Path $script:moduleRoot -ChildPath 'DSCR Import-Module (Join-Path -Path $script:moduleRoot -ChildPath 'Tools\TestHelper\TestHelper.psm1' ) -Force Import-Module (Join-Path -Path $script:moduleRoot -ChildPath 'DSCResource.Tests\TestHelper.psm1') -Force +[Diagnostics.CodeAnalysis.SuppressMessageAttribute("PSUseDeclaredVarsMoreThanAssignments",'')] $TestEnvironment = Initialize-TestEnvironment ` -DSCModuleName $script:DSCModuleName ` -DSCResourceName $script:DSCCompositeResourceName ` diff --git a/Tests/Integration/DSCResources/Common.integration.ps1 b/Tests/Integration/DSCResources/Common.integration.ps1 index b7886e257..58f4ef5d0 100644 --- a/Tests/Integration/DSCResources/Common.integration.ps1 +++ b/Tests/Integration/DSCResources/Common.integration.ps1 @@ -2,147 +2,162 @@ This file is dot sourced into every composite. It consolidates testing of exceptions, skipped rules, and organizational objects that were provided to the composite #> -Describe "$($stig.Technology) $($stig.TechnologyVersion) $($stig.TechnologyRole) $($stig.StigVersion) mof output" { - $testhash = @{ - StigVersion = $stig.StigVersion - BrowserVersion = $stig.TechnologyVersion - OfficeApp = $stig.TechnologyVersion - OsVersion = $stig.TechnologyVersion - SqlVersion = $stig.TechnologyVersion - OsRole = $stig.TechnologyRole - SqlRole = $stig.TechnologyRole - ForestName = 'integration.test' - DomainName = 'integration.test' - Exception = $exception - ConfigPath = $configPath - OutputPath = $TestDrive - PropertiesPath = $propertiesPath - WebAppPool = $WebAppPool - WebsiteName = $WebsiteName - LogPath = $TestDrive +$title = "$($stig.Technology) $($stig.TechnologyVersion)" +if ($stig.TechnologyRole) +{ + $title = $title + " $($stig.TechnologyRole)" +} + +Describe ($title + " $($stig.StigVersion) mof output") { + + $technologyConfig = "$($script:DSCCompositeResourceName)_config" + + $testParameterList = @{ + TechnologyVersion = $stig.TechnologyVersion + TechnologyRole = $stig.TechnologyRole + StigVersion = $stig.StigVersion + OutputPath = $TestDrive + } + + # Add additional test parameters to current test configuration + if($additionalTestParameterList) + { + $testParameterList += $additionalTestParameterList } It 'Should compile the MOF without throwing' { - {& $technologyConfig @testhash} | Should -Not -Throw + {& $technologyConfig @testParameterList} | Should -Not -Throw } - <#{TODO}#> <#Add back modified version after migration $configurationDocumentPath = "$TestDrive\localhost.mof" $instances = [Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache]::ImportInstances($configurationDocumentPath, 4) - $ruleNames = (Get-Member -InputObject $DscXml.DISASTIG | - Where-Object -FilterScript {$_.Name -match '.*Rule' -and $_.Name -ne 'DocumentRule' -and $_.Name -ne 'ManualRule'}).Name + $ruleNames = (Get-Member -InputObject $powerstigXml.DISASTIG | + Where-Object -FilterScript {$_.Name -match '.*Rule' -and $_.Name -ne 'DocumentRule' -and $_.Name -ne 'ManualRule'}).Name foreach ($ruleName in $ruleNames) { Context $ruleName { - $hasAllSettings = $true - $dscXml = @($dscXml.DISASTIG.$ruleName.Rule) | - Where-Object {$PSItem.conversionstatus -eq 'pass' -and $PSItem.dscResource -ne 'ActiveDirectoryAuditRuleEntry'} + $hasAllRules = $true + $ruleList = @($powerstigXml.DISASTIG.$ruleName.Rule | + Where-Object {$PSItem.conversionstatus -eq 'pass' -and $PSItem.dscResource -ne 'ActiveDirectoryAuditRuleEntry'}) + $dscMof = $instances | - Where-Object {Get-ResourceMatchStatement -ruleName $ruleName} + Where-Object {$PSItem.ResourceID -match (Get-ResourceMatchStatement -RuleName $ruleName)} - foreach ($setting in $dscXml) + foreach ($rule in $ruleList) { - if (-not($dscMof.ResourceID -match $setting.id)) + <# + $dscMof is a collection of items, so the -not operator is used + in place of a -notmatch, since the -notmatch removes the + match from the collection. + #> + if (-not ($dscMof.ResourceID -match $rule.id)) { - Write-Warning -Message "Missing $ruleName Setting $($setting.id)" - $hasAllSettings = $false + Write-Warning -Message "Missing $ruleName $($rule.id)" + $hasAllRules = $false } } - It "Should have $($dscXml.count) $ruleName settings" { - $hasAllSettings | Should -Be $true + It "Should have $($ruleList.count) $ruleName settings" { + $hasAllRules | Should -Be $true } } } - Context 'Single Exception' { - It "Should compile the MOF with STIG exception $exception without throwing" { - {& $technologyConfig @testhash} | Should -Not -Throw - } - } + <# + Only run the detailed integration tests against one of the STIG + files to verify that all functionality is working properly. If the + functionality works for the first STIG is will work the same for + remaining because the STIG class will have been tested. - Context 'Multiple Exceptions' { - $testhash.exception = $exceptionMultiple - It "Should compile the MOF with STIG exceptions $exceptionMultiple without throwing" { - {& $technologyConfig @testhash} | Should -Not -Throw + $stigList is recast as an array incase a single item is returned + #> + if (@($stigList).IndexOf($stig) -le '0') + { + Context 'Single Exception' { + It "Should compile the MOF with STIG exception $exception without throwing" { + {& $technologyConfig @testParameterList -Exception $exception} | Should -Not -Throw + } } - } - Context 'Single Rule' { - It 'Should compile the MOF without throwing' { - {& $technologyConfig @testhash -SkipRule $skipRule } | Should -Not -Throw + Context 'Multiple Exceptions' { + It "Should compile the MOF with STIG exceptions $exceptionMultiple without throwing" { + {& $technologyConfig @testParameterList -Exception $exceptionMultiple} | Should -Not -Throw + } } - # Gets the mof content - $configurationDocumentPath = "$TestDrive\localhost.mof" - $instances = [Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache]::ImportInstances($configurationDocumentPath, 4) + Context 'Single Rule' { + It 'Should compile the MOF without throwing' { + {& $technologyConfig @testParameterList -SkipRule $skipRule } | Should -Not -Throw + } - # Counts how many skips there are and how many there should be. - $dscXml = $skipRule.count - $dscMof = @($instances | Where-Object -FilterScript {$PSItem.ResourceID -match "\[Skip\]"}) + # Gets the mof content + $configurationDocumentPath = "$TestDrive\localhost.mof" + $instances = [Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache]::ImportInstances($configurationDocumentPath, 4) - It "Should have $dscXml Skipped settings" { - $dscMof.count | Should -Be $dscXml - } - } + $dscMof = @($instances | Where-Object -FilterScript {$PSItem.ResourceID -match "\[Skip\]"}) - Context 'Multiple Rules' { - It 'Should compile the MOF without throwing' { - {& $technologyConfig @testhash -SkipRule $skipRuleMultiple} | Should -Not -Throw + It "Should have $($skipRule.count) Skipped settings" { + $dscMof.count | Should -Be $skipRule.count + } } - # Gets the mof content - $configurationDocumentPath = "$TestDrive\localhost.mof" - $instances = [Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache]::ImportInstances($configurationDocumentPath, 4) + Context 'Multiple Rules' { + It 'Should compile the MOF without throwing' { + {& $technologyConfig @testParameterList -SkipRule $skipRuleMultiple} | Should -Not -Throw + } - # Counts how many Skips there are and how many there should be. - $expectedSkipRuleCount = $skipRuleMultiple.count - $dscMof = $instances | Where-Object -FilterScript {$PSItem.ResourceID -match "\[Skip\]"} + # Gets the mof content + $configurationDocumentPath = "$TestDrive\localhost.mof" + $instances = [Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache]::ImportInstances($configurationDocumentPath, 4) - It "Should have $expectedSkipRuleCount Skipped settings" { - $dscMof.count | Should -Be $expectedSkipRuleCount - } - } + # Counts how many Skips there are and how many there should be. + $expectedSkipRuleCount = $skipRuleMultiple.count + $dscMof = $instances | Where-Object -FilterScript {$PSItem.ResourceID -match "\[Skip\]"} - Context "$($stig.TechnologyRole) $($stig.StigVersion) Single Type" { - It "Should compile the MOF without throwing" { - {& $technologyConfig @testhash -SkipruleType $skipRuleType} | Should -Not -Throw + It "Should have $expectedSkipRuleCount Skipped settings" { + $dscMof.count | Should -Be $expectedSkipRuleCount + } } - # Gets the mof content - $configurationDocumentPath = "$TestDrive\localhost.mof" - $instances = [Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache]::ImportInstances($configurationDocumentPath, 4) - # Counts how many Skips there are and how many there should be. - $dscMof = $instances | Where-Object -FilterScript {$PSItem.ResourceID -match "\[Skip\]"} + Context "$($stig.TechnologyRole) $($stig.StigVersion) Single Type" { + It "Should compile the MOF without throwing" { + {& $technologyConfig @testParameterList -SkipRuleType $skipRuleType} | Should -Not -Throw + } + # Gets the mof content + $configurationDocumentPath = "$TestDrive\localhost.mof" + $instances = [Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache]::ImportInstances($configurationDocumentPath, 4) - It "Should have $expectedSkipRuleTypeCount Skipped settings" { - $dscMof.count | Should -Be $expectedSkipRuleTypeCount - } - } + # Counts how many Skips there are and how many there should be. + $dscMof = $instances | Where-Object -FilterScript {$PSItem.ResourceID -match "\[Skip\]"} - Context 'Multiple Types' { - It "Should compile the MOF without throwing" { - {& $technologyConfig @testhash -SkipruleType $skipRuleTypeMultiple} | Should -Not -Throw + It "Should have $expectedSkipRuleTypeCount Skipped settings" { + $dscMof.count | Should -Be $expectedSkipRuleTypeCount + } } - # Gets the mof content - $configurationDocumentPath = "$TestDrive\localhost.mof" - $instances = [Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache]::ImportInstances($configurationDocumentPath, 4) - # Counts how many Skips there are and how many there should be. - $dscMof = $instances | Where-Object -FilterScript {$PSItem.ResourceID -match "\[Skip\]"} + Context 'Multiple Types' { + It "Should compile the MOF without throwing" { + {& $technologyConfig @testParameterList -SkipruleType $skipRuleTypeMultiple} | Should -Not -Throw + } + # Gets the mof content + $configurationDocumentPath = "$TestDrive\localhost.mof" + $instances = [Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache]::ImportInstances($configurationDocumentPath, 4) + + # Counts how many Skips there are and how many there should be. + $dscMof = $instances | Where-Object -FilterScript {$PSItem.ResourceID -match "\[Skip\]"} - It "Should have $expectedSkipRuleTypeMultipleCount Skipped settings" { - $dscMof.count | Should -Be $expectedSkipRuleTypeMultipleCount + It "Should have $expectedSkipRuleTypeMultipleCount Skipped settings" { + $dscMof.count | Should -Be $expectedSkipRuleTypeMultipleCount + } } - } - #> - $stigPath = $stig.path.TrimEnd(".xml") - $orgSettings = $stigPath + ".org.default.xml" + $stigPath = $stig.path.TrimEnd(".xml") + $orgSettings = $stigPath + ".org.default.xml" - It "Should compile the MOF with OrgSettings without throwing" { - {& $technologyConfig @testhash -Orgsettings $orgSettings} | Should -Not -Throw + It "Should compile the MOF with OrgSettings without throwing" { + {& $technologyConfig @testParameterList -Orgsettings $orgSettings} | Should -Not -Throw + } } } diff --git a/Tests/Integration/DSCResources/DotNetFramework.integration.tests.ps1 b/Tests/Integration/DSCResources/DotNetFramework.integration.tests.ps1 index 885c20ba6..687e4703f 100644 --- a/Tests/Integration/DSCResources/DotNetFramework.integration.tests.ps1 +++ b/Tests/Integration/DSCResources/DotNetFramework.integration.tests.ps1 @@ -5,58 +5,55 @@ $script:DSCCompositeResourceName = ($MyInvocation.MyCommand.Name -split '\.')[0] # Using try/finally to always cleanup even if something awful happens. try { - #region Integration Tests $configFile = Join-Path -Path $PSScriptRoot -ChildPath "$($script:DSCCompositeResourceName).config.ps1" . $configFile $stigList = Get-StigVersionTable -CompositeResourceName $script:DSCCompositeResourceName - #region Integration Tests foreach ($stig in $stigList) { Describe "Framework $($stig.TechnologyVersion) $($stig.StigVersion) mof output" { - It 'Should compile the MOF without throwing' { - { - & "$($script:DSCCompositeResourceName)_config" ` - -FrameworkVersion $stig.TechnologyVersion ` - -StigVersion $stig.StigVersion ` - -OutputPath $TestDrive - } | Should -Not -Throw - } + It 'Should compile the MOF without throwing' { + { + & "$($script:DSCCompositeResourceName)_config" ` + -FrameworkVersion $stig.TechnologyVersion ` + -StigVersion $stig.StigVersion ` + -OutputPath $TestDrive + } | Should -Not -Throw + } - [xml] $dscXml = Get-Content -Path $stig.Path + [xml] $dscXml = Get-Content -Path $stig.Path - if (Test-AutomatableRuleType -StigObject $dscXml) - { - $configurationDocumentPath = "$TestDrive\localhost.mof" + if (Test-AutomatableRuleType -StigObject $dscXml) + { + $configurationDocumentPath = "$TestDrive\localhost.mof" - $instances = [Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache]::ImportInstances($configurationDocumentPath, 4) + $instances = [Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache]::ImportInstances($configurationDocumentPath, 4) - Context 'Registry' { - $hasAllSettings = $true - $dscXml = @($dscXml.DISASTIG.RegistryRule.Rule) - $dscMof = $instances | - Where-Object {$PSItem.ResourceID -match "\[xRegistry\]"} + Context 'Registry' { + $hasAllSettings = $true + $dscXml = @($dscXml.DISASTIG.RegistryRule.Rule) + $dscMof = $instances | + Where-Object {$PSItem.ResourceID -match "\[xRegistry\]"} - foreach ($setting in $dscXml) - { - If (-not ($dscMof.ResourceID -match $setting.Id) ) + foreach ($setting in $dscXml) { - Write-Warning -Message "Missing registry Setting $($setting.Id)" - $hasAllSettings = $false + If (-not ($dscMof.ResourceID -match $setting.Id) ) + { + Write-Warning -Message "Missing registry Setting $($setting.Id)" + $hasAllSettings = $false + } } - } - It "Should have $($dscXml.Count) Registry settings" { - $hasAllSettings | Should Be $true + It "Should have $($dscXml.Count) Registry settings" { + $hasAllSettings | Should Be $true + } } } } } } -#endregion Tests -} finally { Restore-TestEnvironment -TestEnvironment $TestEnvironment diff --git a/Tests/Integration/DSCResources/Firefox.config.ps1 b/Tests/Integration/DSCResources/Firefox.config.ps1 index cdf8b30d4..fb0cc8abb 100644 --- a/Tests/Integration/DSCResources/Firefox.config.ps1 +++ b/Tests/Integration/DSCResources/Firefox.config.ps1 @@ -2,90 +2,35 @@ Configuration Firefox_config { param ( - [Parameter(Mandatory = $true)] - [string] - $StigVersion, - - [Parameter()] - [string[]] - $SkipRule, - - [Parameter()] - [string[]] - $SkipRuleType, - - [Parameter()] - [string[]] - $Exception, - - [Parameter()] - [string[]] - $OrgSettings, - - [Parameter()] - [AllowNull()] - [string] - $BrowserVersion, - - [Parameter()] - [AllowNull()] - [string[]] - $OfficeApp, - - [Parameter()] - [AllowNull()] - [string] - $ConfigPath, - - [Parameter()] - [AllowNull()] - [string] - $PropertiesPath, - [Parameter()] [AllowNull()] [string] - $SqlVersion, + $TechnologyVersion, [Parameter()] [AllowNull()] [string] - $SqlRole, + $TechnologyRole, - [Parameter()] - [AllowNull()] - [string] - $ForestName, - - [Parameter()] - [AllowNull()] - [string] - $DomainName, - - [Parameter()] - [AllowNull()] + [Parameter(Mandatory = $true)] [string] - $OsVersion, + $StigVersion, [Parameter()] - [AllowNull()] - [string] - $OsRole, + [string[]] + $SkipRule, [Parameter()] - [AllowNull()] [string[]] - $WebAppPool, + $SkipRuleType, [Parameter()] - [AllowNull()] [string[]] - $WebSiteName, + $Exception, [Parameter()] - [AllowNull()] - [string] - $LogPath + [string[]] + $OrgSettings ) Import-DscResource -ModuleName PowerStig @@ -102,7 +47,7 @@ Configuration Firefox_config }) $(if ($null -ne $Exception) { - "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem'= @{'Value'='1234567'}"}) -join "`n" )}" + "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem' = '1234567'"}) -join "`n" )}" }) $(if ($null -ne $SkipRule) { diff --git a/Tests/Integration/DSCResources/Firefox.integration.tests.ps1 b/Tests/Integration/DSCResources/Firefox.integration.tests.ps1 index 514b6f76d..57986bb34 100644 --- a/Tests/Integration/DSCResources/Firefox.integration.tests.ps1 +++ b/Tests/Integration/DSCResources/Firefox.integration.tests.ps1 @@ -7,34 +7,28 @@ $script:DSCCompositeResourceName = ($MyInvocation.MyCommand.Name -split '\.')[0] # Using try/finally to always cleanup even if something awful happens. try { - #region Integration Tests $configFile = Join-Path -Path $PSScriptRoot -ChildPath "$($script:DSCCompositeResourceName).config.ps1" . $configFile $stigList = Get-StigVersionTable -CompositeResourceName $script:DSCCompositeResourceName - #region Integration Tests foreach ($stig in $stigList) { - [xml] $dscXml = Get-Content -Path $stig.Path + [xml] $powerstigXml = Get-Content -Path $stig.Path - $technologyConfig = "$($script:DSCCompositeResourceName)_config" - - $skipRule = Get-Random -InputObject $dscXml.DISASTIG.FileContentRule.Rule.id + $skipRule = Get-Random -InputObject $powerstigXml.DISASTIG.FileContentRule.Rule.id $skipRuleType = $null $expectedSkipRuleTypeCount = 0 - $skipRuleMultiple = Get-Random -InputObject $dscXml.DISASTIG.FileContentRule.Rule.id -Count 2 + $skipRuleMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.FileContentRule.Rule.id -Count 2 $skipRuleTypeMultiple = $null $expectedSkipRuleTypeMultipleCount = 0 - $exception = Get-Random -InputObject $dscXml.DISASTIG.FileContentRule.Rule.id - $exceptionMultiple = Get-Random -InputObject $dscXml.DISASTIG.FileContentRule.Rule.id -Count 2 + $exception = Get-Random -InputObject $powerstigXml.DISASTIG.FileContentRule.Rule.id + $exceptionMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.FileContentRule.Rule.id -Count 2 - $userSettingsPath = "$PSScriptRoot\Common.integration.ps1" - . $userSettingsPath + . "$PSScriptRoot\Common.integration.ps1" } - #endregion Tests } finally { diff --git a/Tests/Integration/DSCResources/IisServer.config.ps1 b/Tests/Integration/DSCResources/IisServer.config.ps1 index 34469e9f2..5812d8f76 100644 --- a/Tests/Integration/DSCResources/IisServer.config.ps1 +++ b/Tests/Integration/DSCResources/IisServer.config.ps1 @@ -2,85 +2,35 @@ Configuration IisServer_Config { param ( - [Parameter(Mandatory = $true)] - [string] - $StigVersion, - - [Parameter()] - [string[]] - $SkipRule, - - [Parameter()] - [string[]] - $SkipRuleType, - - [Parameter()] - [string[]] - $Exception, - - [Parameter()] - [string[]] - $OrgSettings, - - [Parameter()] - [AllowNull()] - [string] - $BrowserVersion, - - [Parameter()] - [AllowNull()] - [string[]] - $OfficeApp, - [Parameter()] [AllowNull()] [string] - $ConfigPath, + $TechnologyVersion, [Parameter()] [AllowNull()] [string] - $PropertiesPath, + $TechnologyRole, - [Parameter()] - [AllowNull()] - [string] - $SqlVersion, - - [Parameter()] - [AllowNull()] - [string] - $SqlRole, - - [Parameter()] - [AllowNull()] - [string] - $ForestName, - - [Parameter()] - [AllowNull()] + [Parameter(Mandatory = $true)] [string] - $DomainName, + $StigVersion, [Parameter()] - [AllowNull()] - [string] - $OsVersion, + [string[]] + $SkipRule, [Parameter()] - [AllowNull()] - [string] - $OsRole, + [string[]] + $SkipRuleType, [Parameter()] - [AllowNull()] [string[]] - $WebAppPool, + $Exception, [Parameter()] - [AllowNull()] [string[]] - $WebSiteName, + $OrgSettings, [Parameter()] [AllowNull()] @@ -94,16 +44,16 @@ Configuration IisServer_Config & ([scriptblock]::Create(" IisServer ServerConfiguration { - IisVersion = '$OsVersion' + IisVersion = '$TechnologyVersion' StigVersion = '$StigVersion' - LogPath = '$LogPath' + LogPath = '$LogPath' $(if ($null -ne $OrgSettings) { "Orgsettings = '$OrgSettings'" }) $(if ($null -ne $Exception) { - "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem'= @{'Value'='1234567'}"}) -join "`n" )}" + "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem' = '1234567'"}) -join "`n" )}" }) $(if ($null -ne $SkipRule) { diff --git a/Tests/Integration/DSCResources/IisServer.integration.tests.ps1 b/Tests/Integration/DSCResources/IisServer.integration.tests.ps1 index a43592679..44d3c6465 100644 --- a/Tests/Integration/DSCResources/IisServer.integration.tests.ps1 +++ b/Tests/Integration/DSCResources/IisServer.integration.tests.ps1 @@ -7,35 +7,33 @@ $script:DSCCompositeResourceName = ($MyInvocation.MyCommand.Name -split '\.')[0] # Using try/finally to always cleanup even if something awful happens. try { - #region Integration Tests $configFile = Join-Path -Path $PSScriptRoot -ChildPath "$($script:DSCCompositeResourceName).config.ps1" . $configFile $stigList = Get-StigVersionTable -CompositeResourceName $script:DSCCompositeResourceName - #region Integration Tests + $additionalTestParameterList = @{ + LogPath = $env:temp + } + foreach ($stig in $stigList) { - [xml] $dscXml = Get-Content -Path $stig.Path - - $technologyConfig = "$($script:DSCCompositeResourceName)_config" + [xml] $powerstigXml = Get-Content -Path $stig.Path - $skipRule = Get-Random -InputObject $dscXml.DISASTIG.MimeTypeRule.Rule.id + $skipRule = Get-Random -InputObject $powerstigXml.DISASTIG.MimeTypeRule.Rule.id $skipRuleType = "IisLoggingRule" - $expectedSkipRuleTypeCount = $dscXml.DISASTIG.IisLoggingRule.ChildNodes.Count + $expectedSkipRuleTypeCount = $powerstigXml.DISASTIG.IisLoggingRule.ChildNodes.Count - $skipRuleMultiple = Get-Random -InputObject $dscXml.DISASTIG.WebConfigurationPropertyRule.Rule.id -Count 2 + $skipRuleMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.WebConfigurationPropertyRule.Rule.id -Count 2 $skipRuleTypeMultiple = @('MimeTypeRule','IisLoggingRule') - $expectedSkipRuleTypeMultipleCount = $dscXml.DISASTIG.MimeTypeRule.ChildNodes.Count + $dscXml.DISASTIG.IisLoggingRule.ChildNodes.Count + $expectedSkipRuleTypeMultipleCount = $powerstigXml.DISASTIG.MimeTypeRule.ChildNodes.Count + $powerstigXml.DISASTIG.IisLoggingRule.ChildNodes.Count - $exception = Get-Random -InputObject $dscXml.DISASTIG.WebConfigurationPropertyRule.Rule.id - $exceptionMultiple = Get-Random -InputObject $dscXml.DISASTIG.WebConfigurationPropertyRule.Rule.id -Count 2 + $exception = Get-Random -InputObject $powerstigXml.DISASTIG.WebConfigurationPropertyRule.Rule.id + $exceptionMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.WebConfigurationPropertyRule.Rule.id -Count 2 - $userSettingsPath = "$PSScriptRoot\Common.integration.ps1" - . $userSettingsPath + . "$PSScriptRoot\Common.integration.ps1" } } -#endregion Tests finally { Restore-TestEnvironment -TestEnvironment $TestEnvironment diff --git a/Tests/Integration/DSCResources/IisSite.config.ps1 b/Tests/Integration/DSCResources/IisSite.config.ps1 index ac723dd94..85db5ae08 100644 --- a/Tests/Integration/DSCResources/IisSite.config.ps1 +++ b/Tests/Integration/DSCResources/IisSite.config.ps1 @@ -2,6 +2,16 @@ Configuration IisSite_config { param ( + [Parameter()] + [AllowNull()] + [string] + $TechnologyVersion, + + [Parameter()] + [AllowNull()] + [string] + $TechnologyRole, + [Parameter(Mandatory = $true)] [string] $StigVersion, @@ -22,56 +32,6 @@ Configuration IisSite_config [string[]] $OrgSettings, - [Parameter()] - [AllowNull()] - [string] - $BrowserVersion, - - [Parameter()] - [AllowNull()] - [string[]] - $OfficeApp, - - [Parameter()] - [AllowNull()] - [string] - $ConfigPath, - - [Parameter()] - [AllowNull()] - [string] - $PropertiesPath, - - [Parameter()] - [AllowNull()] - [string] - $SqlVersion, - - [Parameter()] - [AllowNull()] - [string] - $SqlRole, - - [Parameter()] - [AllowNull()] - [string] - $ForestName, - - [Parameter()] - [AllowNull()] - [string] - $DomainName, - - [Parameter()] - [AllowNull()] - [string] - $OsVersion, - - [Parameter()] - [AllowNull()] - [string] - $OsRole, - [Parameter()] [AllowNull()] [string[]] @@ -80,12 +40,7 @@ Configuration IisSite_config [Parameter()] [AllowNull()] [string[]] - $WebSiteName, - - [Parameter()] - [AllowNull()] - [string] - $LogPath + $WebSiteName ) Import-DscResource -ModuleName PowerStig @@ -94,20 +49,20 @@ Configuration IisSite_config & ([scriptblock]::Create(" IisSite SiteConfiguration { + IisVersion = '$TechnologyVersion' + StigVersion = '$StigVersion' $(if ($null -ne $WebAppPool) { "WebAppPool = @($( ($WebAppPool | ForEach-Object {"'$PSItem'"}) -join ',' ))`n" }) $( "WebSiteName = @($( ($WebSiteName | ForEach-Object {"'$PSItem'"}) -join ',' ))`n" ) - IisVersion = '$OsVersion' - StigVersion = '$StigVersion' $(if ($null -ne $OrgSettings) { "Orgsettings = '$OrgSettings'" }) $(if ($null -ne $Exception) { - "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem'= @{'Value'='1234567'}"}) -join "`n" )}" + "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem' = '1234567'"}) -join "`n" )}" }) $(if ($null -ne $SkipRule) { diff --git a/Tests/Integration/DSCResources/IisSite.integration.tests.ps1 b/Tests/Integration/DSCResources/IisSite.integration.tests.ps1 index 9b0212a1e..72840a2fe 100644 --- a/Tests/Integration/DSCResources/IisSite.integration.tests.ps1 +++ b/Tests/Integration/DSCResources/IisSite.integration.tests.ps1 @@ -7,43 +7,36 @@ $script:DSCCompositeResourceName = ($MyInvocation.MyCommand.Name -split '\.')[0] # Using try/finally to always cleanup even if something awful happens. try { - #region Integration Tests $configFile = Join-Path -Path $PSScriptRoot -ChildPath "$($script:DSCCompositeResourceName).config.ps1" . $configFile $stigList = Get-StigVersionTable -CompositeResourceName $script:DSCCompositeResourceName - #region Test Setup - $WebsiteName = @('WarioSite', 'DKSite') - $WebAppPool = @('MushroomBeach', 'ToadHarbor') - #endregionTest Setup + $additionalTestParameterList = @{ + WebsiteName = @('WarioSite', 'DKSite') + WebAppPool = @('MushroomBeach', 'ToadHarbor') + } - #region Tests foreach ($stig in $stigList) { - [xml] $dscXml = Get-Content -Path $stig.Path - - $technologyConfig = "$($script:DSCCompositeResourceName)_config" + [xml] $powerstigXml = Get-Content -Path $stig.Path - $skipRule = Get-Random -InputObject $dscXml.DISASTIG.WebConfigurationPropertyRule.Rule.id + $skipRule = Get-Random -InputObject $powerstigXml.DISASTIG.WebConfigurationPropertyRule.Rule.id $skipRuleType = "IisLoggingRule" - $expectedSkipRuleTypeCount = $dscXml.DISASTIG.IisLoggingRule.ChildNodes.Count + $expectedSkipRuleTypeCount = $powerstigXml.DISASTIG.IisLoggingRule.ChildNodes.Count - $skipRuleMultiple = Get-Random -InputObject $dscXml.DISASTIG.MimeTypeRule.Rule.id -Count 2 + $skipRuleMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.MimeTypeRule.Rule.id -Count 2 $skipRuleTypeMultiple = @('WebAppPoolRule','IisLoggingRule') - $expectedSkipRuleTypeMultipleCount = $dscXml.DISASTIG.WebAppPoolRule.ChildNodes.Count + $dscXml.DISASTIG.IisLoggingRule.ChildNodes.Count + $expectedSkipRuleTypeMultipleCount = $powerstigXml.DISASTIG.WebAppPoolRule.ChildNodes.Count + $powerstigXml.DISASTIG.IisLoggingRule.ChildNodes.Count - $exception = Get-Random -InputObject $dscXml.DISASTIG.WebConfigurationPropertyRule.Rule.id - $exceptionMultiple = Get-Random -InputObject $dscXml.DISASTIG.WebAppPoolRule.Rule.id -Count 2 + $exception = Get-Random -InputObject ($powerstigXml.DISASTIG.WebConfigurationPropertyRule.Rule | + Where-Object {[string]::IsNullOrEmpty($PSItem.DuplicateOf)}).id + $exceptionMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.WebAppPoolRule.Rule.id -Count 2 - $userSettingsPath = "$PSScriptRoot\Common.integration.ps1" - . $userSettingsPath + . "$PSScriptRoot\Common.integration.ps1" } - #endregion Tests } finally { - #region FOOTER Restore-TestEnvironment -TestEnvironment $TestEnvironment - #endregion } diff --git a/Tests/Integration/DSCResources/InternetExplorer.config.ps1 b/Tests/Integration/DSCResources/InternetExplorer.config.ps1 index 0477627d4..043831192 100644 --- a/Tests/Integration/DSCResources/InternetExplorer.config.ps1 +++ b/Tests/Integration/DSCResources/InternetExplorer.config.ps1 @@ -2,90 +2,35 @@ Configuration InternetExplorer_config { param ( - [Parameter(Mandatory = $true)] - [string] - $StigVersion, - - [Parameter()] - [string[]] - $SkipRule, - - [Parameter()] - [string[]] - $SkipRuleType, - - [Parameter()] - [string[]] - $Exception, - - [Parameter()] - [string[]] - $OrgSettings, - - [Parameter()] - [AllowNull()] - [string] - $BrowserVersion, - - [Parameter()] - [AllowNull()] - [string[]] - $OfficeApp, - - [Parameter()] - [AllowNull()] - [string] - $ConfigPath, - - [Parameter()] - [AllowNull()] - [string] - $PropertiesPath, - [Parameter()] [AllowNull()] [string] - $SqlVersion, + $TechnologyVersion, [Parameter()] [AllowNull()] [string] - $SqlRole, + $TechnologyRole, - [Parameter()] - [AllowNull()] - [string] - $ForestName, - - [Parameter()] - [AllowNull()] - [string] - $DomainName, - - [Parameter()] - [AllowNull()] + [Parameter(Mandatory = $true)] [string] - $OsVersion, + $StigVersion, [Parameter()] - [AllowNull()] - [string] - $OsRole, + [string[]] + $SkipRule, [Parameter()] - [AllowNull()] [string[]] - $WebAppPool, + $SkipRuleType, [Parameter()] - [AllowNull()] [string[]] - $WebSiteName, + $Exception, [Parameter()] - [AllowNull()] - [string] - $LogPath + [string[]] + $OrgSettings ) Import-DscResource -ModuleName PowerStig @@ -95,15 +40,15 @@ Configuration InternetExplorer_config & ([scriptblock]::Create(" InternetExplorer STIG { - BrowserVersion = '$BrowserVersion' - StigVersion = '$StigVersion' + BrowserVersion = '$TechnologyVersion' + StigVersion = '$StigVersion' $(if ($null -ne $OrgSettings) { "Orgsettings = '$OrgSettings'" }) $(if ($null -ne $Exception) { - "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem'= @{'ValueData'='1234567'}"}) -join "`n" )}" + "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem' = '1234567'"}) -join "`n" )}" }) $(if ($null -ne $SkipRule) { diff --git a/Tests/Integration/DSCResources/InternetExplorer.integration.tests.ps1 b/Tests/Integration/DSCResources/InternetExplorer.integration.tests.ps1 index b71f79750..716ebd26d 100644 --- a/Tests/Integration/DSCResources/InternetExplorer.integration.tests.ps1 +++ b/Tests/Integration/DSCResources/InternetExplorer.integration.tests.ps1 @@ -7,34 +7,28 @@ $script:DSCCompositeResourceName = ($MyInvocation.MyCommand.Name -split '\.')[0] # Using try/finally to always cleanup even if something awful happens. try { - #region Integration Tests $configFile = Join-Path -Path $PSScriptRoot -ChildPath "$($script:DSCCompositeResourceName).config.ps1" . $configFile $stigList = Get-StigVersionTable -CompositeResourceName $script:DSCCompositeResourceName - #region Integration Tests foreach ($stig in $stigList) { - [xml] $dscXml = Get-Content -Path $stig.Path + [xml] $powerstigXml = Get-Content -Path $stig.Path - $technologyConfig = "$($script:DSCCompositeResourceName)_config" - - $skipRule = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id + $skipRule = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id $skipRuleType = $null $expectedSkipRuleTypeCount = 0 - $skipRuleMultiple = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id -Count 2 + $skipRuleMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id -Count 2 $skipRuleTypeMultiple = $null $expectedSkipRuleTypeMultipleCount = 0 - $exception = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id - $exceptionMultiple = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id -Count 2 + $exception = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id + $exceptionMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id -Count 2 - $userSettingsPath = "$PSScriptRoot\Common.integration.ps1" - . $userSettingsPath + . "$PSScriptRoot\Common.integration.ps1" } - #endregion Tests } finally { diff --git a/Tests/Integration/DSCResources/Office.config.ps1 b/Tests/Integration/DSCResources/Office.config.ps1 index d73c88a69..ba6f34d82 100644 --- a/Tests/Integration/DSCResources/Office.config.ps1 +++ b/Tests/Integration/DSCResources/Office.config.ps1 @@ -2,91 +2,35 @@ Configuration Office_config { param ( - [Parameter(Mandatory = $true)] - [version] - $StigVersion, - - [Parameter()] - [string[]] - $SkipRule, - - [Parameter()] - [string[]] - $SkipRuleType, - - [Parameter()] - [string[]] - $Exception, - - [Parameter()] - [string[]] - $OrgSettings, - - [Parameter()] - [AllowNull()] - [string] - $BrowserVersion, - - [Parameter()] - [AllowNull()] - [string[]] - $OfficeApp, - - [Parameter()] - [AllowNull()] - [string] - $ConfigPath, - [Parameter()] [AllowNull()] [string] - $PropertiesPath, + $TechnologyVersion, [Parameter()] [AllowNull()] [string] - $SqlVersion, + $TechnologyRole, - [Parameter()] - [AllowNull()] - [string] - $SqlRole, - - [Parameter()] - [AllowNull()] - [string] - $ForestName, - - [Parameter()] - [AllowNull()] - [string] - $DomainName, - - [Parameter()] - [AllowNull()] - [string] - $OsVersion, + [Parameter(Mandatory = $true)] + [version] + $StigVersion, [Parameter()] - [AllowNull()] - [string] - $OsRole, + [string[]] + $SkipRule, [Parameter()] - [AllowNull()] [string[]] - $WebAppPool, + $SkipRuleType, [Parameter()] - [AllowNull()] [string[]] - $WebSiteName, + $Exception, [Parameter()] - [AllowNull()] - [string] - $LogPath - + [string[]] + $OrgSettings ) Import-DscResource -ModuleName PowerStig @@ -96,7 +40,7 @@ Configuration Office_config & ([scriptblock]::Create(" Office BaseLineSettings { - OfficeApp = '$OfficeApp' + OfficeApp = '$TechnologyVersion' StigVersion = '$StigVersion' $(if ($null -ne $OrgSettings) { @@ -104,7 +48,7 @@ Configuration Office_config }) $(if ($null -ne $Exception) { - "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem'= @{'ValueData'='1234567'}"}) -join "`n" )}" + "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem' = '1234567'"}) -join "`n" )}" }) $(if ($null -ne $SkipRule) { diff --git a/Tests/Integration/DSCResources/Office.integration.tests.ps1 b/Tests/Integration/DSCResources/Office.integration.tests.ps1 index 11c56fd49..716ebd26d 100644 --- a/Tests/Integration/DSCResources/Office.integration.tests.ps1 +++ b/Tests/Integration/DSCResources/Office.integration.tests.ps1 @@ -7,34 +7,28 @@ $script:DSCCompositeResourceName = ($MyInvocation.MyCommand.Name -split '\.')[0] # Using try/finally to always cleanup even if something awful happens. try { - #region Integration Tests$ $configFile = Join-Path -Path $PSScriptRoot -ChildPath "$($script:DSCCompositeResourceName).config.ps1" . $configFile $stigList = Get-StigVersionTable -CompositeResourceName $script:DSCCompositeResourceName - #region Integration Tests foreach ($stig in $stigList) { - [xml] $dscXml = Get-Content -Path $stig.Path + [xml] $powerstigXml = Get-Content -Path $stig.Path - $technologyConfig = "$($script:DSCCompositeResourceName)_config" - - $skipRule = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id + $skipRule = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id $skipRuleType = $null $expectedSkipRuleTypeCount = 0 - $skipRuleMultiple = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id -Count 2 + $skipRuleMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id -Count 2 $skipRuleTypeMultiple = $null $expectedSkipRuleTypeMultipleCount = 0 - $exception = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id - $exceptionMultiple = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id -Count 2 + $exception = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id + $exceptionMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id -Count 2 - $userSettingsPath = "$PSScriptRoot\Common.integration.ps1" - . $userSettingsPath + . "$PSScriptRoot\Common.integration.ps1" } -#endregion Tests } finally { diff --git a/Tests/Integration/DSCResources/OracleJRE.config.ps1 b/Tests/Integration/DSCResources/OracleJRE.config.ps1 index 38e8eecda..a1d88b45a 100644 --- a/Tests/Integration/DSCResources/OracleJRE.config.ps1 +++ b/Tests/Integration/DSCResources/OracleJRE.config.ps1 @@ -2,6 +2,16 @@ Configuration OracleJRE_config { param ( + [Parameter()] + [AllowNull()] + [string] + $TechnologyVersion, + + [Parameter()] + [AllowNull()] + [string] + $TechnologyRole, + [Parameter(Mandatory = $true)] [string] $StigVersion, @@ -22,16 +32,6 @@ Configuration OracleJRE_config [string[]] $OrgSettings, - [Parameter()] - [AllowNull()] - [string] - $BrowserVersion, - - [Parameter()] - [AllowNull()] - [string[]] - $OfficeApp, - [Parameter()] [AllowNull()] [string] @@ -40,52 +40,7 @@ Configuration OracleJRE_config [Parameter()] [AllowNull()] [string] - $PropertiesPath, - - [Parameter()] - [AllowNull()] - [string] - $SqlVersion, - - [Parameter()] - [AllowNull()] - [string] - $SqlRole, - - [Parameter()] - [AllowNull()] - [string] - $ForestName, - - [Parameter()] - [AllowNull()] - [string] - $DomainName, - - [Parameter()] - [AllowNull()] - [string] - $OsVersion, - - [Parameter()] - [AllowNull()] - [string] - $OsRole, - - [Parameter()] - [AllowNull()] - [string[]] - $WebAppPool, - - [Parameter()] - [AllowNull()] - [string[]] - $WebSiteName, - - [Parameter()] - [AllowNull()] - [string] - $LogPath + $PropertiesPath ) Import-DscResource -ModuleName PowerStig @@ -95,16 +50,16 @@ Configuration OracleJRE_config & ([scriptblock]::Create(" OracleJRE OracleConfiguration { - ConfigPath = '$ConfigPath' + ConfigPath = '$ConfigPath' PropertiesPath = '$PropertiesPath' - StigVersion = '$StigVersion' + StigVersion = '$StigVersion' $(if ($null -ne $OrgSettings) { "Orgsettings = '$OrgSettings'" }) $(if ($null -ne $Exception) { - "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem'= @{'Value'='1234567'}"}) -join "`n" )}" + "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem' = '1234567'"}) -join "`n" )}" }) $(if ($null -ne $SkipRule) { diff --git a/Tests/Integration/DSCResources/OracleJRE.integration.tests.ps1 b/Tests/Integration/DSCResources/OracleJRE.integration.tests.ps1 index e071061cc..ef4825a0d 100644 --- a/Tests/Integration/DSCResources/OracleJRE.integration.tests.ps1 +++ b/Tests/Integration/DSCResources/OracleJRE.integration.tests.ps1 @@ -7,39 +7,33 @@ $script:DSCCompositeResourceName = ($MyInvocation.MyCommand.Name -split '\.')[0] # Using try/finally to always cleanup even if something awful happens. try { - #region Integration Tests $configFile = Join-Path -Path $PSScriptRoot -ChildPath "$($script:DSCCompositeResourceName).config.ps1" . $configFile $stigList = Get-StigVersionTable -CompositeResourceName $script:DSCCompositeResourceName - #region Test Setup - $configPath = 'C:\Windows\Sun\Java\Deployment\deployment.config' - $propertiesPath = 'C:\Windows\Java\Deployment\deployment.properties' - #endregionTest Setup + $additionalTestParameterList = @{ + configPath = 'C:\Windows\Sun\Java\Deployment\deployment.config' + propertiesPath = 'C:\Windows\Java\Deployment\deployment.properties' + } - #region Integration Tests foreach ($stig in $stigList) { - [xml] $dscXml = Get-Content -Path $stig.Path - - $technologyConfig = "$($script:DSCCompositeResourceName)_config" + [xml] $powerstigXml = Get-Content -Path $stig.Path - $skipRule = Get-Random -InputObject $dscXml.DISASTIG.FileContentRule.Rule.id + $skipRule = Get-Random -InputObject $powerstigXml.DISASTIG.FileContentRule.Rule.id $skipRuleType = $null $expectedSkipRuleTypeCount = 0 - $skipRuleMultiple = Get-Random -InputObject $dscXml.DISASTIG.FileContentRule.Rule.id -Count 2 + $skipRuleMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.FileContentRule.Rule.id -Count 2 $skipRuleTypeMultiple = $null $expectedSkipRuleTypeMultipleCount = 0 - $exception = Get-Random -InputObject $dscXml.DISASTIG.FileContentRule.Rule.id - $exceptionMultiple = Get-Random -InputObject $dscXml.DISASTIG.FileContentRule.Rule.id -Count 2 + $exception = Get-Random -InputObject $powerstigXml.DISASTIG.FileContentRule.Rule.id + $exceptionMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.FileContentRule.Rule.id -Count 2 - $userSettingsPath = "$PSScriptRoot\Common.integration.ps1" - . $userSettingsPath + . "$PSScriptRoot\Common.integration.ps1" } - #endregion Tests } finally { diff --git a/Tests/Integration/DSCResources/SqlServer.config.ps1 b/Tests/Integration/DSCResources/SqlServer.config.ps1 index 0e62c46d4..78958c9a0 100644 --- a/Tests/Integration/DSCResources/SqlServer.config.ps1 +++ b/Tests/Integration/DSCResources/SqlServer.config.ps1 @@ -1,92 +1,37 @@ -Configuration SqlServerInstance_config +Configuration SqlServer_config { param ( [Parameter()] - [string] - $StigVersion, - - [Parameter()] - [string[]] - $SkipRule, - - [Parameter()] - [string[]] - $SkipRuleType, - - [Parameter()] - [string[]] - $Exception, - - [Parameter()] - [string[]] - $OrgSettings, - - [Parameter()] - [string] - [AllowNull()] - $BrowserVersion, - - [Parameter()] - [string[]] [AllowNull()] - $OfficeApp, - - [Parameter()] [string] - [AllowNull()] - $ConfigPath, + $TechnologyVersion, [Parameter()] - [string] [AllowNull()] - $PropertiesPath, - - [Parameter()] - [string] - [AllowNull()] - $SqlVersion, - - [Parameter()] - [string] - [AllowNull()] - $SqlRole, - - [Parameter()] [string] - [AllowNull()] - $ForestName, + $TechnologyRole, [Parameter()] [string] - [AllowNull()] - $DomainName, + $StigVersion, [Parameter()] - [string] - [AllowNull()] - $OsVersion, + [string[]] + $SkipRule, [Parameter()] - [string] - [AllowNull()] - $OsRole, + [string[]] + $SkipRuleType, [Parameter()] [string[]] - [AllowNull()] - $WebAppPool, + $Exception, [Parameter()] [string[]] - [AllowNull()] - $WebSiteName, + $OrgSettings - [Parameter()] - [string] - [AllowNull()] - $LogPath - ) Import-DscResource -ModuleName PowerStig @@ -96,8 +41,8 @@ Configuration SqlServerInstance_config & ([scriptblock]::Create(" SqlServer Instance { - SqlVersion = $SqlVersion - SqlRole = '$SqlRole' + SqlVersion = $TechnologyVersion + SqlRole = '$TechnologyRole' StigVersion = $StigVersion ServerInstance = 'TestServer' $(if ($null -ne $OrgSettings) @@ -106,7 +51,7 @@ Configuration SqlServerInstance_config }) $(if ($null -ne $Exception) { - "Exception = @{$( ($Exception | ForEach-Object {"'$$PSItem'= @{'SetScript'='TestScript'}"}) -join "`n" )}" + "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem' = '1234567'"}) -join "`n" )}" }) $(if ($null -ne $SkipRule) { @@ -125,90 +70,35 @@ Configuration SqlServerDatabase_config { param ( - [Parameter()] - [string] - $StigVersion, - - [Parameter()] - [psobject] - $SkipRule, - - [Parameter()] - [psobject] - $SkipRuleType, - - [Parameter()] - [psobject] - $Exception, - - [Parameter()] - [string[]] - $OrgSettings, - - [Parameter()] - [AllowNull()] - [string] - $BrowserVersion, - - [Parameter()] - [AllowNull()] - [string[]] - $OfficeApp, - - [Parameter()] - [AllowNull()] - [string] - $ConfigPath, - - [Parameter()] - [AllowNull()] - [string] - $PropertiesPath, - - [Parameter()] - [AllowNull()] - [string] - $SqlVersion, - [Parameter()] [AllowNull()] [string] - $SqlRole, + $TechnologyVersion, [Parameter()] [AllowNull()] [string] - $ForestName, + $TechnologyRole, [Parameter()] - [AllowNull()] [string] - $DomainName, + $StigVersion, [Parameter()] - [AllowNull()] - [string] - $OsVersion, + [psobject] + $SkipRule, [Parameter()] - [AllowNull()] - [string] - $OsRole, + [psobject] + $SkipRuleType, [Parameter()] - [AllowNull()] - [string[]] - $WebAppPool, + [psobject] + $Exception, [Parameter()] - [AllowNull()] [string[]] - $WebSiteName, - - [Parameter()] - [AllowNull()] - [string] - $LogPath + $OrgSettings ) Import-DscResource -ModuleName PowerStig @@ -218,11 +108,11 @@ Configuration SqlServerDatabase_config & ([scriptblock]::Create(" SqlServer Database { - SqlVersion = '$SqlVersion' - SqlRole = '$SqlRole' - StigVersion = '$StigVersion' + SqlVersion = '$TechnologyVersion' + SqlRole = '$TechnologyRole' + StigVersion = '$StigVersion' ServerInstance = 'TestServer' - Database = 'TestDataBase' + Database = 'TestDataBase' $(if ($null -ne $OrgSettings) { "Orgsettings = '$OrgSettings'" diff --git a/Tests/Integration/DSCResources/SqlServer.integration.tests.ps1 b/Tests/Integration/DSCResources/SqlServer.integration.tests.ps1 index 1d104a9e6..37fbc8a1c 100644 --- a/Tests/Integration/DSCResources/SqlServer.integration.tests.ps1 +++ b/Tests/Integration/DSCResources/SqlServer.integration.tests.ps1 @@ -7,34 +7,28 @@ $script:DSCCompositeResourceName = ($MyInvocation.MyCommand.Name -split '\.')[0] # Using try/finally to always cleanup even if something awful happens. try { - #region Integration Tests $configFile = Join-Path -Path $PSScriptRoot -ChildPath "$($script:DSCCompositeResourceName).config.ps1" . $configFile $stigList = Get-StigVersionTable -CompositeResourceName $script:DSCCompositeResourceName - #region Integration Tests foreach ($stig in $stigList) { - [xml] $dscXml = Get-Content -Path $stig.Path + [xml] $powerstigXml = Get-Content -Path $stig.Path - $technologyConfig = "$($script:DSCCompositeResourceName)$($stig.TechnologyRole)_config" - - $skipRule = Get-Random -InputObject $dscXml.DISASTIG.SqlScriptQueryRule.Rule.id + $skipRule = Get-Random -InputObject $powerstigXml.DISASTIG.SqlScriptQueryRule.Rule.id $skipRuleType = "DocumentRule" - $expectedSkipRuleTypeCount = $dscXml.DISASTIG.DocumentRule.ChildNodes.Count + $expectedSkipRuleTypeCount = $powerstigXml.DISASTIG.DocumentRule.ChildNodes.Count - $skipRuleMultiple = Get-Random -InputObject $dscXml.DISASTIG.DocumentRule.Rule.id -Count 2 + $skipRuleMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.DocumentRule.Rule.id -Count 2 $skipRuleTypeMultiple = $null $expectedSkipRuleTypeMultipleCount = 0 - $exception = Get-Random -InputObject $dscXml.DISASTIG.SqlScriptQueryRule.Rule.id + $exception = Get-Random -InputObject $powerstigXml.DISASTIG.SqlScriptQueryRule.Rule.id $exceptionMultiple = $null - $userSettingsPath = "$PSScriptRoot\Common.integration.ps1" - . $userSettingsPath + . "$PSScriptRoot\Common.integration.ps1" } - #endregion Tests } finally { diff --git a/Tests/Integration/DSCResources/WindowsClient.config.ps1 b/Tests/Integration/DSCResources/WindowsClient.config.ps1 index 7fa5fbe27..4de0ef628 100644 --- a/Tests/Integration/DSCResources/WindowsClient.config.ps1 +++ b/Tests/Integration/DSCResources/WindowsClient.config.ps1 @@ -2,6 +2,16 @@ Configuration WindowsClient_config { param ( + [Parameter()] + [AllowNull()] + [string] + $TechnologyVersion, + + [Parameter()] + [AllowNull()] + [string] + $TechnologyRole, + [Parameter(Mandatory = $true)] [version] $StigVersion, @@ -22,36 +32,6 @@ Configuration WindowsClient_config [string[]] $OrgSettings, - [Parameter()] - [AllowNull()] - [string] - $BrowserVersion, - - [Parameter()] - [AllowNull()] - [string[]] - $OfficeApp, - - [Parameter()] - [AllowNull()] - [string] - $ConfigPath, - - [Parameter()] - [AllowNull()] - [string] - $PropertiesPath, - - [Parameter()] - [AllowNull()] - [string] - $SqlVersion, - - [Parameter()] - [AllowNull()] - [string] - $SqlRole, - [Parameter()] [AllowNull()] [string] @@ -60,32 +40,7 @@ Configuration WindowsClient_config [Parameter()] [AllowNull()] [string] - $DomainName, - - [Parameter()] - [AllowNull()] - [string] - $OsVersion, - - [Parameter()] - [AllowNull()] - [string] - $OsRole, - - [Parameter()] - [AllowNull()] - [string[]] - $WebAppPool, - - [Parameter()] - [AllowNull()] - [string[]] - $WebSiteName, - - [Parameter()] - [AllowNull()] - [string] - $LogPath + $DomainName ) Import-DscResource -ModuleName PowerStig @@ -95,17 +50,17 @@ Configuration WindowsClient_config & ([scriptblock]::Create(" WindowsClient BaseLineSettings { - OsVersion = '$OsVersion' + OsVersion = '$TechnologyVersion' StigVersion = '$StigVersion' - ForestName = '$ForestName' - DomainName = '$DomainName' + ForestName = '$ForestName' + DomainName = '$DomainName' $(if ($null -ne $OrgSettings) { "Orgsettings = '$OrgSettings'" }) $(if ($null -ne $Exception) { - "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem'= @{'ValueData'='1234567'}"}) -join "`n" )}" + "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem' = '1234567'"}) -join "`n" )}" }) $(if ($null -ne $SkipRule) { diff --git a/Tests/Integration/DSCResources/WindowsClient.integration.tests.ps1 b/Tests/Integration/DSCResources/WindowsClient.integration.tests.ps1 index f1f58d2fd..7bce06a86 100644 --- a/Tests/Integration/DSCResources/WindowsClient.integration.tests.ps1 +++ b/Tests/Integration/DSCResources/WindowsClient.integration.tests.ps1 @@ -7,34 +7,33 @@ $script:DSCCompositeResourceName = ($MyInvocation.MyCommand.Name -split '\.')[0] # Using try/finally to always cleanup even if something awful happens. try { - #region Integration Tests $configFile = Join-Path -Path $PSScriptRoot -ChildPath "$($script:DSCCompositeResourceName).config.ps1" . $configFile $stigList = Get-StigVersionTable -CompositeResourceName $script:DSCCompositeResourceName - #region Integration Tests + $additionalTestParameterList = @{ + ForestName = 'integration.test' + DomainName = 'integration.test' + } + foreach ($stig in $stigList) { - [xml] $dscXml = Get-Content -Path $stig.Path - - $technologyConfig = "$($script:DSCCompositeResourceName)_config" + [xml] $powerstigXml = Get-Content -Path $stig.Path - $skipRule = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id + $skipRule = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id $skipRuleType = "AuditPolicyRule" - $expectedSkipRuleTypeCount = $dscXml.DISASTIG.AuditPolicyRule.ChildNodes.Count + $expectedSkipRuleTypeCount = $powerstigXml.DISASTIG.AuditPolicyRule.ChildNodes.Count - $skipRuleMultiple = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id -Count 2 + $skipRuleMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id -Count 2 $skipRuleTypeMultiple = @('AuditPolicyRule','AccountPolicyRule') - $expectedSkipRuleTypeMultipleCount = $dscXml.DISASTIG.AuditPolicyRule.ChildNodes.Count + $dscXml.DISASTIG.AccountPolicyRule.ChildNodes.Count + $expectedSkipRuleTypeMultipleCount = $powerstigXml.DISASTIG.AuditPolicyRule.ChildNodes.Count + $powerstigXml.DISASTIG.AccountPolicyRule.ChildNodes.Count - $exception = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id - $exceptionMultiple = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id -Count 2 + $exception = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id + $exceptionMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id -Count 2 - $userSettingsPath = "$PSScriptRoot\Common.integration.ps1" - . $userSettingsPath + . "$PSScriptRoot\Common.integration.ps1" } - #endregion Tests } finally { diff --git a/Tests/Integration/DSCResources/WindowsDnsServer.config.ps1 b/Tests/Integration/DSCResources/WindowsDnsServer.config.ps1 index ba717f8a6..b7f9c32af 100644 --- a/Tests/Integration/DSCResources/WindowsDnsServer.config.ps1 +++ b/Tests/Integration/DSCResources/WindowsDnsServer.config.ps1 @@ -2,6 +2,16 @@ Configuration WindowsDnsServer_config { param ( + [Parameter()] + [AllowNull()] + [string] + $TechnologyVersion, + + [Parameter()] + [AllowNull()] + [string] + $TechnologyRole, + [Parameter(Mandatory = $true)] [version] $StigVersion, @@ -22,36 +32,6 @@ Configuration WindowsDnsServer_config [string[]] $OrgSettings, - [Parameter()] - [AllowNull()] - [string] - $BrowserVersion, - - [Parameter()] - [AllowNull()] - [string[]] - $OfficeApp, - - [Parameter()] - [AllowNull()] - [string] - $ConfigPath, - - [Parameter()] - [AllowNull()] - [string] - $PropertiesPath, - - [Parameter()] - [AllowNull()] - [string] - $SqlVersion, - - [Parameter()] - [AllowNull()] - [string] - $SqlRole, - [Parameter()] [AllowNull()] [string] @@ -60,32 +40,7 @@ Configuration WindowsDnsServer_config [Parameter()] [AllowNull()] [string] - $DomainName, - - [Parameter()] - [AllowNull()] - [string] - $OsVersion, - - [Parameter()] - [AllowNull()] - [string] - $OsRole, - - [Parameter()] - [AllowNull()] - [string[]] - $WebAppPool, - - [Parameter()] - [AllowNull()] - [string[]] - $WebSiteName, - - [Parameter()] - [AllowNull()] - [string] - $LogPath + $DomainName ) Import-DscResource -ModuleName PowerStig @@ -95,17 +50,17 @@ Configuration WindowsDnsServer_config & ([scriptblock]::Create(" WindowsDnsServer BaseLineSettings { - OsVersion = '$OsVersion' + OsVersion = '$TechnologyVersion' StigVersion = '$StigVersion' - ForestName = '$ForestName' - DomainName = '$DomainName' + ForestName = '$ForestName' + DomainName = '$DomainName' $(if ($null -ne $OrgSettings) { "Orgsettings = '$OrgSettings'" }) $(if ($null -ne $Exception) { - "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem'= @{'PropertyValue'='1234567'}"}) -join "`n" )}" + "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem' = '1234567'"}) -join "`n" )}" }) $(if ($null -ne $SkipRule) { diff --git a/Tests/Integration/DSCResources/WindowsDnsServer.integration.tests.ps1 b/Tests/Integration/DSCResources/WindowsDnsServer.integration.tests.ps1 index b5887bc93..859093049 100644 --- a/Tests/Integration/DSCResources/WindowsDnsServer.integration.tests.ps1 +++ b/Tests/Integration/DSCResources/WindowsDnsServer.integration.tests.ps1 @@ -7,35 +7,33 @@ $script:DSCCompositeResourceName = ($MyInvocation.MyCommand.Name -split '\.')[0] # Using try/finally to always cleanup even if something awful happens. try { - #region Integration Tests $configFile = Join-Path -Path $PSScriptRoot -ChildPath "$($script:DSCCompositeResourceName).config.ps1" . $configFile $stigList = Get-StigVersionTable -CompositeResourceName $script:DSCCompositeResourceName - #region Integration Tests + $additionalTestParameterList = @{ + ForestName = 'integration.test' + DomainName = 'integration.test' + } foreach ($stig in $stigList) { - [xml] $dscXml = Get-Content -Path $stig.Path - - $technologyConfig = "$($script:DSCCompositeResourceName)_config" + [xml] $powerstigXml = Get-Content -Path $stig.Path - $skipRule = Get-Random -InputObject $dscXml.DISASTIG.DnsServerSettingRule.Rule.id + $skipRule = Get-Random -InputObject $powerstigXml.DISASTIG.DnsServerSettingRule.Rule.id $skipRuleType = "PermissionRule" - $expectedSkipRuleTypeCount = $dscXml.DISASTIG.PermissionRule.ChildNodes.Count + $expectedSkipRuleTypeCount = $powerstigXml.DISASTIG.PermissionRule.ChildNodes.Count - $skipRuleMultiple = Get-Random -InputObject $dscXml.DISASTIG.DnsServerSettingRule.Rule.id -Count 2 + $skipRuleMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.DnsServerSettingRule.Rule.id -Count 2 $skipRuleTypeMultiple = @('PermissionRule','UserRightRule') - $expectedSkipRuleTypeMultipleCount = $dscXml.DISASTIG.PermissionRule.ChildNodes.Count + $dscXml.DISASTIG.UserRightRule.ChildNodes.Count + $expectedSkipRuleTypeMultipleCount = $powerstigXml.DISASTIG.PermissionRule.ChildNodes.Count + $powerstigXml.DISASTIG.UserRightRule.ChildNodes.Count - $exception = Get-Random -InputObject $dscXml.DISASTIG.DnsServerSettingRule.Rule.id - $exceptionMultiple = Get-Random -InputObject $dscXml.DISASTIG.DnsServerSettingRule.Rule.id -Count 2 + $exception = Get-Random -InputObject $powerstigXml.DISASTIG.DnsServerSettingRule.Rule.id + $exceptionMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.DnsServerSettingRule.Rule.id -Count 2 - $userSettingsPath = "$PSScriptRoot\Common.integration.ps1" - . $userSettingsPath + . "$PSScriptRoot\Common.integration.ps1" } - #endregion Tests } finally { diff --git a/Tests/Integration/DSCResources/WindowsFirewall.config.ps1 b/Tests/Integration/DSCResources/WindowsFirewall.config.ps1 index 95d64a9ce..b840fc3f4 100644 --- a/Tests/Integration/DSCResources/WindowsFirewall.config.ps1 +++ b/Tests/Integration/DSCResources/WindowsFirewall.config.ps1 @@ -2,90 +2,35 @@ Configuration WindowsFirewall_config { param ( - [Parameter(Mandatory = $true)] - [version] - $StigVersion, - - [Parameter()] - [string[]] - $SkipRule, - - [Parameter()] - [string[]] - $SkipRuleType, - - [Parameter()] - [string[]] - $Exception, - - [Parameter()] - [string[]] - $OrgSettings, - - [Parameter()] - [AllowNull()] - [string] - $BrowserVersion, - - [Parameter()] - [AllowNull()] - [string[]] - $OfficeApp, - - [Parameter()] - [AllowNull()] - [string] - $ConfigPath, - - [Parameter()] - [AllowNull()] - [string] - $PropertiesPath, - [Parameter()] [AllowNull()] [string] - $SqlVersion, + $TechnologyVersion, [Parameter()] [AllowNull()] [string] - $SqlRole, + $TechnologyRole, - [Parameter()] - [AllowNull()] - [string] - $ForestName, - - [Parameter()] - [AllowNull()] - [string] - $DomainName, - - [Parameter()] - [AllowNull()] - [string] - $OsVersion, + [Parameter(Mandatory = $true)] + [version] + $StigVersion, [Parameter()] - [AllowNull()] - [string] - $OsRole, + [string[]] + $SkipRule, [Parameter()] - [AllowNull()] [string[]] - $WebAppPool, + $SkipRuleType, [Parameter()] - [AllowNull()] [string[]] - $WebSiteName, + $Exception, [Parameter()] - [AllowNull()] - [string] - $LogPath + [string[]] + $OrgSettings ) Import-DscResource -ModuleName PowerStig @@ -102,7 +47,7 @@ Configuration WindowsFirewall_config }) $(if ($null -ne $Exception) { - "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem'= @{'ValueData'='1234567'}"}) -join "`n" )}" + "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem' = '1234567'"}) -join "`n" )}" }) $(if ($null -ne $SkipRule) { diff --git a/Tests/Integration/DSCResources/WindowsFirewall.integration.tests.ps1 b/Tests/Integration/DSCResources/WindowsFirewall.integration.tests.ps1 index a341702b5..716ebd26d 100644 --- a/Tests/Integration/DSCResources/WindowsFirewall.integration.tests.ps1 +++ b/Tests/Integration/DSCResources/WindowsFirewall.integration.tests.ps1 @@ -7,35 +7,28 @@ $script:DSCCompositeResourceName = ($MyInvocation.MyCommand.Name -split '\.')[0] # Using try/finally to always cleanup even if something awful happens. try { - #region Integration Tests $configFile = Join-Path -Path $PSScriptRoot -ChildPath "$($script:DSCCompositeResourceName).config.ps1" . $configFile $stigList = Get-StigVersionTable -CompositeResourceName $script:DSCCompositeResourceName - #region Integration Tests - foreach ($stig in $stigList) { - [xml] $dscXml = Get-Content -Path $stig.Path - - $technologyConfig = "$($script:DSCCompositeResourceName)_config" + [xml] $powerstigXml = Get-Content -Path $stig.Path - $skipRule = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id + $skipRule = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id $skipRuleType = $null $expectedSkipRuleTypeCount = 0 - $skipRuleMultiple = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id -Count 2 + $skipRuleMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id -Count 2 $skipRuleTypeMultiple = $null $expectedSkipRuleTypeMultipleCount = 0 - $exception = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id - $exceptionMultiple = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id -Count 2 + $exception = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id + $exceptionMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id -Count 2 - $userSettingsPath = "$PSScriptRoot\Common.integration.ps1" - . $userSettingsPath + . "$PSScriptRoot\Common.integration.ps1" } - #endregion Tests } finally { diff --git a/Tests/Integration/DSCResources/WindowsServer.config.ps1 b/Tests/Integration/DSCResources/WindowsServer.config.ps1 index a66afb915..5d8eab6b9 100644 --- a/Tests/Integration/DSCResources/WindowsServer.config.ps1 +++ b/Tests/Integration/DSCResources/WindowsServer.config.ps1 @@ -2,6 +2,16 @@ Configuration WindowsServer_config { param ( + [Parameter()] + [AllowNull()] + [string] + $TechnologyVersion, + + [Parameter()] + [AllowNull()] + [string] + $TechnologyRole, + [Parameter(Mandatory = $true)] [version] $StigVersion, @@ -22,36 +32,6 @@ Configuration WindowsServer_config [string[]] $OrgSettings, - [Parameter()] - [AllowNull()] - [string] - $BrowserVersion, - - [Parameter()] - [AllowNull()] - [string[]] - $OfficeApp, - - [Parameter()] - [AllowNull()] - [string] - $ConfigPath, - - [Parameter()] - [AllowNull()] - [string] - $PropertiesPath, - - [Parameter()] - [AllowNull()] - [string] - $SqlVersion, - - [Parameter()] - [AllowNull()] - [string] - $SqlRole, - [Parameter()] [AllowNull()] [string] @@ -60,32 +40,7 @@ Configuration WindowsServer_config [Parameter()] [AllowNull()] [string] - $DomainName, - - [Parameter()] - [AllowNull()] - [string] - $OsVersion, - - [Parameter()] - [AllowNull()] - [string] - $OsRole, - - [Parameter()] - [AllowNull()] - [string[]] - $WebAppPool, - - [Parameter()] - [AllowNull()] - [string[]] - $WebSiteName, - - [Parameter()] - [AllowNull()] - [string] - $LogPath + $DomainName ) Import-DscResource -ModuleName PowerStig @@ -95,18 +50,18 @@ Configuration WindowsServer_config & ([scriptblock]::Create(" WindowsServer BaseLineSettings { - OsVersion = '$OsVersion' - OsRole = '$OsRole' + OsVersion = '$TechnologyVersion' + OsRole = '$TechnologyRole' StigVersion = '$StigVersion' - ForestName = '$ForestName' - DomainName = '$DomainName' + ForestName = '$ForestName' + DomainName = '$DomainName' $(if ($null -ne $OrgSettings) { "Orgsettings = '$OrgSettings'" }) $(if ($null -ne $Exception) { - "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem'= @{'ValueData'='1234567'}"}) -join "`n" )}" + "Exception = @{$( ($Exception | ForEach-Object {"'$PSItem' = '1234567'"}) -join "`n" )}" }) $(if ($null -ne $SkipRule) { diff --git a/Tests/Integration/DSCResources/WindowsServer.integration.tests.ps1 b/Tests/Integration/DSCResources/WindowsServer.integration.tests.ps1 index 5a64477cb..312710594 100644 --- a/Tests/Integration/DSCResources/WindowsServer.integration.tests.ps1 +++ b/Tests/Integration/DSCResources/WindowsServer.integration.tests.ps1 @@ -7,49 +7,38 @@ $script:DSCCompositeResourceName = ($MyInvocation.MyCommand.Name -split '\.')[0] # Using try/finally to always cleanup even if something awful happens. try { - #region Integration Tests $configFile = Join-Path -Path $PSScriptRoot -ChildPath "$($script:DSCCompositeResourceName).config.ps1" . $configFile $stigList = Get-StigVersionTable -CompositeResourceName $script:DSCCompositeResourceName - #region Integration Tests + + $additionalTestParameterList = @{ + ForestName = 'integration.test' + DomainName = 'integration.test' + } + foreach ($stig in $stigList) { - [xml] $dscXml = Get-Content -Path $stig.Path + [xml] $powerstigXml = Get-Content -Path $stig.Path - $technologyConfig = "$($script:DSCCompositeResourceName)_config" - - if ($stig.TechnologyRole -eq 'DNS') - { - $exception = Get-Random -InputObject $dscXml.DISASTIG.UserRightRule.Rule.id - $exceptionMultiple = Get-Random -InputObject $dscXml.DISASTIG.UserRightRule.Rule.id -Count 2 - $skipRule = Get-Random -InputObject $dscXml.DISASTIG.DnsServerRootHintRule.Rule.id - $skipRuleMultiple = Get-Random -InputObject $dscXml.DISASTIG.DnsServerRootHintRule.Rule.id -Count 2 - $skipRuleType = "UserRightRule" - $expectedSkipRuleTypeCount = $dscXml.DISASTIG.UserRightRule.ChildNodes.Count - $skipRuleTypeMultiple = @('PermissionRule', 'UserRightRule') - $expectedSkipRuleTypeMultipleCount = $dscXml.DISASTIG.PermissionRule.ChildNodes.Count + $dscXml.DISASTIG.UserRightRule.ChildNodes.Count - } - elseif ($stig.TechnologyRole -eq 'Domain') + if ($stig.TechnologyRole -eq 'Domain') { continue } else { - $exception = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id - $exceptionMultiple = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id -Count 2 - $skipRule = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id - $skipRuleMultiple = Get-Random -InputObject $dscXml.DISASTIG.RegistryRule.Rule.id -Count 2 + $exception = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id + $exceptionMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id -Count 2 + $skipRule = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id + $skipRuleMultiple = Get-Random -InputObject $powerstigXml.DISASTIG.RegistryRule.Rule.id -Count 2 $skipRuleType = "AuditPolicyRule" - $expectedSkipRuleTypeCount = $dscXml.DISASTIG.AuditPolicyRule.ChildNodes.Count + $expectedSkipRuleTypeCount = $powerstigXml.DISASTIG.AuditPolicyRule.ChildNodes.Count $skipRuleTypeMultiple = @('AuditPolicyRule', 'AccountPolicyRule') - $expectedSkipRuleTypeMultipleCount = $dscXml.DISASTIG.AuditPolicyRule.ChildNodes.Count + $dscXml.DISASTIG.AccountPolicyRule.ChildNodes.Count + $expectedSkipRuleTypeMultipleCount = $powerstigXml.DISASTIG.AuditPolicyRule.ChildNodes.Count + $powerstigXml.DISASTIG.AccountPolicyRule.ChildNodes.Count } - $userSettingsPath = "$PSScriptRoot\Common.integration.ps1" - . $userSettingsPath + . "$PSScriptRoot\Common.integration.ps1" } - #endregion Tests } finally { diff --git a/Tests/Integration/DSCResources/helper.psm1 b/Tests/Integration/DSCResources/helper.psm1 index 11e601c35..546bcf9eb 100644 --- a/Tests/Integration/DSCResources/helper.psm1 +++ b/Tests/Integration/DSCResources/helper.psm1 @@ -13,89 +13,91 @@ function Get-ResourceMatchStatement { 'RegistryRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[xRegistry\]" -or $PSItem.ResourceID -match "\[cAdministrativeTemplateSetting\]"' + return '\[xRegistry\]|\[cAdministrativeTemplateSetting\]' } 'FileContentRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[ReplaceText\]"' + return '\[ReplaceText\]|\[KeyValuePairFile\]' } 'IisLoggingRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[xIisLogging\]" -or $PSItem.ResourceID -match "\[xWebSite\]"' + return '\[xIisLogging\]|\[xWebSite\]' } 'WebConfigurationPropertyRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[xWebConfigProperty\]"' + return '\[xWebConfigProperty\]' } 'MimeTypeRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[xIisMimeTypeMapping\]"' + return '\[xIisMimeTypeMapping\]' } 'PermissionRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[NTFSAccessEntry\]" -or $PSItem.ResourceID -match "\[RegistryAccessEntry\]"' + return '\[NTFSAccessEntry\]|\[RegistryAccessEntry\]' } 'WindowsFeatureRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[WindowsFeature\]" -or $PSItem.ResourceID -match "\[WindowsOptionalFeature\]"' + return '\[xWindowsFeature\]|\[xWindowsOptionalFeature\]' } 'WebAppPoolRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[xWebAppPool\]"' + return '\[xWebAppPool\]' } 'KeyValuePairRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[KeyValuePairFile\]"' + return '\[KeyValuePairFile\]' } 'SqlScriptQueryRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[SqlScriptQuery\]"' + return '\[SqlScriptQuery\]' } 'AccountPolicyRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[AccountPolicy\]"' + return '\[AccountPolicy\]' } 'AuditPolicyRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[AuditPolicySubcategory\]"' + return '\[AuditPolicySubcategory\]' } 'Group' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[Group\]"' + return '\[Group\]' } 'ProcessMitigationRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[ProcessMitigation\]"' + return '\[ProcessMitigation\]' } 'SecurityOptionRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[SecurityOption\]"' + return '\[SecurityOption\]' } 'ServiceRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[xService\]"' + return '\[xService\]' } 'UserRightRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[UserRightsAssignment\]"' + return '\[UserRightsAssignment\]' } 'WmiRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[Script\]"' + return '\[Script\]' } 'WinEventLogRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[xWinEventLog\]"' + return '\[xWinEventLog\]' } 'DnsServerRootHintRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[script\]"' + return '\[script\]' } 'DnsServerSettingRule' { - $resourceMatchStatement = '$PSItem.ResourceID -match "\[xDnsServerSetting\]"' + return '\[xDnsServerSetting\]' + } + 'SslSettingsRule' + { + return '\[xSSLSettings\]' } } - - return $resourceMatchStatement } diff --git a/appveyor.yml b/appveyor.yml index d9e9e07e1..75b9dd704 100644 --- a/appveyor.yml +++ b/appveyor.yml @@ -8,7 +8,7 @@ # general configuration # #---------------------------------# -version: 3.0.0.{build} +version: 3.0.1.{build} skip_commits: files: