From cce2d021a6a49a3951a794f6e3fb7675d862dcb7 Mon Sep 17 00:00:00 2001 From: hinderjd Date: Fri, 1 Mar 2024 08:52:27 -0700 Subject: [PATCH] Update Powerstig to parse\apply U_MS_SQL_Server_2016_Instance_V2R11_Manual_STIG (#1322) Co-authored-by: Eric Jenkins --- CHANGELOG.md | 1 + ...2016_Instance_STIG_V2R11_Manual-xccdf.log} | 0 ...2016_Instance_STIG_V2R11_Manual-xccdf.xml} | 42 +++++++++++++++---- ...Server-2016-Instance-2.11.org.default.xml} | 2 +- ...9.xml => SqlServer-2016-Instance-2.11.xml} | 41 ++++++++++++++++-- 5 files changed, 74 insertions(+), 12 deletions(-) rename source/StigData/Archive/SQL Server/{U_MS_SQL_Server_2016_Instance_STIG_V2R9_Manual-xccdf.log => U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.log} (100%) rename source/StigData/Archive/SQL Server/{U_MS_SQL_Server_2016_Instance_STIG_V2R9_Manual-xccdf.xml => U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.xml} (90%) rename source/StigData/Processed/{SqlServer-2016-Instance-2.9.org.default.xml => SqlServer-2016-Instance-2.11.org.default.xml} (92%) rename source/StigData/Processed/{SqlServer-2016-Instance-2.9.xml => SqlServer-2016-Instance-2.11.xml} (99%) diff --git a/CHANGELOG.md b/CHANGELOG.md index b186012b7..5fe2992c0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,7 @@ ## [Unreleased] +* Update Powerstig to parse\apply U_MS_SQL_Server_2016_Instance_V2R11_Manual_STIG [#1321](https://github.com/microsoft/PowerStig/issues/1321) * Update Powerstig to parse\apply U_CAN_Ubuntu_18-04_LTS_V2R13_STIG [#1319](https://github.com/microsoft/PowerStig/issues/1319) * Fix for Invalid value for V-221588 in default Chrome organizational settings [#1329](https://github.com/microsoft/PowerStig/issues/1329) * Update PowerSTIG to Parse/Apply U_RHEL_7_V3R14_STIG [#1315](https://github.com/microsoft/PowerStig/issues/1315) diff --git a/source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R9_Manual-xccdf.log b/source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.log similarity index 100% rename from source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R9_Manual-xccdf.log rename to source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.log diff --git a/source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R9_Manual-xccdf.xml b/source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.xml similarity index 90% rename from source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R9_Manual-xccdf.xml rename to source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.xml index 84f4ee909..a550a0d82 100644 --- a/source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R9_Manual-xccdf.xml +++ b/source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.xml @@ -1,4 +1,4 @@ -acceptedMS SQL Server 2016 Instance 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: 9 Benchmark Date: 27 Apr 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-DB-000031<GroupDescription></GroupDescription>SQL6-D0-003600SQL Server must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.<VulnDiscussion>Database management includes the ability to control the number of users and user sessions utilizing SQL Server. Unlimited concurrent connections to SQL Server could allow a successful Denial of Service (DoS) attack by exhausting connection resources; and a system can also fail or be degraded by an overload of legitimate users. Limiting the number of concurrent sessions per user is helpful in reducing these risks. +acceptedMS SQL Server 2016 Instance 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: 11 Benchmark Date: 24 Jan 20243.4.1.229161.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>