diff --git a/CHANGELOG.md b/CHANGELOG.md index cfca1af7..f821c76d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,17 @@ ## [Unreleased] +## [4.16.0] - 2023-03-16 + +* Update PowerSTIG to Parse/Apply Red Hat Enterprise Linux 7 STIG V3R10: [#1193](https://github.com/microsoft/PowerStig/issues/1193) +* Update PowerSTIG to Parse/Apply CAN_Ubuntu_18-04_LTS_V2R10_STIG: [#1191](https://github.com/microsoft/PowerStig/issues/1191) +* Update PowerSTIG to Parse/Apply Microsoft IIS 10.0 STIG V2R8: [#1196](https://github.com/microsoft/PowerStig/issues/1196) +* Update PowerSTIG to Parse/Apply Google Chrome V2R8 [#1192](https://github.com/microsoft/PowerStig/issues/1192) +* Update PowerSTIG to Parse/Apply Microsoft IIS 8.5 Site V2R7 & Server STIG V2R5 [#1195](https://github.com/microsoft/PowerStig/issues/1195) +* Update PowerSTIG to Parse/Apply Microsoft Office 365 ProPlus V2R8 #1194: [#1194](https://github.com/microsoft/PowerStig/issues/1194) +* Update PowerSTIG to Parse/Apply Microsoft Windows Server 2022 V1R1 STIG - Ver 1, Rel 1: [#1190](https://github.com/microsoft/PowerStig/issues/1190) +* Update Readme to reflect all covered technologies [#1184](https://github.com/microsoft/PowerStig/issues/1184) + ## [4.15.0] - 2022-12-29 * Update PowerSTIG to Parse/Apply Canonical Ubuntu 18.04 LTS STIG - Ver 2, Rel 9: [#1164](https://github.com/microsoft/PowerStig/issues/1164) diff --git a/FILEHASH.md b/FILEHASH.md index c5f24755..28505e0a 100644 --- a/FILEHASH.md +++ b/FILEHASH.md @@ -1,156 +1,160 @@ -# PowerSTIG File Hashes : Module Version 4.15.0 - -Hashes for **PowerSTIG** files are listed in the following table: - -| File | SHA256 Hash | Size (bytes) | +# PowerSTIG File Hashes : Module Version 4.16.0 + +Hashes for **PowerSTIG** files are listed in the following table: + +| File | SHA256 Hash | Size (bytes) | | :---- | ---- | ---: | -| Adobe-AcrobatPro-2.1.org.default.xml | F0B2B9A0106BD445822FD658B135BB5BC1A2AB7DF20F3AFCC726917F25E853CF | 297 | -| Adobe-AcrobatPro-2.1.xml | 04AB72A08B8BEAD381DE0AB0BE5AD762D1ECE5428139A7A6CE2ABD2CC8B6118B | 54113 | -| Adobe-AcrobatReader-1.6.org.default.xml | C91A1AC1475E57CB90BB229633EA32A0ECFB6400479FAB33CB42DBAA6A562C7C | 297 | -| Adobe-AcrobatReader-1.6.xml | 0FEFDC7088E15320B2E94D52A718512DB3B677FB37D2AD0B00AE40E2CE89ADC1 | 54786 | -| Adobe-AcrobatReader-2.1.org.default.xml | F0B2B9A0106BD445822FD658B135BB5BC1A2AB7DF20F3AFCC726917F25E853CF | 297 | -| Adobe-AcrobatReader-2.1.xml | D4EB78A7A898274EA19F9067236068E267387E853D4877C12E944ADD9778750F | 55467 | -| DotNetFramework-4-2.1.org.default.xml | F0B2B9A0106BD445822FD658B135BB5BC1A2AB7DF20F3AFCC726917F25E853CF | 297 | -| DotNetFramework-4-2.1.xml | 4D6A3404C39C2846B686E97D66B78F9B1D1F921520CF1A276CF3CE39FD1F2938 | 57332 | -| DotNetFramework-4-2.2.org.default.xml | 4A5C75A3C0B8E0252DBFDF39D2B68C4172CD36DD8C167575070005A4AE65DA1B | 297 | -| DotNetFramework-4-2.2.xml | 8E4AB02FE2C34C76FA578CADC767F323E714C9B8DAF6373E922EDC2B93A89D6D | 57276 | -| FireFox-All-5.1.org.default.xml | E7C6EC873CBA03D49FAC68B22CD558C1D0108B32D441BEF3C5BD48EB3B95B911 | 297 | -| FireFox-All-5.1.xml | B285EFC9F6A51899D65DC601ACF60A351C087A9C1E6C58F8E499B86BC92F599F | 46615 | -| FireFox-All-5.2.org.default.xml | 9B72F155F7A22AEF2201C6CE20EC05E50FEF8B9EF8DA02AB5EDF920A16B18CC2 | 297 | -| FireFox-All-5.2.xml | D19F32C9F4AA0DD54C38CAF228CF4CC1C2C5E0CD2C5EA8C726768A0DCD8B3D44 | 46744 | -| Google-Chrome-2.6.org.default.xml | 7C81D2916C14787A5B0009A1E9CE9C41FF5E33235B35BDDE4467104F79082215 | 990 | -| Google-Chrome-2.6.xml | 113ACBBA58E7578BC2B550DFAF4256E0B56C441AC8CD5DC80F6C63CD36C5668F | 93353 | -| Google-Chrome-2.7.org.default.xml | 9B1559EAC6822D505F9BCA3C91570DA4818E3D5ACC6B836E774F2CBD621EB598 | 990 | -| Google-Chrome-2.7.xml | EFB0D58A0B2B66020695A79396039A7D93848C13F65648D3079A47749CEAC715 | 93355 | -| IISServer-10.0-2.6.org.default.xml | 95A59D5BB86845326537CC9A82DBB798BFEC89508560D1E34449310A03210AA4 | 752 | -| IISServer-10.0-2.6.xml | C03F56D30CFBA90C6AFAD08CB088A0D968D9DA6EB658A1A4A1243E4E2D348896 | 136405 | -| IISServer-10.0-2.7.org.default.xml | F145355FD8DD5CBFE84E3FC76A69E4AF046D2CCCE04F498704F928503F5F5C85 | 739 | -| IISServer-10.0-2.7.xml | 8102C44BE74D7BC1214603BC77B49890E21E3DB7EB4BEA2652817A6EEEAB218A | 135599 | -| IISServer-8.5-2.3.org.default.xml | 5214CE6723F1FDC543275D4C6D626F9C36428CDBEBCF3952F5DDECC9EF052EC5 | 739 | -| IISServer-8.5-2.3.xml | F31E4A7F05EB5D84260F1ED9272254D68170C6E538EEA922C57F44E2D8A98ED5 | 131783 | +| Adobe-AcrobatPro-2.1.org.default.xml | 90B8C7718C06C930178B621218A629B44A4F18885F0B5816E06AC76E8A1DA329 | 305 | +| Adobe-AcrobatPro-2.1.xml | 014A3C048B3C3CF43597155E564EDB802182C3C14E4BE68DEF85B148071FD320 | 54732 | +| Adobe-AcrobatReader-1.6.org.default.xml | 737AEDF59D64684358B3E58ED4D0C42E5FD99AA4495489B8E625B79CE838E663 | 305 | +| Adobe-AcrobatReader-1.6.xml | E5661CDA5DC7B532EED196E7864F70DE96144E010EC6DB5A3ABA921DBC359664 | 55466 | +| Adobe-AcrobatReader-2.1.org.default.xml | 90B8C7718C06C930178B621218A629B44A4F18885F0B5816E06AC76E8A1DA329 | 305 | +| Adobe-AcrobatReader-2.1.xml | 9D48DF1B16B1D22B60CA4AA59B898421119E88CE0A24BB170D8FBAC1C4DD7573 | 56174 | +| DotNetFramework-4-2.1.org.default.xml | 90B8C7718C06C930178B621218A629B44A4F18885F0B5816E06AC76E8A1DA329 | 305 | +| DotNetFramework-4-2.1.xml | D5DE0BFBE10D48D9EB1D7EDBAD55BAB654D6E7D44AC7BDFF6AA33AFB428CCD29 | 57984 | +| DotNetFramework-4-2.2.org.default.xml | 7A8F784B74E6FA1575783B1849B258F4DD6B7CD87B165802CCA6A16839CCA5AD | 305 | +| DotNetFramework-4-2.2.xml | 294B45354DCFFAF12E1B859C64BEB70C27DB3942E32908DF8F259EA0B6503728 | 57926 | +| FireFox-All-5.1.org.default.xml | C945966A44DEE00C73906437983A9BE413F6012F7E796F127545317096170D61 | 305 | +| FireFox-All-5.1.xml | 7221F60B2D2AF30F506229A4A4429F3D1BEFBE07122CA61132407F35AB0BBC7E | 47024 | +| FireFox-All-5.2.org.default.xml | 246A15D8F07D6ABC702CEA0C105CA89F93F36BDB8702C8FF81D960BEB66B9759 | 305 | +| FireFox-All-5.2.xml | C7A987AADBF8B82CF2C200D7412C09D2C3ED4798B1F4E3F5F99DB627155BC909 | 47155 | +| Google-Chrome-2.7.org.default.xml | 2C72514682BD1028908E63B2F5BAC8A72D5CC35CD1C402BA48EDFC4C5545BD1C | 1009 | +| Google-Chrome-2.7.xml | 9F538B3A661952B4FB4AA38F7CBFEDFB8157B843A2F7046CEB918243FB751363 | 94337 | +| Google-Chrome-2.8.org.default.xml | FE3FC2904EF4CC4D17D6911070C5B6C2CE86F279E7EE7487A2DA7F83F83066D0 | 1009 | +| Google-Chrome-2.8.xml | 09AC14A7D31C20FC91E6DD7406CF22A775CA596AE2DF850A963C915DF483C9BC | 94052 | +| IISServer-10.0-2.7.org.default.xml | ECA311FFECCBCEADB27A2F7CF1FD88C489EDF98206D65C755FBD794437E4852A | 752 | +| IISServer-10.0-2.7.xml | B8757CCF4C8AA892346C70DD8312C3059ACEDDA0A730D0D7FAC190796EBCBE17 | 137334 | +| IISServer-10.0-2.8.org.default.xml | 8482D17674D96660A2E213FDDC2A93552E81C3A4D96A43F8BC6DF08342E388C9 | 752 | +| IISServer-10.0-2.8.xml | BE89F02F51BCEC375D64FA0CC94990E4CC501B8B640A761FB2B35D7C985C77B4 | 137396 | | IISServer-8.5-2.4.org.default.xml | 8034D2946139C2F0A6C93192F60CCE03C7DBEBEBDFA1F2C1FB01BE9597D873BB | 752 | | IISServer-8.5-2.4.xml | 081C0F929BF700DD594719DE11E343660DFB906716916DFB28BCDA4F41896685 | 132589 | +| IISServer-8.5-2.5.org.default.xml | 956622CF2F23549C3AA1660AAC823D5EF0DD73A9C193303D142FD168D4CBDEE5 | 752 | +| IISServer-8.5-2.5.xml | 0F8D082DB66148BE08F530F523B7B2B55124F57ACF5EEB05D699151F07B71B1B | 133450 | | IISSite-10.0-2.6.org.default.xml | 1C1E203AB4D6971068E09CBEB35C9C39BCA13B271C9EFE4FB95BBB9DC2957F91 | 1413 | | IISSite-10.0-2.6.xml | 4FA0844B38F05E4BCDE6B4D01CF3A3C08DBDFDF78A33B4EED2432EE8F06F577B | 113306 | -| IISSite-10.0-2.7.org.default.xml | 66043BE739DA43C4D041D790961D28396707A71FC0EC7DC1C2C53112AF96F13B | 1388 | -| IISSite-10.0-2.7.xml | C60114335C33CF0A6AD3C11B837428FE920E528F0AC79AA08A608B2D6F2AA925 | 110678 | -| IISSite-8.5-2.5.org.default.xml | 1CC2FC4D560DC20509DD735506D3A05CD7013F052BA118D250A5437BAF1A9D4B | 1882 | -| IISSite-8.5-2.5.xml | 6C107E0B975115D4C32A7EE327ECE07A7BB52118F4BB063A3C0FF7C0D98B071D | 124809 | +| IISSite-10.0-2.7.org.default.xml | 0DB0FE0B6B2796ED6555C4029D8571135C55E31DB080B5351C97931EF4338EA8 | 1413 | +| IISSite-10.0-2.7.xml | A84303C30AB3BAA48CAC47B5014BB714704B1D0B480F651FC4832E14B9DF2581 | 112015 | | IISSite-8.5-2.6.org.default.xml | 79EF409B1998296B7187B4F9DC0DC680E7E903C4F5C6DACBA55DD7CBF65ED6AE | 1819 | | IISSite-8.5-2.6.xml | 6FD8BBD8AC83EE0C14C5D64ED57D00FDCA692C9523F4D5DB7DF02191A90DF5AA | 122787 | -| InternetExplorer-11-2.1.org.default.xml | F0B2B9A0106BD445822FD658B135BB5BC1A2AB7DF20F3AFCC726917F25E853CF | 297 | -| InternetExplorer-11-2.1.xml | 8E0E2B418E99BA217D9E0A4060D62FCCF053F6E6A1C5B5EB8ABDE6477A75C2DF | 329761 | +| IISSite-8.5-2.7.org.default.xml | 41C5060A27C20B65330926366D4EDFF5C7108538BE6F9C314F35F991B2B939DF | 1819 | +| IISSite-8.5-2.7.xml | 95A8C6FB824718CC9A13F3AF24781DAAEBC802DE2E677BC000E3A3EC817AED24 | 123589 | +| InternetExplorer-11-2.1.org.default.xml | 90B8C7718C06C930178B621218A629B44A4F18885F0B5816E06AC76E8A1DA329 | 305 | +| InternetExplorer-11-2.1.xml | 1CDBB4ADA92FFB610BBD57F05D7055FC108CBBCA7770473907E8024C5637234B | 331854 | | InternetExplorer-11-2.2.org.default.xml | CFAFCD73ED15B911604867FF6423AB21CF6F66976DA781D58C2FFC7FCA70CF60 | 299 | | InternetExplorer-11-2.2.xml | D1C082EEB7B774413BCDE4BA7293FEAAD291F53A5FBDBB2E649F25E8ED61150E | 334340 | -| McAfee-8.8-VirusScan-5.16.org.default.xml | 0122D7BC3AB85E7EEC2C8A989687541AEB6A7DCC025692894EB208B9ED5EDF2B | 760 | -| McAfee-8.8-VirusScan-5.16.xml | 5A2E6A31CA07BF76F6F3A7F77D3FC1A180128D390C70F4ECFFFA3F9B19408625 | 241862 | +| McAfee-8.8-VirusScan-5.16.org.default.xml | 28792D63E69F797CA02CCAE52F537B1001D9069BD7DE4F5A73375424C19FE660 | 777 | +| McAfee-8.8-VirusScan-5.16.xml | 22CAEE788CA69690819D46548D19E40163FD8EB799F8EC7FAA4E5FB714C4F445 | 244268 | | MS-Edge-1.5.org.default.xml | 562551BABBA8AB74289B0FF4E7C88914ED7B771D35D4FADC33305459C7C11B3C | 1057 | | MS-Edge-1.5.xml | AF60D4691669E4A78E7BD907D32AF6FE6168EFEC8773DC71728EBDE4DA05EB9D | 115218 | -| MS-Edge-1.6.org.default.xml | E191F7717B75893560A6CB4C9293CA84BD279116730C6790733AD90DCA452A13 | 1040 | -| MS-Edge-1.6.xml | 8F2B0A0066454392D766F3FB12A99880BE64967AD8A412B3E4A0169B168F662C | 114286 | -| Office-365ProPlus-2.6.org.default.xml | 630EF8AE632A67453ACF1983C01460CFAA8140E034F121B8DD9CC2AD828D8AFA | 2401 | -| Office-365ProPlus-2.6.xml | 9EECC40ACC3387E33CE35251763D47FEF89D15F9594684857A0FA09BEF3A0A8A | 372098 | -| Office-365ProPlus-2.7.org.default.xml | 76C543682926BE1640EF623637BB9C8CB08A72CFFEF19A7C527E9502F710257A | 2397 | -| Office-365ProPlus-2.7.xml | C11EAD7FE98355F91A9569561893771D2A8837D0CF44017AB41910EBFB1DCB00 | 372099 | -| Office-Excel2013-1.7.org.default.xml | 7112F164172614EEB9F470466C91609C1AA0EA8AD13F2A1A5AB0147FB0F8E790 | 418 | -| Office-Excel2013-1.7.xml | 7F3C9FDDA62BD48C271890C2150381BD40A3E40254D5ED8702BA612F52B9863C | 109725 | -| Office-Excel2016-1.2.org.default.xml | C7D6B6B2EFE31CCDBC9A072AEC52E17D5F9C7C52F326CF480E4B0BBCBEBBE779 | 517 | -| Office-Excel2016-1.2.xml | C1EEAE1896224260C7EEB48EFEF773D3ECE42F1BD799CB1D4E923CC299CAF812 | 107254 | -| Office-Outlook2013-1.12.org.default.xml | 6DE2F8E0E9DF57570762FBB22BAF17F389C74DF88E8737D9463DA7491C2DE862 | 298 | -| Office-Outlook2013-1.12.xml | DCD510AFDC92DD03136480DA09353C4919E01438118D6D0FE9232CE933E7E4EE | 192069 | -| Office-Outlook2013-1.13.org.default.xml | E0AABF9650DB6A37E05A15A6B943C7B05AA31B2581506380188172B171BA2339 | 450 | -| Office-Outlook2013-1.13.xml | E7020C1084BD4090C8BB50BE8DFC0B865C3698CBF1802C0D1F7E01EF261437E1 | 192186 | -| Office-Outlook2016-2.2.org.default.xml | 4A5C75A3C0B8E0252DBFDF39D2B68C4172CD36DD8C167575070005A4AE65DA1B | 297 | -| Office-Outlook2016-2.2.xml | 509C5F1A353E9B18F5AF2EFE11D4389D47A89581676CC8BC3F71BBB9FDD4FD5F | 149729 | -| Office-Outlook2016-2.3.org.default.xml | 985584822EF58BCE107E522081D8FB5EA24CC74856040D93EC88252958F12EDA | 297 | -| Office-Outlook2016-2.3.xml | 52CC95E49055AE1DC22B2643868F38093979D9F925399DDB3EA9F7692F606C9B | 149853 | -| Office-PowerPoint2013-1.6.org.default.xml | C91A1AC1475E57CB90BB229633EA32A0ECFB6400479FAB33CB42DBAA6A562C7C | 297 | -| Office-PowerPoint2013-1.6.xml | F58B0231BCF94AF8E0808FEFE48CFC00E4F1F0636E73ED7E974ECAEB1F5A46AA | 93353 | -| Office-PowerPoint2016-1.1.org.default.xml | 440A06FFB09F4FECB3546372E20FDB16C30F84B55F41EA5DA1AC891491E11F4C | 420 | -| Office-PowerPoint2016-1.1.xml | CEAF4E6451621201D948A61DBFE57C303AA2F025CD0035374F2B24C68D9ADBCB | 90836 | -| Office-Publisher2016-1.3.org.default.xml | 6E4C29EB64180DC23653B089C5734F0E4D493FE896DD0A2F4FCAFDC6407DD6AE | 422 | +| MS-Edge-1.6.org.default.xml | 97393C5F48012A8890502024D487EF0DE2D67DE47B3EC5FD186352D08B233390 | 1057 | +| MS-Edge-1.6.xml | A292381A242DA221D31BEAB2A3398E3599187B9E80C8DCDA92FB48EED9F9AF73 | 115719 | +| Office-365ProPlus-2.7.org.default.xml | 43C03EA6FECC580FA689DBF77CC9E860D18C7ACF75A8A34B006A3699B8697AFB | 2448 | +| Office-365ProPlus-2.7.xml | CC7BC37FEEF400CA37A3C7D83EEB77D51852FAF00ED47F9D3F0E0E2515B81140 | 375810 | +| Office-365ProPlus-2.8.org.default.xml | 1E07FF9CBB7524B55843474F1BC04D9C2CAA1111F29EB9965F6AA2137EB26385 | 2450 | +| Office-365ProPlus-2.8.xml | D7CB2059E061425C28777F8953976C16897A6F813898AB46FA99EDED997F434E | 375774 | +| Office-Excel2013-1.7.org.default.xml | 6A8FBC7AD79015A5261C617A2EFC0084E58BCAFAAD3FA2B8E61BC01A860C102C | 429 | +| Office-Excel2013-1.7.xml | E99C7824EB50B0727D7834F8D68FA6840BE8F69921DA49525C3B2921B9AD5A3B | 110738 | +| Office-Excel2016-1.2.org.default.xml | EE134DCD15DEFBD412AF18477F75248DE83A705E10CA061776F2AE74884749E3 | 530 | +| Office-Excel2016-1.2.xml | 5685CF03939CA92E8F4C854095344EA88B613E3CC1AB581E3DA4F70D70E69B77 | 108096 | +| Office-Outlook2013-1.12.org.default.xml | 6691883C5ACE1CBF9ACAFC536E0E335620A9A1B158B75EAB7FE2E661C7C31A63 | 306 | +| Office-Outlook2013-1.12.xml | DBF4FF03D3214F753B76C5ADFE0FEFB228E87EFD767BBDF1D3847080D67CF3D4 | 193739 | +| Office-Outlook2013-1.13.org.default.xml | 624856564A2FB618BDF6A41263806BC2BE08B1AE58226425C07EFBADDC98FAF5 | 461 | +| Office-Outlook2013-1.13.xml | 3446E121027400CE6C4834E4507EA94B5CFD24F65CFA4D5F0524873D32B07D8A | 193858 | +| Office-Outlook2016-2.2.org.default.xml | 7A8F784B74E6FA1575783B1849B258F4DD6B7CD87B165802CCA6A16839CCA5AD | 305 | +| Office-Outlook2016-2.2.xml | 9246147D3FA9E79A70F7024A3AC38FF526341B84CECD6F7175958A69D83B89DD | 151022 | +| Office-Outlook2016-2.3.org.default.xml | 65560374E19492C3BBA42CC0A40AFC2F74C82AD01977E5061F41A4BCEDC2BF8E | 305 | +| Office-Outlook2016-2.3.xml | ABF1B429B65076A3C44984451975C4FB264F2721CD47244F8C900290DB2011B0 | 151146 | +| Office-PowerPoint2013-1.6.org.default.xml | 737AEDF59D64684358B3E58ED4D0C42E5FD99AA4495489B8E625B79CE838E663 | 305 | +| Office-PowerPoint2013-1.6.xml | 563E20C0149E0CB20880EB777439A7B67C4FE1BBF4347EA7677048E6DD2D2EAA | 94142 | +| Office-PowerPoint2016-1.1.org.default.xml | 3FEE8C811ED3DB6986E24ABF9BBA833975A908C82EFAECC2E91755E10D02C30C | 431 | +| Office-PowerPoint2016-1.1.xml | 8F17DC18B9997782E98DACA5044ACB1E63B178A80240AE130D0AC7F64B703531 | 91626 | +| Office-Publisher2016-1.3.org.default.xml | 87A4435821A71C1861AC3F9103E35FDE176D42FCE97880B4B26439CF49F58C0E | 433 | | Office-Publisher2016-1.3.xml | 89F37914B868D581E4253D8ED819544B61C5D5D750A6F09598FBCAFB41E618E3 | 37769 | -| Office-System2013-1.9.org.default.xml | 4036D829A31308CD45CC8B5A76A9A84612F2593B7700190B5FF1B08EFBF089EF | 852 | -| Office-System2013-1.9.xml | 96E75BC4A4922BB6D57BE63701AC030EC055AB1D660A8F45D3668E6B0A798959 | 121552 | -| Office-System2013-2.1.org.default.xml | 5062DB411E0A0E8F42774CA34BB51D8DDCFCE5C5CA316E354520DE4D7C3D8B20 | 856 | -| Office-System2013-2.1.xml | 89EEA327D7A227B42B981B5A8EA8D80A4E2E7D18F8C40B03C048B09CDEE1F397 | 116188 | -| Office-System2016-2.1.org.default.xml | F0B2B9A0106BD445822FD658B135BB5BC1A2AB7DF20F3AFCC726917F25E853CF | 297 | -| Office-System2016-2.1.xml | 9EDFB96DA919A0B9A002F01576949275A3A6D6FC68E25B62729FFCC30C0AD357 | 64487 | -| Office-System2016-2.2.org.default.xml | 4A5C75A3C0B8E0252DBFDF39D2B68C4172CD36DD8C167575070005A4AE65DA1B | 297 | -| Office-System2016-2.2.xml | 4B2AF660B2CECFDFD5113710652DE5A3A41DBF6C6E5ACF88C488C35C6DBD1962 | 64776 | -| Office-Visio2013-1.4.org.default.xml | 955053441F378268498E15AC859046B2E2805E405AC294DDD8C6493A3FD2CC64 | 297 | -| Office-Visio2013-1.4.xml | A1CFAABF789BD8C3958D35415F23B5B192F028CA98EDD391ECCEE85D87B6543F | 30039 | -| Office-Word2013-1.6.org.default.xml | C91A1AC1475E57CB90BB229633EA32A0ECFB6400479FAB33CB42DBAA6A562C7C | 297 | -| Office-Word2013-1.6.xml | C6D5620E7977EDA5B59134D0DABFA42AA4AC6C87EFB3FFF6502CE615DF157285 | 80779 | -| Office-Word2016-1.1.org.default.xml | 724DB22065C11F47D376186EB1A5F959C9721A47A3A2E00F125DFB36BBD96EBD | 420 | -| Office-Word2016-1.1.xml | CF23511AE9EF837FE49B19F0888F2CC38D1D4E3BF1F054EA35903732A6781858 | 87615 | -| OracleJRE-8-1.5.org.default.xml | C832884FF191F9D9AD20652CBE1D9C68BE15C2DD9B57CF15B8F85EB1F770BBEF | 491 | -| OracleJRE-8-1.5.xml | E61F226FA4BC02C4225A3399E4543A3E83DA51F8F813650E246F6472ACFE3982 | 44880 | -| OracleJRE-8-2.1.org.default.xml | 3DC5157025F594B12BD2E1F5FC7B76818897F5C69555E8396DC8AACB986C8644 | 492 | -| OracleJRE-8-2.1.xml | B76FEF48981D375C0F604D586D98622D05D8121AAB81A8BB06298BE650FB8DCE | 45903 | -| RHEL-7-3.8.org.default.xml | 2E74668308150FE9E2F8E817899E5D498E32327AF59E0AB5F3BE607864AD47C8 | 6589 | -| RHEL-7-3.8.xml | 19A0CF80DC537555C3F568DDBA0575AEE4FE785630A8A59BCD9988774CD31AE9 | 583777 | -| RHEL-7-3.9.org.default.xml | A4D0A233417A210F173ECF0B20935162045B9E3B67BDB24EC1D39DF826424F16 | 7417 | +| Office-System2013-1.9.org.default.xml | 45055F756C705090A9F8D6470EF55C2FC8838EA00B2103E372E22B948A06DF63 | 869 | +| Office-System2013-1.9.xml | 346A48CA6FD98889F0E60928AA0E87E138CF4E8A45E1BDB82BB04005428638C5 | 122545 | +| Office-System2013-2.1.org.default.xml | 96C2EFAF8780965F18914EB31F6C869AF63ADDB780CB3EA537626BA7DA2B7358 | 873 | +| Office-System2013-2.1.xml | 40657EF393151DFE4D8FD1B5ABD4C5E87DD4AFD3A7F0B230DD22502F0B9DBF4C | 117184 | +| Office-System2016-2.1.org.default.xml | 90B8C7718C06C930178B621218A629B44A4F18885F0B5816E06AC76E8A1DA329 | 305 | +| Office-System2016-2.1.xml | 37E5D07510D1AEC51E6D08A502B7CAFDB3B316188EC2EE6B84D985CC1207DAA7 | 64932 | +| Office-System2016-2.2.org.default.xml | 7A8F784B74E6FA1575783B1849B258F4DD6B7CD87B165802CCA6A16839CCA5AD | 305 | +| Office-System2016-2.2.xml | 21F9CF9D4F17F183D6D5DF03090866E502F5C3D36BBD5B81FAAFFAD62A047EB7 | 65225 | +| Office-Visio2013-1.4.org.default.xml | DEB619FD6632472F27796C703DB93523035A5BCD84A2FE878DABBCFC968FFFD9 | 305 | +| Office-Visio2013-1.4.xml | 4DDEFCDD8E1D316BB2498D95CC033CBABD536A90EF9D6D1278127F4C4FF8DDA8 | 30296 | +| Office-Word2013-1.6.org.default.xml | 737AEDF59D64684358B3E58ED4D0C42E5FD99AA4495489B8E625B79CE838E663 | 305 | +| Office-Word2013-1.6.xml | 85E667D9899F3B98270275D1E2F1E5BEAF3AC39C0D8F3143E61F53FBA74263B9 | 81466 | +| Office-Word2016-1.1.org.default.xml | 7C6CDD5943A445A748835DDAEA1C2AC2615A2BC21B0570751F234E5AB5D7B14B | 431 | +| Office-Word2016-1.1.xml | 3309F6DCAFFDC4521E2B40CD6D1FC8DBEFB69972B64BBEC5C4C43BAF74542B84 | 88318 | +| OracleJRE-8-1.5.org.default.xml | 9F29E6AA7A905712FC4BBA768764219CB4CD7F259A0515A486E0E9EE4BE03F66 | 502 | +| OracleJRE-8-1.5.xml | D8D451B6E2B88C4F7FA14809CA7E6485E19C6295460342C01EF78E6787F073F3 | 45264 | +| OracleJRE-8-2.1.org.default.xml | 83D686E66B98E318AB87ED95F05B1C01265DB40D202C9F1D4BEDE52790EA834D | 503 | +| OracleJRE-8-2.1.xml | 34B2B1060088BD4A915B3F713464A636DCD98D6B8A32163F831A485F51DEC211 | 46312 | +| RHEL-7-3.10.org.default.xml | 3A22CFED34A7C489B98C7663B16235B044D0B0B01BF8A66B594CB0D08CF6A3B8 | 7594 | +| RHEL-7-3.10.xml | ACB557ED8C652EE1EB42B4398559E3199F565ECA1479F7AB8C93A31B03769B67 | 601397 | +| RHEL-7-3.9.org.default.xml | 9048B69CAD2A4E9C53C2F8865C6AD0965FAFE20D71D345EFC19F3779F6C9F489 | 7470 | | RHEL-7-3.9.xml | 6563FE66082A9329FA349507801FB4EA2FCC7145AA30CF8A35E4466E9D30373F | 592180 | -| SqlServer-2012-Database-1.19.org.default.xml | F0BCFA8BA56A51AB40F7AC1433B0BDB70F8FD15AB83BE236E8FCD182EB12818C | 427 | -| SqlServer-2012-Database-1.19.xml | A8B5D94FA2D1EC2E9F85C034FAA7453F6554050A10D32A4534F787CC805A18D4 | 85981 | -| SqlServer-2012-Database-1.20.org.default.xml | 88F0F0E3C3828B8DF4861F67F528D385DA47059F1255E35538209335B9F36C0C | 427 | -| SqlServer-2012-Database-1.20.xml | 5EB429E846A241764E46144C2CEA4645FEA23291BA8B6DC24000F0054E6A1D83 | 85927 | -| SqlServer-2012-Instance-1.19.org.default.xml | CBDC914F56AA1E306F5AF10B611B4C0B95E5CAAC8C2A792C0E640557FFF247DC | 1077 | -| SqlServer-2012-Instance-1.19.xml | 198E9CFB9C9B5F115A41DBED956416389CF03E603D21CC3B6EF343E18308A184 | 716637 | -| SqlServer-2012-Instance-1.20.org.default.xml | 2FFFB13390E0D6D4DDFBCCC6BB0E607D2CB028F57A521D85610B2D04E5D4230F | 1077 | -| SqlServer-2012-Instance-1.20.xml | 75F35AB3641E3F11BBC173C57156706A5B57F27AB1FC511CA6256DBBFB9BA962 | 709174 | -| SqlServer-2016-Instance-2.7.org.default.xml | 575803F6ED47AB833E3BD857BF7F049A6A986A74FCE54213739A0B87803814B2 | 610 | -| SqlServer-2016-Instance-2.7.xml | 31D0FD81EA21C3586C00A538529058E8C2D046C6FD5D2E49D1EEC1F58F6DB9A5 | 548824 | -| SqlServer-2016-Instance-2.8.org.default.xml | 36FD816F5FCAD2AF38C53BBDEAD90EBB6DFE195133613B5F407E6399C0AF2BA9 | 610 | -| SqlServer-2016-Instance-2.8.xml | 6DDFAA3449EDB8C1D3518F317D8ADBE9048751A4FEE71C5A207D07FB4C918F82 | 549523 | -| Ubuntu-18.04-2.8.org.default.xml | 08CF6671D3A376D8537B68E48971635C07ABB1B49BFC12F47BF7A2C7D153E2D2 | 6879 | -| Ubuntu-18.04-2.8.xml | 978B0E087CBF6A33E4AF2FCEBB1D6122FC39FF92FB583CBEF229161ADF7E532F | 484056 | +| SqlServer-2012-Database-1.19.org.default.xml | 282BCFAC931096F13AA661132D8E0BADF93A17034C98057A68DEC20D43612C88 | 438 | +| SqlServer-2012-Database-1.19.xml | EA869867AE70E1ED3E80906C7CE800523071A95CB1DE72492F1DB20C4A924A9D | 86839 | +| SqlServer-2012-Database-1.20.org.default.xml | 572218B2318BFB1F1160B2D1835DE985D09F269260038ED6CFE26573573C5014 | 438 | +| SqlServer-2012-Database-1.20.xml | F01743D2CA5E914C215ECB13D86A5D58723DD7AB7C328B81D284911DEFA0D9C4 | 86785 | +| SqlServer-2012-Instance-1.19.org.default.xml | D78829081352C7766AB1E9639C1649A46FDAD69819BCE14599CB3A5C096DF4E6 | 1098 | +| SqlServer-2012-Instance-1.19.xml | 1313489DECFD7B137F53C9A55DA8068075CDD8015DBE24AEC77CC4276D910185 | 725272 | +| SqlServer-2012-Instance-1.20.org.default.xml | BB9345EFCFBDB1FDCF731620B233BBD6B1CFD8856A25422D753D9D668D850860 | 1098 | +| SqlServer-2012-Instance-1.20.xml | 6E8F27FE02ACF7877AB36F90F8C2CADCD8A93A3500288D41EF06070E7C992C66 | 717809 | +| SqlServer-2016-Instance-2.7.org.default.xml | B966FDBE624E10243DFC71F153A7656F50A414E9A41C7DFAB286318C7783D67F | 623 | +| SqlServer-2016-Instance-2.7.xml | 689D85FE26F58624FA6493992501D1EB565376805FFF1BAB1EDF2F9B6875C416 | 553591 | +| SqlServer-2016-Instance-2.8.org.default.xml | 8F7BABE8A06CF091B7BA30D9A7038CE055D18036A0CE47EE5E89C01FDCEBC0BD | 623 | +| SqlServer-2016-Instance-2.8.xml | 91D9A3D72336382ED3B2FABCD2311BCCA43302B9774085A0F93443879867C923 | 554296 | +| Ubuntu-18.04-2.10.org.default.xml | 69E03214AA101407BE74394CE1D2CBCD133EDA7AFEFF2C2E3F05D84201195403 | 6920 | +| Ubuntu-18.04-2.10.xml | 8EA37985B73C1114235CA1E20611896E37969C56D13ABC5F43B08E78A696720A | 491684 | | Ubuntu-18.04-2.9.org.default.xml | 937F52BBA9FD68C3E227705A6B7A64EB934B9042C2FBFA7DFE26FAB515135521 | 6922 | | Ubuntu-18.04-2.9.xml | 5180802F8E98B6B0B113BFC23EF235600690E753BED9C3C11ED8920A69E0C13A | 486825 | -| Vsphere-6.5-2.2.org.default.xml | A9EE6773BD2F1593A0E33BD4E048AD43DE3E5709E5BE089CBBF7FB3C4B30288A | 782 | -| Vsphere-6.5-2.2.xml | F7324FB4B6CDF705560BA1DA66AE1EB4A538BDC78D768813B3D1C367D2B4964B | 142766 | -| Vsphere-6.5-2.3.org.default.xml | E7BDBC6948AA1E0999792F9054C2065B4AD0AD304B7F033D1378270A355D715D | 782 | -| Vsphere-6.5-2.3.xml | 4E152C8A94517F45022D1C0BB8E5F3D3646D8CD1B4747C00034B3E646F1E678C | 144921 | -| WindowsClient-10-2.4.org.default.xml | E0BB6F34998B2D1B9E7E25A7C9EA5ED43E448EF0EC3BF8CE9F030C5DA3A33037 | 5989 | -| WindowsClient-10-2.4.xml | 9F90E8AAE9CEF0987D1BB5E2EE00254CFF504EA0B995D54100767AE4FB1B3F98 | 534076 | +| Vsphere-6.5-2.2.org.default.xml | 9050F39FC140A633AD41A884A3E0F87720EFA566C91E82E74A13B918B8C04323 | 797 | +| Vsphere-6.5-2.2.xml | E3A2F2D4C89416D14A8F3AB4DC6A5444DEA9683AFB2A21A653749995F289AD24 | 144122 | +| Vsphere-6.5-2.3.org.default.xml | B8539D6118706486E3F451AC2466FE5BABC1C9DB30C1A48C80D3FFA32354056E | 797 | +| Vsphere-6.5-2.3.xml | DE07939A8EC08F52E77FF411FF04359FCE02035C5038B70FBA2ADC42B994BEAA | 146293 | +| WindowsClient-10-2.4.org.default.xml | FDC65417DFF986055A4CE952B575479EE650DC566D4C5C35CEB3B5B2140EE207 | 6086 | +| WindowsClient-10-2.4.xml | C326D08FFA97F42AE5EFF12E50DC4925C8E240C20D6FD4DFDF74F9174A5B8482 | 540794 | | WindowsClient-10-2.5.org.default.xml | E39DBCAAC643D0CF020B3FDE5C655963B614DA55D7FF0264D55348234C5318BB | 6086 | -| WindowsClient-10-2.5.xml | 519508254CFDE17F0308F8CA4FBE523567B618351ADBA0DC3103E9EE65D5067D | 534039 | +| WindowsClient-10-2.5.xml | F37EBE9608CB4C0997AED5BA9F1A0C7ABFE3379CF7E81418E0639EF4CE5052CF | 540755 | | WindowsClient-11-1.2.org.default.xml | C03F1939072743A5F17C771C3E120976996FA159D293064EB8B4FEBBD3EF6070 | 5988 | | WindowsClient-11-1.2.xml | B0D8BC1B572AB08ACBD4CFEF99E88A2B4AAD80772C05C904A8F7FA916FDCD9B9 | 520538 | -| WindowsDefender-All-2.3.org.default.xml | 2EF81E87FDF1D24158DCD2BFD2176921ED21ABBEA2C29ED14096EEEA54F8EB40 | 1065 | -| WindowsDefender-All-2.3.xml | 34B17B00509BA3F4934861F383E2C133FCA2F19C65F38AA6DB77DBC9B0728A24 | 95099 | -| WindowsDefender-All-2.4.org.default.xml | 96EA1084F1F2A3C9860013346ACCD29A805A73D79E6A313E759CDBC775A906E8 | 1065 | -| WindowsDefender-All-2.4.xml | 6657A5CD51F7396976A05A03D3EDB358303D1D320935B51A953765E77063EF6C | 95829 | -| WindowsDnsServer-2012R2-2.4.org.default.xml | 7A37266D66DFDB51BDCE149BF242559529AE0A3CB111EE3D7124CB02BFDC6B3F | 297 | -| WindowsDnsServer-2012R2-2.4.xml | 597FE2821DDF156B17D136FF132AEF287E7CC60DB6263CA256385197CDBA24B6 | 241691 | -| WindowsDnsServer-2012R2-2.5.org.default.xml | 5C4EAECF345C25E9688AA38AFEC397FFA392213486C8E9B0FA06B080AECA50A7 | 297 | -| WindowsDnsServer-2012R2-2.5.xml | 5E54B2B89FA2E07B721B5461C2BBC2A4C831D696198D6EFD02D344C01CF22C9D | 242163 | -| WindowsFirewall-All-1.7.org.default.xml | BF71BCE35DD772AA32964B7E6E3A20FCDAAA24C494FC51E58DEA5DB6DEFFC0EB | 945 | -| WindowsFirewall-All-1.7.xml | 2B8E3CC4782FB3DC7718C1E6E75A7638E5CE7BEF417FA37530C807FEEF9355AF | 64830 | -| WindowsFirewall-All-2.1.org.default.xml | 1EAC25EE60798B820C06DC8895361F69E31ED9A2950A8D3E86053F6BD9357C06 | 957 | -| WindowsFirewall-All-2.1.xml | DE85F4E98D148246857F5C7356437371167BD9BB41BE3ABFF3E8B0B66BB12848 | 65807 | -| WindowsServer-2012R2-DC-3.3.org.default.xml | 836CCA23864E7ACBC60CD988879F95BAE5E6F08CFAF0F0A60D54360848AE920F | 6935 | -| WindowsServer-2012R2-DC-3.3.xml | B257636D672651195B540336EEBE4A216E98041493FC85980CB71373E4CFCCC6 | 765949 | -| WindowsServer-2012R2-DC-3.4.org.default.xml | A727A575B307945E8430081B484383F732FAB7153EC0F14E3F33DB6D7BEACEEB | 6812 | -| WindowsServer-2012R2-DC-3.4.xml | 3E89014E572DA400DA8D668985317D940B688AA856569F2BC56606CF43C32C86 | 764218 | -| WindowsServer-2012R2-MS-3.3.org.default.xml | 1E04A871219379FF22D44916C0CE4143979F5082C9BAE9678D0DE29C638F1668 | 6377 | -| WindowsServer-2012R2-MS-3.3.xml | 19C5930FBA78D6D4D619E9CAEEA505F63EAD73A600D220BBB33BF5EA98B40F02 | 661643 | -| WindowsServer-2012R2-MS-3.4.org.default.xml | EFDC3D61F4DE48302E1AF28FB8C84F165AFA5BC67323EF87C32B653623D6D384 | 6254 | -| WindowsServer-2012R2-MS-3.4.xml | 71559E19258D176E6E4FADC311A7DA1235DAE285EB02C4AC690567117EF3ED71 | 659969 | -| WindowsServer-2016-DC-2.4.org.default.xml | 48F25F35D1F8DB5401FE38088B58E4822EA38A8244D266EC3B699A262CDB8A5C | 5901 | -| WindowsServer-2016-DC-2.4.xml | 0DB57634F42E73C46EAC3BC932954927A8932887721B4035BDB48197F954773A | 550779 | -| WindowsServer-2016-DC-2.5.org.default.xml | CBDFDF1C21BD31D29ABEAA2B9A8E1F6D6A2B25A3D8D2460F6BD8FC04849E9FDA | 5901 | -| WindowsServer-2016-DC-2.5.xml | C3D3D5B3F8138A91AC036D4AD6EB78893F41C3AFA9358A52B9147777CAC3EBBC | 551071 | -| WindowsServer-2016-MS-2.4.org.default.xml | F196F497D58C066D3F1566AB048F8D55DA7AE75CF6E42834CAF4066BE4564545 | 6015 | -| WindowsServer-2016-MS-2.4.xml | 26ADB3522D644C726C5855D980B295BFA8EB6C3EF8B44C5DB892CF728F7C48EE | 474194 | -| WindowsServer-2016-MS-2.5.org.default.xml | C573B016540D824D448A9EC5FE004ED963A223B5DE09F693CF276CD1A0E155BE | 6014 | -| WindowsServer-2016-MS-2.5.xml | 33B6553EEEF755D1DBE476DE1C81F0722C4DBA8694CA77F2262A986FEB5DA03B | 474790 | -| WindowsServer-2019-DC-2.4.org.default.xml | 683B2A4EE968FBF488C563122DFE55304A0EA37C5843A510DFC5C8459BB0DD55 | 6002 | -| WindowsServer-2019-DC-2.4.xml | 77AFD942245805482D991269FC32B5D4F9C1D6FBAEC00C2EB274CA4418D03CA2 | 558030 | +| WindowsDefender-All-2.3.org.default.xml | C0577AA9DBF69E5CC7323B458E8D956A678FBC20D1786CD5FF972BABF8B3BD08 | 1088 | +| WindowsDefender-All-2.3.xml | 9B56A4155EC35DC5D1E5E502367513DA01FFCDC02D5FF674A1D184C78BA575A0 | 96015 | +| WindowsDefender-All-2.4.org.default.xml | 38BA1392F6B093D85D8A6289E4D2C76687BBA2F3E4077681917DD2A841CD8102 | 1088 | +| WindowsDefender-All-2.4.xml | FE2A715FF673114A8571FFB92D364072D7B0FBD67B2477A616F3F24D2748D12F | 96852 | +| WindowsDnsServer-2012R2-2.4.org.default.xml | E0665B930674B4382F93865B8F0FEE6D9ADCC2CDD263EC06D5ECBBC8751EE62A | 305 | +| WindowsDnsServer-2012R2-2.4.xml | 12849FAFEADA9477E79C42C19AF5636772AF682B3BDEB40C71393F57ACC537DA | 244440 | +| WindowsDnsServer-2012R2-2.5.org.default.xml | 331B93A209C36BC1DBB5760FBA8F2BF5E0788E7A4D47C58A0697570882B280DB | 305 | +| WindowsDnsServer-2012R2-2.5.xml | FC766E2AE054AE1E898263A49CDFE61A3F029C56B5BE7C7F6ED81F6115E86873 | 244914 | +| WindowsFirewall-All-1.7.org.default.xml | 64E9FFA9B456C36DD36B5824BF641E473931B5C350F473DDFFDF31B1B64DD016 | 966 | +| WindowsFirewall-All-1.7.xml | BBB13C6D675EB591D972EF8AD9B46472CFE80FCAD76E9D453586E6BE430F01B6 | 65518 | +| WindowsFirewall-All-2.1.org.default.xml | 54A9F5D8C7E859CFC8C177DFCD4621814166A4DC6FD1967BAB03062B17489949 | 978 | +| WindowsFirewall-All-2.1.xml | C2D9F1754E8F3A537448E73A1F627E94E72F2A5A7900939E5823B6AD694CC617 | 66534 | +| WindowsServer-2012R2-DC-3.3.org.default.xml | 8040D5FDCF6EC673550168EECBAA8295DE37CE261D5F6679C57CE3A39150FE71 | 7046 | +| WindowsServer-2012R2-DC-3.3.xml | F43AB8FA145C575EC2887F94029613F70AA1DD0B6B4074624593564EDA44C98A | 775734 | +| WindowsServer-2012R2-DC-3.4.org.default.xml | 5423A10BF684CB3FA5F64C77670BA1AA3C94A69FE176065C9720B763019B35C4 | 6921 | +| WindowsServer-2012R2-DC-3.4.xml | 47373591AF4F0186F7949C5354A73A277DFC158211A5A49CB4F23D6AC3F98563 | 773991 | +| WindowsServer-2012R2-MS-3.3.org.default.xml | 30D3509BF3AA9BA29E82E5EDFCA82AE8DBDF450A6A178B8A3A61568A56F0E18A | 6476 | +| WindowsServer-2012R2-MS-3.3.xml | A415746E95E262FE7547687C22B89555694C47A40C182F1E4AE403AF7DF460A4 | 670131 | +| WindowsServer-2012R2-MS-3.4.org.default.xml | 50F77131D17E1FE349CB81FBC8FE7278DEBB09A3321F75D92B9F3AC85352D869 | 6351 | +| WindowsServer-2012R2-MS-3.4.xml | BBC62A7ADC3365A3AED0067051712C3643FFAAB9157129E0FEE322768036E4AA | 668445 | +| WindowsServer-2016-DC-2.4.org.default.xml | C6F13BDEC76ECC5F02317296D189312D401A9522D6B65F478B4CBB5D2FB39ACE | 5996 | +| WindowsServer-2016-DC-2.4.xml | 411E53051F5154C377653359438BF3633240D74957A814664EE3A97A7022F069 | 558255 | +| WindowsServer-2016-DC-2.5.org.default.xml | A051E222710532B44CD2A67A0D953344D53CA5FB38BE49DDD69941D16B7AD50C | 5996 | +| WindowsServer-2016-DC-2.5.xml | E7BBB817054921AD9CC22912A6ECBE418D14F3A706694A2A9D03EFB62C9121B3 | 558541 | +| WindowsServer-2016-MS-2.4.org.default.xml | 4597212B8DC738BC901EE25CDA3EDA04F49D3F53A873EA4063CFA864C2DCF37D | 6108 | +| WindowsServer-2016-MS-2.4.xml | 3C2B4FFE25FD8BA3A4702A07AFE4E4074AD31E9749C83D5375B6FF4C443DCA65 | 480555 | +| WindowsServer-2016-MS-2.5.org.default.xml | 28A6CC76C5C22C10C57B9F3F37BB023CA151CF4DB877CF6E5C07B5AF1166E6A9 | 6107 | +| WindowsServer-2016-MS-2.5.xml | BB49ECFFFEC86C4F01311491935BCF2F11981E523A08FB0712025511C1425FED | 481151 | +| WindowsServer-2019-DC-2.4.org.default.xml | 0094F20B2B061FF05BD885B213776F7ADBC7E2D75EEEC66CB994281CE19891DC | 6095 | +| WindowsServer-2019-DC-2.4.xml | 4CCF9BC6032C0EC069D1CD3BBCBCC55DC598D5815593F6B6903753E0ED8C5B2B | 565567 | | WindowsServer-2019-DC-2.5.org.default.xml | 2B3EBC94F5503C005071520D4487334E047241231F81A7154F2A07EE21B20104 | 6095 | -| WindowsServer-2019-DC-2.5.xml | 667BBBFD0731C0B1CDE0D6811382DFE59031DA4BA02A1B00DC18FF3497C95182 | 558239 | -| WindowsServer-2019-MS-2.4.org.default.xml | 8F9E845B06B92DCEABF081B2B80F3D37F2C833181D352339034889187C9B92EB | 5938 | -| WindowsServer-2019-MS-2.4.xml | 4E699813B3A6B360729729993740D2B1E597CD83E852AB00FBA7F49FE2F9EC38 | 481067 | +| WindowsServer-2019-DC-2.5.xml | 6D2683085611516785604724BBFD4DFB6D773E78ED3662D055D9B0BE7EB216FD | 565775 | +| WindowsServer-2019-MS-2.4.org.default.xml | CABC2B5A3691044BCDD96E1ACA53B997BCCB14BC41927A4EFAC68E11F80686D5 | 6027 | +| WindowsServer-2019-MS-2.4.xml | EED082B900AC5D0F68FC8EF060D801CE357F42895A4A5A324B2137DCFAE9F77C | 487488 | | WindowsServer-2019-MS-2.5.org.default.xml | C11EF1E1576DDFA46432BE2A202A2BF520652CC21B475B217150AAF3F158CBB1 | 6027 | -| WindowsServer-2019-MS-2.5.xml | B1996B3BDF822010F82BD2B3932359957830F086DA3CD1EFB581DBF9D151486B | 481486 | +| WindowsServer-2019-MS-2.5.xml | 6B5BFDFD3A668D0F3307DB87CC686ADB4AF84FF0D42BAE6898E61D6C3075D8C6 | 487906 | +| WindowsServer-2022-DC-1.1.org.default.xml | A84DA0AA242D80FB25A68E417D05A315D0EFFC33B4A1F626096984CCB46277AA | 6222 | +| WindowsServer-2022-DC-1.1.xml | E41B69D3EA64BD9C4406BA39697BBB75D2D230CF5844D4DEE3EC1C50CE57C04D | 565193 | +| WindowsServer-2022-MS-1.1.org.default.xml | E2F3863090F2E81F6E19432881BEEFC6D620C2D05AE5E06DAF7A824117A4F339 | 6154 | +| WindowsServer-2022-MS-1.1.xml | CC4041ABCB8AE786245D738927D1CA6EA23711B6BE2338872B95ECE3C6B9B599 | 488173 | diff --git a/README.md b/README.md index b337a0c5..2c3879fe 100644 --- a/README.md +++ b/README.md @@ -72,7 +72,7 @@ For detailed information, please see the [StigData Wiki](https://github.com/Micr PowerStig.DSC is not really a specific module, but rather a collection of PowerShell Desired State Configuration (DSC) composite resources to manage the configurable items in each STIG. Each composite uses [PowerStig.Data](#powerstigdata) classes to retrieve PowerStig XML. -This allows the PowerStig.Data classes to manage exceptions, Org settings, and skipped rules uniformly across all composite resources. The standard DSC ResourceID's can them be used by additional automation to automatically generate compliance reports or trigger other automation solutions. +This allows the PowerStig.Data classes to manage exceptions, Org settings, and skipped rules uniformly across all composite resources. The standard DSC ResourceID's can then be used by additional automation to automatically generate compliance reports or trigger other automation solutions. ### Composite Resources @@ -80,10 +80,23 @@ The list of STIGs that we are currently covering. |Name|Description| | ---- | --- | -|[Browser](https://github.com/Microsoft/PowerStig/wiki/Browser) | Provides a mechanism to manage Browser STIG settings. | +|[Adobe](https://github.com/Microsoft/PowerStig/wiki/Adobe)| Provides a mechanism to manage Adobe STIG settings.| +|[Chrome](https://github.com/Microsoft/PowerStig/wiki/Chrome)| Provides a mechanism to manage Google Chrome STIG settings.| |[DotNetFramework](https://github.com/Microsoft/PowerStig/wiki/DotNetFramework) | Provides a mechanism to manage .Net Framework STIG settings. | +|[Edge](https://github.com/Microsoft/PowerStig/wiki/Edge) | Provides a mechanism to manage Microsoft Edge STIG settings. | +|[Firefox](https://github.com/Microsoft/PowerStig/wiki/Firefox) | Provides a mechanism to manage Firefox STIG settings. | +|[IisServer](https://github.com/Microsoft/PowerStig/wiki/IisServer) | Provides a mechanism to manage IIS Server settings. | +|[IisSite](https://github.com/Microsoft/PowerStig/wiki/IisSite) | Provides a mechanism to manage IIS Site settings. | +|[InternetExplorer](https://github.com/Microsoft/PowerStig/wiki/InternetExplorer) | Provides a mechanism to manage Microsoft Internet Explorer settings. | +|[McAfee](https://github.com/Microsoft/PowerStig/wiki/McAfee) | Provides a mechanism to manage McAfee settings. | |[Office](https://github.com/Microsoft/PowerStig/wiki/Office) | Provides a mechanism to manage Microsoft Office STIG settings. | +|[OracleJRE](https://github.com/Microsoft/PowerStig/wiki/OracleJRE) | Provides a mechanism to manage Oracle Java Runtime Environment STIG settings. | +|[RHEL](https://github.com/Microsoft/PowerStig/wiki/RHEL) | Provides a mechanism to manage RedHat Enterprise Linux STIG settings. | |[SqlServer](https://github.com/Microsoft/PowerStig/wiki/SqlServer) | Provides a mechanism to manage SqlServer STIG settings. | +|[Ubuntu](https://github.com/Microsoft/PowerStig/wiki/Ubuntu) | Provides a mechanism to manage Ubuntu Linux STIG settings. | +|[Vsphere](https://github.com/Microsoft/PowerStig/wiki/Vsphere) | Provides a mechanism to manage VMware Vsphere STIG settings. | +|[WindowsClient](https://github.com/Microsoft/PowerStig/wiki/WindowsClient) | Provides a mechanism to manage Windows Client STIG settings. | +|[WindowsDefender](https://github.com/Microsoft/PowerStig/wiki/WindowsDefender) | Provides a mechanism to manage Windows Defender STIG settings. | |[WindowsDnsServer](https://github.com/Microsoft/PowerStig/wiki/WindowsDnsServer) | Provides a mechanism to manage Windows DNS Server STIG settings. | |[WindowsFirewall](https://github.com/Microsoft/PowerStig/wiki/WindowsFirewall) | Provides a mechanism to manage the Windows Firewall STIG settings. | |[WindowsServer](https://github.com/Microsoft/PowerStig/wiki/WindowsServer) | Provides a mechanism to manage the Windows Server STIG settings. | @@ -134,3 +147,4 @@ We are especially thankful for those who have contributed pull requests to the c * [@mikedzikowski](https://github.com/mikedzikowski) (Mike Dzikowski) * [@togriffith](https://github.com/mikedzikowski) (Tony Griffith) * [@hinderjd](https://github.com/hinderjd) (James Hinders) +* [@ruandersMSFT](https://github.com/ruandersMSFT) (Russell Anderson) diff --git a/source/Module/Common/Convert/Data.ps1 b/source/Module/Common/Convert/Data.ps1 index 8c84db70..4b727ad6 100644 --- a/source/Module/Common/Convert/Data.ps1 +++ b/source/Module/Common/Convert/Data.ps1 @@ -86,6 +86,8 @@ data exclusionRuleList V-204440 = 'RHEL: At present, unable to automate rule' V-204456 = 'RHEL: At present, unable to automate rule' V-228564 = 'RHEL: At present, unable to automate rule' + V-251704 = 'RHEL: At present, unable to automate rule' + V-255927 = 'RHEL: At present, unable to automate rule' V-219151 = 'Ubuntu: At present, unable to automate rule' V-219155 = 'Ubuntu: At present, unable to automate rule' V-219164 = 'Ubuntu: At present, unable to automate rule' @@ -103,6 +105,16 @@ data exclusionRuleList V-219326 = 'Ubuntu: At present, unable to automate rule' V-219331 = 'Ubuntu: At present, unable to automate rule' V-219341 = 'Ubuntu: At present, unable to automate rule' + V-219159 = 'Ubuntu: At present, unable to automate rule' + V-219163 = 'Ubuntu: At present, unable to automate rule' + V-219228 = 'Ubuntu: At present, unable to automate rule' + V-219229 = 'Ubuntu: At present, unable to automate rule' + V-219230 = 'Ubuntu: At present, unable to automate rule' + V-219231 = 'Ubuntu: At present, unable to automate rule' + V-219232 = 'Ubuntu: At present, unable to automate rule' + V-219233 = 'Ubuntu: At present, unable to automate rule' + V-219330 = 'Ubuntu: At present, unable to automate rule' + V-255907 = 'Ubuntu: At present, unable to automate rule' V-235722 = 'Edge: Rule requires an unknown list and count of whitelisted domains, unable to automate rule' V-235753 = 'Edge: Rule requires an unknown list and count of whitelisted domains, unable to automate rule' V-235755 = 'Edge: Rule requires an unknown list and count of whitelisted extensions, unable to automate rule' diff --git a/source/Module/Common/Functions.XccdfXml.ps1 b/source/Module/Common/Functions.XccdfXml.ps1 index 5462429f..31b331b5 100644 --- a/source/Module/Common/Functions.XccdfXml.ps1 +++ b/source/Module/Common/Functions.XccdfXml.ps1 @@ -451,6 +451,7 @@ function Split-BenchmarkId # The Windows Server 2012 and 2012 R2 STIGs are combined, so return the 2012R2 $id = $id -replace '_2012_', '_2012R2_' $returnId = $id -replace ($windowsVariations -join '|'), 'WindowsServer' + $returnId = $returnId -replace 'MS_', '' continue } {$PSItem -match "Active_Directory"} @@ -514,8 +515,8 @@ function Split-BenchmarkId {$PSItem -match 'Ubuntu'} { $ubuntuId = $id -split '_' - $ubuntuVersion = $ubuntuId[3] -replace '-', '.' - $returnId = '{0}_{1}' -f $ubuntuId[2], $ubuntuVersion + $ubuntuVersion = $ubuntuId[-1] -replace '-', '.' + $returnId = '{0}_{1}' -f $ubuntuId[-2], $ubuntuVersion continue } default diff --git a/source/Module/Rule.AuditPolicy/Convert/AuditPolicyRule.Convert.psm1 b/source/Module/Rule.AuditPolicy/Convert/AuditPolicyRule.Convert.psm1 index 05579cfa..69d98950 100644 --- a/source/Module/Rule.AuditPolicy/Convert/AuditPolicyRule.Convert.psm1 +++ b/source/Module/Rule.AuditPolicy/Convert/AuditPolicyRule.Convert.psm1 @@ -66,6 +66,9 @@ class AuditPolicyRuleConvert : AuditPolicyRule $thisSubcategory = $regex.Groups.Where( {$_.Name -eq 'subcategory'} ).Value + + # Windows STIGS have 'Audit Audit' as part of the string, but the actual policy is 'Audit Policy Change' + $thisSubcategory = $thisSubcategory -replace 'Audit Audit', 'Audit' if (-not $this.SetStatus($thisSubcategory)) { diff --git a/source/PowerStig.psd1 b/source/PowerStig.psd1 index ac156dc2..d59e4f01 100644 --- a/source/PowerStig.psd1 +++ b/source/PowerStig.psd1 @@ -6,7 +6,7 @@ RootModule = 'PowerStig.psm1' # Version number of this module. - ModuleVersion = '4.15.0' + ModuleVersion = '4.16.0' # ID used to uniquely identify this module GUID = 'a132f6a5-8f96-4942-be25-b213ee7e4af3' diff --git a/source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R7_Manual-xccdf.log b/source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R7_Manual-xccdf.log index 6db46d9a..38ff6f0f 100644 --- a/source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R7_Manual-xccdf.log +++ b/source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R7_Manual-xccdf.log @@ -1,4 +1,4 @@ -V-221561::3. If the value name DefaultPopupsSetting::3. If the DefaultPopupsSetting value name +V-221561::3. If the value name DefaultPopupsSetting::3. If the DefaultPopupsSetting value name V-221562::3. If the a registry value name of 1 does not exist under that key or its value is not set to *::3. If the 1 value name does not exist under that key or its value data is not set to * V-221597::3. If the “::3. If the " V-221599::3. If the key "DeveloperToolsAvailability"::3. If the "DeveloperToolsAvailability" value name @@ -10,4 +10,4 @@ V-221588::*::HardCodedRule(RegistryRule)@{DscResource = 'RegistryPolicyFile'; Ke V-221596::*::HardCodedRule(RegistryRule)@{DscResource = 'RegistryPolicyFile'; Key = 'HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome'; ValueName = 'AutoplayAllowlist'; ValueType = 'MultiString'; ValueData = $null; OrganizationValueTestString = "{0} -eq 'a list of administrator-approved URLs"} V-234701::*::HardCodedRule(RegistryRule)@{DscResource = 'RegistryPolicyFile'; Key = 'HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome'; ValueName = 'SSLVersionMin'; ValueType = 'String'; ValueData = 'tls1.2'} V-245539::*::HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Absent'; Key = 'HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome'; ValueName = 'CookiesSessionOnlyForUrls'} -V-221572::*::HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\URLBlocklis'; ValueName = 'CookiesSessionOnlyForUrls'; ValueType = 'String'; ValueData = 'javascript://*'} +V-221572::*::HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\URLBlocklist'; ValueName = 'CookiesSessionOnlyForUrls'; ValueType = 'String'; ValueData = 'javascript://*'} diff --git a/source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R6_Manual-xccdf.log b/source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R8_Manual-xccdf.log similarity index 98% rename from source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R6_Manual-xccdf.log rename to source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R8_Manual-xccdf.log index fe03ecd4..38ff6f0f 100644 --- a/source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R6_Manual-xccdf.log +++ b/source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R8_Manual-xccdf.log @@ -1,4 +1,4 @@ -V-221561::3. If the value name DefaultPopupsSetting::3. If the DefaultPopupsSetting value name +V-221561::3. If the value name DefaultPopupsSetting::3. If the DefaultPopupsSetting value name V-221562::3. If the a registry value name of 1 does not exist under that key or its value is not set to *::3. If the 1 value name does not exist under that key or its value data is not set to * V-221597::3. If the “::3. If the " V-221599::3. If the key "DeveloperToolsAvailability"::3. If the "DeveloperToolsAvailability" value name diff --git a/source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R6_Manual-xccdf.xml b/source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R8_Manual-xccdf.xml similarity index 98% rename from source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R6_Manual-xccdf.xml rename to source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R8_Manual-xccdf.xml index 4b2b92ca..cc152378 100644 --- a/source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R6_Manual-xccdf.xml +++ b/source/StigData/Archive/Chrome/U_Google_Chrome_STIG_V2R8_Manual-xccdf.xml @@ -1,4 +1,4 @@ -acceptedGoogle Chrome Current Windows Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 6 Benchmark Date: 27 Apr 20223.3.0.273751.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>SRG-APP-000039<GroupDescription></GroupDescription>DTBC-0001Firewall traversal from remote host must be disabled.<VulnDiscussion>Remote connections should never be allowed that bypass the firewall, as there is no way to verify if they can be trusted. Enables usage of STUN and relay servers when remote clients are trying to establish a connection to this machine. If this setting is enabled, then remote clients can discover and connect to this machine even if they are separated by a firewall. If this setting is disabled and outgoing UDP connections are filtered by the firewall, then this machine will only allow connections from client machines within the local network. If this policy is left not set the setting will be enabled. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Google Chrome Current WindowsDISADPMS TargetGoogle Chrome Current Windows4081SV-57545V-44711CCI-001414Windows group policy: 1. Open the group policy editor tool with gpedit.msc 2. Navigate to Policy Path: Computer Configuration\Administrative\Templates\Google\Google Chrome\Remote Access Policy Name: Enable firewall traversal from remote access host @@ -266,18 +266,18 @@ Windows method: 1. Start regedit 2. Navigate to HKLM\Software\Policies\Google\Chrome\ 3. If the EnableOnlineRevocationChecks value name does not exist or its value data is not set to 1, then this is a finding. -SRG-APP-000206<GroupDescription></GroupDescription>DTBC-0038Safe Browsing must be enabled,<VulnDiscussion>Allows you to control whether Google Chrome's Safe Browsing feature is enabled and the mode it operates in. +SRG-APP-000206<GroupDescription></GroupDescription>DTBC-0038Safe Browsing must be enabled.<VulnDiscussion>Allows you to control whether Google Chrome's Safe Browsing feature is enabled and the mode it operates in. If this policy is set to 'NoProtection' (value 0), Safe Browsing is never active. If this policy is set to 'StandardProtection' (value 1, which is the default), Safe Browsing is always active in the standard mode. -If this policy is set to 'EnhancedProtection' (value 2), Safe Browsing is always active in the enhanced mode, which provides better security, but requires sharing more browsing information with Google.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Google Chrome Current WindowsDISADPMS TargetGoogle Chrome Current Windows4081SV-57625V-44791CCI-001166Windows group policy: +If this policy is set to 'EnhancedProtection' (value 2), Safe Browsing is always active in the enhanced mode, which provides better security, but requires sharing more browsing information with Google.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Google Chrome Current WindowsDISADPMS TargetGoogle Chrome Current Windows4081SV-57625V-44791CCI-001166Windows group policy: 1. Open the “group policy editor” tool with gpedit.msc 2. Navigate to Policy Path: Computer Configuration\Administrative Templates\Google\Google Chrome\Safe Browsing Settings Policy Name: Safe Browsing Protection Level Policy State: Enabled - Policy Value: StandardProtection or EnhancedProtectionUniversal method: + Policy Value: "(1) Safe Browsing is active in the standard mode", or "(2) Safe Browsing is active in the enhanced mode. This mode provides better security, but requires sharing more browsing information with Google".Universal method: 1. In the omnibox (address bar) type chrome://policy 2. If SafeBrowsingProtectionLevel is not displayed under the Policy Name column or it is not set to 1 or 2 under the Policy Value column, then this is a finding. @@ -297,7 +297,7 @@ Windows method: 1. Start regedit 2. Navigate to HKLM\Software\Policies\Google\Chrome\ 3. If the SavingBrowserHistoryDisabled value name does not exist or its value data is not set to 0, then this is a finding. -SRG-APP-000456<GroupDescription></GroupDescription>DTBC-0050The version of Google Chrome running on the system must be a supported version.<VulnDiscussion>Google Chrome is being continually updated by the vendor in order to address identified security vulnerabilities. Running an older version of the browser can introduce security vulnerabilities to the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Google Chrome Current WindowsDISADPMS TargetGoogle Chrome Current Windows4081SV-57639V-44805CCI-002605Install a supported version of Google Chrome.Universal method: +SRG-APP-000456<GroupDescription></GroupDescription>DTBC-0050The version of Google Chrome running on the system must be a supported version.<VulnDiscussion>Google Chrome is being continually updated by the vendor in order to address identified security vulnerabilities. Running an older version of the browser can introduce security vulnerabilities to the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Google Chrome Current WindowsDISADPMS TargetGoogle Chrome Current Windows4081SV-57639V-44805CCI-002605Install a supported version of Google Chrome.Universal method: 1. In the omnibox (address bar) type chrome://settings/help 2. Cross-reference the build information displayed with the Google Chrome site to identify, at minimum, the oldest supported build available. As of July 2019, this is 74.x.x. 3. If the installed version of Chrome is not supported by Google, this is a finding.SRG-APP-000089<GroupDescription></GroupDescription>DTBC-0052Deletion of browser history must be disabled.<VulnDiscussion>Disabling this function will prevent users from deleting their browsing history, which could be used to identify malicious websites and files that could later be used for anti-virus and Intrusion Detection System (IDS) signatures. Furthermore, preventing users from deleting browsing history could be used to identify abusive web surfing on government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Google Chrome Current WindowsDISADPMS TargetGoogle Chrome Current Windows4081SV-89845V-75165CCI-000169Windows group policy: @@ -373,18 +373,18 @@ If this policy is left not set, ”3” will be used, and the user will be able Windows method: 1. Start regedit 2. Navigate to HKLM\Software\Policies\Google\Chrome\ - 3. If the "DefaultWebUsbGuardSetting" value name does not exist or its value data is not set to "2", this is a finding.SRG-APP-000089<GroupDescription></GroupDescription>DTBC-0060Chrome Cleanup must be disabled.<VulnDiscussion>If set to “False”, prevents Chrome Cleanup from scanning the system for unwanted software and performing cleanups. Manually triggering Chrome Cleanup from chrome://settings/cleanup is disabled. -If set to “True” or unset, Chrome Cleanup periodically scans the system for unwanted software and should any be found, will ask the user if they wish to remove it. Manually triggering Chrome Cleanup from chrome://settings is enabled. -This policy is available only on Windows instances that are joined to a Microsoft Active Directory domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Google Chrome Current WindowsDISADPMS TargetGoogle Chrome Current Windows4081SV-96305V-81591CCI-000169Windows group policy: -1. Open the “group policy editor” tool with gpedit.msc + 3. If the "DefaultWebUsbGuardSetting" value name does not exist or its value data is not set to "2", this is a finding.SRG-APP-000089<GroupDescription></GroupDescription>DTBC-0060Chrome Cleanup must be disabled.<VulnDiscussion>If set to "False", prevents Chrome Cleanup from scanning the system for unwanted software and performing cleanups. Manually triggering Chrome Cleanup from chrome://settings/cleanup is disabled. +If set to "True" or unset, Chrome Cleanup periodically scans the system for unwanted software and should any be found, will ask the user if they wish to remove it. Manually triggering Chrome Cleanup from chrome://settings is enabled. +This policy is available only on Windows instances that are joined to a Microsoft Active Directory domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Google Chrome Current WindowsDISADPMS TargetGoogle Chrome Current Windows4081SV-96305V-81591CCI-000169Windows group policy: +1. Open the "group policy editor" tool with gpedit.msc. 2. Navigate to Policy Path: Computer Configuration\Administrative Templates\Google\Google Chrome -Policy Name: Enables Chrome Cleanup on Windows +Policy Name: Enable Chrome Cleanup on Windows Policy State: Disabled -Policy Value: N/AUniversal method: +Policy Value: N/AUniversal method: 1. In the omnibox (address bar) type chrome://policy 2. If "ChromeCleanupEnabled" is not displayed under the "Policy Name" column or it is not set to "False", this is a finding. Windows method: - 1. Start regedit + 1. Start regedit. 2. Navigate to HKLM\Software\Policies\Google\Chrome\ 3. If the "ChromeCleanupEnabled" value name does not exist or its value data is not set to "0", this is a finding.SRG-APP-000089<GroupDescription></GroupDescription>DTBC-0061Chrome Cleanup reporting must be disabled.<VulnDiscussion>If unset, should Chrome Cleanup detect unwanted software, it may report metadata about the scan to Google in accordance with policy set by “SafeBrowsingExtendedReportingEnabled”. Chrome Cleanup will then ask the user if they wish to clean up the unwanted software. The user can choose to share results of the cleanup with Google to assist with future unwanted software detection. These results contain file metadata and registry keys as described by the Chrome Privacy Whitepaper. If set to “false”, should Chrome Cleanup detect unwanted software, it will not report metadata about the scan to Google, overriding any policy set by “SafeBrowsingExtendedReportingEnabled”. Chrome Cleanup will ask the user if they wish to clean up the unwanted software. Results of the cleanup will not be reported to Google and the user will not have the option to do so. @@ -537,16 +537,16 @@ Windows method: 1. Start regedit 2. Navigate to HKLM\Software\Policies\Google\Chrome\ 3. If the ImportAutofillFormData value name does not exist or its value data is not set to 0, this is a finding. -SRG-APP-000416<GroupDescription></GroupDescription>DTBC-0056Chrome must be configured to allow only TLS.<VulnDiscussion>If this policy is not configured then Google Chrome uses a default minimum version, which is TLS 1.0. Otherwise, it may be set to one of the following values: "tls1", "tls1.1" or "tls1.2". +SRG-APP-000416<GroupDescription></GroupDescription>DTBC-0056Chrome must be configured to allow only TLS.<VulnDiscussion>If this policy is not configured then Google Chrome uses a default minimum version, which is TLS 1.0. Otherwise, it may be set to one of the following values: "tls1", "tls1.1" or "tls1.2". When set, Google Chrome will not use SSL/TLS versions less than the specified version. An unrecognized value will be ignored. "tls1" = TLS 1.0 "tls1.1" = TLS 1.1 -"tls1.2" = TLS 1.2</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Google Chrome Current WindowsDISADPMS TargetGoogle Chrome Current Windows4081V-81583CCI-002450Windows group policy: +"tls1.2" = TLS 1.2</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Google Chrome Current WindowsDISADPMS TargetGoogle Chrome Current Windows4081V-81583CCI-002450Windows group policy: 1. Open the “group policy editor” tool with gpedit.msc. 2. Navigate to Policy Path: Computer Configuration\Administrative Templates\Google\Google Chrome\ Policy Name: Minimum SSL version enabled Policy State: Enabled - Policy Value: TLS 1.2Universal method: + Policy Value: TLS 1.2Universal method: 1. In the omnibox (address bar) type chrome://policy 2. If "SSLVersionMin" is not displayed under the "Policy Name" column or it is not set to "tls1.2", this is a finding. Windows method: @@ -569,7 +569,7 @@ Leaving the policy unset lets sites ask for access, but users can change this se Windows method: 1. Start regedit 2. Navigate to HKLM\Software\Policies\Google\Chrome\ - 3. If the DefaultWebBluetoothGuardSetting value name does not exist or its value data is not set to 2, then this is a finding.SRG-APP-000383<GroupDescription></GroupDescription>DTBC-0074Use of the QUIC protocol must be disabled.<VulnDiscussion>QUIC is used by more than half of all connections from the Chrome web browser to Google's servers, and this activity is undesirable in the DoD. + 3. If the DefaultWebBluetoothGuardSetting value name does not exist or its value data is not set to 2, then this is a finding.SRG-APP-000383<GroupDescription></GroupDescription>DTBC-0074Use of the QUIC protocol must be disabled.<VulnDiscussion>QUIC is used by more than half of all connections from the Chrome web browser to Google's servers, and this activity is undesirable in the DoD. Setting the policy to Enabled or leaving it unset allows the use of QUIC protocol in Google Chrome. diff --git a/source/StigData/Archive/Linux.RHEL/U_RHEL_7_STIG_V3R8_Manual-xccdf.log b/source/StigData/Archive/Linux.RHEL/U_RHEL_7_STIG_V3R10_Manual-xccdf.log similarity index 90% rename from source/StigData/Archive/Linux.RHEL/U_RHEL_7_STIG_V3R8_Manual-xccdf.log rename to source/StigData/Archive/Linux.RHEL/U_RHEL_7_STIG_V3R10_Manual-xccdf.log index 1197b7c9..198d8524 100644 --- a/source/StigData/Archive/Linux.RHEL/U_RHEL_7_STIG_V3R8_Manual-xccdf.log +++ b/source/StigData/Archive/Linux.RHEL/U_RHEL_7_STIG_V3R10_Manual-xccdf.log @@ -22,7 +22,7 @@ V-204511::*::HardCodedRule(nxFileLineRule)@{DscResource = 'nxFileLine'; Contains V-204512::*::HardCodedRule(nxFileLineRule)@{DscResource = 'nxFileLine'; ContainsLine = $null; DoesNotContainPattern = $null; FilePath = '/etc/audisp/audisp-remote.conf'; OrganizationValueTestString = 'the "network_failure_action" option is set to "SYSLOG", "SINGLE", or "HALT"; i.e.: "network_failure_action = syslog" '} V-204515::*::HardCodedRule(nxFileLineRule)@{DscResource = 'nxFileLine'; ContainsLine = $null; DoesNotContainPattern = $null; FilePath = '/etc/audit/auditd.conf'; OrganizationValueTestString = 'the value of the "action_mail_acct" keyword is set to "root" and/or other accounts for security personnel; i.e.: "action_mail_acct = root" '} V-204576::*::HardCodedRule(nxFileRule)@{DscResource = 'nxFile'; Contents = $null; FilePath = '/etc/security/limits.d/204576-powerstig.conf'; OrganizationValueTestString = 'the "maxlogins" value is set to "10" or less '} -V-204579::*::HardCodedRule(nxFileRule)@{DscResource = 'nxFile'; FilePath = '/etc/profile.d/tmout.sh'}HardCodedRule(nxFileLineRule)@{DscResource = 'nxFileLine'; ContainsLine = $null; DoesNotContainPattern = $null; FilePath = '/etc/profile.d/tmout.sh'; OrganizationValueTestString = 'the following statement is true when leveraging the correct nxFileLine ContainsLine format: "If the file "/etc/profile.d/tmout.sh" does not exist with the contents shown above, the value of "TMOUT" is greater than 900, or the timeout values are commented out, this is a finding.'} +V-204579::*::HardCodedRule(nxFileRule)@{DscResource = 'nxFile'; FilePath = '/etc/profile.d/tmout.sh'}HardCodedRule(nxFileLineRule)@{DscResource = 'nxFileLine'; ContainsLine = $null; DoesNotContainPattern = $null; FilePath = '/etc/profile.d/tmout.sh'; OrganizationValueTestString = 'the following statement is true when leveraging the correct nxFileLine ContainsLine format: "If the file "/etc/profile.d/tmout.sh" does not exist with the contents shown above, the value of "TMOUT" is greater than 900, or the timeout values are commented out, this is a finding.'}HardCodedRule(nxFileLineRule)@{DscResource = 'nxFileLine'; ContainsLine = $null; DoesNotContainPattern = $null; FilePath = '/etc/bashrc'; OrganizationValueTestString = 'the following statement is true when leveraging the correct nxFileLine ContainsLine format: "If the file "/etc/bashrc" does not exist with the contents shown above, the value of "TMOUT" is greater than 900, or the timeout values are commented out, this is a finding.'}HardCodedRule(nxFileLineRule)@{DscResource = 'nxFileLine'; ContainsLine = $null; DoesNotContainPattern = $null; FilePath = '/etc/profile'; OrganizationValueTestString = 'the following statement is true when leveraging the correct nxFileLine ContainsLine format: "If the file "/etc/profile" does not exist with the contents shown above, the value of "TMOUT" is greater than 900, or the timeout values are commented out, this is a finding.'} V-204584::*::HardCodedRule(nxFileRule)@{DscResource = 'nxFile'; Contents = 'kernel.randomize_va_space = 2'; FilePath = '/etc/sysctl.d/204584-powerstig.conf'} V-204609::*::HardCodedRule(nxFileRule)@{DscResource = 'nxFile'; Contents = 'net.ipv4.conf.all.accept_source_route = 0'; FilePath = '/etc/sysctl.d/204609-powerstig.conf'} V-204610::*::HardCodedRule(nxFileRule)@{DscResource = 'nxFile'; Contents = 'net.ipv4.conf.all.rp_filter = 1'; FilePath = '/etc/sysctl.d/204610-powerstig.conf'} @@ -40,4 +40,4 @@ V-237635::*::HardCodedRule(nxFileRule)@{DscResource = 'nxFile'; Contents = $null V-244557::*::HardCodedRule(nxFileLineRule)@{DscResource = 'nxFileLine'; ContainsLine = $null; DoesNotContainPattern = $null; FilePath = '/boot/grub2/grub.cfg'; OrganizationValueTestString = '"set superusers =" is set to a unique name in /boot/grub2/grub.cfg'} V-244558::*::HardCodedRule(nxFileLineRule)@{DscResource = 'nxFileLine'; ContainsLine = $null; DoesNotContainPattern = $null; FilePath = '/boot/efi/EFI/redhat/grub.cfg'; OrganizationValueTestString = '"set superusers =" is set to a unique name in /boot/efi/EFI/redhat/grub.cfg'} V-250314::*::HardCodedRule(nxFileRule)@{DscResource = 'nxFile'; Contents = '%wheel ALL=(ALL) TYPE=sysadm_t ROLE=sysadm_r ALL'; FilePath = '/etc/sudoers.d/250314-powerstig.conf'} -V-251704::*::HardCodedRule(ManualRule)@{DscResource = 'None'} +V-255926::*::HardCodedRule(nxPackageRule)@{DscResource = 'nxPackage'; Ensure = 'Present'; Name = $null; OrganizationValueTestString = 'Specify either tmux or screen depending on preference'} diff --git a/source/StigData/Archive/Linux.RHEL/U_RHEL_7_STIG_V3R8_Manual-xccdf.xml b/source/StigData/Archive/Linux.RHEL/U_RHEL_7_STIG_V3R10_Manual-xccdf.xml similarity index 79% rename from source/StigData/Archive/Linux.RHEL/U_RHEL_7_STIG_V3R8_Manual-xccdf.xml rename to source/StigData/Archive/Linux.RHEL/U_RHEL_7_STIG_V3R10_Manual-xccdf.xml index f5ca2a00..2ac417f0 100644 --- a/source/StigData/Archive/Linux.RHEL/U_RHEL_7_STIG_V3R8_Manual-xccdf.xml +++ b/source/StigData/Archive/Linux.RHEL/U_RHEL_7_STIG_V3R10_Manual-xccdf.xml @@ -1,30 +1,30 @@ -acceptedRed Hat Enterprise Linux 7 Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 8 Benchmark Date: 27 Jul 20223.3.0.273751.10.03I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-OS-000257-GPOS-00098<GroupDescription></GroupDescription>RHEL-07-010010The Red Hat Enterprise Linux operating system must be configured so that the file permissions, ownership, and group membership of system files and commands match the vendor values.<VulnDiscussion>Discretionary access control is weakened if a user or group has access permissions to system files and directories greater than the default. +acceptedRed Hat Enterprise Linux 7 Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 10 Benchmark Date: 26 Jan 20233.4.0.342221.10.03I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>UBTU-18-010000Ubuntu operating systems booted with a BIOS must require authentication upon booting into single-user and maintenance modes.<VulnDiscussion>To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. +acceptedCanonical Ubuntu 18.04 LTS Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 10 Benchmark Date: 26 Jan 20233.4.0.342221.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>SRG-APP-000179<GroupDescription></GroupDescription>O365-AC-000001Macros must be blocked from running in Access files from the Internet.<VulnDiscussion>This policy setting allows you to block macros from running in Office files that come from the Internet. +acceptedMicrosoft Office 365 ProPlus Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 8 Benchmark Date: 26 Jan 20233.4.0.342221.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>SRG-APP-000015-WSR-000014<GroupDescription></GroupDescription>IIST-SV-000100The IIS 10.0 web server remote authors or content providers must only use secure encrypted logons and connections to upload web server content.<VulnDiscussion>Logging onto a web server remotely using an unencrypted protocol or service when performing updates and maintenance is a major risk. Data, such as user account, is transmitted in plaintext and can easily be compromised. When performing remote administrative tasks, a protocol or service that encrypts the communication channel must be used. +acceptedMicrosoft IIS 10.0 Server Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 8 Benchmark Date: 26 Jan 20233.4.0.342221.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>SRG-APP-000001-WSR-000002<GroupDescription></GroupDescription>IISW-SI-000201The IIS 8.5 website session state must be enabled.<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. +acceptedMicrosoft IIS 8.5 Site Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 7 Benchmark Date: 26 Jan 20233.4.0.342221.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-APP-000001-WSR-000002<GroupDescription></GroupDescription>IISW-SI-000201The IIS 8.5 website session state must be enabled.<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. @@ -36,13 +36,13 @@ Verify the "mode" reflects "InProc". If the "mode" is not set to "InProc", this is a finding. -If the system being reviewed is part of a Web Farm, interview the System Administrator to ensure Session State Tracking is enabled via a SQL server, or other means. If Session State Tracking is enabled on the Web Farm, this is not a finding.SRG-APP-000001-WSR-000002<GroupDescription></GroupDescription>IISW-SI-000202The IIS 8.5 website session state cookie settings must be configured to Use Cookies mode.<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. +If the system being reviewed is part of a Web Farm, interview the System Administrator to ensure Session State Tracking is enabled via a SQL server, or other means. If Session State Tracking is enabled on the Web Farm, this is not a finding.SRG-APP-000001-WSR-000002<GroupDescription></GroupDescription>IISW-SI-000202The IIS 8.5 website session state cookie settings must be configured to Use Cookies mode.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91473V-76777CCI-000054Follow the procedures below for each site hosted on the IIS 8.5 web server: +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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91473V-76777CCI-000054Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -66,7 +66,7 @@ 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 "cookieless" is set to "UseCookies". If the "cookieless" is not set to "UseCookies", this is a finding. -Note: If IIS 8.5 server/site is used only for system-to-system maintenance, does not allow users to connect to interface, and is restricted to specific system IPs, this is Not Applicable.SRG-APP-000014-WSR-000006<GroupDescription></GroupDescription>IISW-SI-000203A private IIS 8.5 website must only accept Secure Socket Layer connections.<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. +Note: If IIS 8.5 server/site is used only for system-to-system maintenance, does not allow users to connect to interface, and is restricted to specific system IPs, this is Not Applicable.SRG-APP-000014-WSR-000006<GroupDescription></GroupDescription>IISW-SI-000203A private IIS 8.5 website must only accept Secure Socket Layer connections.<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. 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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91475V-76779CCI-000068Note: If the server being reviewed is a public IIS 8.5 web server, this is Not Applicable. @@ -91,7 +91,7 @@ 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.SRG-APP-000014-WSR-000006<GroupDescription></GroupDescription>IISW-SI-000204A public IIS 8.5 website must only accept Secure Socket Layer connections when authentication is required.<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. +If the "Require SSL" check box is not selected, this is a finding.SRG-APP-000014-WSR-000006<GroupDescription></GroupDescription>IISW-SI-000204A public IIS 8.5 website must only accept Secure Socket Layer connections when authentication is required.<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. 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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91477V-76781CCI-000068Note: If the server being reviewed is a private IIS 8.5 web server, this is Not Applicable. @@ -113,7 +113,7 @@ 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.SRG-APP-000092-WSR-000055<GroupDescription></GroupDescription>IISW-SI-000205The enhanced logging for each IIS 8.5 website must be enabled and capture, record, and log all content related to a user session.<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. +If the "Require SSL" check box is not selected, this is a finding.SRG-APP-000092-WSR-000055<GroupDescription></GroupDescription>IISW-SI-000205The enhanced logging for each IIS 8.5 website must be enabled and capture, record, and log all content related to a user session.<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. @@ -143,7 +143,7 @@ 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.SRG-APP-000092-WSR-000055<GroupDescription></GroupDescription>IISW-SI-000206Both the log file and Event Tracing for Windows (ETW) for each IIS 8.5 website must be enabled.<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. +If the "W3C" is not selected as the logging format OR any of the required fields are not selected, this is a finding.SRG-APP-000092-WSR-000055<GroupDescription></GroupDescription>IISW-SI-000206Both the log file and Event Tracing for Windows (ETW) for each IIS 8.5 website must be enabled.<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. @@ -167,7 +167,7 @@ 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.SRG-APP-000098-WSR-000060<GroupDescription></GroupDescription>IISW-SI-000208An IIS 8.5 website behind a load balancer or proxy server, must produce log records containing the source client IP and destination information.<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. +If the "Both log file and ETW event" radio button is not selected, this is a finding.SRG-APP-000098-WSR-000060<GroupDescription></GroupDescription>IISW-SI-000208An IIS 8.5 website behind a load balancer or proxy server, must produce log records containing the source client IP and destination information.<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. @@ -191,7 +191,7 @@ If the website is not behind a load balancer or proxy server, this is Not Applic 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 provisions have been made to log the client IP via another field (i.e., utilizing X-Forwarded-For), this is not a finding.SRG-APP-000099-WSR-000061<GroupDescription></GroupDescription>IISW-SI-000209The IIS 8.5 website must produce log records that contain sufficient information to establish the outcome (success or failure) of IIS 8.5 website events.<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. +If provisions have been made to log the client IP via another field (i.e., utilizing X-Forwarded-For), this is not a finding.SRG-APP-000099-WSR-000061<GroupDescription></GroupDescription>IISW-SI-000209The IIS 8.5 website must produce log records that contain sufficient information to establish the outcome (success or failure) of IIS 8.5 website events.<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. @@ -229,7 +229,7 @@ Request Header >> Connection Request Header >> Warning -If any of the above fields are not selected, this is a finding.SRG-APP-000100-WSR-000064<GroupDescription></GroupDescription>IISW-SI-000210The IIS 8.5 website must produce log records containing sufficient information to establish the identity of any user/subject or process associated with an event.<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. +If any of the above fields are not selected, this is a finding.SRG-APP-000100-WSR-000064<GroupDescription></GroupDescription>IISW-SI-000210The IIS 8.5 website must produce log records containing sufficient information to establish the identity of any user/subject or process associated with an event.<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. @@ -267,13 +267,13 @@ 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: Request Header >> Authorization Response Header >> Content-Type -If any of the above fields are not selected, this is a finding.SRG-APP-000141-WSR-000081<GroupDescription></GroupDescription>IISW-SI-000214The IIS 8.5 website must have Multipurpose Internet Mail Extensions (MIME) that invoke OS shell programs disabled.<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. +If any of the above fields are not selected, this is a finding.SRG-APP-000141-WSR-000081<GroupDescription></GroupDescription>IISW-SI-000214The IIS 8.5 website must have Multipurpose Internet Mail Extensions (MIME) that invoke OS shell programs disabled.<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. @@ -313,7 +313,7 @@ From the list of extensions under "Application", verify MIME types for OS shell .bat .csh -If any OS shell MIME types are configured, this is a finding.SRG-APP-000141-WSR-000082<GroupDescription></GroupDescription>IISW-SI-000215Mappings to unused and vulnerable scripts on the IIS 8.5 website must be removed.<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". +If any OS shell MIME types are configured, this is a finding.SRG-APP-000141-WSR-000082<GroupDescription></GroupDescription>IISW-SI-000215Mappings to unused and vulnerable scripts on the IIS 8.5 website must be removed.<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 "Request Filtering", 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 "Request Filtering" in IIS 8. "Request Filtering" at the site level take precedence over "Request Filtering" 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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91495V-76799CCI-000381Open the IIS 8.5 Manager. @@ -323,7 +323,7 @@ Double-click "Request Filtering". Deny any script file extensions listed on the black list. -Select "Apply" from the "Actions" pane.For Request Filtering, the ISSO must document and approve all allowable scripts the website allows (white list) and denies (black list). The white list and black list will be compared to the Request Filtering in IIS 8.5. +Select "Apply" from the "Actions" pane.For Request Filtering, the ISSO must document and approve all allowable scripts the website allows (white list) and denies (black list). The white list and black list will be compared to the Request Filtering in IIS 8.5. Open the IIS 8.5 Manager. @@ -331,11 +331,11 @@ Click the site name under review. Double-click "Request Filtering". -If any script file extensions from the black list are enabled, this is a finding.SRG-APP-000141-WSR-000083<GroupDescription></GroupDescription>IISW-SI-000216The IIS 8.5 website must have resource mappings set to disable the serving of certain file types.<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. +If any script file extensions from the black list are enabled, this is a finding.SRG-APP-000141-WSR-000083<GroupDescription></GroupDescription>IISW-SI-000216The IIS 8.5 website must have resource mappings set to disable the serving of certain file types.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91497V-76801CCI-000381Follow the procedures below for each site hosted on the IIS 8.5 web server: +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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91497V-76801CCI-000381Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. Click the site name to review. @@ -343,13 +343,13 @@ Double-click Request Filtering >> File Name Extensions Tab >> Deny F Add any script file extensions listed on the black list that are not listed. Select "Apply" from the "Actions" pane.For Request Filtering, the ISSO must document and approve all allowable scripts the website allows (white list) and denies (black list). The white list and black list will be compared to the Request Filtering in IIS 8.5. Request Filtering at the site level take precedence over Request Filtering 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. Click the site name to review. Double-click Request Filtering >> File Name Extensions Tab. -If any script file extensions from the black list are not denied, this is a finding.SRG-APP-000141-WSR-000085<GroupDescription></GroupDescription>IISW-SI-000217The IIS 8.5 website must have Web Distributed Authoring and Versioning (WebDAV) disabled.<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. +If any script file extensions from the black list are not denied, this is a finding.SRG-APP-000141-WSR-000085<GroupDescription></GroupDescription>IISW-SI-000217The IIS 8.5 website must have Web Distributed Authoring and Versioning (WebDAV) disabled.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91499V-76803CCI-000381Follow the procedures below for each site hosted on the IIS 8.5 web server: @@ -379,7 +379,7 @@ 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.SRG-APP-000142-WSR-000089<GroupDescription></GroupDescription>IISW-SI-000219Each IIS 8.5 website must be assigned a default host header.<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. +If the "WebDAV Authoring Rules" icon exists, this is a finding.SRG-APP-000142-WSR-000089<GroupDescription></GroupDescription>IISW-SI-000219Each IIS 8.5 website must be assigned a default host header.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91503V-76807CCI-000382Note: If the server is hosting SharePoint, this is Not Applicable. @@ -405,28 +405,35 @@ Select “Edit Bindings”. Verify there are hostname entries and unique IP addresses assigned to port 80 for HTTP and port 443 for HTTPS. Other approved and documented ports may be used. -If both hostname entries and unique IP addresses are not configure to port 80 for HTTP and port 443 for HTTPS (or other approved and documented port), this is a finding.SRG-APP-000172-WSR-000104<GroupDescription></GroupDescription>IISW-SI-000220A private websites authentication mechanism must use client certificates to transmit session identifier to assure integrity.<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. +If both hostname entries and unique IP addresses are not configure to port 80 for HTTP and port 443 for HTTPS (or other approved and documented port), this is a finding.SRG-APP-000172-WSR-000104<GroupDescription></GroupDescription>IISW-SI-000220A private websites authentication mechanism must use client certificates to transmit session identifier to assure integrity.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91505V-76809CCI-000197CCI-001188CCI-002470Note: If the server being reviewed is a public IIS 8.5 web server, this is Not Applicable. +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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91505V-76809CCI-000197CCI-001188CCI-002470Note: If the server being reviewed is a public IIS 8.5 web server, this is Not Applicable. Note: If the server is hosting Exchange, this is Not Applicable. +Note: If the server is hosting SharePoint, this is Not Applicable. Note: If certificate handling is performed at the Proxy/Load Balancer, this is not a finding. 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. -Select "Apply" from the "Actions" pane.Note: If the server being reviewed is a public IIS 8.5 web server, this is Not Applicable. + +Select "Apply" from the "Actions" pane.Note: If the server being reviewed is a public IIS 8.5 web server, this is Not Applicable. Note: If the server is hosting Exchange, this is Not Applicable. +Note: If the server is hosting SharePoint, this is Not Applicable. Note: If certificate handling is performed at the Proxy/Load Balancer, this is not a finding. 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.SRG-APP-000211-WSR-000031<GroupDescription></GroupDescription>IISW-SI-000221Anonymous IIS 8.5 website access accounts must be restricted.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91507V-76811CCI-001082Remove the Anonymous access account from all privileged accounts and all privileged groups.Check the account used for anonymous access to the website. +If the "Clients Certificate Required" check box is not selected, this is a finding.SRG-APP-000211-WSR-000031<GroupDescription></GroupDescription>IISW-SI-000221Anonymous IIS 8.5 website access accounts must be restricted.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91507V-76811CCI-001082Remove the Anonymous access account from all privileged accounts and all privileged groups.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. @@ -467,7 +474,7 @@ Replicator 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.SRG-APP-000224-WSR-000136<GroupDescription></GroupDescription>IISW-SI-000223The IIS 8.5 website must generate unique session identifiers that cannot be reliably reproduced.<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. +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.SRG-APP-000224-WSR-000136<GroupDescription></GroupDescription>IISW-SI-000223The IIS 8.5 website must generate unique session identifiers that cannot be reliably reproduced.<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. @@ -503,7 +510,7 @@ Verify the "mode" reflects "InProc". If the "mode" is not set to "InProc", this is a finding. -If the system being reviewed is part of a Web Farm, interview the System Administrator to ensure Session State Tracking is enabled via a SQL server, or other means. If Session State Tracking is enabled on the Web Farm, this is not a finding.SRG-APP-000233-WSR-000146<GroupDescription></GroupDescription>IISW-SI-000224The IIS 8.5 website document directory must be in a separate partition from the IIS 8.5 websites system files.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91511V-76815CCI-001084Follow the procedures below for each site hosted on the IIS 8.5 web server: +If the system being reviewed is part of a Web Farm, interview the System Administrator to ensure Session State Tracking is enabled via a SQL server, or other means. If Session State Tracking is enabled on the Web Farm, this is not a finding.SRG-APP-000233-WSR-000146<GroupDescription></GroupDescription>IISW-SI-000224The IIS 8.5 website document directory must be in a separate partition from the IIS 8.5 websites system files.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91511V-76815CCI-001084Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -521,7 +528,7 @@ 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.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IISW-SI-000225The IIS 8.5 website must be configured to limit the maxURL.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91513V-76817CCI-001094Follow the procedures below for each site hosted on the IIS 8.5 web server: +If the Path is on the same partition as the OS, this is a finding.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IISW-SI-000225The IIS 8.5 website must be configured to limit the maxURL.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91513V-76817CCI-001094Follow the procedures below for each site hosted on the IIS 8.5 web server: Click the site name under review. @@ -539,7 +546,7 @@ 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.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IISW-SI-000226The IIS 8.5 website must be configured to limit the size of web requests.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91515V-76819CCI-001094Follow the procedures below for each site hosted on the IIS 8.5 web server: +If the "maxUrl" value is not set to "4096" or less, this is a finding.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IISW-SI-000226The IIS 8.5 website must be configured to limit the size of web requests.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91515V-76819CCI-001094Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -560,7 +567,7 @@ 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. -SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IISW-SI-000227The IIS 8.5 websites Maximum Query String limit must be configured.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91517V-76821CCI-001094Follow the procedures below for each site hosted on the IIS 8.5 web server: +SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IISW-SI-000227The IIS 8.5 websites Maximum Query String limit must be configured.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91517V-76821CCI-001094Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -580,7 +587,7 @@ 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.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IISW-SI-000228Non-ASCII characters in URLs must be prohibited by any IIS 8.5 website.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91519V-76823CCI-001094Follow the procedures below for each site hosted on the IIS 8.5 web server: +If the "Maximum Query String" value is not set to "2048" or less, this is a finding.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IISW-SI-000228Non-ASCII characters in URLs must be prohibited by any IIS 8.5 website.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91519V-76823CCI-001094Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -600,7 +607,7 @@ 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.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IISW-SI-000229Double encoded URL requests must be prohibited by any IIS 8.5 website.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91521V-76825CCI-001094Follow the procedures below for each site hosted on the IIS 8.5 web server: +If the "Allow high-bit characters" check box is checked, this is a finding.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IISW-SI-000229Double encoded URL requests must be prohibited by any IIS 8.5 website.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91521V-76825CCI-001094Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -620,7 +627,7 @@ 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.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IISW-SI-000230Unlisted file extensions in URL requests must be filtered by any IIS 8.5 website.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91523V-76827CCI-001094Follow the procedures below for each site hosted on the IIS 8.5 web server: +If the "Allow double escaping" check box is checked, this is a finding.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IISW-SI-000230Unlisted file extensions in URL requests must be filtered by any IIS 8.5 website.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91523V-76827CCI-001094Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -644,7 +651,7 @@ If "Allow unlisted file name extensions" check box is checked, this is a finding Note: If this IIS 8.5 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. -Note: If this IIS 8.5 installation is supporting Splunk, this requirement is Not Applicable.SRG-APP-000251-WSR-000157<GroupDescription></GroupDescription>IISW-SI-000231Directory Browsing on the IIS 8.5 website must be disabled.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91525V-76829CCI-001310Follow the procedures below for each site hosted on the IIS 8.5 web server: +Note: If this IIS 8.5 installation is supporting Splunk, this requirement is Not Applicable.SRG-APP-000251-WSR-000157<GroupDescription></GroupDescription>IISW-SI-000231Directory Browsing on the IIS 8.5 website must be disabled.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91525V-76829CCI-001310Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -664,7 +671,7 @@ 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.SRG-APP-000266-WSR-000159<GroupDescription></GroupDescription>IISW-SI-000233Warning and error messages displayed to clients must be modified to minimize the identity of the IIS 8.5 website, patches, loaded modules, and directory paths.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91531V-76835CCI-001312Follow the procedures below for each site hosted on the IIS 8.5 web server: +If "Directory Browsing" is not "Disabled", this is a finding.SRG-APP-000266-WSR-000159<GroupDescription></GroupDescription>IISW-SI-000233Warning and error messages displayed to clients must be modified to minimize the identity of the IIS 8.5 website, patches, loaded modules, and directory paths.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91531V-76835CCI-001312Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -682,7 +689,7 @@ 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.SRG-APP-000266-WSR-000160<GroupDescription></GroupDescription>IISW-SI-000234Debugging and trace information used to diagnose the IIS 8.5 website must be disabled.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91533V-76837CCI-001312Follow the procedures below for each site hosted on the IIS 8.5 web server: +If any error message is not set to “Detailed errors for local requests and custom error pages for remote requests”, this is a finding.SRG-APP-000266-WSR-000160<GroupDescription></GroupDescription>IISW-SI-000234Debugging and trace information used to diagnose the IIS 8.5 website must be disabled.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91533V-76837CCI-001312Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -702,7 +709,7 @@ 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.SRG-APP-000295-WSR-000012<GroupDescription></GroupDescription>IISW-SI-000235The Idle Time-out monitor for each IIS 8.5 website must be enabled.<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. +If the "Debug" value is not set to "False", this is a finding.SRG-APP-000295-WSR-000012<GroupDescription></GroupDescription>IISW-SI-000235The Idle Time-out monitor for each IIS 8.5 website must be enabled.<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. @@ -728,7 +735,7 @@ Scroll down to the "Process Model" section and verify the value for "Idle Time-o If the "Idle Time-out" is not set to "20" or less, this is a finding. -If the "Idle Time-out" is set to "0", this is a finding.SRG-APP-000295-WSR-000134<GroupDescription></GroupDescription>IISW-SI-000236The IIS 8.5 websites connectionTimeout setting must be explicitly configured to disconnect an idle session.<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. +If the "Idle Time-out" is set to "0", this is a finding.SRG-APP-000295-WSR-000134<GroupDescription></GroupDescription>IISW-SI-000236The IIS 8.5 websites connectionTimeout setting must be explicitly configured to disconnect an idle session.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91537V-76841CCI-002361Follow the procedures below for each site hosted on the IIS 8.5 web server: @@ -738,12 +745,12 @@ 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". +From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". Set the "timeout" 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. -In the "Actions" pane, click "Apply". +In the "Actions" pane, click "Apply". Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -759,7 +766,7 @@ Acceptable values are 5 minutes for high-value applications, 10 minutes for medi If "timeout" is not set to "00:20:00 or less”, this is a finding. -SRG-APP-000316-WSR-000170<GroupDescription></GroupDescription>IISW-SI-000237The IIS 8.5 website must provide the capability to immediately disconnect or disable remote access to the hosted applications.<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. +SRG-APP-000316-WSR-000170<GroupDescription></GroupDescription>IISW-SI-000237The IIS 8.5 website must provide the capability to immediately disconnect or disable remote access to the hosted applications.<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. @@ -797,7 +804,7 @@ If necessary, stop the IIS 8.5 web server by selecting the web server in the IIS 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.SRG-APP-000357-WSR-000150<GroupDescription></GroupDescription>IISW-SI-000238The IIS 8.5 website must use a logging mechanism that is configured to allocate log record storage capacity large enough to accommodate the logging requirements of the IIS 8.5 website.<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. +If there are not documented procedures with, at a minimum, the mentioned steps for stopping a website, this is a finding.SRG-APP-000357-WSR-000150<GroupDescription></GroupDescription>IISW-SI-000238The IIS 8.5 website must use a logging mechanism that is configured to allocate log record storage capacity large enough to accommodate the logging requirements of the IIS 8.5 website.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001V-76845SV-91541CCI-001849Follow the procedures below for each site hosted on the IIS 8.5 web server: @@ -823,7 +830,7 @@ 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.SRG-APP-000383-WSR-000175<GroupDescription></GroupDescription>IISW-SI-000239The IIS 8.5 websites must utilize ports, protocols, and services according to PPSM guidelines.<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. +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.SRG-APP-000383-WSR-000175<GroupDescription></GroupDescription>IISW-SI-000239The IIS 8.5 websites must utilize ports, protocols, and services according to PPSM guidelines.<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. @@ -847,7 +854,7 @@ 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.SRG-APP-000427-WSR-000186<GroupDescription></GroupDescription>IISW-SI-000241The IIS 8.5 private website have a server certificate issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs).<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91545V-76849CCI-002470Follow the procedures below for each site hosted on the IIS 8.5 web server: +Review the ports and protocols. If unknown ports or protocols are used, then this is a finding.SRG-APP-000427-WSR-000186<GroupDescription></GroupDescription>IISW-SI-000241The IIS 8.5 private website have a server certificate issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs).<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91545V-76849CCI-002470Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. @@ -887,7 +894,7 @@ If HTTPS is not an available type under site bindings, this is a finding. If HTTPS is not an available type under site bindings, and the Web Server ONLY communicates directly with a load balancer/proxy server, with IP address and Domain Restrictions in place, this is not a finding. -For systems with load balancers that perform SSL offloading, this is Not Applicable.SRG-APP-000429-WSR-000113<GroupDescription></GroupDescription>IISW-SI-000242The IIS 8.5 private website must employ cryptographic mechanisms (TLS) and require client certificates.<VulnDiscussion>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. +For systems with load balancers that perform SSL offloading, this is Not Applicable.SRG-APP-000429-WSR-000113<GroupDescription></GroupDescription>IISW-SI-000242The IIS 8.5 private website must employ cryptographic mechanisms (TLS) and require client certificates.<VulnDiscussion>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. 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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91547V-76851CCI-002476Note: If this is a public facing web server, this requirement is Not Applicable. Note: If the server is hosting SharePoint, this is Not Applicable. @@ -942,7 +949,7 @@ 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.SRG-APP-000439-WSR-000152<GroupDescription></GroupDescription>IISW-SI-000244IIS 8.5 website session IDs must be sent to the client using TLS.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91551V-76855CCI-002418Follow the procedures below for each site hosted on the IIS 8.5 web server: +If the "sslFlags" is not set to "ssl128", this is a finding.SRG-APP-000439-WSR-000152<GroupDescription></GroupDescription>IISW-SI-000244IIS 8.5 website session IDs must be sent to the client using TLS.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91551V-76855CCI-002418Follow the procedures below for each site hosted on the IIS 8.5 web server: Access the IIS 8.5 Manager. @@ -970,9 +977,9 @@ Expand the "session" section. Verify the "keepSessionIdSecure" is set to "True". -If the "keepSessionIdSecure" is not set to "True", this is a finding.SRG-APP-000439-WSR-000154<GroupDescription></GroupDescription>IISW-SI-000246Cookies exchanged between the IIS 8.5 website and the client must use SSL/TLS, have cookie properties set to prohibit client-side scripts from reading the cookie data and must not be compressed.<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. +If the "keepSessionIdSecure" is not set to "True", this is a finding.SRG-APP-000439-WSR-000154<GroupDescription></GroupDescription>IISW-SI-000246Cookies exchanged between the IIS 8.5 website and the client must use SSL/TLS, have cookie properties set to prohibit client-side scripts from reading the cookie data and must not be compressed.<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. @@ -980,7 +987,7 @@ A cookie can be read by client-side scripts easily if cookie properties are not -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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91555V-76859CCI-002418Note: If the server being reviewed is a public IIS 8.5 web server, this is Not Applicable. +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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91555V-76859CCI-002418Note: 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: @@ -996,7 +1003,7 @@ From the "Section:" drop-down list, select "system.web/httpCookies". Set the "require SSL" to "True". From the "Section:" drop-down list, select "system.web/sessionState". Set the "compressionEnabled" to "False". -Select "Apply" from the "Actions" pane.Note: If the server being reviewed is a public IIS 8.5 web server, this is Not Applicable. +Select "Apply" from the "Actions" pane.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/proxy server through which traffic is routed to the IIS 8.5 server, and the IIS 8.5 server receives traffic from the load balancer/proxy server, the SSL requirement must be met on the load balancer/proxy server. Follow the procedures below for each site hosted on the IIS 8.5 web server: @@ -1008,15 +1015,15 @@ Verify the "require SSL" is set to "True". From the "Section:" drop-down list, select "system.web/sessionState". Verify the "compressionEnabled" is set to "False". -If both the "system.web/httpCookies:require SSL" is set to "True" and the "system.web/sessionState:compressionEnabled" is set to "False", this is not a finding.SRG-APP-000441-WSR-000181<GroupDescription></GroupDescription>IISW-SI-000249The IIS 8.5 website must maintain the confidentiality and integrity of information during preparation for transmission and during reception.<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. +If both the "system.web/httpCookies:require SSL" is set to "True" and the "system.web/sessionState:compressionEnabled" is set to "False", this is not a finding.SRG-APP-000441-WSR-000181<GroupDescription></GroupDescription>IISW-SI-000249The IIS 8.5 website must maintain the confidentiality and integrity of information during preparation for transmission and during reception.<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. @@ -1048,7 +1055,7 @@ 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.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000251The IIS 8.5 website must have a unique application pool.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91561V-76865CCI-000366Open the IIS 8.5 Manager. +If the "sslFlags" is not set to "ssl128", this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000251The IIS 8.5 website must have a unique application pool.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91561V-76865CCI-000366Open the IIS 8.5 Manager. Click the site name under review. @@ -1062,7 +1069,7 @@ Expand "Sites" from the "Connections" pane. For every Site listed: Highlight Site name. Click "Basic Settings" and document the name of the Application Pool. -If any Application Pools are being used for more than one website, this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000252The maximum number of requests an application pool can process for each IIS 8.5 website must be explicitly set.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91563V-76867CCI-000366Open the IIS 8.5 Manager. +If any Application Pools are being used for more than one website, this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000252The maximum number of requests an application pool can process for each IIS 8.5 website must be explicitly set.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91563V-76867CCI-000366Open the IIS 8.5 Manager. Click "Application Pools". @@ -1084,43 +1091,21 @@ 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.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000254The amount of private memory an application pool uses for each IIS 8.5 website must be explicitly set.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91567V-76871CCI-000366Open the IIS 8.5 Manager. +If the "Request Limit" is set to a value of "0", this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000255The application pool for each IIS 8.5 website must have a recycle time explicitly set.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91569V-76873CCI-000366Open the IIS 8.5 Manager. -Click "Application Pools". +Click the "Application Pools". Perform the following for each Application Pool: -Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. +Highlight an Application Pool and click "Recycling" in the "Actions" pane. -Scroll down to the "Recycling" section and set the value for "Private Memory Limit" to a value other than "0".Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. +In the" Recycling Conditions" window, select at least one means to recycle the Application Pool. -If this IIS 8.5 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. +Click "Next". -Open the IIS 8.5 Manager. +In the "Recycling Events to Log" windows, select both the "Regular time interval" and "Scheduled time" boxes. -Perform the following for each Application Pool: - -Click "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.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000255The application pool for each IIS 8.5 website must have a recycle time explicitly set.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91569V-76873CCI-000366Open the IIS 8.5 Manager. - -Click the “Application Pools”. - -Perform the following for each Application Pool: - -Highlight an Application Pool and click "Recycling" in the “Actions” pane. - -In the Recycling Conditions window, select at least one means to recycle the Application Pool. - -Click Next. - -In the Recycling Events to Log windows, select both the "Regular time interval" and "Specific time" boxes. - -Click Finish.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. +Click "Finish".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. Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. @@ -1128,23 +1113,23 @@ Note: If the IIS Application Pool is hosting Microsoft Exchange and not otherwis Open the IIS 8.5 Manager. -Click the “Application Pools”. +Click the "Application Pools". Perform the following for each Application Pool: -Highlight an Application Pool and click "Recycling" in the “Actions” pane. +Highlight an Application Pool and click "Recycling" in the "Actions" pane. -In the Recycling Conditions window, verify at least one condition is checked as desired by the organization. +In the Recycling Conditions window, verify at least one condition is checked as desired by the organization. If no conditions are checked, this is a finding. -Click Next. +Click "Next". -In the Recycling Events to Log window, verify both the "Regular time interval" and "Specific time" boxes are selected. +In the "Recycling Events to Log" window, verify both the "Regular time interval" and "Scheduled time" boxes are selected. -If both the "Regular time interval" and "Specific time" options are not selected, this is a finding. +If both the "Regular time interval" and "Scheduled time" options are not selected, this is a finding. -Click Cancel.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000256The maximum queue length for HTTP.sys for each IIS 8.5 website must be explicitly configured.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91571V-76875CCI-000366Open the IIS 8.5 Manager. +Click "Cancel".SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000256The maximum queue length for HTTP.sys for each IIS 8.5 website must be explicitly configured.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91571V-76875CCI-000366Open the IIS 8.5 Manager. Click the "Application Pools". @@ -1164,7 +1149,7 @@ Highlight an Application Pool to review and click "Advanced Settings" in the "Ac 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.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000257The application pools pinging monitor for each IIS 8.5 website must be enabled.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91573V-76877CCI-000366Open the IIS 8.5 Manager. +If the "Queue Length" is set to "1000" or less, this is not a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000257The application pools pinging monitor for each IIS 8.5 website must be enabled.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91573V-76877CCI-000366Open the IIS 8.5 Manager. Click the "Application Pools". @@ -1186,7 +1171,7 @@ Highlight an Application Pool to review and click "Advanced Settings" in the "Ac 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.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000258The application pools rapid fail protection for each IIS 8.5 website must be enabled.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91575V-76879CCI-000366Open the IIS 8.5 Manager. +If the value for "Ping Enabled" is not set to "True", this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000258The application pools rapid fail protection for each IIS 8.5 website must be enabled.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91575V-76879CCI-000366Open the IIS 8.5 Manager. Click the "Application Pools". @@ -1208,7 +1193,7 @@ Highlight an Application Pool to review and click "Advanced Settings" in the "Ac 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.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000259The application pools rapid fail protection settings for each IIS 8.5 website must be managed.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91577V-76881CCI-000366Open the IIS 8.5 Manager. +If the "Rapid Fail Protection:Enabled" is not set to "True", this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000259The application pools rapid fail protection settings for each IIS 8.5 website must be managed.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91577V-76881CCI-000366Open the IIS 8.5 Manager. Click the “Application Pools”. @@ -1228,7 +1213,7 @@ Highlight an Application Pool to review and click "Advanced Settings" in the "Ac 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.SRG-APP-000141-WSR-000087<GroupDescription></GroupDescription>IISW-SI-000261Interactive scripts on the IIS 8.5 web server must be located in unique and designated folders.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91581V-76885CCI-000381All interactive programs must be placed in unique designated folders based on CGI or ASP script type. +If the "Failure Interval" is not set to "5" or less, this is a finding.SRG-APP-000141-WSR-000087<GroupDescription></GroupDescription>IISW-SI-000261Interactive scripts on the IIS 8.5 web server must be located in unique and designated folders.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91581V-76885CCI-000381All interactive programs must be placed in unique designated folders based on CGI or ASP script type. Open the IIS 8.5 Manager. @@ -1245,8 +1230,8 @@ TrustedInstaller: FULL SYSTEM: FULL ApplicationPoolId:READ Custom Service Account: READ -Users: READ -ALL APPLICATION PACKAGES: READDetermine whether scripts are used on the web server for the target website. Common file extensions include, but are not limited to: .cgi, .pl, .vbs, .class, .c, .php, and .asp. +Users: READ +ALL APPLICATION PACKAGES: READDetermine whether scripts are used on the web server for the target website. Common file extensions include, but are not limited to: .cgi, .pl, .vbs, .class, .c, .php, and .asp. All interactive programs must be placed in unique designated folders based on CGI or ASP script type. For modular and/or third-party applications, it is permissible to have script files in multiple folders. @@ -1256,7 +1241,7 @@ 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, this is a finding.SRG-APP-000141-WSR-000087<GroupDescription></GroupDescription>IISW-SI-000262Interactive scripts on the IIS 8.5 web server must have restrictive access controls.<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. +If scripts are not segregated from web content and in their own unique folders, this is a finding.SRG-APP-000141-WSR-000087<GroupDescription></GroupDescription>IISW-SI-000262Interactive scripts on the IIS 8.5 web server must have restrictive access controls.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91583V-76887CCI-000381Determine 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. @@ -1302,7 +1287,7 @@ ApplicationPoolId: READ Custom Service Account: READ Users: READ -If the permissions are less restrictive than listed above, this is a finding.SRG-APP-000141-WSR-000087<GroupDescription></GroupDescription>IISW-SI-000263Backup interactive scripts on the IIS 8.5 server must be removed.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91585V-76889CCI-000381Remove the backup files from the production web server.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 permissions are less restrictive than listed above, this is a finding.SRG-APP-000141-WSR-000087<GroupDescription></GroupDescription>IISW-SI-000263Backup interactive scripts on the IIS 8.5 server must be removed.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91585V-76889CCI-000381Remove the backup files from the production web server.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. @@ -1314,30 +1299,30 @@ 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.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000264The required DoD banner page must be displayed to authenticated users accessing a DoD private website.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91587V-76891CCI-000366Configure a DoD private website to display the required DoD banner page when authentication is required for user access.Note: This requirement is only applicable for private DoD websites. +If files with these extensions are found, this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IISW-SI-000264The required DoD banner page must be displayed to authenticated users accessing a DoD private website.<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>DPMS Target Microsoft IIS 8.5 SiteDISADPMS TargetMicrosoft IIS 8.5 Site4001SV-91587V-76891CCI-000366Configure a DoD private website to display the required DoD banner page when authentication is required for user access.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. \ No newline at end of file +If the access-controlled website does not display this banner page before entry, this is a finding. diff --git a/source/StigData/Archive/Windows.Server.2022/U_MS_Windows_Server_2022_DC_STIG_V1R1_Manual-xccdf.log b/source/StigData/Archive/Windows.Server.2022/U_MS_Windows_Server_2022_DC_STIG_V1R1_Manual-xccdf.log new file mode 100644 index 00000000..abc09a5c --- /dev/null +++ b/source/StigData/Archive/Windows.Server.2022/U_MS_Windows_Server_2022_DC_STIG_V1R1_Manual-xccdf.log @@ -0,0 +1,19 @@ +V-254248::*::HardCodedRule(ServiceRule)@{DscResource = 'Service'; Ensure = 'Present'; ServiceName = $null; ServiceState = 'Running'; StartupType = $null; OrganizationValueTestString = 'ServiceName/StartupType is populated with correct AntiVirus service information'} +V-254255::*::'' +V-254265::*::HardCodedRule(ServiceRule)@{DscResource = 'Service'; Ensure = 'Present'; ServiceName = $null; ServiceState = 'Running'; StartupType = $null; OrganizationValueTestString = 'ServiceName/StartupType is populated with correct Firewall service information'} +V-254291::"Minimum password length,"::"Minimum password length" +V-254356::0x00000000 (0) (Security), 0x00000001 (1) (Basic)::0 or 1 +V-254357::0x00000000 (0) - No peering (HTTP Only)::0, 1, 2, 99 or 100 +V-254362::0x00000000 (0) (or if the Value Name does not exist)::0 +V-254363::0x00000000 (0) (or if the Value Name does not exist)::0 +V-254364::0x00000000 (0) (or if the Value Name does not exist)::0 +V-254371::0x00000000 (0) (or if the Value Name does not exist)::0 +V-254375::0x00000000 (0) (or if the Value Name does not exist)::0 +V-254443::DoD Root CA 3- DoD Interoperability Root CA 2 - 49CBE933151872E17C8EAE7F0ABA97FB610F6477::DoD Root CA 3 - DoD Interoperability Root CA 2 - 49CBE933151872E17C8EAE7F0ABA97FB610F6477 +V-254443::Subject: CN=DoD Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US::Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +V-254443::Thumbprint: A8C27332CCB4CA49554CE55D34062A7DD2850C02::Thumbprint: 49CBE933151872E17C8EAE7F0ABA97FB610F6477 +V-254443::NotAfter: 8/26/2022 9:25:51 AM::NotAfter: 11/16/2024 +V-254458::*::HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System'; ValueName = 'LegalNoticeCaption'; ValueType = 'String'; ValueData = $null; OrganizationValueTestString = "'{0}' -match '^(DoD Notice and Consent Banner|US Department of Defense Warning Statement)$'"} +V-254484::0x00000002 (2) (Prompt for consent on the secure desktop)::1 or 2 +V-254490::0x00000002 (2) (or if the Value Name does not exist)::2 +V-254499::- Administrators::- Administrators`r`nSystems that have the Hyper-V role will also have "Virtual Machines" given this user right (this may be displayed as "NT Virtual Machine\Virtual Machines", SID S-1-5-83-0). This is not a finding. diff --git a/source/StigData/Archive/Windows.Server.2022/U_MS_Windows_Server_2022_DC_STIG_V1R1_Manual-xccdf.xml b/source/StigData/Archive/Windows.Server.2022/U_MS_Windows_Server_2022_DC_STIG_V1R1_Manual-xccdf.xml new file mode 100644 index 00000000..cd1f5690 --- /dev/null +++ b/source/StigData/Archive/Windows.Server.2022/U_MS_Windows_Server_2022_DC_STIG_V1R1_Manual-xccdf.xml @@ -0,0 +1,13270 @@ + + + + accepted + Microsoft Windows Server 2022 Security Technical Implementation Guide + This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil. + + + + + DISA + STIG.DOD.MIL + + Release: 1 Benchmark Date: 09 Sep 2022 + 3.4.0.34222 + 1.10.0 + 1 + + I - Mission Critical Classified + <ProfileDescription></ProfileDescription> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + I - Mission Critical Sensitive + <ProfileDescription></ProfileDescription> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + II - Mission Support Public + <ProfileDescription></ProfileDescription> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + III - Administrative Classified + <ProfileDescription></ProfileDescription> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + III - Administrative Sensitive + <ProfileDescription></ProfileDescription> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + I - Mission Critical Public + <ProfileDescription></ProfileDescription> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + II - Mission Support Classified + <ProfileDescription></ProfileDescription> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + II - Mission Support Sensitive + <ProfileDescription></ProfileDescription> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + III - Administrative Public + <ProfileDescription></ProfileDescription> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000010 + Windows Server 2022 users with Administrative privileges must have separate accounts for administrative duties and normal operational tasks. + <VulnDiscussion>Using a privileged account to perform routine functions makes the computer vulnerable to malicious software inadvertently introduced during a session that has been granted full privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Ensure each user with administrative privileges has a separate account for user duties and one for privileged duties. + + + + Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account. + +If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding. + + + + + SRG-OS-000076-GPOS-00044 + <GroupDescription></GroupDescription> + + WN22-00-000020 + Windows Server 2022 passwords for the built-in Administrator account must be changed at least every 60 days. + <VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password may not be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure. + +It is highly recommended to use Microsoft's Local Administrator Password Solution (LAPS). Domain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default. The AO still has the overall authority to use another equivalent capability to accomplish the check.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000199 + Change the built-in Administrator account password at least every "60" days. + +It is highly recommended to use Microsoft's LAPS, which may be used on domain-joined member servers to accomplish this. The AO still has the overall authority to use another equivalent capability to accomplish the check. + + + + Review the password last set date for the built-in Administrator account. + +Domain controllers: + +Open "PowerShell". + +Enter "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like "*-500" | Ft Name, SID, PasswordLastSet". + +If the "PasswordLastSet" date is greater than "60" days old, this is a finding. + +Member servers and standalone or nondomain-joined systems: + +Open "Command Prompt". + +Enter 'Net User [account name] | Find /i "Password Last Set"', where [account name] is the name of the built-in administrator account. + +(The name of the built-in Administrator account must be changed to something other than "Administrator" per STIG requirements.) + +If the "PasswordLastSet" date is greater than "60" days old, this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000030 + Windows Server 2022 administrative accounts must not be used with applications that access the internet, such as web browsers, or with potential internet sources, such as email. + <VulnDiscussion>Using applications that access the internet or have potential internet sources using administrative privileges exposes a system to compromise. If a flaw in an application is exploited while running as a privileged user, the entire system could be compromised. Web browsers and email are common attack vectors for introducing malicious code and must not be run with an administrative account. + +Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy require administrative accounts to not access the internet or use applications such as email. + +The policy must define specific exceptions for local service administration. These exceptions may include HTTP(S)-based tools that are used for the administration of the local system, services, or attached devices. + +Whitelisting can be used to enforce the policy to ensure compliance. + +Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000205-GPOS-00083</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + CCI-001312 + Establish a policy, at minimum, to prohibit administrative accounts from using applications that access the internet, such as web browsers, or with potential internet sources, such as email. Ensure the policy is enforced. + +The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. + + + + Determine whether organization policy, at a minimum, prohibits administrative accounts from using applications that access the internet, such as web browsers, or with potential internet sources, such as email, except as necessary for local service administration. + +If it does not, this is a finding. + +The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000040 + Windows Server 2022 members of the Backup Operators group must have separate accounts for backup duties and normal operational tasks. + <VulnDiscussion>Backup Operators are able to read and write to any file in the system, regardless of the rights assigned to it. Backup and restore rights permit users to circumvent the file access restrictions present on NTFS disk drives for backup and restore purposes. Members of the Backup Operators group must have separate logon accounts for performing backup duties.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Ensure each member of the Backup Operators group has separate accounts for backup functions and standard user functions. + + + + If no accounts are members of the Backup Operators group, this is NA. + +Verify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks. + +If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding. + + + + + SRG-OS-000078-GPOS-00046 + <GroupDescription></GroupDescription> + + WN22-00-000050 + Windows Server 2022 manually managed application account passwords must be at least 15 characters in length. + <VulnDiscussion>Application/service account passwords must be of sufficient length to prevent being easily cracked. Application/service accounts that are manually managed must have passwords at least 15 characters in length.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000205 + Establish a policy that requires application/service account passwords that are manually managed to be at least 15 characters in length. Ensure the policy is enforced. + + + + Determine if manually managed application/service accounts exist. If none exist, this is NA. + +Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least 15 characters in length. + +If such a policy does not exist or has not been implemented, this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000060 + Windows Server 2022 manually managed application account passwords must be changed at least annually or when a system administrator with knowledge of the password leaves the organization. + <VulnDiscussion>Setting application account passwords to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. If managed service accounts are used, this alleviates the need to manually change application account passwords.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Change passwords for manually managed application/service accounts at least annually or when an administrator with knowledge of the password leaves the organization. + +It is recommended that system-managed service accounts be used whenever possible. + + + + Determine if manually managed application/service accounts exist. If none exist, this is NA. + +If passwords for manually managed application/service accounts are not changed at least annually or when an administrator with knowledge of the password leaves the organization, this is a finding. + +Identify manually managed application/service accounts. + +To determine the date a password was last changed: + +Domain controllers: + +Open "PowerShell". + +Enter "Get-AdUser -Identity [application account name] -Properties PasswordLastSet | FT Name, PasswordLastSet", where [application account name] is the name of the manually managed application/service account. + +If the "PasswordLastSet" date is more than one year old, this is a finding. + +Member servers and standalone or nondomain-joined systems: + +Open "Command Prompt". + +Enter 'Net User [application account name] | Find /i "Password Last Set"', where [application account name] is the name of the manually managed application/service account. + +If the "Password Last Set" date is more than one year old, this is a finding. + + + + + SRG-OS-000104-GPOS-00051 + <GroupDescription></GroupDescription> + + WN22-00-000070 + Windows Server 2022 shared user accounts must not be permitted. + <VulnDiscussion>Shared accounts (accounts where two or more people log on with the same user identification) do not provide adequate identification and authentication. There is no way to provide for nonrepudiation or individual accountability for system access and resource usage.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000764 + Remove unapproved shared accounts from the system. + +Document required shared accounts with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. + + + + Determine whether any shared accounts exist. If no shared accounts exist, this is NA. + +Shared accounts, such as required by an application, may be approved by the organization. This must be documented with the Information System Security Officer (ISSO). Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. + +If unapproved shared accounts exist, this is a finding. + + + + + SRG-OS-000370-GPOS-00155 + <GroupDescription></GroupDescription> + + WN22-00-000080 + Windows Server 2022 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. + <VulnDiscussion>Using a whitelist provides a configuration management method to allow the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. + +The organization must identify authorized software programs and only permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001774 + Configure an application whitelisting program to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. + +Configuration of whitelisting applications will vary by the program. AppLocker is a whitelisting application built in to Windows Server. + +If AppLocker is used, it is configured through group policy in Computer Configuration >> Windows Settings >> Security Settings >> Application Control Policies >> AppLocker. + +Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" at the following link: + +https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm + + + + Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. + +If an application whitelisting program is not in use on the system, this is a finding. + +Configuration of whitelisting applications will vary by the program. + +AppLocker is a whitelisting application built in to Windows Server. A deny-by-default implementation is initiated by enabling any AppLocker rules within a category, only allowing what is specified by defined rules. + +If AppLocker is used, perform the following to view the configuration of AppLocker: + +Open "PowerShell". + +If the AppLocker PowerShell module has not been imported previously, execute the following first: + +Import-Module AppLocker + +Execute the following command, substituting [c:\temp\file.xml] with a location and file name appropriate for the system: + +Get-AppLockerPolicy -Effective -XML > c:\temp\file.xml + +This will produce an xml file with the effective settings that can be viewed in a browser or opened in a program such as Excel for review. + +Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" at the following link: + +https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000090 + Windows Server 2022 domain-joined systems must have a Trusted Platform Module (TPM) enabled and ready for use. + <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. A number of system requirements must be met in order for Credential Guard to be configured and enabled properly. Without a TPM enabled and ready for use, Credential Guard keys are stored in a less secure method using software.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Ensure domain-joined systems have a TPM that is configured for use. (Versions 2.0 or 1.2 support Credential Guard.) + +The TPM must be enabled in the firmware. + +Run "tpm.msc" for configuration options in Windows. + + + + For standalone or nondomain-joined systems, this is NA. + +Verify the system has a TPM and it is ready for use. + +Run "tpm.msc". + +Review the sections in the center pane. + +"Status" must indicate it has been configured with a message such as "The TPM is ready for use" or "The TPM is on and ownership has been taken". + +TPM Manufacturer Information - Specific Version = 2.0 or 1.2 + +If a TPM is not found or is not ready for use, this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000100 + Windows Server 2022 must be maintained at a supported servicing level. + <VulnDiscussion>Systems at unsupported servicing levels will not receive security updates for new vulnerabilities, which leave them subject to exploitation. Systems must be maintained at a servicing level supported by the vendor with new security updates.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Update the system to a Version 21H2 (Build 20348.xxx) or greater. + + + + Open "Command Prompt". + +Enter "winver.exe". + +If the "About Windows" dialog box does not display "Microsoft Windows Server Version 21H1 (Build 20348.xxx)" or greater, this is a finding. + +Preview versions must not be used in a production environment. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000110 + Windows Server 2022 must use an antivirus program. + <VulnDiscussion>Malicious software can establish a base on individual desktops and servers. Employing an automated mechanism to detect this type of software will aid in elimination of the software from the operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + If no antivirus software is in use, install Microsoft Defender or third-party antivirus. + +Open "PowerShell". + +Enter "Install-WindowsFeature -Name Windows-Defender". + +For third-party antivirus, install per antivirus instructions and disable Windows Defender. + +Open "PowerShell". + +Enter "Uninstall-WindowsFeature -Name Windows-Defender". + + + + Verify an antivirus solution is installed on the system. The antivirus solution may be bundled with an approved host-based security solution. + +If there is no antivirus solution installed on the system, this is a finding. + +Verify if Microsoft Defender antivirus is in use or enabled: + +Open "PowerShell". + +Enter "get-service | where {$_.DisplayName -Like "*Defender*"} | Select Status,DisplayName" + +Verify if third-party antivirus is in use or enabled: + +Open "PowerShell". + +Enter "get-service | where {$_.DisplayName -Like "*mcafee*"} | Select Status,DisplayName + +Enter "get-service | where {$_.DisplayName -Like "*symantec*"} | Select Status,DisplayName + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000120 + Windows Server 2022 must have a host-based intrusion detection or prevention system. + <VulnDiscussion>A properly configured Host-based Intrusion Detection System (HIDS) or Host-based Intrusion Prevention System (HIPS) provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Install a HIDS or HIPS on each server. + + + + Determine whether there is a HIDS or HIPS on each server. + +If the HIPS component of ESS is installed and active on the host and the alerts of blocked activity are being logged and monitored, this meets the requirement. + +A HIDS device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the Information System Security Officer (ISSO). + +If a HIDS is not installed on the system, this is a finding. + + + + + SRG-OS-000080-GPOS-00048 + <GroupDescription></GroupDescription> + + WN22-00-000130 + Windows Server 2022 local volumes must use a format that supports NTFS attributes. + <VulnDiscussion>The ability to set access permissions and auditing is critical to maintaining the security and proper access controls of a system. To support this, volumes must be formatted using a file system that supports NTFS attributes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000213 + Format volumes to use NTFS or ReFS. + + + + Open "Computer Management". + +Select "Disk Management" under "Storage". + +For each local volume, if the file system does not indicate "NTFS", this is a finding. + +"ReFS" (resilient file system) is also acceptable and would not be a finding. + +This does not apply to system partitions such the Recovery and EFI System Partition. + + + + + SRG-OS-000312-GPOS-00122 + <GroupDescription></GroupDescription> + + WN22-00-000140 + Windows Server 2022 permissions for the system drive root directory (usually C:\) must conform to minimum requirements. + <VulnDiscussion>Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications. + +The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN22-SO-000240). + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002165 + Maintain the default permissions for the system drive's root directory and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN22-SO-000240). + +Default Permissions +C:\ +Type - "Allow" for all +Inherited from - "None" for all + +Principal - Access - Applies to + +SYSTEM - Full control - This folder, subfolders, and files +Administrators - Full control - This folder, subfolders, and files +Users - Read & execute - This folder, subfolders, and files +Users - Create folders/append data - This folder and subfolders +Users - Create files/write data - Subfolders only +CREATOR OWNER - Full Control - Subfolders and files only + + + + The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN22-SO-000240). + +Review the permissions for the system drive's root directory (usually C:\). Nonprivileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions except where noted as defaults. Individual accounts must not be used to assign permissions. + +If permissions are not as restrictive as the default permissions listed below, this is a finding. + +Viewing in File Explorer: + +View the Properties of the system drive's root directory. + +Select the "Security" tab, and the "Advanced" button. + +Default permissions: +C:\ +Type - "Allow" for all +Inherited from - "None" for all + +Principal - Access - Applies to + +SYSTEM - Full control - This folder, subfolders, and files +Administrators - Full control - This folder, subfolders, and files +Users - Read & execute - This folder, subfolders, and files +Users - Create folders/append data - This folder and subfolders +Users - Create files/write data - Subfolders only +CREATOR OWNER - Full Control - Subfolders and files only + +Alternately, use icacls: + +Open "Command Prompt (Admin)". + +Enter "icacls" followed by the directory: + +"icacls c:\" + +The following results must be displayed: + +c:\ +NT AUTHORITY\SYSTEM:(OI)(CI)(F) +BUILTIN\Administrators:(OI)(CI)(F) +BUILTIN\Users:(OI)(CI)(RX) +BUILTIN\Users:(CI)(AD) +BUILTIN\Users:(CI)(IO)(WD) +CREATOR OWNER:(OI)(CI)(IO)(F) +Successfully processed 1 files; Failed processing 0 files + + + + + SRG-OS-000312-GPOS-00122 + <GroupDescription></GroupDescription> + + WN22-00-000150 + Windows Server 2022 permissions for program file directories must conform to minimum requirements. + <VulnDiscussion>Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications. + +The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN22-SO-000240). + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002165 + Maintain the default permissions for the program file directories and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN22-SO-000240). + +Default permissions: +\Program Files and \Program Files (x86) +Type - "Allow" for all +Inherited from - "None" for all + +Principal - Access - Applies to + +TrustedInstaller - Full control - This folder and subfolders +SYSTEM - Modify - This folder only +SYSTEM - Full control - Subfolders and files only +Administrators - Modify - This folder only +Administrators - Full control - Subfolders and files only +Users - Read & execute - This folder, subfolders, and files +CREATOR OWNER - Full control - Subfolders and files only +ALL APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files + + + + The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN22-SO-000240). + +Review the permissions for the program file directories (Program Files and Program Files [x86]). Nonprivileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. + +If permissions are not as restrictive as the default permissions listed below, this is a finding. + +Viewing in File Explorer: + +For each folder, view the Properties. + +Select the "Security" tab, and the "Advanced" button. + +Default permissions: +\Program Files and \Program Files (x86) +Type - "Allow" for all +Inherited from - "None" for all + +Principal - Access - Applies to + +TrustedInstaller - Full control - This folder and subfolders +SYSTEM - Modify - This folder only +SYSTEM - Full control - Subfolders and files only +Administrators - Modify - This folder only +Administrators - Full control - Subfolders and files only +Users - Read & execute - This folder, subfolders and files +CREATOR OWNER - Full control - Subfolders and files only +ALL APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files + +Alternately, use icacls: + +Open a Command prompt (admin). + +Enter "icacls" followed by the directory: + +'icacls "c:\program files"' +'icacls "c:\program files (x86)"' + +The following results must be displayed for each when entered: + +c:\program files (c:\program files (x86)) +NT SERVICE\TrustedInstaller:(F) +NT SERVICE\TrustedInstaller:(CI)(IO)(F) +NT AUTHORITY\SYSTEM:(M) +NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) +BUILTIN\Administrators:(M) +BUILTIN\Administrators:(OI)(CI)(IO)(F) +BUILTIN\Users:(RX) +BUILTIN\Users:(OI)(CI)(IO)(GR,GE) +CREATOR OWNER:(OI)(CI)(IO)(F) +APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(RX) +APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) +Successfully processed 1 files; Failed processing 0 files + + + + + SRG-OS-000312-GPOS-00122 + <GroupDescription></GroupDescription> + + WN22-00-000160 + Windows Server 2022 permissions for the Windows installation directory must conform to minimum requirements. + <VulnDiscussion>Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications. + +The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN22-SO-000240). + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002165 + Maintain the default file ACLs and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN22-SO-000240). + +Default permissions: +Type - "Allow" for all +Inherited from - "None" for all + +Principal - Access - Applies to + +TrustedInstaller - Full control - This folder and subfolders +SYSTEM - Modify - This folder only +SYSTEM - Full control - Subfolders and files only +Administrators - Modify - This folder only +Administrators - Full control - Subfolders and files only +Users - Read & execute - This folder, subfolders, and files +CREATOR OWNER - Full control - Subfolders and files only +ALL APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files + + + + The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN22-SO-000240). + +Review the permissions for the Windows installation directory (usually C:\Windows). Nonprivileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. + +If permissions are not as restrictive as the default permissions listed below, this is a finding: + +Viewing in File Explorer: + +For each folder, view the Properties. + +Select the "Security" tab and the "Advanced" button. + +Default permissions: +\Windows +Type - "Allow" for all +Inherited from - "None" for all + +Principal - Access - Applies to + +TrustedInstaller - Full control - This folder and subfolders +SYSTEM - Modify - This folder only +SYSTEM - Full control - Subfolders and files only +Administrators - Modify - This folder only +Administrators - Full control - Subfolders and files only +Users - Read & execute - This folder, subfolders, and files +CREATOR OWNER - Full control - Subfolders and files only +ALL APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files + +Alternately, use icacls: + +Open a Command prompt (admin). + +Enter "icacls" followed by the directory: + +"icacls c:\windows" + +The following results must be displayed for each when entered: + +c:\windows +NT SERVICE\TrustedInstaller:(F) +NT SERVICE\TrustedInstaller:(CI)(IO)(F) +NT AUTHORITY\SYSTEM:(M) +NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) +BUILTIN\Administrators:(M) +BUILTIN\Administrators:(OI)(CI)(IO)(F) +BUILTIN\Users:(RX) +BUILTIN\Users:(OI)(CI)(IO)(GR,GE) +CREATOR OWNER:(OI)(CI)(IO)(F) +APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(RX) +APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) +Successfully processed 1 files; Failed processing 0 files + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-00-000170 + Windows Server 2022 default permissions for the HKEY_LOCAL_MACHINE registry hive must be maintained. + <VulnDiscussion>The registry is integral to the function, security, and stability of the Windows system. Changing the system's registry permissions allows the possibility of unauthorized and anonymous modification to the operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Maintain the default permissions for the HKEY_LOCAL_MACHINE registry hive. + +The default permissions of the higher-level keys are noted below. + +HKEY_LOCAL_MACHINE\SECURITY + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +SYSTEM - Full Control - This key and subkeys +Administrators - Special - This key and subkeys + +HKEY_LOCAL_MACHINE\SOFTWARE + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - This key and subkeys +ALL APPLICATION PACKAGES - Read - This key and subkeys + +HKEY_LOCAL_MACHINE\SYSTEM + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - Subkeys only +ALL APPLICATION PACKAGES - Read - This key and subkeys +Server Operators - Read - This Key and subkeys (Domain controllers only) + +Microsoft has also given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2022 to the following SID. +S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 + + + + Review the registry permissions for the keys of the HKEY_LOCAL_MACHINE hive noted below. + +If any nonprivileged groups such as Everyone, Users, or Authenticated Users have greater than Read permission, this is a finding. + +If permissions are not as restrictive as the default permissions listed below, this is a finding: + +Run "Regedit". + +Right-click on the registry areas noted below. + +Select "Permissions" and the "Advanced" button. + +HKEY_LOCAL_MACHINE\SECURITY + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +SYSTEM - Full Control - This key and subkeys +Administrators - Special - This key and subkeys + +HKEY_LOCAL_MACHINE\SOFTWARE + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - This key and subkeys +ALL APPLICATION PACKAGES - Read - This key and subkeys + +HKEY_LOCAL_MACHINE\SYSTEM + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - Subkeys only +ALL APPLICATION PACKAGES - Read - This key and subkeys +Server Operators - Read - This Key and subkeys (Domain controllers only) + +Other examples under the noted keys may also be sampled. There may be some instances where nonprivileged groups have greater than Read permission. + +Microsoft has given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2022 to the following SID, this is currently not a finding. +S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 + +If the defaults have not been changed, these are not a finding. + + + + + SRG-OS-000080-GPOS-00048 + <GroupDescription></GroupDescription> + + WN22-00-000180 + Windows Server 2022 nonadministrative accounts or groups must only have print permissions on printer shares. + <VulnDiscussion>Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000213 + Configure the permissions on shared printers to restrict standard users to only have Print permissions. + + + + Open "Printers & scanners" in "Settings". + +If there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) + +For each printer: + +Select the printer and "Manage". + +Select "Printer Properties". + +Select the "Sharing" tab. + +If "Share this printer" is checked, select the "Security" tab. + +If any standard user accounts or groups have permissions other than "Print", this is a finding. + +The default is for the "Everyone" group to be given "Print" permission. + +"All APPLICATION PACKAGES" and "CREATOR OWNER" are not standard user accounts. + + + + + SRG-OS-000118-GPOS-00060 + <GroupDescription></GroupDescription> + + WN22-00-000190 + Windows Server 2022 outdated or unused accounts must be removed or disabled. + <VulnDiscussion>Outdated or unused accounts provide penetration points that may go undetected. Inactive accounts must be deleted if no longer necessary or, if still required, disabled until needed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000795 + Regularly review accounts to determine if they are still active. Remove or disable accounts that have not been used in the last 35 days. + + + + Open "Windows PowerShell". + +Domain Controllers: + +Enter "Search-ADAccount -AccountInactive -UsersOnly -TimeSpan 35.00:00:00" + +This will return accounts that have not been logged on to for 35 days, along with various attributes such as the Enabled status and LastLogonDate. + +Member servers and standalone or nondomain-joined systems: + +Copy or enter the lines below to the PowerShell window and enter. (Entering twice may be required. Do not include the quotes at the beginning and end of the query.) + +"([ADSI]('WinNT://{0}' -f $env:COMPUTERNAME)).Children | Where { $_.SchemaClassName -eq 'user' } | ForEach { + $user = ([ADSI]$_.Path) + $lastLogin = $user.Properties.LastLogin.Value + $enabled = ($user.Properties.UserFlags.Value -band 0x2) -ne 0x2 + if ($lastLogin -eq $null) { + $lastLogin = 'Never' + } + Write-Host $user.Name $lastLogin $enabled +}" + +This will return a list of local accounts with the account name, last logon, and if the account is enabled (True/False). +For example: User1 10/31/2015 5:49:56 AM True + +Review the list of accounts returned by the above queries to determine the finding validity for each account reported. + +Exclude the following accounts: + +- Built-in administrator account (Renamed, SID ending in 500) +- Built-in guest account (Renamed, Disabled, SID ending in 501) +- Application accounts + +If any enabled accounts have not been logged on to within the past 35 days, this is a finding. + +Inactive accounts that have been reviewed and deemed to be required must be documented with the Information System Security Officer (ISSO). + + + + + SRG-OS-000104-GPOS-00051 + <GroupDescription></GroupDescription> + + WN22-00-000200 + Windows Server 2022 accounts must require passwords. + <VulnDiscussion>The lack of password protection enables anyone to gain access to the information system, which opens a backdoor opportunity for intruders to compromise the system as well as other resources. Accounts on a system must require passwords.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000764 + Configure all enabled accounts to require passwords. + +The password required flag can be set by entering the following on a command line: "Net user [username] /passwordreq:yes", substituting [username] with the name of the user account. + + + + Review the password required status for enabled user accounts. + +Open "PowerShell". + +Domain Controllers: + +Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled". + +Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs). + +If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding. + +Member servers and standalone or nondomain-joined systems: + +Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. + +Exclude disabled accounts (e.g., DefaultAccount, Guest). + +If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding. + + + + + SRG-OS-000076-GPOS-00044 + <GroupDescription></GroupDescription> + + WN22-00-000210 + Windows Server 2022 passwords must be configured to expire. + <VulnDiscussion>Passwords that do not expire or are reused increase the exposure of a password with greater probability of being discovered or cracked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000199 + Configure all enabled user account passwords to expire. + +Uncheck "Password never expires" for all enabled user accounts in Active Directory Users and Computers for domain accounts and Users in Computer Management for member servers and standalone or nondomain-joined systems. Document any exceptions with the Information System Security Officer (ISSO). + + + + Review the password never expires status for enabled user accounts. + +Open "PowerShell". + +Domain Controllers: + +Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled". + +Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. + +If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. + +Member servers and standalone or nondomain-joined systems: + +Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'. + +Exclude application accounts and disabled accounts (e.g., DefaultAccount, Guest). + +If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding. + + + + + SRG-OS-000363-GPOS-00150 + <GroupDescription></GroupDescription> + + WN22-00-000220 + Windows Server 2022 system files must be monitored for unauthorized changes. + <VulnDiscussion>Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001744 + Monitor the system for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. This can be done with the use of various monitoring tools. + + + + Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. + +If system files are not monitored for unauthorized changes, this is a finding. + +A properly configured and approved DoD ESS solution that supports a File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. + + + + + SRG-OS-000138-GPOS-00069 + <GroupDescription></GroupDescription> + + WN22-00-000230 + Windows Server 2022 nonsystem-created file shares must limit access to groups that require it. + <VulnDiscussion>Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to accounts that require it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001090 + If a nonsystem-created share is required on a system, configure the share and NTFS permissions to limit access to the specific groups or accounts that require it. + +Remove any unnecessary nonsystem-created shares. + + + + If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.) + +Run "Computer Management". + +Navigate to System Tools >> Shared Folders >> Shares. + +Right-click any nonsystem-created shares. + +Select "Properties". + +Select the "Share Permissions" tab. + +If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. + +Select the "Security" tab. + +If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000240 + Windows Server 2022 must have software certificate installation files removed. + <VulnDiscussion>Use of software certificates and their accompanying installation files for end users to access resources is less secure than the use of hardware-based certificates.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Remove any certificate installation files (*.p12 and *.pfx) found on a system. + +Note: This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. + + + + Search all drives for *.p12 and *.pfx files. + +If any files with these extensions exist, this is a finding. + +This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. Some applications create files with extensions of .p12 that are not certificate installation files. Removal of noncertificate installation files from systems is not required. These must be documented with the Information System Security Officer (ISSO). + + + + + SRG-OS-000185-GPOS-00079 + <GroupDescription></GroupDescription> + + WN22-00-000250 + Windows Server 2022 systems requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. + <VulnDiscussion>This requirement addresses protection of user-generated data as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. + +Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). + +Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001199 + CCI-002475 + CCI-002476 + Configure systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data to employ encryption to protect the confidentiality and integrity of all information at rest. + + + + Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest. + +If they do not, this is a finding. + + + + + SRG-OS-000425-GPOS-00189 + <GroupDescription></GroupDescription> + + WN22-00-000260 + Windows Server 2022 must implement protection methods such as TLS, encrypted VPNs, or IPsec if the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. + <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, 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. + +Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. + +Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPsec. + +Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002420 + CCI-002422 + Configure protection methods such as TLS, encrypted VPNs, or IPsec when the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. + + + + If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPsec have been implemented. + +If protection methods have not been implemented, this is a finding. + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-00-000270 + Windows Server 2022 must have the roles and features required by the system documented. + <VulnDiscussion>Unnecessary roles and features increase the attack surface of a system. Limiting roles and features of a system to only those necessary reduces this potential. The standard installation option (previously called Server Core) further reduces this when selected at installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Document the roles and features required for the system to operate. Uninstall any that are not required. + + + + Required roles and features will vary based on the function of the individual system. + +Roles and features specifically required to be disabled per the STIG are identified in separate requirements. + +If the organization has not documented the roles and features required for the system(s), this is a finding. + +The PowerShell command "Get-WindowsFeature" will list all roles and features with an "Install State". + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000280 + Windows Server 2022 must have a host-based firewall installed and enabled. + <VulnDiscussion>A firewall provides a line of defense against attack, allowing or blocking inbound and outbound connections based on a set of rules. + +Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000480-GPOS-00232</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + CCI-002080 + Install and enable a host-based firewall on the system. + + + + Determine if a host-based firewall is installed and enabled on the system. + +If a host-based firewall is not installed and enabled on the system, this is a finding. + +The configuration requirements will be determined by the applicable firewall STIG. + + + + + SRG-OS-000191-GPOS-00080 + <GroupDescription></GroupDescription> + + WN22-00-000290 + Windows Server 2022 must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where Endpoint Security Solution (ESS) is used; 30 days, for any additional internal network scans not covered by ESS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP). + <VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using ESS and periodic scanning using other tools.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001233 + Install a DoD-approved ESS software and ensure it is operating continuously. + + + + Verify DoD-approved ESS software is installed and properly operating. Ask the site Information System Security Manager (ISSM) for documentation of the ESS software installation and configuration. + +If the ISSM is not able to provide a documented configuration for an installed ESS or if the ESS software is not properly maintained or used, this is a finding. + +Note: Example of documentation can be a copy of the site's configuration control board (CCB)-approved software baseline with version of software noted or a memo from the ISSM stating current ESS software and version. + + + + + SRG-OS-000002-GPOS-00002 + <GroupDescription></GroupDescription> + + WN22-00-000300 + Windows Server 2022 must automatically remove or disable temporary user accounts after 72 hours. + <VulnDiscussion>If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. + +Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. + +If temporary accounts are used, the operating system must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours. + +To address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000016 + Configure temporary user accounts to automatically expire within 72 hours. + +Domain accounts can be configured with an account expiration date, under "Account" properties. + +Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where [username] is the name of the temporary user account. + +Delete any temporary user accounts that are no longer necessary. + + + + Review temporary user accounts for expiration dates. + +Determine if temporary user accounts are used and identify any that exist. If none exist, this is NA. + +Domain Controllers: + +Open "PowerShell". + +Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". + +If "AccountExpirationDate" has not been defined within 72 hours for any temporary user account, this is a finding. + +Member servers and standalone or nondomain-joined systems: + +Open "Command Prompt". + +Run "Net user [username]", where [username] is the name of the temporary user account. + +If "Account expires" has not been defined within 72 hours for any temporary user account, this is a finding. + + + + + SRG-OS-000123-GPOS-00064 + <GroupDescription></GroupDescription> + + WN22-00-000310 + Windows Server 2022 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours. + <VulnDiscussion>Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. + +Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account must be established for privileged users who need long-term maintenance accounts. + +To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001682 + Remove emergency administrator accounts after a crisis has been resolved or configure the accounts to automatically expire within 72 hours. + +Domain accounts can be configured with an account expiration date, under "Account" properties. + +Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where [username] is the name of the temporary user account. + + + + Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA. + +If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved. + +If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding. + +Domain Controllers: + +Open "PowerShell". + +Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". + +If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. + +Member servers and standalone or nondomain-joined systems: + +Open "Command Prompt". + +Run "Net user [username]", where [username] is the name of the emergency account. + +If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-00-000320 + Windows Server 2022 must not have the Fax Server role installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Uninstall the "Fax Server" role. + +Start "Server Manager". + +Select the server with the role. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "Fax Server" on the "Roles" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq Fax". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. + + + + + SRG-OS-000096-GPOS-00050 + <GroupDescription></GroupDescription> + + WN22-00-000330 + Windows Server 2022 must not have the Microsoft FTP service installed unless required by the organization. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000382 + Uninstall the "FTP Server" role. + +Start "Server Manager". + +Select the server with the role. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "FTP Server" under "Web Server (IIS)" on the "Roles" page. + +Click "Next" and "Remove" as prompted. + + + + If the server has the role of an FTP server, this is NA. + +Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq Web-Ftp-Service". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. + +If the system has the role of an FTP server, this must be documented with the Information System Security Officer (ISSO). + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-00-000340 + Windows Server 2022 must not have the Peer Name Resolution Protocol installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Uninstall the "Peer Name Resolution Protocol" feature. + +Start "Server Manager". + +Select the server with the feature. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "Peer Name Resolution Protocol" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq PNRP". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-00-000350 + Windows Server 2022 must not have Simple TCP/IP Services installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Uninstall the "Simple TCP/IP Services" feature. + +Start "Server Manager". + +Select the server with the feature. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "Simple TCP/IP Services" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq Simple-TCPIP". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. + + + + + SRG-OS-000096-GPOS-00050 + <GroupDescription></GroupDescription> + + WN22-00-000360 + Windows Server 2022 must not have the Telnet Client installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000382 + Uninstall the "Telnet Client" feature. + +Start "Server Manager". + +Select the server with the feature. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "Telnet Client" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq Telnet-Client". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-00-000370 + Windows Server 2022 must not have the TFTP Client installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Uninstall the "TFTP Client" feature. + +Start "Server Manager". + +Select the server with the feature. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "TFTP Client" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq TFTP-Client". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-00-000380 + Windows Server 2022 must not the Server Message Block (SMB) v1 protocol installed. + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks and is not FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Uninstall the SMBv1 protocol. + +Open "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Uninstall-WindowsFeature -Name FS-SMB1 -Restart". +(Omit the Restart parameter if an immediate restart of the system cannot be done.) + +Alternately: + +Start "Server Manager". + +Select the server with the feature. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "SMB 1.0/CIFS File Sharing Support" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Different methods are available to disable SMBv1 on Windows Server 2022. This is the preferred method, however if WN22-00-000390 and WN22-00-000400 are configured, this is NA. + +Open "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-WindowsFeature -Name FS-SMB1". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-00-000390 + Windows Server 2022 must have the Server Message Block (SMB) v1 protocol disabled on the SMB server. + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> Configure SMBv1 Server to "Disabled". + +The system must be restarted for the change to take effect. + +This policy setting requires the installation of the SecGuide custom templates included with the STIG package. "SecGuide.admx" and "SecGuide.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively. + + + + Different methods are available to disable SMBv1 on Windows Server 2022, if WN22-00-000380 is configured, this is NA. + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\ + +Value Name: SMB1 + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-00-000400 + Windows Server 2022 must have the Server Message Block (SMB) v1 protocol disabled on the SMB client. + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> Configure SMBv1 client driver to "Enabled" with "Disable driver (recommended)" selected for "Configure MrxSmb10 driver". + +The system must be restarted for the changes to take effect. + +This policy setting requires the installation of the SecGuide custom templates included with the STIG package. "SecGuide.admx" and "SecGuide.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively. + + + + Different methods are available to disable SMBv1 on Windows Server 2022, if WN22-00-000380 is configured, this is NA. + +If the following registry value is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\mrxsmb10\ + +Value Name: Start + +Type: REG_DWORD +Value: 0x00000004 (4) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-00-000410 + Windows Server 2022 must not have Windows PowerShell 2.0 installed. + <VulnDiscussion>Windows PowerShell 5.x added advanced logging features that can provide additional detail when malware has been run on a system. Disabling the Windows PowerShell 2.0 mitigates against a downgrade attack that evades the Windows PowerShell 5.x script block logging feature.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Uninstall the "Windows PowerShell 2.0 Engine". + +Start "Server Manager". + +Select the server with the feature. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "Windows PowerShell 2.0 Engine" under "Windows PowerShell" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq PowerShell-v2". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000420 + Windows Server 2022 FTP servers must be configured to prevent anonymous logons. + <VulnDiscussion>The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult. + +Using accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the FTP service to prevent anonymous logons. + +Open "Internet Information Services (IIS) Manager". + +Select the server. + +Double-click "FTP Authentication". + +Select "Anonymous Authentication". + +Select "Disabled" under "Actions". + + + + If FTP is not installed on the system, this is NA. + +Open "Internet Information Services (IIS) Manager". + +Select the server. + +Double-click "FTP Authentication". + +If the "Anonymous Authentication" status is "Enabled", this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000430 + Windows Server 2022 FTP servers must be configured to prevent access to the system drive. + <VulnDiscussion>The FTP service allows remote users to access shared files and directories that could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the FTP sites to allow access only to specific FTP shared resources. Do not allow access to other areas of the system. + + + + If FTP is not installed on the system, this is NA. + +Open "Internet Information Services (IIS) Manager". + +Select "Sites" under the server name. + +For any sites with a Binding that lists FTP, right-click the site and select "Explore". + +If the site is not defined to a specific folder for shared FTP resources, this is a finding. + +If the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding. + + + + + SRG-OS-000355-GPOS-00143 + <GroupDescription></GroupDescription> + + WN22-00-000440 + The Windows Server 2022 time service must synchronize with an appropriate DoD time source. + <VulnDiscussion>The Windows Time Service controls time synchronization settings. Time synchronization is essential for authentication and auditing purposes. If the Windows Time Service is used, it must synchronize with a secure, authorized time source. Domain-joined systems are automatically configured to synchronize with domain controllers. If an NTP server is configured, it must synchronize with a secure, authorized time source.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001891 + Configure the system to synchronize time with an appropriate DoD time source. + +Domain-joined systems use NT5DS to synchronize time from other systems in the domain by default. + +If the system needs to be configured to an NTP server, configure the system to point to an authorized time server by setting the policy value for Computer Configuration >> Administrative Templates >> System >> Windows Time Service >> Time Providers. Change "Configure Windows NTP Client" to "Enabled", and configure the "NtpServer" field to point to an appropriate DoD time server. + +The US Naval Observatory operates stratum 1 time servers, identified at https://www.usno.navy.mil/USNO/time/ntp/dod-customers. Time synchronization will occur through a hierarchy of time servers down to the local level. Clients and lower-level servers will synchronize with an authorized time server in the hierarchy. + + + + Review the Windows time service configuration. + +Open an elevated "Command Prompt" (run as administrator). + +Enter "W32tm /query /configuration". + +Domain-joined systems (excluding the domain controller with the PDC emulator role): + +If the value for "Type" under "NTP Client" is not "NT5DS", this is a finding. + +Other systems: + +If systems are configured with a "Type" of "NTP", including standalone or nondomain-joined systems and the domain controller with the PDC Emulator role, and do not have a DoD time server defined for "NTPServer", this is a finding. + +To determine the domain controller with the PDC Emulator role: + +Open "PowerShell". + +Enter "Get-ADDomain | FT PDCEmulator". + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000460 + Windows Server 2022 systems must have Unified Extensible Firmware Interface (UEFI) firmware and be configured to run in UEFI mode, not Legacy BIOS. + <VulnDiscussion>UEFI provides additional security features in comparison to legacy BIOS firmware, including Secure Boot. UEFI is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. Systems with UEFI that are operating in "Legacy BIOS" mode will not support these security features.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure UEFI firmware to run in "UEFI" mode, not "Legacy BIOS" mode. + + + + Devices that have UEFI firmware must run in "UEFI" mode. + +Verify the system firmware is configured to run in "UEFI" mode, not "Legacy BIOS". + +Run "System Information". + +Under "System Summary", if "BIOS Mode" does not display "UEFI", this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000470 + Windows Server 2022 must have Secure Boot enabled. + <VulnDiscussion>Secure Boot is a standard that ensures systems boot only to a trusted operating system. Secure Boot is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. If Secure Boot is turned off, these security features will not function.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Enable Secure Boot in the system firmware. + + + + Devices that have UEFI firmware must have Secure Boot enabled. + +Run "System Information". + +Under "System Summary", if "Secure Boot State" does not display "On", this is a finding. + +On server core installations, run the following PowerShell command: + +Confirm-SecureBootUEFI + +If a value of "True" is not returned, this is a finding. + + + + + SRG-OS-000342-GPOS-00133 + <GroupDescription></GroupDescription> + + WN22-AU-000010 + Windows Server 2022 audit records must be backed up to a different system or media than the system being audited. + <VulnDiscussion>Protection of log data includes ensuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001851 + Establish and implement a process for backing up log data to another system or media other than the system being audited. + + + + Determine if a process to back up log data to a different system or media than the system being audited has been implemented. + +If it has not, this is a finding. + + + + + SRG-OS-000479-GPOS-00224 + <GroupDescription></GroupDescription> + + WN22-AU-000020 + Windows Server 2022 must, at a minimum, offload audit records of interconnected systems in real time and offload standalone or nondomain-joined systems weekly. + <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001851 + Configure the system to, at a minimum, offload audit records of interconnected systems in real time and offload standalone or nondomain-joined systems weekly. + + + + Verify the audit records, at a minimum, are offloaded for interconnected systems in real time and offloaded for standalone or nondomain-joined systems weekly. + +If they are not, this is a finding. + + + + + SRG-OS-000057-GPOS-00027 + <GroupDescription></GroupDescription> + + WN22-AU-000030 + Windows Server 2022 permissions for the Application event log must prevent access by nonprivileged accounts. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The Application event log may be susceptible to tampering if proper permissions are not applied. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000162 + CCI-000163 + CCI-000164 + Configure the permissions on the Application event log file (Application.evtx) to prevent access by nonprivileged accounts. The default permissions listed below satisfy this requirement: + +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. + +If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". + + + + Navigate to the Application event log file. + +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. + +If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding: + +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + + + + + SRG-OS-000057-GPOS-00027 + <GroupDescription></GroupDescription> + + WN22-AU-000040 + Windows Server 2022 permissions for the Security event log must prevent access by nonprivileged accounts. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The Security event log may disclose sensitive information or be susceptible to tampering if proper permissions are not applied. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000162 + CCI-000163 + CCI-000164 + Configure the permissions on the Security event log file (Security.evtx) to prevent access by nonprivileged accounts. The default permissions listed below satisfy this requirement: + +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. + +If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". + + + + Navigate to the Security event log file. + +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. + +If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding: + +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + + + + + SRG-OS-000057-GPOS-00027 + <GroupDescription></GroupDescription> + + WN22-AU-000050 + Windows Server 2022 permissions for the System event log must prevent access by nonprivileged accounts. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The System event log may be susceptible to tampering if proper permissions are not applied. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000162 + CCI-000163 + CCI-000164 + Configure the permissions on the System event log file (System.evtx) to prevent access by nonprivileged accounts. The default permissions listed below satisfy this requirement: + +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. + +If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". + + + + Navigate to the System event log file. + +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. + +If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding: + +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + + + + + SRG-OS-000257-GPOS-00098 + <GroupDescription></GroupDescription> + + WN22-AU-000060 + Windows Server 2022 Event Viewer must be protected from unauthorized modification and deletion. + <VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. + +Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys to make access decisions regarding the modification or deletion of audit tools. + +Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001494 + CCI-001495 + Configure the permissions on the "Eventvwr.exe" file to prevent modification by any groups or accounts other than TrustedInstaller. The default permissions listed below satisfy this requirement: + +TrustedInstaller - Full Control +Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute + +The default location is the "%SystemRoot%\System32" folder. + + + + Navigate to "%SystemRoot%\System32". + +View the permissions on "Eventvwr.exe". + +If any groups or accounts other than TrustedInstaller have "Full control" or "Modify" permissions, this is a finding. + +The default permissions below satisfy this requirement: + +TrustedInstaller - Full Control +Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute + + + + + SRG-OS-000470-GPOS-00214 + <GroupDescription></GroupDescription> + + WN22-AU-000070 + Windows Server 2022 must be configured to audit Account Logon - Credential Validation successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Credential Validation records events related to validation tests on credentials for a user account logon.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Account Logon >> Audit Credential Validation with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Account Logon >> Credential Validation - Success + + + + + SRG-OS-000470-GPOS-00214 + <GroupDescription></GroupDescription> + + WN22-AU-000080 + Windows Server 2022 must be configured to audit Account Logon - Credential Validation failures. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Credential Validation records events related to validation tests on credentials for a user account logon.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Account Logon >> Audit Credential Validation with "Failure" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Account Logon >> Credential Validation - Failure + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000090 + Windows Server 2022 must be configured to audit Account Management - Other Account Management Events successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Other Account Management Events records events such as the access of a password hash or the Password Policy Checking API being called. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Account Management >> Audit Other Account Management Events with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding: + +Account Management >> Other Account Management Events - Success + + + + + SRG-OS-000004-GPOS-00004 + <GroupDescription></GroupDescription> + + WN22-AU-000100 + Windows Server 2022 must be configured to audit Account Management - Security Group Management successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Security Group Management records events such as creating, deleting, or changing security groups, including changes in group members. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000018 + CCI-000172 + CCI-001403 + CCI-001404 + CCI-001405 + CCI-002130 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Account Management >> Audit Security Group Management with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Account Management >> Security Group Management - Success + + + + + SRG-OS-000004-GPOS-00004 + <GroupDescription></GroupDescription> + + WN22-AU-000110 + Windows Server 2022 must be configured to audit Account Management - User Account Management successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000018 + CCI-000172 + CCI-001403 + CCI-001404 + CCI-001405 + CCI-002130 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Account Management >> Audit User Account Management with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Account Management >> User Account Management - Success + + + + + SRG-OS-000004-GPOS-00004 + <GroupDescription></GroupDescription> + + WN22-AU-000120 + Windows Server 2022 must be configured to audit Account Management - User Account Management failures. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000018 + CCI-000172 + CCI-001403 + CCI-001404 + CCI-001405 + CCI-002130 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Account Management >> Audit User Account Management with "Failure" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Account Management >> User Account Management - Failure + + + + + SRG-OS-000474-GPOS-00219 + <GroupDescription></GroupDescription> + + WN22-AU-000130 + Windows Server 2022 must be configured to audit Detailed Tracking - Plug and Play Events successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Plug and Play activity records events related to the successful connection of external devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Detailed Tracking >> Audit PNP Activity with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Detailed Tracking >> Plug and Play Events - Success + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000140 + Windows Server 2022 must be configured to audit Detailed Tracking - Process Creation successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Process Creation records events related to the creation of a process and the source. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Detailed Tracking >> Audit Process Creation with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Detailed Tracking >> Process Creation - Success + + + + + SRG-OS-000240-GPOS-00090 + <GroupDescription></GroupDescription> + + WN22-AU-000150 + Windows Server 2022 must be configured to audit Logon/Logoff - Account Lockout successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Account Lockout events can be used to identify potentially malicious logon attempts. + +Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-001404 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> Audit Account Lockout with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Logon/Logoff >> Account Lockout - Success + + + + + SRG-OS-000240-GPOS-00090 + <GroupDescription></GroupDescription> + + WN22-AU-000160 + Windows Server 2022 must be configured to audit Logon/Logoff - Account Lockout failures. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Account Lockout events can be used to identify potentially malicious logon attempts. + +Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-001404 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> Audit Account Lockout with "Failure" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Logon/Logoff >> Account Lockout - Failure + + + + + SRG-OS-000470-GPOS-00214 + <GroupDescription></GroupDescription> + + WN22-AU-000170 + Windows Server 2022 must be configured to audit Logon/Logoff - Group Membership successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Audit Group Membership records information related to the group membership of a user's logon token.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> Audit Group Membership with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Logon/Logoff >> Group Membership - Success + + + + + SRG-OS-000472-GPOS-00217 + <GroupDescription></GroupDescription> + + WN22-AU-000180 + Windows Server 2022 must be configured to audit logoff successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Logoff records user logoffs. If this is an interactive logoff, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> Audit Logoff with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Logon/Logoff >> Logoff - Success + + + + + SRG-OS-000032-GPOS-00013 + <GroupDescription></GroupDescription> + + WN22-AU-000190 + Windows Server 2022 must be configured to audit logon successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Logon records user logons. If this is an interactive logon, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed. + +Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000067 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> Audit Logon with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Logon/Logoff >> Logon - Success + + + + + SRG-OS-000032-GPOS-00013 + <GroupDescription></GroupDescription> + + WN22-AU-000200 + Windows Server 2022 must be configured to audit logon failures. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Logon records user logons. If this is an interactive logon, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed. + +Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000067 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> Audit Logon with "Failure" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Logon/Logoff >> Logon - Failure + + + + + SRG-OS-000470-GPOS-00214 + <GroupDescription></GroupDescription> + + WN22-AU-000210 + Windows Server 2022 must be configured to audit Logon/Logoff - Special Logon successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Special Logon records special logons that have administrative privileges and can be used to elevate processes. + +Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> Audit Special Logon with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Logon/Logoff >> Special Logon - Success + + + + + SRG-OS-000470-GPOS-00214 + <GroupDescription></GroupDescription> + + WN22-AU-000220 + Windows Server 2022 must be configured to audit Object Access - Other Object Access Events successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit Other Object Access Events with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Object Access >> Other Object Access Events - Success + + + + + SRG-OS-000470-GPOS-00214 + <GroupDescription></GroupDescription> + + WN22-AU-000230 + Windows Server 2022 must be configured to audit Object Access - Other Object Access Events failures. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit Other Object Access Events with "Failure" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Object Access >> Other Object Access Events - Failure + + + + + SRG-OS-000474-GPOS-00219 + <GroupDescription></GroupDescription> + + WN22-AU-000240 + Windows Server 2022 must be configured to audit Object Access - Removable Storage successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Removable Storage auditing under Object Access records events related to access attempts on file system objects on removable storage devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit Removable Storage with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Object Access >> Removable Storage - Success + +Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. + + + + + SRG-OS-000474-GPOS-00219 + <GroupDescription></GroupDescription> + + WN22-AU-000250 + Windows Server 2022 must be configured to audit Object Access - Removable Storage failures. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Removable Storage auditing under Object Access records events related to access attempts on file system objects on removable storage devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit Removable Storage with "Failure" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Object Access >> Removable Storage - Failure + +Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000260 + Windows Server 2022 must be configured to audit Policy Change - Audit Policy Change successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Audit Policy Change records events related to changes in audit policy. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Policy Change >> Audit Audit Policy Change with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Policy Change >> Audit Audit Policy Change - Success + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000270 + Windows Server 2022 must be configured to audit Policy Change - Audit Policy Change failures. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Audit Policy Change records events related to changes in audit policy. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Policy Change >> Audit Audit Policy Change with "Failure" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Policy Change >> Audit Audit Policy Change - Failure + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000280 + Windows Server 2022 must be configured to audit Policy Change - Authentication Policy Change successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Authentication Policy Change records events related to changes in authentication policy, including Kerberos policy and Trust changes. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Policy Change >> Audit Authentication Policy Change with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Policy Change >> Authentication Policy Change - Success + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000290 + Windows Server 2022 must be configured to audit Policy Change - Authorization Policy Change successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Authorization Policy Change records events related to changes in user rights, such as "Create a token object". + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Policy Change >> Audit Authorization Policy Change with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Policy Change >> Authorization Policy Change - Success + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000300 + Windows Server 2022 must be configured to audit Privilege Use - Sensitive Privilege Use successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Sensitive Privilege Use records events related to use of sensitive privileges, such as "Act as part of the operating system" or "Debug programs". + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Privilege Use >> Audit Sensitive Privilege Use with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Privilege Use >> Sensitive Privilege Use - Success + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000310 + Windows Server 2022 must be configured to audit Privilege Use - Sensitive Privilege Use failures. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Sensitive Privilege Use records events related to use of sensitive privileges, such as "Act as part of the operating system" or "Debug programs". + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Privilege Use >> Audit Sensitive Privilege Use with "Failure" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Privilege Use >> Sensitive Privilege Use - Failure + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000320 + Windows Server 2022 must be configured to audit System - IPsec Driver successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +IPsec Driver records events related to the IPsec Driver, such as dropped packets. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> Audit IPsec Driver with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +System >> IPsec Driver - Success + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000330 + Windows Server 2022 must be configured to audit System - IPsec Driver failures. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +IPsec Driver records events related to the IPsec Driver, such as dropped packets. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> Audit IPsec Driver with "Failure" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +System >> IPsec Driver - Failure + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000340 + Windows Server 2022 must be configured to audit System - Other System Events successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> Audit Other System Events with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +System >> Other System Events - Success + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000350 + Windows Server 2022 must be configured to audit System - Other System Events failures. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> Audit Other System Events with "Failure" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +System >> Other System Events - Failure + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000360 + Windows Server 2022 must be configured to audit System - Security State Change successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Security State Change records events related to changes in the security state, such as startup and shutdown of the system. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> Audit Security State Chang with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +System >> Security State Change - Success + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000370 + Windows Server 2022 must be configured to audit System - Security System Extension successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Security System Extension records events related to extension code being loaded by the security subsystem. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> Audit Security System Extension with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +System >> Security System Extension - Success + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000380 + Windows Server 2022 must be configured to audit System - System Integrity successes. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +System Integrity records events related to violations of integrity to the security subsystem. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> Audit System Integrity with "Success" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +System >> System Integrity - Success + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN22-AU-000390 + Windows Server 2022 must be configured to audit System - System Integrity failures. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +System Integrity records events related to violations of integrity to the security subsystem. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> Audit System Integrity with "Failure" selected. + + + + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +System >> System Integrity - Failure + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-CC-000010 + Windows Server 2022 must prevent the display of slide shows on the lock screen. + <VulnDiscussion>Slide shows that are displayed on the lock screen could display sensitive information to unauthorized personnel. Turning off this feature will limit access to the information to a logged-on user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> Control Panel >> Personalization >> Prevent enabling lock screen slide show to "Enabled". + + + + Verify the registry value below. + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Personalization\ + +Value Name: NoLockScreenSlideshow + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-CC-000020 + Windows Server 2022 must have WDigest Authentication disabled. + <VulnDiscussion>When the WDigest Authentication protocol is enabled, plain-text passwords are stored in the Local Security Authority Subsystem Service (LSASS), exposing them to theft. WDigest is disabled by default in Windows Server 2022. This setting ensures this is enforced.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide . Set "WDigest Authentication (disabling may require KB2871997)" to "Disabled". + +This policy setting requires the installation of the SecGuide custom templates included with the STIG package. "SecGuide.admx" and " SecGuide.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest\ + +Value Name: UseLogonCredential + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000030 + Windows Server 2022 Internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing. + <VulnDiscussion>Configuring the system to disable IPv6 source routing protects against spoofing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing) to "Enabled" with "Highest protection, source routing is completely disabled" selected. + +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ + +Value Name: DisableIPSourceRouting + +Type: REG_DWORD +Value: 0x00000002 (2) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000040 + Windows Server 2022 source routing must be configured to the highest protection level to prevent Internet Protocol (IP) source routing. + <VulnDiscussion>Configuring the system to disable IP source routing protects against spoofing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing) to "Enabled" with "Highest protection, source routing is completely disabled" selected. + +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ + +Value Name: DisableIPSourceRouting + +Value Type: REG_DWORD +Value: 0x00000002 (2) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000050 + Windows Server 2022 must be configured to prevent Internet Control Message Protocol (ICMP) redirects from overriding Open Shortest Path First (OSPF)-generated routes. + <VulnDiscussion>Allowing ICMP redirect of routes can lead to traffic not being routed properly. When disabled, this forces ICMP to be routed via the shortest path first.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes to "Disabled". + +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ + +Value Name: EnableICMPRedirect + +Value Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000420-GPOS-00186 + <GroupDescription></GroupDescription> + + WN22-CC-000060 + Windows Server 2022 must be configured to ignore NetBIOS name release requests except from WINS servers. + <VulnDiscussion>Configuring the system to ignore name release requests, except from WINS servers, prevents a denial of service (DoS) attack. The DoS consists of sending a NetBIOS name release request to the server for each entry in the server's cache, causing a response delay in the normal operation of the server's WINS resolution capability.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002385 + Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers to "Enabled". + +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netbt\Parameters\ + +Value Name: NoNameReleaseOnDemand + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000070 + Windows Server 2022 insecure logons to an SMB server must be disabled. + <VulnDiscussion>Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Lanman Workstation >> Enable insecure guest logons to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation\ + +Value Name: AllowInsecureGuestAuth + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000080 + Windows Server 2022 hardened Universal Naming Convention (UNC) paths must be defined to require mutual authentication and integrity for at least the \\*\SYSVOL and \\*\NETLOGON shares. + <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Network Provider >> Hardened UNC Paths" to "Enabled" with at least the following configured in "Hardened UNC Paths" (click the "Show" button to display): + +Value Name: \\*\SYSVOL +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + +Value Name: \\*\NETLOGON +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + + + + This requirement is applicable to domain-joined systems. For standalone or nondomain-joined systems, this is NA. + +If the following registry values do not exist or are not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ + +Value Name: \\*\NETLOGON +Value Type: REG_SZ +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + +Value Name: \\*\SYSVOL +Value Type: REG_SZ +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + +Additional entries would not be a finding. + + + + + SRG-OS-000042-GPOS-00020 + <GroupDescription></GroupDescription> + + WN22-CC-000090 + Windows Server 2022 command line data must be included in process creation events. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Enabling "Include command line data for process creation events" will record the command line information with the process creation events in the log. This can provide additional detail when malware has run on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000135 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Audit Process Creation >> Include command line in process creation events to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit\ + +Value Name: ProcessCreationIncludeCmdLine_Enabled + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000100 + Windows Server 2022 must be configured to enable Remote host allows delegation of nonexportable credentials. + <VulnDiscussion>An exportable version of credentials is provided to remote hosts when using credential delegation which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of nonexportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> Remote host allows delegation of nonexportable credentials to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\ + +Value Name: AllowProtectedCreds + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000110 + Windows Server 2022 virtualization-based security must be enabled with the platform security level configured to Secure Boot or Secure Boot with DMA Protection. + <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> Turn On Virtualization Based Security to "Enabled" with "Secure Boot" or "Secure Boot and DMA Protection" selected. + +A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: + +https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard + + + + For standalone or nondomain-joined systems, this is NA. + +Open "PowerShell" with elevated privileges (run as administrator). + +Enter the following: + +"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" + +If "RequiredSecurityProperties" does not include a value of "2" indicating "Secure Boot" (e.g., "{1, 2}"), this is a finding. + +If "Secure Boot and DMA Protection" is configured, "3" will also be displayed in the results (e.g., "{1, 2, 3}"). + +If "VirtualizationBasedSecurityStatus" is not a value of "2" indicating "Running", this is a finding. + +Alternately: + +Run "System Information". + +Under "System Summary", verify the following: + +If "Device Guard Virtualization based security" does not display "Running", this is a finding. + +If "Device Guard Required Security Properties" does not display "Base Virtualization Support, Secure Boot", this is a finding. + +If "Secure Boot and DMA Protection" is configured, "DMA Protection" will also be displayed (e.g., "Base Virtualization Support, Secure Boot, DMA Protection"). + +The policy settings referenced in the Fix section will configure the following registry values; however, due to hardware requirements, the registry values alone do not ensure proper function. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ + +Value Name: EnableVirtualizationBasedSecurity +Value Type: REG_DWORD +Value: 0x00000001 (1) + +Value Name: RequirePlatformSecurityFeatures +Value Type: REG_DWORD +Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection) + +A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: + +https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000130 + Windows Server 2022 Early Launch Antimalware, Boot-Start Driver Initialization Policy must prevent boot drivers identified as bad. + <VulnDiscussion>Compromised boot drivers can introduce malware prior to protection mechanisms that load after initialization. The Early Launch Antimalware driver can limit allowed drivers based on classifications determined by the malware protection application. At a minimum, drivers determined to be bad must not be allowed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). + +If this needs to be corrected or a more secure setting is desired, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Early Launch Antimalware >> Boot-Start Driver Initialization Policy to "Not Configured" or "Enabled" with any option other than "All" selected. + + + + The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0x00000007 (7)", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Policies\EarlyLaunch\ + +Value Name: DriverLoadPolicy + +Value Type: REG_DWORD +Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist) + +Possible values for this setting are: +8 - Good only +1 - Good and unknown +3 - Good, unknown and bad but critical +7 - All (which includes "bad" and would be a finding) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000140 + Windows Server 2022 group policy objects must be reprocessed even if they have not changed. + <VulnDiscussion>Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures the policies will be reprocessed even if none have been changed. This way, any unauthorized changes are forced to match the domain-based group policy settings again.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Group Policy >> Configure registry policy processing to "Enabled" with the option "Process even if the Group Policy objects have not changed" selected. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\ + +Value Name: NoGPOListChanges + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-CC-000150 + Windows Server 2022 downloading print driver packages over HTTP must be turned off. + <VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and will prevent uncontrolled updates to the system. + +This setting prevents the computer from downloading print driver packages over HTTP.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Internet Communication Management >> Internet Communication settings >> Turn off downloading of print drivers over HTTP to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ + +Value Name: DisableWebPnPDownload + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-CC-000160 + Windows Server 2022 printing over HTTP must be turned off. + <VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and will prevent uncontrolled updates to the system. + +This setting prevents the client computer from printing over HTTP, which allows the computer to print to printers on the intranet as well as the internet.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Internet Communication Management >> Internet Communication settings >> Turn off printing over HTTP to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ + +Value Name: DisableHTTPPrinting + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-CC-000170 + Windows Server 2022 network selection user interface (UI) must not be displayed on the logon screen. + <VulnDiscussion>Enabling interaction with the network selection UI allows users to change connections to available networks without signing in to Windows.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Logon >> Do not display network selection UI to "Enabled". + + + + Verify the registry value below. If it does not exist or is not configured as specified, this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ + +Value Name: DontDisplayNetworkSelectionUI + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000180 + Windows Server 2022 users must be prompted to authenticate when the system wakes from sleep (on battery). + <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes from sleep (on battery).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Power Management >> Sleep Settings >> Require a password when a computer wakes (on battery) to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ + +Value Name: DCSettingIndex + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000190 + Windows Server 2022 users must be prompted to authenticate when the system wakes from sleep (plugged in). + <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes from sleep (plugged in).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Power Management >> Sleep Settings >> Require a password when a computer wakes (plugged in) to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ + +Value Name: ACSettingIndex + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-CC-000200 + Windows Server 2022 Application Compatibility Program Inventory must be prevented from collecting data and sending the information to Microsoft. + <VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and will prevent uncontrolled updates to the system. + +This setting will prevent the Program Inventory from collecting data about a system and sending the information to Microsoft.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Application Compatibility >> Turn off Inventory Collector to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\AppCompat\ + +Value Name: DisableInventory + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000368-GPOS-00154 + <GroupDescription></GroupDescription> + + WN22-CC-000210 + Windows Server 2022 Autoplay must be turned off for nonvolume devices. + <VulnDiscussion>Allowing AutoPlay to execute may introduce malicious code to a system. AutoPlay begins reading from a drive as soon as media is inserted into the drive. As a result, the setup file of programs or music on audio media may start. This setting will disable AutoPlay for nonvolume devices, such as Media Transfer Protocol (MTP) devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001764 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> Disallow Autoplay for nonvolume devices to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ + +Value Name: NoAutoplayfornonVolume + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000368-GPOS-00154 + <GroupDescription></GroupDescription> + + WN22-CC-000220 + Windows Server 2022 default AutoRun behavior must be configured to prevent AutoRun commands. + <VulnDiscussion>Allowing AutoRun commands to execute may introduce malicious code to a system. Configuring this setting prevents AutoRun commands from executing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001764 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> Set the default behavior for AutoRun to "Enabled" with "Do not execute any autorun commands" selected. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ + +Value Name: NoAutorun + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000368-GPOS-00154 + <GroupDescription></GroupDescription> + + WN22-CC-000230 + Windows Server 2022 AutoPlay must be disabled for all drives. + <VulnDiscussion>Allowing AutoPlay to execute may introduce malicious code to a system. AutoPlay begins reading from a drive as soon media is inserted into the drive. As a result, the setup file of programs or music on audio media may start. By default, AutoPlay is disabled on removable drives, such as the floppy disk drive (but not the CD-ROM drive) and on network drives. Enabling this policy disables AutoPlay on all drives.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001764 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> Turn off AutoPlay to "Enabled" with "All Drives" selected. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\ + +Value Name: NoDriveTypeAutoRun + +Type: REG_DWORD +Value: 0x000000ff (255) + + + + + SRG-OS-000134-GPOS-00068 + <GroupDescription></GroupDescription> + + WN22-CC-000240 + Windows Server 2022 administrator accounts must not be enumerated during elevation. + <VulnDiscussion>Enumeration of administrator accounts when elevating can provide part of the logon information to an unauthorized user. This setting configures the system to always require users to type in a username and password to elevate a running application.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001084 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Credential User Interface >> Enumerate administrator accounts on elevation to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI\ + +Value Name: EnumerateAdministrators + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000250 + Windows Server 2022 Telemetry must be configured to Security or Basic. + <VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "Security" option for Telemetry configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and telemetry client settings. "Basic" sends basic diagnostic and usage data and may be required to support some Microsoft services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Data Collection and Preview Build >> Allow Telemetry to "Enabled" with "0 - Security [Enterprise Only]" or "1 - Basic" selected in "Options". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DataCollection\ + +Value Name: AllowTelemetry + +Type: REG_DWORD +Value: 0x00000000 (0) (Security), 0x00000001 (1) (Basic) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000260 + Windows Server 2022 Windows Update must not obtain updates from other PCs on the internet. + <VulnDiscussion>Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the internet. This is part of the Windows Update trusted process; however, to minimize outside exposure, obtaining updates from or sending to systems on the internet must be prevented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Delivery Optimization >> Download Mode to "Enabled" with any option except "Internet" selected. + +Acceptable selections include: + +Bypass (100) +Group (2) +HTTP only (0) +LAN (1) +Simple (99) + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization\ + +Value Name: DODownloadMode + +Value Type: REG_DWORD +Value: 0x00000000 (0) - No peering (HTTP Only) +0x00000001 (1) - Peers on same NAT only (LAN) +0x00000002 (2) - Local Network / Private group peering (Group) +0x00000063 (99) - Simple download mode, no peering (Simple) +0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass) + +A value of 0x00000003 (3), Internet, is a finding. + + + + + SRG-OS-000341-GPOS-00132 + <GroupDescription></GroupDescription> + + WN22-CC-000270 + Windows Server 2022 Application event log size must be configured to 32768 KB or greater. + <VulnDiscussion>Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001849 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Event Log Service >> Application >> Specify the maximum log file size (KB) to "Enabled" with a "Maximum Log Size (KB)" of "32768" or greater. + + + + If the system is configured to write events directly to an audit server, this is NA. + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Application\ + +Value Name: MaxSize + +Type: REG_DWORD +Value: 0x00008000 (32768) (or greater) + + + + + SRG-OS-000341-GPOS-00132 + <GroupDescription></GroupDescription> + + WN22-CC-000280 + Windows Server 2022 Security event log size must be configured to 196608 KB or greater. + <VulnDiscussion>Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001849 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Event Log Service >> Security >> Specify the maximum log file size (KB) to "Enabled" with a "Maximum Log Size (KB)" of "196608" or greater. + + + + If the system is configured to write events directly to an audit server, this is NA. + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Security\ + +Value Name: MaxSize + +Type: REG_DWORD +Value: 0x00030000 (196608) (or greater) + + + + + SRG-OS-000341-GPOS-00132 + <GroupDescription></GroupDescription> + + WN22-CC-000290 + Windows Server 2022 System event log size must be configured to 32768 KB or greater. + <VulnDiscussion>Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001849 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Event Log Service >> System >> Specify the maximum log file size (KB) to "Enabled" with a "Maximum Log Size (KB)" of "32768" or greater. + + + + If the system is configured to write events directly to an audit server, this is NA. + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\System\ + +Value Name: MaxSize + +Type: REG_DWORD +Value: 0x00008000 (32768) (or greater) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-CC-000300 + Windows Server 2022 Microsoft Defender antivirus SmartScreen must be enabled. + <VulnDiscussion>Microsoft Defender antivirus SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Configure Windows Defender SmartScreen to "Enabled" with either option "Warn" or "Warn and prevent bypass" selected. + +Windows Server 2022 includes duplicate policies for this setting. It can also be configured under Computer Configuration >> Administrative Templates >> Windows Components >> Windows Defender SmartScreen >> Explorer. + + + + This is applicable to unclassified systems; for other systems, this is NA. + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ + +Value Name: EnableSmartScreen + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000433-GPOS-00192 + <GroupDescription></GroupDescription> + + WN22-CC-000310 + Windows Server 2022 Explorer Data Execution Prevention must be enabled. + <VulnDiscussion>Data Execution Prevention provides additional protection by performing checks on memory to help prevent malicious code from running. This setting will prevent Data Execution Prevention from being turned off for File Explorer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002824 + The default behavior is for data execution prevention to be turned on for File Explorer. + +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Turn off Data Execution Prevention for Explorer to "Not Configured" or "Disabled". + + + + The default behavior is for Data Execution Prevention to be turned on for File Explorer. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ + +Value Name: NoDataExecutionPrevention + +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000320 + Windows Server 2022 Turning off File Explorer heap termination on corruption must be disabled. + <VulnDiscussion>Legacy plug-in applications may continue to function when a File Explorer session has become corrupt. Disabling this feature will prevent this.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + The default behavior is for File Explorer heap termination on corruption to be disabled. + +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Turn off heap termination on corruption to "Not Configured" or "Disabled". + + + + The default behavior is for File Explorer heap termination on corruption to be enabled. + +If the registry Value Name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ + +Value Name: NoHeapTerminationOnCorruption + +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000330 + Windows Server 2022 File Explorer shell protocol must run in protected mode. + <VulnDiscussion>The shell protocol will limit the set of folders that applications can open when run in protected mode. Restricting files an application can open to a limited set of folders increases the security of Windows.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + The default behavior is for shell protected mode to be turned on for File Explorer. + +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Turn off shell protocol protected mode to "Not Configured" or "Disabled". + + + + The default behavior is for shell protected mode to be turned on for File Explorer. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ + +Value Name: PreXPSP2ShellProtocolBehavior + +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) + + + + + SRG-OS-000373-GPOS-00156 + <GroupDescription></GroupDescription> + + WN22-CC-000340 + Windows Server 2022 must not save passwords in the Remote Desktop Client. + <VulnDiscussion>Saving passwords in the Remote Desktop Client could allow an unauthorized user to establish a remote desktop session to another system. The system must be configured to prevent users from saving passwords in the Remote Desktop Client. + +Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002038 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Remote Desktop Services >> Remote Desktop Connection Client >> Do not allow passwords to be saved to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ + +Value Name: DisablePasswordSaving + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000138-GPOS-00069 + <GroupDescription></GroupDescription> + + WN22-CC-000350 + Windows Server 2022 Remote Desktop Services must prevent drive redirection. + <VulnDiscussion>Preventing users from sharing the local drives on their client computers with Remote Session Hosts that they access helps reduce possible exposure of sensitive data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001090 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Remote Desktop Services >> Remote Desktop Session Host >> Device and Resource Redirection >> Do not allow drive redirection to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ + +Value Name: fDisableCdm + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000373-GPOS-00156 + <GroupDescription></GroupDescription> + + WN22-CC-000360 + Windows Server 2022 Remote Desktop Services must always prompt a client for passwords upon connection. + <VulnDiscussion>This setting controls the ability of users to supply passwords automatically as part of their remote desktop connection. Disabling this setting would allow anyone to use the stored credentials in a connection item to connect to the terminal server. + +Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002038 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Remote Desktop Services >> Remote Desktop Session Host >> Security >> Always prompt for password upon connection to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ + +Value Name: fPromptForPassword + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000033-GPOS-00014 + <GroupDescription></GroupDescription> + + WN22-CC-000370 + Windows Server 2022 Remote Desktop Services must require secure Remote Procedure Call (RPC) communications. + <VulnDiscussion>Allowing unsecure RPC communication exposes the system to man-in-the-middle attacks and data disclosure attacks. A man-in-the-middle attack occurs when an intruder captures packets between a client and server and modifies them before allowing the packets to be exchanged. Usually the attacker will modify the information in the packets in an attempt to cause either the client or server to reveal sensitive information. + +Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000068 + CCI-001453 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Remote Desktop Services >> Remote Desktop Session Host >> Security >> Require secure RPC communication to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ + +Value Name: fEncryptRPCTraffic + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000033-GPOS-00014 + <GroupDescription></GroupDescription> + + WN22-CC-000380 + Windows Server 2022 Remote Desktop Services must be configured with the client connection encryption set to High Level. + <VulnDiscussion>Remote connections must be encrypted to prevent interception of data or sensitive information. Selecting "High Level" will ensure encryption of Remote Desktop Services sessions in both directions. + +Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000068 + CCI-001453 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Remote Desktop Services >> Remote Desktop Session Host >> Security >> Set client connection encryption level to "Enabled" with "High Level" selected. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ + +Value Name: MinEncryptionLevel + +Type: REG_DWORD +Value: 0x00000003 (3) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000390 + Windows Server 2022 must prevent attachments from being downloaded from RSS feeds. + <VulnDiscussion>Attachments from RSS feeds may not be secure. This setting will prevent attachments from being downloaded from RSS feeds.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> RSS Feeds >> Prevent downloading of enclosures to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ + +Value Name: DisableEnclosureDownload + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-CC-000400 + Windows Server 2022 must disable Basic authentication for RSS feeds over HTTP. + <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. + +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> RSS Feeds >> Turn on Basic feed authentication over HTTP to "Not Configured" or "Disabled". + + + + The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ + +Value Name: AllowBasicAuthInClear + +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-CC-000410 + Windows Server 2022 must prevent Indexing of encrypted files. + <VulnDiscussion>Indexing of encrypted files may expose sensitive data. This setting prevents encrypted files from being indexed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Search >> Allow indexing of encrypted files to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Windows Search\ + +Value Name: AllowIndexingEncryptedStoresOrItems + +Value Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000362-GPOS-00149 + <GroupDescription></GroupDescription> + + WN22-CC-000420 + Windows Server 2022 must prevent users from changing installation options. + <VulnDiscussion>Installation options for applications are typically controlled by administrators. This setting prevents users from changing installation options that may bypass security features.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001812 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> Allow user control over installs to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ + +Value Name: EnableUserControl + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000362-GPOS-00149 + <GroupDescription></GroupDescription> + + WN22-CC-000430 + Windows Server 2022 must disable the Windows Installer Always install with elevated privileges option. + <VulnDiscussion>Standard user accounts must not be granted elevated privileges. Enabling Windows Installer to elevate privileges when installing applications can allow malicious persons and applications to gain full control of a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001812 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> Always install with elevated privileges to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ + +Value Name: AlwaysInstallElevated + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-CC-000440 + Windows Server 2022 users must be notified if a web-based program attempts to install software. + <VulnDiscussion>Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. + +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> Prevent Internet Explorer security prompt for Windows Installer scripts to "Not Configured" or "Disabled". + + + + The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ + +Value Name: SafeForScripting + +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) + + + + + SRG-OS-000480-GPOS-00229 + <GroupDescription></GroupDescription> + + WN22-CC-000450 + Windows Server 2022 must disable automatically signing in the last interactive user after a system-initiated restart. + <VulnDiscussion>Windows can be configured to automatically sign the user back in after a Windows Update restart. Some protections are in place to help ensure this is done in a secure fashion; however, disabling this will prevent the caching of credentials for this purpose and also ensure the user is aware of the restart.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Logon Options >> Sign-in and lock last interactive user automatically after a restart to "Disabled". + + + + Verify the registry value below. If it does not exist or is not configured as specified, this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: DisableAutomaticRestartSignOn + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000042-GPOS-00020 + <GroupDescription></GroupDescription> + + WN22-CC-000460 + Windows Server 2022 PowerShell script block logging must be enabled. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Enabling PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. This can provide additional detail when malware has run on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000135 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> Turn on PowerShell Script Block Logging to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ + +Value Name: EnableScriptBlockLogging + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000125-GPOS-00065 + <GroupDescription></GroupDescription> + + WN22-CC-000470 + Windows Server 2022 Windows Remote Management (WinRM) client must not use Basic authentication. + <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000877 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Client >> Allow Basic authentication to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ + +Value Name: AllowBasic + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000393-GPOS-00173 + <GroupDescription></GroupDescription> + + WN22-CC-000480 + Windows Server 2022 Windows Remote Management (WinRM) client must not allow unencrypted traffic. + <VulnDiscussion>Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this. + +Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002890 + CCI-003123 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Client >> Allow unencrypted traffic to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ + +Value Name: AllowUnencryptedTraffic + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000125-GPOS-00065 + <GroupDescription></GroupDescription> + + WN22-CC-000490 + Windows Server 2022 Windows Remote Management (WinRM) client must not use Digest authentication. + <VulnDiscussion>Digest authentication is not as strong as other options and may be subject to man-in-the-middle attacks. Disallowing Digest authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000877 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Client >> Disallow Digest authentication to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ + +Value Name: AllowDigest + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000125-GPOS-00065 + <GroupDescription></GroupDescription> + + WN22-CC-000500 + Windows Server 2022 Windows Remote Management (WinRM) service must not use Basic authentication. + <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000877 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Service >> Allow Basic authentication to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ + +Value Name: AllowBasic + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000393-GPOS-00173 + <GroupDescription></GroupDescription> + + WN22-CC-000510 + Windows Server 2022 Windows Remote Management (WinRM) service must not allow unencrypted traffic. + <VulnDiscussion>Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this. + +Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002890 + CCI-003123 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Service >> Allow unencrypted traffic to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ + +Value Name: AllowUnencryptedTraffic + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000373-GPOS-00156 + <GroupDescription></GroupDescription> + + WN22-CC-000520 + Windows Server 2022 Windows Remote Management (WinRM) service must not store RunAs credentials. + <VulnDiscussion>Storage of administrative credentials could allow unauthorized access. Disallowing the storage of RunAs credentials for Windows Remote Management will prevent them from being used with plug-ins. + +Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002038 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Service >> Disallow WinRM from storing RunAs credentials to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ + +Value Name: DisableRunAs + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000041-GPOS-00019 + <GroupDescription></GroupDescription> + + WN22-CC-000530 + Windows Server 2022 must have PowerShell Transcription enabled. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. + +Enabling PowerShell Transcription will record detailed information from the processing of PowerShell commands and scripts. This can provide additional detail when malware has run on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000134 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> "Turn on PowerShell Transcription" to "Enabled". + +Specify the Transcript output directory to point to a Central Log Server or another secure location to prevent user access. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\PowerShell\Transcription\ + +Value Name: EnableTranscripting + +Value Type: REG_DWORD +Value: 1 + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-MS-000010 + Windows Server 2022 must only allow administrators responsible for the member server or standalone or nondomain-joined system to have Administrator rights on the system. + <VulnDiscussion>An account that does not have Administrator duties must not have Administrator rights. Such rights would allow the account to bypass or modify required security restrictions on that machine and make it vulnerable to attack. + +System administrators must log on to systems using only accounts with the minimum level of authority necessary. + +For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group (see V-243468 in the Active Directory Domain STIG). Restricting highly privileged accounts from the local Administrators group helps mitigate the risk of privilege escalation resulting from credential theft attacks. + +Standard user accounts must not be members of the built-in Administrators group.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the local "Administrators" group to include only administrator groups or accounts responsible for administration of the system. + +For domain-joined member servers, replace the Domain Admins group with a domain member server administrator group. + +Remove any standard user accounts. + + + + This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers. + +Open "Computer Management". + +Navigate to "Groups" under "Local Users and Groups". + +Review the local "Administrators" group. + +Only administrator groups or accounts responsible for administration of the system may be members of the group. + +For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group. + +Standard user accounts must not be members of the local Administrator group. + +If accounts that do not have responsibility for administration of the system are members of the local Administrators group, this is a finding. + +If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding. + + + + + SRG-OS-000134-GPOS-00068 + <GroupDescription></GroupDescription> + + WN22-MS-000020 + Windows Server 2022 local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain-joined member servers. + <VulnDiscussion>A compromised local administrator account can provide means for an attacker to move laterally between domain systems. + +With User Account Control enabled, filtering the privileged token for local administrator accounts will prevent the elevated privileges of these accounts from being used over the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001084 + Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> Apply UAC restrictions to local accounts on network logons to "Enabled". + +This policy setting requires the installation of the SecGuide custom templates included with the STIG package. "SecGuide.admx" and " SecGuide.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively. + + + + This applies to member servers. For domain controllers and standalone or nondomain-joined systems, this is NA. + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + +Value Name: LocalAccountTokenFilterPolicy + +Type: REG_DWORD +Value: 0x00000000 (0) + +This setting may cause issues with some network scanning tools if local administrative accounts are used remotely. Scans must use domain accounts where possible. If a local administrative account must be used, temporarily enabling the privileged token by configuring the registry value to "1" may be required. + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN22-MS-000030 + Windows Server 2022 local users on domain-joined member servers must not be enumerated. + <VulnDiscussion>The username is one part of logon credentials that could be used to gain access to a system. Preventing the enumeration of users limits this information to authorized personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Logon >> Enumerate local users on domain-joined computers to "Disabled". + + + + This applies to member servers. For domain controllers and standalone or nondomain-joined systems, this is NA. + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ + +Value Name: EnumerateLocalUsers + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000379-GPOS-00164 + <GroupDescription></GroupDescription> + + WN22-MS-000040 + Windows Server 2022 must restrict unauthenticated Remote Procedure Call (RPC) clients from connecting to the RPC server on domain-joined member servers and standalone or nondomain-joined systems. + <VulnDiscussion>Unauthenticated RPC clients may allow anonymous access to sensitive information. Configuring RPC to restrict unauthenticated RPC clients from connecting to the RPC server will prevent anonymous connections.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001967 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Remote Procedure Call >> Restrict Unauthenticated RPC clients to "Enabled" with "Authenticated" selected. + + + + This applies to member servers and standalone or nondomain-joined systems, it is NA for domain controllers. + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Rpc\ + +Value Name: RestrictRemoteClients + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-MS-000050 + Windows Server 2022 must limit the caching of logon credentials to four or less on domain-joined member servers. + <VulnDiscussion>The default Windows configuration caches the last logon credentials for users who log on interactively to a system. This feature is provided for system availability reasons, such as the user's machine being disconnected from the network or domain controllers being unavailable. Even though the credential cache is well protected, if a system is attacked, an unauthorized individual may isolate the password to a domain user account using a password-cracking program and gain access to the domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Interactive Logon: Number of previous logons to cache (in case Domain Controller is not available) to "4" logons or less. + + + + This applies to member servers. For domain controllers and standalone or nondomain-joined systems, this is NA. + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ + +Value Name: CachedLogonsCount + +Value Type: REG_SZ +Value: 4 (or less) + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-MS-000060 + Windows Server 2022 must restrict remote calls to the Security Account Manager (SAM) to Administrators on domain-joined member servers and standalone or nondomain-joined systems. + <VulnDiscussion>The Windows SAM stores users' passwords. Restricting Remote Procedure Call (RPC) connections to the SAM to Administrators helps protect those credentials.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Navigate to the policy Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network access: Restrict clients allowed to make remote calls to SAM. + +Select "Edit Security" to configure the "Security descriptor:". + +Add "Administrators" in "Group or user names:" if it is not already listed (this is the default). + +Select "Administrators" in "Group or user names:". + +Select "Allow" for "Remote Access" in "Permissions for "Administrators". + +Click "OK". + +The "Security descriptor:" must be populated with "O:BAG:BAD:(A;;RC;;;BA) for the policy to be enforced. + + + + This applies to member servers and standalone or nondomain-joined systems; it is NA for domain controllers. + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ + +Value Name: RestrictRemoteSAM + +Value Type: REG_SZ +Value: O:BAG:BAD:(A;;RC;;;BA) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-MS-000140 + Windows Server 2022 must be running Credential Guard on domain-joined member servers. + <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. This authentication information, which was stored in the Local Security Authority (LSA) in previous versions of Windows, is isolated from the rest of operating system and can only be accessed by privileged system software.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> Turn On Virtualization Based Security to "Enabled" with "Enabled with UEFI lock" selected for "Credential Guard Configuration". + +A Microsoft article on Credential Guard system requirement can be found at the following link: + +https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements + +Severity Override Guidance: The AO can allow the severity override if they have reviewed the overall protection provided to the affected servers that are not capable of complying with the Credential Guard requirement. Items that must be reviewed/considered for compliance or mitigation for non-Credential Guard compliance are: + +The use of Microsoft Local Administrator Password Solution (LAPS) or similar products to control different local administrative passwords for all affected servers. This is to include a strict password change requirement (60 days or less). +.... +Strict separation of roles and duties. Server administrator credentials cannot be used on Windows 10 desktop to administer it. Documentation of all exceptions must be supplied. +.... +Use of a Privileged Access Workstation (PAW) and adherence to the Clean Source principle for administering affected servers. +.... +Boundary Protection that is currently in place to protect from vulnerabilities in the network/servers. +.... +Windows Defender rule block credential stealing from LSASS.exe is applied. This rule can only be applied if Windows Defender is in use. +.... +The overall number of vulnerabilities that are unmitigated on the network/servers. + + + + For domain controllers and standalone or nondomain-joined systems, this is NA. + +Open "PowerShell" with elevated privileges (run as administrator). + +Enter the following: + +"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" + +If "SecurityServicesRunning" does not include a value of "1" (e.g., "{1, 2}"), this is a finding. + +Alternately: + +Run "System Information". + +Under "System Summary", verify the following: + +If "Device Guard Security Services Running" does not list "Credential Guard", this is a finding. + +The policy settings referenced in the Fix section will configure the following registry value. However, due to hardware requirements, the registry value alone does not ensure proper function. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ + +Value Name: LsaCfgFlags +Value Type: REG_DWORD +Value: 0x00000001 (1) (Enabled with UEFI lock) + +A Microsoft article on Credential Guard system requirement can be found at the following link: + +https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements + + + + + SRG-OS-000066-GPOS-00034 + <GroupDescription></GroupDescription> + + WN22-PK-000010 + Windows Server 2022 must have the DoD Root Certificate Authority (CA) certificates installed in the Trusted Root Store. + <VulnDiscussion>To ensure secure DoD websites and DoD-signed code are properly validated, the system must trust the DoD Root CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. + +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000185 + CCI-002470 + Install the DoD Root CA certificates: + +DoD Root CA 3 +DoD Root CA 4 +DoD Root CA 5 + +The InstallRoot tool is available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. + + + + The certificates and thumbprints referenced below apply to unclassified systems; see PKE documentation for other networks. + +Open "Windows PowerShell" as an administrator. + +Execute the following command: + +Get-ChildItem -Path Cert:Localmachine\root | Where Subject -Like "*DoD*" | FL Subject, Thumbprint, NotAfter + +If the following certificate "Subject" and "Thumbprint" information is not displayed, this is a finding. + +Subject: CN=DoD Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 +NotAfter: 12/5/2029 + +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB +NotAfter: 12/30/2029 + +Subject: CN=DoD Root CA 4, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 +NotAfter: 7/25/2032 + +Subject: CN=DoD Root CA 5, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B +NotAfter: 6/14/2041 + +Alternately, use the Certificates MMC snap-in: + +Run "MMC". + +Select "File", "Add/Remove Snap-in". + +Select "Certificates" and click "Add". + +Select "Computer account" and click "Next". + +Select "Local computer: (the computer this console is running on)" and click "Finish". + +Click "OK". + +Expand "Certificates" and navigate to "Trusted Root Certification Authorities >> Certificates". + +For each of the DoD Root CA certificates noted below: + +Right-click on the certificate and select "Open". + +Select the "Details" tab. + +Scroll to the bottom and select "Thumbprint". + +If the DoD Root CA certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding. + +DoD Root CA 3 +Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB +Valid to: Sunday, December 30, 2029 + +DoD Root CA 4 +Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 +Valid to: Sunday, July 25, 2032 + +DoD Root CA 5 +Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B +Valid to: Friday, June 14, 2041 + + + + + SRG-OS-000066-GPOS-00034 + <GroupDescription></GroupDescription> + + WN22-PK-000020 + Windows Server 2022 must have the DoD Interoperability Root Certificate Authority (CA) cross-certificates installed in the Untrusted Certificates Store on unclassified systems. + <VulnDiscussion>To ensure users do not experience denial of service when performing certificate-based authentication to DoD websites due to the system chaining to a root other than DoD Root CAs, the DoD Interoperability Root CA cross-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems. + +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000185 + CCI-002470 + Install the DoD Interoperability Root CA cross-certificates on unclassified systems. + +Issued To - Issued By - Thumbprint + +DoD Root CA 3- DoD Interoperability Root CA 2 - 49CBE933151872E17C8EAE7F0ABA97FB610F6477 + +DoD Root CA 3 - DoD Interoperability Root CA 2 - AC06108CA348CC03B53795C64BF84403C1DBD341 + +Administrators must run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user. + +The FBCA Cross-Certificate Remover Tool and User Guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. + + + + This is applicable to unclassified systems. It is NA for others. + +Open "PowerShell" as an administrator. + +Execute the following command: + +Get-ChildItem -Path Cert:Localmachine\disallowed | Where {$_.Issuer -Like "*DoD Interoperability*" -and $_.Subject -Like "*DoD*"} | FL Subject, Issuer, Thumbprint, NotAfter + +If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. + +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Issuer: CN=DoD Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: AC06108CA348CC03B53795C64BF84403C1DBD341 +NotAfter: 1/22/2022 10:22:56 AM + +Subject: CN=DoD Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Issuer: CN=DoD Interoperability Root CA 1, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: A8C27332CCB4CA49554CE55D34062A7DD2850C02 +NotAfter: 8/26/2022 9:25:51 AM + +Alternately, use the Certificates MMC snap-in: + +Run "MMC". + +Select "File", "Add/Remove Snap-in". + +Select "Certificates" and click "Add". + +Select "Computer account" and click "Next". + +Select "Local computer: (the computer this console is running on)" and click "Finish". + +Click "OK". + +Expand "Certificates" and navigate to Untrusted Certificates >> Certificates. + +For each certificate with "DoD Root CA..." under "Issued To" and "DoD Interoperability Root CA..." under "Issued By": + +Right-click on the certificate and select "Open". + +Select the "Details" tab. + +Scroll to the bottom and select "Thumbprint". + +If the certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding. + +Issued To: DoD Root CA 3 +Issued By: DoD Interoperability Root CA 2 +Thumbprint: 49CBE933151872E17C8EAE7F0ABA97FB610F6477 +Valid to: Wednesday, November 16, 2024 + +Issued To: DoD Root CA 3 +Issued By: DoD Interoperability Root CA 2 +Thumbprint: AC06108CA348CC03B53795C64BF84403C1DBD341 +Valid to: Saturday, January 22, 2022 + + + + + SRG-OS-000066-GPOS-00034 + <GroupDescription></GroupDescription> + + WN22-PK-000030 + Windows Server 2022 must have the US DoD CCEB Interoperability Root CA cross-certificates in the Untrusted Certificates Store on unclassified systems. + <VulnDiscussion>To ensure users do not experience denial of service when performing certificate-based authentication to DoD websites due to the system chaining to a root other than DoD Root CAs, the US DoD CCEB Interoperability Root CA cross-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems. + +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000185 + CCI-002470 + Install the US DoD CCEB Interoperability Root CA cross-certificate on unclassified systems. + +Issued To - Issued By - Thumbprint + +DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 + +DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - 929BF3196896994C0A201DF4A5B71F603FEFBF2E + +Administrators must run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user. + +The FBCA Cross-Certificate Remover Tool and User Guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. + + + + This is applicable to unclassified systems. It is NA for others. + +Open "PowerShell" as an administrator. + +Execute the following command: + +Get-ChildItem -Path Cert:Localmachine\disallowed | Where Issuer -Like "*CCEB Interoperability*" | FL Subject, Issuer, Thumbprint, NotAfter + +If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. + +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 +NotAfter: 8/26/2022 9:07:50 AM + +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E +NotAfter: 9/27/2022 + +Alternately, use the Certificates MMC snap-in: + +Run "MMC". + +Select "File", "Add/Remove Snap-in". + +Select "Certificates" and click "Add". + +Select "Computer account" and click "Next". + +Select "Local computer: (the computer this console is running on)" and click "Finish". + +Click "OK". + +Expand "Certificates" and navigate to Untrusted Certificates >> Certificates. + +For each certificate with "US DoD CCEB Interoperability Root CA ..." under "Issued By": + +Right-click on the certificate and select "Open". + +Select the "Details" tab. + +Scroll to the bottom and select "Thumbprint". + +If the certificate below is not listed or the value for the "Thumbprint" field is not as noted, this is a finding. + +Issued To: DoD Root CA 3 +Issued By: US DoD CCEB Interoperability Root CA 2 +Thumbprint: AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 +Valid to: Friday, August 26, 2022 + +Issued To: DoD Root CA 3 +Issued By: US DoD CCEB Interoperability Root CA 2 +Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E +Valid: Friday, September 27, 2022 + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000020 + Windows Server 2022 must prevent local accounts with blank passwords from being used from the network. + <VulnDiscussion>An account without a password can allow unauthorized access to a system as only the username would be required. Password policies must prevent accounts with blank passwords from existing on a system. However, if a local account with a blank password does exist, enabling this setting will prevent network access, limiting the account to local console logon only.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Accounts: Limit local account use of blank passwords to console logon only to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ + +Value Name: LimitBlankPasswordUse + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000062-GPOS-00031 + <GroupDescription></GroupDescription> + + WN22-SO-000050 + Windows Server 2022 must force audit policy subcategory settings to override audit policy category settings. + <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. This setting allows administrators to enable more precise auditing capabilities.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000169 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ + +Value Name: SCENoApplyLegacyAuditPolicy + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN22-SO-000060 + Windows Server 2022 setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled. + <VulnDiscussion>Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but not all information is encrypted. If this policy is enabled, outgoing secure channel traffic will be encrypted and signed. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002418 + CCI-002421 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain member: Digitally encrypt or sign secure channel data (always) to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ + +Value Name: RequireSignOrSeal + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN22-SO-000070 + Windows Server 2022 setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to Enabled. + <VulnDiscussion>Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but not all information is encrypted. If this policy is enabled, outgoing secure channel traffic will be encrypted. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002418 + CCI-002421 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain member: Digitally encrypt secure channel data (when possible) to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ + +Value Name: SealSecureChannel + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN22-SO-000080 + Windows Server 2022 setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled. + <VulnDiscussion>Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but the channel is not integrity checked. If this policy is enabled, outgoing secure channel traffic will be signed. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002418 + CCI-002421 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain member: Digitally sign secure channel data (when possible) to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ + +Value Name: SignSecureChannel + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000379-GPOS-00164 + <GroupDescription></GroupDescription> + + WN22-SO-000090 + Windows Server 2022 computer account password must not be prevented from being reset. + <VulnDiscussion>Computer account passwords are changed automatically on a regular basis. Disabling automatic password changes can make the system more vulnerable to malicious access. Frequent password changes can be a significant safeguard for the system. A new password for the computer account will be generated every 30 days.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001967 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain member: Disable machine account password changes to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ + +Value Name: DisablePasswordChange + +Value Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000100 + Windows Server 2022 maximum age for machine account passwords must be configured to 30 days or less. + <VulnDiscussion>Computer account passwords are changed automatically on a regular basis. This setting controls the maximum password age that a machine account may have. This must be set to no more than 30 days, ensuring the machine changes its password monthly.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + This is the default configuration for this setting (30 days). + +Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain member: Maximum machine account password age to "30" or less (excluding "0", which is unacceptable). + + + + This is the default configuration for this setting (30 days). + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ + +Value Name: MaximumPasswordAge + +Value Type: REG_DWORD +Value: 0x0000001e (30) (or less, but not 0) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN22-SO-000110 + Windows Server 2022 must be configured to require a strong session key. + <VulnDiscussion>A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002418 + CCI-002421 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain member: Require strong (Windows 2000 or Later) session key to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ + +Value Name: RequireStrongKey + +Value Type: REG_DWORD +Value: 0x00000001 (1) + +This setting may prevent a system from being joined to a domain if not configured consistently between systems. + + + + + SRG-OS-000028-GPOS-00009 + <GroupDescription></GroupDescription> + + WN22-SO-000120 + Windows Server 2022 machine inactivity limit must be set to 15 minutes or less, locking the system with the screen saver. + <VulnDiscussion>Unattended systems are susceptible to unauthorized use and must be locked when unattended. The screen saver must be set at a maximum of 15 minutes and be password protected. This protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer. + +Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000056 + CCI-000057 + CCI-000060 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Interactive logon: Machine inactivity limit to "900" seconds or less, excluding "0" which is effectively disabled. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: InactivityTimeoutSecs + +Value Type: REG_DWORD +Value: 0x00000384 (900) (or less, excluding "0" which is effectively disabled) + + + + + SRG-OS-000023-GPOS-00006 + <GroupDescription></GroupDescription> + + WN22-SO-000130 + Windows Server 2022 required legal notice must be configured to display before console logon. + <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. + +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000048 + CCI-000050 + CCI-001384 + CCI-001385 + CCI-001386 + CCI-001387 + CCI-001388 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Interactive Logon: Message text for users attempting to log on to the following: + +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. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: LegalNoticeText + +Value Type: REG_SZ +Value: See message text below + +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. + + + + + SRG-OS-000023-GPOS-00006 + <GroupDescription></GroupDescription> + + WN22-SO-000140 + Windows Server 2022 title for legal banner dialog box must be configured with the appropriate text. + <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. + +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000048 + CCI-001384 + CCI-001385 + CCI-001386 + CCI-001387 + CCI-001388 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Interactive Logon: Message title for users attempting to log on to "DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. + +If an organization-defined title is used, it can in no case contravene or modify the language of the message text required in WN22-SO-000150. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: LegalNoticeCaption + +Value Type: REG_SZ +Value: See message title options below + +"DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. + +If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN22-SO-000150. + +Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000150 + Windows Server 2022 Smart Card removal option must be configured to Force Logoff or Lock Workstation. + <VulnDiscussion>Unattended systems are susceptible to unauthorized use and must be locked. Configuring a system to lock when a smart card is removed will ensure the system is inaccessible when unattended.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Interactive logon: Smart card removal behavior to "Lock Workstation" or "Force Logoff". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ + +Value Name: scremoveoption + +Value Type: REG_SZ +Value: 1 (Lock Workstation) or 2 (Force Logoff) + +If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the Information System Security Officer (ISSO). + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN22-SO-000160 + Windows Server 2022 setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled. + <VulnDiscussion>The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB client will only communicate with an SMB server that performs SMB packet signing. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002418 + CCI-002421 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Microsoft network client: Digitally sign communications (always) to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ + +Value Name: RequireSecuritySignature + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN22-SO-000170 + Windows Server 2022 setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled. + <VulnDiscussion>The server message block (SMB) protocol provides the basis for many network operations. If this policy is enabled, the SMB client will request packet signing when communicating with an SMB server that is enabled or required to perform SMB packet signing. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002418 + CCI-002421 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Microsoft network client: Digitally sign communications (if server agrees) to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ + +Value Name: EnableSecuritySignature + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000074-GPOS-00042 + <GroupDescription></GroupDescription> + + WN22-SO-000180 + Windows Server 2022 unencrypted passwords must not be sent to third-party Server Message Block (SMB) servers. + <VulnDiscussion>Some non-Microsoft SMB servers only support unencrypted (plain-text) password authentication. Sending plain-text passwords across the network when authenticating to an SMB server reduces the overall security of the environment. Check with the vendor of the SMB server to determine if there is a way to support encrypted password authentication.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000197 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Microsoft Network Client: Send unencrypted password to third-party SMB servers to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ + +Value Name: EnablePlainTextPassword + +Value Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN22-SO-000190 + Windows Server 2022 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled. + <VulnDiscussion>The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will only communicate with an SMB client that performs SMB packet signing. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002418 + CCI-002421 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Microsoft network server: Digitally sign communications (always) to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ + +Value Name: RequireSecuritySignature + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN22-SO-000200 + Windows Server 2022 setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled. + <VulnDiscussion>The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will negotiate SMB packet signing as requested by the client. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002418 + CCI-002421 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Microsoft network server: Digitally sign communications (if client agrees) to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ + +Value Name: EnableSecuritySignature + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000210 + Windows Server 2022 must not allow anonymous SID/Name translation. + <VulnDiscussion>Allowing anonymous SID/Name translation can provide sensitive information for accessing a system. Only authorized users must be able to perform such translations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network access: Allow anonymous SID/Name translation to "Disabled". + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. + +If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000220 + Windows Server 2022 must not allow anonymous enumeration of Security Account Manager (SAM) accounts. + <VulnDiscussion>Anonymous enumeration of SAM accounts allows anonymous logon users (null session connections) to list all accounts names, thus providing a list of potential points to attack the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network access: Do not allow anonymous enumeration of SAM accounts to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ + +Value Name: RestrictAnonymousSAM + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000138-GPOS-00069 + <GroupDescription></GroupDescription> + + WN22-SO-000230 + Windows Server 2022 must not allow anonymous enumeration of shares. + <VulnDiscussion>Allowing anonymous logon users (null session connections) to list all account names and enumerate all shared resources can provide a map of potential points to attack the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001090 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network access: Do not allow anonymous enumeration of SAM accounts and shares to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ + +Value Name: RestrictAnonymous + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000240 + Windows Server 2022 must be configured to prevent anonymous users from having the same permissions as the Everyone group. + <VulnDiscussion>Access by anonymous users must be restricted. If this setting is enabled, anonymous users have the same rights and permissions as the built-in Everyone group. Anonymous users must not have these permissions or rights.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network access: Let Everyone permissions apply to anonymous users to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ + +Value Name: EveryoneIncludesAnonymous + +Value Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000138-GPOS-00069 + <GroupDescription></GroupDescription> + + WN22-SO-000250 + Windows Server 2022 must restrict anonymous access to Named Pipes and Shares. + <VulnDiscussion>Allowing anonymous access to named pipes or shares provides the potential for unauthorized system access. This setting restricts access to those defined in "Network access: Named Pipes that can be accessed anonymously" and "Network access: Shares that can be accessed anonymously", both of which must be blank under other requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001090 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network access: Restrict anonymous access to Named Pipes and Shares to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ + +Value Name: RestrictNullSessAccess + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000260 + Windows Server 2022 services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity instead of authenticating anonymously. + <VulnDiscussion>Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus using the computer identity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Allow Local System to use computer identity for NTLM to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\ + +Value Name: UseMachineId + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000270 + Windows Server 2022 must prevent NTLM from falling back to a Null session. + <VulnDiscussion>NTLM sessions that are allowed to fall back to Null (unauthenticated) sessions may gain unauthorized access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Allow LocalSystem NULL session fallback to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\MSV1_0\ + +Value Name: allownullsessionfallback + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000280 + Windows Server 2022 must prevent PKU2U authentication using online identities. + <VulnDiscussion>PKU2U is a peer-to-peer authentication protocol. This setting prevents online identities from authenticating to domain-joined systems. Authentication will be centrally managed with Windows user accounts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Allow PKU2U authentication requests to this computer to use online identities to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\pku2u\ + +Value Name: AllowOnlineID + +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000120-GPOS-00061 + <GroupDescription></GroupDescription> + + WN22-SO-000290 + Windows Server 2022 Kerberos encryption types must be configured to prevent the use of DES and RC4 encryption suites. + <VulnDiscussion>Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. + +Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000803 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Configure encryption types allowed for Kerberos to "Enabled" with only the following selected: + +AES128_HMAC_SHA1 +AES256_HMAC_SHA1 +Future encryption types + +Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\ + +Value Name: SupportedEncryptionTypes + +Value Type: REG_DWORD +Value: 0x7ffffff8 (2147483640) + + + + + SRG-OS-000073-GPOS-00041 + <GroupDescription></GroupDescription> + + WN22-SO-000300 + Windows Server 2022 must be configured to prevent the storage of the LAN Manager hash of passwords. + <VulnDiscussion>The LAN Manager hash uses a weak encryption algorithm and there are several tools available that use this hash to retrieve account passwords. This setting controls whether a LAN Manager hash of the password is stored in the SAM the next time the password is changed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000196 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Do not store LAN Manager hash value on next password change to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ + +Value Name: NoLMHash + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000310 + Windows Server 2022 LAN Manager authentication level must be configured to send NTLMv2 response only and to refuse LM and NTLM. + <VulnDiscussion>The Kerberos v5 authentication protocol is the default for authentication of users who are logging on to domain accounts. NTLM, which is less secure, is retained in later Windows versions for compatibility with clients and servers that are running earlier versions of Windows or applications that still use it. It is also used to authenticate logons to standalone or nondomain-joined computers that are running later versions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: LAN Manager authentication level to "Send NTLMv2 response only. Refuse LM & NTLM". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ + +Value Name: LmCompatibilityLevel + +Value Type: REG_DWORD +Value: 0x00000005 (5) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000320 + Windows Server 2022 must be configured to at least negotiate signing for LDAP client signing. + <VulnDiscussion>This setting controls the signing requirements for LDAP clients. This must be set to "Negotiate signing" or "Require signing", depending on the environment and type of LDAP server in use.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: LDAP client signing requirements to "Negotiate signing" at a minimum. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LDAP\ + +Value Name: LDAPClientIntegrity + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000330 + Windows Server 2022 session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption. + <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (RPC) sessions. All of the options must be enabled to ensure the maximum security level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Minimum session security for NTLM SSP based (including secure RPC) clients to "Require NTLMv2 session security" and "Require 128-bit encryption" (all options selected). + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ + +Value Name: NTLMMinClientSec + +Value Type: REG_DWORD +Value: 0x20080000 (537395200) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000340 + Windows Server 2022 session security for NTLM SSP-based servers must be configured to require NTLMv2 session security and 128-bit encryption. + <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (RPC) sessions. All of the options must be enabled to ensure the maximum security level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Minimum session security for NTLM SSP based (including secure RPC) servers to "Require NTLMv2 session security" and "Require 128-bit encryption" (all options selected). + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ + +Value Name: NTLMMinServerSec + +Value Type: REG_DWORD +Value: 0x20080000 (537395200) + + + + + SRG-OS-000067-GPOS-00035 + <GroupDescription></GroupDescription> + + WN22-SO-000350 + Windows Server 2022 users must be required to enter a password to access private keys stored on the computer. + <VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. + +The cornerstone of the PKI is the private key used to encrypt or digitally sign information. + +If the private key is stolen, this will lead to the compromise of the authentication and nonrepudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. + +Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000186 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> System cryptography: Force strong key protection for user keys stored on the computer to "User must enter a password each time they use a key". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Cryptography\ + +Value Name: ForceKeyProtection + +Type: REG_DWORD +Value: 0x00000002 (2) + + + + + SRG-OS-000478-GPOS-00223 + <GroupDescription></GroupDescription> + + WN22-SO-000360 + Windows Server 2022 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing. + <VulnDiscussion>This setting ensures the system uses algorithms that are FIPS-compliant for encryption, hashing, and signing. FIPS-compliant algorithms meet specific standards established by the U.S. Government and must be the algorithms used for all OS encryption functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002450 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\ + +Value Name: Enabled + +Value Type: REG_DWORD +Value: 0x00000001 (1) + +Clients with this setting enabled will not be able to communicate via digitally encrypted or signed protocols with servers that do not support these algorithms. Both the browser and web server must be configured to use TLS; otherwise the browser will not be able to connect to a secure site. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000370 + Windows Server 2022 default permissions of global system objects must be strengthened. + <VulnDiscussion>Windows systems maintain a global list of shared system resources such as DOS device names, mutexes, and semaphores. Each type of object is created with a default Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing nonadministrative users to read shared objects but not to modify shared objects they did not create.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> System objects: Strengthen default permissions of internal system objects (e.g., Symbolic Links) to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Session Manager\ + +Value Name: ProtectionMode + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000373-GPOS-00156 + <GroupDescription></GroupDescription> + + WN22-SO-000380 + Windows Server 2022 User Account Control (UAC) approval mode for the built-in Administrator must be enabled. + <VulnDiscussion>UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures the built-in Administrator account so that it runs in Admin Approval Mode. + +Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002038 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Admin Approval Mode for the Built-in Administrator account to "Enabled". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience). + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: FilterAdministratorToken + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000134-GPOS-00068 + <GroupDescription></GroupDescription> + + WN22-SO-000390 + Windows Server 2022 UIAccess applications must not be allowed to prompt for elevation without using the secure desktop. + <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001084 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop to "Disabled". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience). + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: EnableUIADesktopToggle + +Value Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000134-GPOS-00068 + <GroupDescription></GroupDescription> + + WN22-SO-000400 + Windows Server 2022 User Account Control (UAC) must, at a minimum, prompt administrators for consent on the secure desktop. + <VulnDiscussion>UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures the elevation requirements for logged-on administrators to complete a task that requires raised privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001084 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode to "Prompt for consent on the secure desktop". + +The more secure option for this setting, "Prompt for credentials on the secure desktop", would also be acceptable. + + + + UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2022 versus Server with Desktop Experience). + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: ConsentPromptBehaviorAdmin + +Value Type: REG_DWORD +Value: 0x00000002 (2) (Prompt for consent on the secure desktop) +0x00000001 (1) (Prompt for credentials on the secure desktop) + + + + + SRG-OS-000373-GPOS-00156 + <GroupDescription></GroupDescription> + + WN22-SO-000410 + Windows Server 2022 User Account Control (UAC) must automatically deny standard user requests for elevation. + <VulnDiscussion>UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. + +Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002038 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Behavior of the elevation prompt for standard users to "Automatically deny elevation requests". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience). + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: ConsentPromptBehaviorUser + +Value Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000134-GPOS-00068 + <GroupDescription></GroupDescription> + + WN22-SO-000420 + Windows Server 2022 User Account Control (UAC) must be configured to detect application installations and prompt for elevation. + <VulnDiscussion>UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting requires Windows to respond to application installation requests by prompting for credentials.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001084 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Detect application installations and prompt for elevation to "Enabled". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience). + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: EnableInstallerDetection + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000134-GPOS-00068 + <GroupDescription></GroupDescription> + + WN22-SO-000430 + Windows Server 2022 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations. + <VulnDiscussion>UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures Windows to only allow applications installed in a secure location on the file system, such as the Program Files or the Windows\System32 folders, to run with elevated privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001084 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Only elevate UIAccess applications that are installed in secure locations to "Enabled". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience). + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: EnableSecureUIAPaths + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000373-GPOS-00156 + <GroupDescription></GroupDescription> + + WN22-SO-000440 + Windows Server 2022 User Account Control (UAC) must run all administrators in Admin Approval Mode, enabling UAC. + <VulnDiscussion>UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting enables UAC. + +Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002038 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Run all administrators in Admin Approval Mode to "Enabled". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience). + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: EnableLUA + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000134-GPOS-00068 + <GroupDescription></GroupDescription> + + WN22-SO-000450 + Windows Server 2022 User Account Control (UAC) must virtualize file and registry write failures to per-user locations. + <VulnDiscussion>UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures non-UAC-compliant applications to run in virtualized file and registry entries in per-user locations, allowing them to run.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-001084 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Virtualize file and registry write failures to per-user locations to "Enabled". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience). + +If the following registry value does not exist or is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: EnableVirtualization + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-UC-000010 + Windows Server 2022 must preserve zone information when saving attachments. + <VulnDiscussion>Attachments from outside sources may contain malicious code. Preserving zone of origin (internet, intranet, local, restricted) information on file attachments allows Windows to determine risk.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + The default behavior is for Windows to mark file attachments with their zone information. + +If this needs to be corrected, configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> Attachment Manager >> Do not preserve zone information in file attachments to "Not Configured" or "Disabled". + + + + The default behavior is for Windows to mark file attachments with their zone information. + +If the registry Value Name below does not exist, this is not a finding. + +If it exists and is configured with a value of "2", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_CURRENT_USER +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments\ + +Value Name: SaveZoneInformation + +Value Type: REG_DWORD +Value: 0x00000002 (2) (or if the Value Name does not exist) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-00-000450 + Windows Server 2022 must have orphaned security identifiers (SIDs) removed from user rights. + <VulnDiscussion>Accounts or groups given rights on a system may show up as unresolved SIDs for various reasons including deletion of the accounts or groups. If the account or group objects are reanimated, there is a potential they may still have rights no longer intended. Valid domain accounts or groups may also show up as unresolved SIDs if a connection to the domain cannot be established.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Remove any unresolved SIDs found in User Rights assignments and determined to not be for currently valid accounts or groups by removing the accounts or groups from the appropriate group policy. + + + + Review the effective User Rights setting in Local Group Policy Editor. +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +Review each User Right listed for any unresolved SIDs to determine whether they are valid, such as due to being temporarily disconnected from the domain. (Unresolved SIDs have the format that begins with "*S-1-".) + +If any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding. + + + + + + + SRG-OS-000329-GPOS-00128 + <GroupDescription></GroupDescription> + + WN22-AC-000010 + Windows Server 2022 account lockout duration must be configured to 15 minutes or greater. + <VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002238 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> Account lockout duration to "15" minutes or greater. + +A value of "0" is also acceptable, requiring an administrator to unlock the account. + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. + +If the "Account lockout duration" is less than "15" minutes (excluding "0"), this is a finding. + + + + + + + SRG-OS-000021-GPOS-00005 + <GroupDescription></GroupDescription> + + WN22-AC-000020 + Windows Server 2022 must have the number of allowed bad logon attempts configured to three or less. + <VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. The higher this value is, the less effective the account lockout feature will be in protecting the local system. The number of bad logon attempts must be reasonably small to minimize the possibility of a successful password attack while allowing for honest errors made during normal user logon.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000044 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> Account lockout threshold to "3" or fewer invalid logon attempts (excluding "0", which is unacceptable). + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. + +If the "Account lockout threshold" is "0" or more than "3" attempts, this is a finding. + + + + + + + SRG-OS-000021-GPOS-00005 + <GroupDescription></GroupDescription> + + WN22-AC-000030 + Windows Server 2022 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater. + <VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that must pass after failed logon attempts before the counter is reset to "0". The smaller this value is, the less effective the account lockout feature will be in protecting the local system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000044 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> Reset account lockout counter after to at least "15" minutes. + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. + +If the "Reset account lockout counter after" value is less than "15" minutes, this is a finding. + + + + + + + SRG-OS-000077-GPOS-00045 + <GroupDescription></GroupDescription> + + WN22-AC-000040 + Windows Server 2022 password history must be configured to 24 passwords remembered. + <VulnDiscussion>A system is more vulnerable to unauthorized access when system users recycle the same password several times without being required to change to a unique password on a regularly scheduled basis. This enables users to effectively negate the purpose of mandating periodic password changes. The default value is "24" for Windows domain systems. DoD has decided this is the appropriate value for all Windows systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000200 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> Enforce password history to "24" passwords remembered. + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for "Enforce password history" is less than "24" passwords remembered, this is a finding. + + + + + + + SRG-OS-000076-GPOS-00044 + <GroupDescription></GroupDescription> + + WN22-AC-000050 + Windows Server 2022 maximum password age must be configured to 60 days or less. + <VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the passwords. Scheduled changing of passwords hinders the ability of unauthorized system users to crack passwords and gain access 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> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000199 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> Maximum password age to "60" days or less (excluding "0", which is unacceptable). + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for the "Maximum password age" is greater than "60" days, this is a finding. + +If the value is set to "0" (never expires), this is a finding. + + + + + + + SRG-OS-000075-GPOS-00043 + <GroupDescription></GroupDescription> + + WN22-AC-000060 + Windows Server 2022 minimum password age must be configured to at least one day. + <VulnDiscussion>Permitting passwords to be changed in immediate succession within the same day allows users to cycle passwords through their history database. This enables users to effectively negate the purpose of mandating periodic password changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000198 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> Minimum password age to at least "1" day. + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for the "Minimum password age" is set to "0" days ("Password can be changed immediately"), this is a finding. + + + + + + + SRG-OS-000078-GPOS-00046 + <GroupDescription></GroupDescription> + + WN22-AC-000070 + Windows Server 2020 minimum password length must be configured to 14 characters. + <VulnDiscussion>Information systems not protected with strong password schemes (including passwords of minimum length) provide the opportunity for anyone to crack the password, thus gaining access to the system and compromising the device, information, or the local network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000205 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password length" to "14" characters. + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for the "Minimum password length," is less than "14" characters, this is a finding. + + + + + + + SRG-OS-000069-GPOS-00037 + <GroupDescription></GroupDescription> + + WN22-AC-000080 + Windows Server 2022 must have the built-in Windows password complexity policy enabled. + <VulnDiscussion>The use of complex passwords increases their strength against attack. The built-in Windows password complexity policy requires passwords to contain at least three of the four types of characters (numbers, uppercase and lowercase letters, and special characters) and prevents the inclusion of user names or parts of user names. + +Satisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000266-GPOS-00101</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000192 + CCI-000193 + CCI-000194 + CCI-001619 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> Password must meet complexity requirements to "Enabled". + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for "Password must meet complexity requirements" is not set to "Enabled", this is a finding. + + + + + + + SRG-OS-000073-GPOS-00041 + <GroupDescription></GroupDescription> + + WN22-AC-000090 + Windows Server 2022 reversible password encryption must be disabled. + <VulnDiscussion>Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords, which are easily compromised. For this reason, this policy must never be enabled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000196 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> Store passwords using reversible encryption to "Disabled". + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for "Store passwords using reversible encryption" is not set to "Disabled", this is a finding. + + + + + + + SRG-OS-000080-GPOS-00048 + <GroupDescription></GroupDescription> + + WN22-MS-000070 + Windows Server 2022 Access this computer from the network user right must only be assigned to the Administrators and Authenticated Users groups on domain-joined member servers and standalone or nondomain-joined systems. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Access this computer from the network" user right may access resources on the system, and this right must be limited to those requiring it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Access this computer from the network to include only the following accounts or groups: + +- Administrators +- Authenticated Users + + + + This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Access this computer from the network" user right, this is a finding: + +- Administrators +- Authenticated Users + + + + + + + SRG-OS-000080-GPOS-00048 + <GroupDescription></GroupDescription> + + WN22-MS-000080 + Windows Server 2022 Deny access to this computer from the network user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and local accounts and from unauthenticated access on all systems. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny access to this computer from the network" user right defines the accounts that are prevented from logging on from the network. + +In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain. + +Local accounts on domain-joined systems must also be assigned this right to decrease the risk of lateral movement resulting from credential theft attacks. + +The Guests group must be assigned this right to prevent unauthenticated access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Deny access to this computer from the network to include the following: + +Domain Systems Only: +- Enterprise Admins group +- Domain Admins group +- "Local account and member of Administrators group" or "Local account" (see Note below) + +All Systems: +- Guests group + +Note: These are built-in security groups. "Local account" is more restrictive but may cause issues on servers such as systems that provide failover clustering. + + + + This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny access to this computer from the network" user right, this is a finding: + +Domain Systems Only: +- Enterprise Admins group +- Domain Admins group +- "Local account and member of Administrators group" or "Local account" (see Note below) + +All Systems: +- Guests group + + + + + + + SRG-OS-000080-GPOS-00048 + <GroupDescription></GroupDescription> + + WN22-MS-000090 + Windows Server 2022 Deny log on as a batch job user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and from unauthenticated access on all systems. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny log on as a batch job" user right defines accounts that are prevented from logging on to the system as a batch job, such as Task Scheduler. + +In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain. + +The Guests group must be assigned to prevent unauthenticated access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Deny log on as a batch job to include the following: + +Domain Systems Only: +- Enterprise Admins Group +- Domain Admins Group + +All Systems: +- Guests Group + + + + This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on as a batch job" user right, this is a finding: + +Domain Systems Only: +- Enterprise Admins Group +- Domain Admins Group + +All Systems: +- Guests Group + + + + + + + SRG-OS-000080-GPOS-00048 + <GroupDescription></GroupDescription> + + WN22-MS-000100 + Windows Server 2022 Deny log on as a service user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts. No other groups or accounts must be assigned this right. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny log on as a service" user right defines accounts that are denied logon as a service. + +In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain. + +Incorrect configurations could prevent services from starting and result in a denial of service.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Deny log on as a service to include the following: + +Domain systems: +- Enterprise Admins Group +- Domain Admins Group + + + + This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on as a service" user right on domain-joined systems, this is a finding: + +- Enterprise Admins Group +- Domain Admins Group + +If any accounts or groups are defined for the "Deny log on as a service" user right on nondomain-joined systems, this is a finding. + + + + + + + SRG-OS-000080-GPOS-00048 + <GroupDescription></GroupDescription> + + WN22-MS-000110 + Windows Server 2022 Deny log on locally user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and from unauthenticated access on all systems. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny log on locally" user right defines accounts that are prevented from logging on interactively. + +In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain. + +The Guests group must be assigned this right to prevent unauthenticated access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Deny log on locally to include the following: + +Domain Systems Only: +- Enterprise Admins Group +- Domain Admins Group + +All Systems: +- Guests Group + + + + This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on locally" user right, this is a finding: + +Domain Systems Only: +- Enterprise Admins Group +- Domain Admins Group + +All Systems: +- Guests Group + + + + + + + SRG-OS-000297-GPOS-00115 + <GroupDescription></GroupDescription> + + WN22-MS-000120 + Windows Server 2022 Deny log on through Remote Desktop Services user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and all local accounts and from unauthenticated access on all systems. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services. + +In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain. + +Local accounts on domain-joined systems must also be assigned this right to decrease the risk of lateral movement resulting from credential theft attacks. + +The Guests group must be assigned this right to prevent unauthenticated access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002314 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Deny log on through Remote Desktop Services to include the following: + +Domain Systems Only: +- Enterprise Admins group +- Domain Admins group +- Local account (see Note below) + +All Systems: +- Guests group + +Note: "Local account" is referring to the Windows built-in security group. + + + + This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: + +Domain Systems Only: +- Enterprise Admins group +- Domain Admins group +- Local account (see Note below) + +All Systems: +- Guests group + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-MS-000130 + Windows Server 2022 Enable computer and user accounts to be trusted for delegation user right must not be assigned to any groups or accounts on domain-joined member servers and standalone or nondomain-joined systems. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Enable computer and user accounts to be trusted for delegation" user right allows the "Trusted for Delegation" setting to be changed. This could allow unauthorized users to impersonate other users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Enable computer and user accounts to be trusted for delegation to be defined but containing no entries (blank). + + + + This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups are granted the "Enable computer and user accounts to be trusted for delegation" user right, this is a finding. + + + + + + + SRG-OS-000121-GPOS-00062 + <GroupDescription></GroupDescription> + + WN22-SO-000010 + Windows Server 2022 must have the built-in guest account disabled. + <VulnDiscussion>A system faces an increased vulnerability threat if the built-in guest account is not disabled. This is a known account that exists on all Windows systems and cannot be deleted. This account is initialized during the installation of the operating system with no password assigned.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000804 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Accounts: Guest account status to "Disabled". + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. + +If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding. + + + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000030 + Windows Server 2022 built-in administrator account must be renamed. + <VulnDiscussion>The built-in administrator account is a well-known account subject to attack. Renaming this account to an unidentified name improves the protection of this account and the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Accounts: Rename administrator account to a name other than "Administrator". + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. + +If the value for "Accounts: Rename administrator account" is not set to a value other than "Administrator", this is a finding. + + + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN22-SO-000040 + Windows Server 2022 built-in guest account must be renamed. + <VulnDiscussion>The built-in guest account is a well-known user account on all Windows systems and, as initially installed, does not require a password. This can allow access to system resources by unauthorized users. Renaming this account to an unidentified name improves the protection of this account and the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Accounts: Rename guest account to a name other than "Guest". + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. + +If the value for "Accounts: Rename guest account" is not set to a value other than "Guest", this is a finding. + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000010 + Windows Server 2022 Access Credential Manager as a trusted caller user right must not be assigned to any groups or accounts. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Access Credential Manager as a trusted caller" user right may be able to retrieve the credentials of other accounts from Credential Manager.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Access Credential Manager as a trusted caller to be defined but containing no entries (blank). + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups are granted the "Access Credential Manager as a trusted caller" user right, this is a finding. + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000020 + Windows Server 2022 Act as part of the operating system user right must not be assigned to any groups or accounts. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Act as part of the operating system" user right can assume the identity of any user and gain access to resources that the user is authorized to access. Any accounts with this right can take complete control of a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Act as part of the operating system to be defined but containing no entries (blank). + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups (to include administrators), are granted the "Act as part of the operating system" user right, this is a finding. + + + + + + + SRG-OS-000080-GPOS-00048 + <GroupDescription></GroupDescription> + + WN22-UR-000030 + Windows Server 2022 Allow log on locally user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Allow log on locally" user right can log on interactively 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> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Allow log on locally to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Allow log on locally" user right, this is a finding: + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000040 + Windows Server 2022 back up files and directories user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Back up files and directories" user right can circumvent file and directory permissions and could allow access to sensitive data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Back up files and directories to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Back up files and directories" user right, this is a finding: + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000050 + Windows Server 2022 create a pagefile user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Create a pagefile" user right can change the size of a pagefile, which could affect system performance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Create a pagefile to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Create a pagefile" user right, this is a finding: + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000060 + Windows Server 2022 create a token object user right must not be assigned to any groups or accounts. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Create a token object" user right allows a process to create an access token. This could be used to provide elevated rights and compromise a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Create a token object to be defined but containing no entries (blank). + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups are granted the "Create a token object" user right, this is a finding. + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000070 + Windows Server 2022 create global objects user right must only be assigned to Administrators, Service, Local Service, and Network Service. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Create global objects" user right can create objects that are available to all sessions, which could affect processes in other users' sessions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Create global objects to include only the following accounts or groups: + +- Administrators +- Service +- Local Service +- Network Service + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Create global objects" user right, this is a finding: + +- Administrators +- Service +- Local Service +- Network Service + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000080 + Windows Server 2022 create permanent shared objects user right must not be assigned to any groups or accounts. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Create permanent shared objects" user right could expose sensitive data by creating shared objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Create permanent shared objects to be defined but containing no entries (blank). + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups are granted the "Create permanent shared objects" user right, this is a finding. + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000090 + Windows Server 2022 create symbolic links user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Create symbolic links" user right can create pointers to other objects, which could expose the system to attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Create symbolic links to include only the following accounts or groups: + +- Administrators + +Systems that have the Hyper-V role will also have "Virtual Machines" given this user right. If this needs to be added manually, enter it as "NT Virtual Machine\Virtual Machines". + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Create symbolic links" user right, this is a finding: + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000100 + Windows Server 2022 debug programs user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Debug programs" user right can attach a debugger to any process or to the kernel, providing complete access to sensitive and critical operating system components. This right is given to Administrators in the default configuration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Debug programs to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Debug programs" user right, this is a finding: + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000110 + Windows Server 2022 force shutdown from a remote system user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Force shutdown from a remote system" user right can remotely shut down a system, which could result in a denial of service.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Force shutdown from a remote system to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Force shutdown from a remote system" user right, this is a finding: + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000120 + Windows Server 2022 generate security audits user right must only be assigned to Local Service and Network Service. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Generate security audits" user right specifies users and processes that can generate Security Log audit records, which must only be the system service accounts defined.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Generate security audits to include only the following accounts or groups: + +- Local Service +- Network Service + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Generate security audits" user right, this is a finding: + +- Local Service +- Network Service + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000130 + Windows Server 2022 impersonate a client after authentication user right must only be assigned to Administrators, Service, Local Service, and Network Service. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Impersonate a client after authentication" user right allows a program to impersonate another user or account to run on their behalf. An attacker could use this to elevate privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Impersonate a client after authentication to include only the following accounts or groups: + +- Administrators +- Service +- Local Service +- Network Service + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Impersonate a client after authentication" user right, this is a finding: + +- Administrators +- Service +- Local Service +- Network Service + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000140 + Windows Server 2022 increase scheduling priority: user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Increase scheduling priority" user right can change a scheduling priority, causing performance issues or a denial of service.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Increase scheduling priority to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Increase scheduling priority" user right, this is a finding: + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000150 + Windows Server 2022 load and unload device drivers user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Load and unload device drivers" user right allows a user to load device drivers dynamically on a system. This could be used by an attacker to install malicious code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Load and unload device drivers to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Load and unload device drivers" user right, this is a finding: + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000160 + Windows Server 2022 lock pages in memory user right must not be assigned to any groups or accounts. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Lock pages in memory" user right allows physical memory to be assigned to processes, which could cause performance issues or a denial of service. + +Satisfies: SRG-OS-000324-GPOS-00125, SRG-OS-000433-GPOS-00193</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + CCI-002824 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Lock pages in memory to be defined but containing no entries (blank). + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups are granted the "Lock pages in memory" user right, this is a finding. + + + + + + + SRG-OS-000057-GPOS-00027 + <GroupDescription></GroupDescription> + + WN22-UR-000170 + Windows Server 2022 manage auditing and security log user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Manage auditing and security log" user right can manage the security log and change auditing configurations. This could be used to clear evidence of tampering. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-000162 + CCI-000163 + CCI-000164 + CCI-000171 + CCI-001914 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Manage auditing and security log to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Manage auditing and security log" user right, this is a finding. + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000180 + Windows Server 2022 modify firmware environment values user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Modify firmware environment values" user right can change hardware configuration environment variables. This could result in hardware failures or a denial of service.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Modify firmware environment values to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Modify firmware environment values" user right, this is a finding: + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000190 + Windows Server 2022 perform volume maintenance tasks user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Perform volume maintenance tasks" user right can manage volume and disk configurations. This could be used to delete volumes, resulting in data loss or a denial of service.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Perform volume maintenance tasks to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Perform volume maintenance tasks" user right, this is a finding: + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000200 + Windows Server 2022 profile single process user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Profile single process" user right can monitor nonsystem processes performance. An attacker could use this to identify processes to attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Profile single process to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Profile single process" user right, this is a finding: + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000210 + Windows Server 2022 restore files and directories user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Restore files and directories" user right can circumvent file and directory permissions and could allow access to sensitive data. It could also be used to overwrite more current data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Restore files and directories to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Restore files and directories" user right, this is a finding: + +- Administrators + + + + + + + SRG-OS-000324-GPOS-00125 + <GroupDescription></GroupDescription> + + WN22-UR-000220 + Windows Server 2022 take ownership of files or other objects user right must only be assigned to the Administrators group. + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Take ownership of files or other objects" user right can take ownership of objects and make changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target Microsoft Windows Server 2022 + DISA + DPMS Target + Microsoft Windows Server 2022 + 5485 + + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Take ownership of files or other objects to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Take ownership of files or other objects" user right, this is a finding: + +- Administrators + + + + + + \ No newline at end of file diff --git a/source/StigData/Archive/Windows.Server.2022/U_MS_Windows_Server_2022_STIG_V1R1_Manual-xccdf.xml b/source/StigData/Archive/Windows.Server.2022/U_MS_Windows_Server_2022_STIG_V1R1_Manual-xccdf.xml new file mode 100644 index 00000000..7c7a723a --- /dev/null +++ b/source/StigData/Archive/Windows.Server.2022/U_MS_Windows_Server_2022_STIG_V1R1_Manual-xccdf.xml @@ -0,0 +1,5488 @@ +acceptedMicrosoft Windows Server 2022 Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 1 Benchmark Date: 09 Sep 20223.4.0.342221.10.01I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>