You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-vulnerability-management/defender-vulnerability-management-faq.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,7 +130,7 @@ The [Windows authenticated scan](windows-authenticated-scan.md) deprecation proc
130
130
131
131
### Why is this product being deprecated?
132
132
133
-
The deprecation is to streamline offerings and focus on features that provide greater value to customers. This change allows our teams to allocate resources to innovations that better meet customer needs. We understand transitions can be challenging, and we're here to support you throughout the process. Let us know if you have any questions or need assistance.
133
+
We're deprecating Windows authenticated scan to allow our teams to allocate resources to other product innovations. We understand transitions can be challenging, and we're here to support you throughout the process. Let us know if you have any questions or need assistance with this change.
134
134
135
135
### When will the product be officially deprecated?
Copy file name to clipboardExpand all lines: defender-vulnerability-management/tvm-security-baselines.md
+103-1Lines changed: 103 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.collection:
12
12
- Tier1
13
13
ms.topic: conceptual
14
14
search.appverid: met150
15
-
ms.date: 03/01/2023
15
+
ms.date: 11/19/2024
16
16
---
17
17
18
18
# Security baselines assessment
@@ -153,6 +153,108 @@ You can run advanced hunting queries on the following tables to gain visibility
153
153
-**DeviceBaselineComplianceAssessment**: device compliance related information.
154
154
-**DeviceBaselineComplianceAssessmentKB**: general settings for CIS and STIG benchmarks (not related to any device).
155
155
156
+
## Known issues with data collection
157
+
158
+
We are aware of known issues affecting data collection in certain versions of the CIS, STIG, and Microsoft benchmarks. The issues might cause inaccurate or incomplete results when running tests in these versions. These issues are being actively worked on and will be resolved in future updates.
159
+
160
+
We recommend to exclude the affected tests from the benchmark profile while running the assessment to avoid the impact of these issues.
161
+
162
+
If your benchmark version is not listed below and you're experiencing issues, please contact [Microsoft Support](https://support.microsoft.com) to help us investigate further and assist you with a resolution.
163
+
164
+
The following CIS, Microsoft, and STIG benchmarks are affected:
165
+
166
+
-**CIS**
167
+
- CIS 17.1.1
168
+
- CIS 17.2.1
169
+
- CIS 17.3.1 to 17.3.2
170
+
- CIS 17.5.1 to 17.5.6
171
+
- CIS 17.6.1 to 17.6.4
172
+
- CIS 17.7.1 to 17.7.5
173
+
- CIS 17.8.1
174
+
- CIS 17.9.1 to 17.9.5
175
+
176
+
-**CIS Checks Additions**
177
+
- CIS 2.3.7.3 to 2.3.7.5
178
+
- CIS 2.3.10.1
179
+
- CIS 1.1.5
180
+
181
+
-**Microsoft Checks**
182
+
- Microsoft 2.1
183
+
- Microsoft 2.10
184
+
- Microsoft 2.12 to 2.30
185
+
- Microsoft 2.33 to 2.37
186
+
- Microsoft 2.40 to 2.50
187
+
- Microsoft 3.55
188
+
- Microsoft 3.57
189
+
- Microsoft 3.60
190
+
- Microsoft 3.72
191
+
192
+
-**Microsoft Certificate Store Checks for Windows and Windows Server**
193
+
- MCS 1.1 for Windows 10 1909 (Temporary) 1.1.5
194
+
- MCS 2.0 for Windows 10 1909 (Temporary) 1.1.5
195
+
- MCS 1.1 for Windows 10 20H2 (Temporary) 1.1.5
196
+
- MCS 2.0 for Windows 10 20H2 (Temporary) 1.1.5
197
+
- MCS 2.0 for Windows 10 v21H2 1.1.5
198
+
- MCS 2.0 for Windows 10 v22H2 1.1.5
199
+
- MCS 2.0 for Windows 11 1.1.5
200
+
- MCS 2.0 for Windows 11 23H2 1.1.5
201
+
- MCS 2.0 for Windows Server 2022 1.1.5
202
+
- MCS 2.0 for Windows Server 2022 Domain Controller 1.1.5
203
+
- MCS 2.0 for Windows Server 2019 1.1.5
204
+
- MCS 2.0 for Windows Server 2019 Domain Controller 1.1.5
205
+
- MCS 2.0 for Windows Server 2016 1.1.5
206
+
- MCS 2.0 for Windows Server 2016 Domain Controller 1.1.5
207
+
- MCS 2.0 for Windows Server 2012_R2 1.1.5
208
+
- MCS 1.1 for Windows Server 2008_R2 (Temporary) 1.1.5
209
+
- MCS 2.0 for Windows Server 2022 Domain Controller 2.3.10.1
210
+
- MCS 2.0 for Windows Server 2019 Domain Controller 2.3.10.1
211
+
- MCS 2.0 for Windows Server 2016 Domain Controller 2.3.10.1
212
+
213
+
-**STIG List**
214
+
- STIG SV-205678r569188
215
+
- STIG SV-220746r569187
216
+
- STIG SV-220754r569187
217
+
- STIG SV-220757r569187
218
+
- STIG SV-220760r569187
219
+
- STIG SV-220767r569187
220
+
- STIG SV-220768r569187
221
+
- STIG SV-220768r851975
222
+
- STIG SV-220775r569187
223
+
- STIG SV-220775r851978
224
+
- STIG SV-220786r569187
225
+
- STIG SV-220769r569187
226
+
- STIG SV-225273r569185
227
+
- STIG SV-225281r569185
228
+
- STIG SV-225284r569185
229
+
- STIG SV-225287r569185
230
+
- STIG SV-225292r569185
231
+
- STIG SV-225294r569185
232
+
- STIG SV-225294r852189
233
+
- STIG SV-225295r569185
234
+
- STIG SV-225302r569185
235
+
- STIG SV-225302r852194
236
+
- STIG SV-226092r569184
237
+
- STIG SV-226092r794343
238
+
- STIG SV-226099r569184
239
+
- STIG SV-226099r794279
240
+
- STIG SV-226102r569184
241
+
- STIG SV-226102r794335
242
+
- STIG SV-226107r569184
243
+
- STIG SV-226107r794336
244
+
- STIG SV-226110r569184
245
+
- STIG SV-226110r794366
246
+
- STIG SV-226117r569184
247
+
- STIG SV-226117r794356
248
+
- STIG SV-226117r852079
249
+
- STIG SV-226109r569184
250
+
- STIG SV-226109r794353
251
+
- STIG SV-226109r852074
252
+
- STIG SV-226063r569184
253
+
- STIG SV-226063r794292
254
+
- STIG SV-254271r848629
255
+
- STIG SV-224873r569186
256
+
257
+
156
258
## Related articles
157
259
158
260
-[Vulnerabilities in my organization](tvm-weaknesses.md)
Copy file name to clipboardExpand all lines: defender-vulnerability-management/whats-new-in-microsoft-defender-vulnerability-management.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ audience: ITPro
11
11
ms.collection:
12
12
- m365-security
13
13
ms.topic: conceptual
14
-
ms.date: 11/07/2024
14
+
ms.date: 11/19/2024
15
15
---
16
16
17
17
# What's new in Microsoft Defender Vulnerability Management
@@ -23,6 +23,7 @@ This article provides information about new features and important product updat
23
23
24
24
## November 2024
25
25
26
+
- We are aware of issues affecting data collection in several versions of CIS, STIG, and Microsoft benchmarks. We are actively working on a fix and will provide an update when the issue is resolved. For more information, see [Known issues with data collection](tvm-security-baselines.md#known-issues-with-data-collection).
26
27
- The deprecation process of the Windows authenticated scan will begin on November 2024 and concludes on November 30, 2025. For more information, see [Windows authenticated scan deprecation FAQs](defender-vulnerability-management-faq.md#windows-authenticated-scan-deprecation-faqs).
0 commit comments