3175x175(CURRENT).thumb.jpg.b05acc060982b36f5891ba728e6d953c.jpg)
Microsoft has announced the release of the June 2025 revision of its security baseline package for Windows Server 2025 (v2506), it is now available to download from the Microsoft Security Compliance Toolkit. After downloading it, you can test the recommended configurations in your environment and customize or implement them as you see fit.
To deal with the evolving threat landscape, new Windows features, and community feedback, Microsoft is planning to revise the Windows Server baseline more frequently in the future. Windows Server security baselines are a collection of Microsoft-recommended configuration settings that help administrators establish secure and consistent Windows Server environments.
This is the first security baseline update for Windows Server 2025 since January, a summary of the changes is presented in this table:
|
Security Policy |
Change Summary |
|---|---|
|
Deny log on through Remote Desktop Services |
Allow remote logon for non-admin local accounts on MS and add “BUILTIN\Guests” to both DC and MS. |
|
WDigest Authentication |
Remove from the baseline |
|
Allow Windows Ink Workspace |
Remove from the baseline |
|
Audit Authorization Policy Change |
Set to “Success” in both DC and MS |
|
Include command line in process creation events |
Enable in both DC and MS |
|
Control whether exclusions are visible to local users |
Moved to Not Configured as it is overridden by the parent setting. |
Of these changes, the removal of WDigest Authentication and the addition of Include command line in process creation events are significant.
Microsoft said it removed WDigest Authentication from the security baseline because it is no longer necessary for Windows Server 2025. The policy was originally enforced so that WDigest couldn’t store plaintext passwords in memory, which was a significant theft risk. Since the 24H2 update in Windows Server 2022, the policy has been deprecated, so there’s no need to enforce this setting.
The update also adds Include command line in process creation events to improve the visibility of how processes are executed across the system. By capturing the command-line arguments, it makes it easier to detect and investigate malicious activity that may otherwise seem legitimate.
If you want to learn more about the other changes in a bit more depth, refer to Microsoft’s announcement of this security baseline update.
Hope you enjoyed this news post.
Thank you for appreciating my time and effort posting news every day for many years.
News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of May): 2,377
RIP Matrix | Farewell my friend
- phen0men4 and RobrPatty
-
2
Recommended Comments
There are no comments to display.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.