<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Microsoft Security Baselines topics</title>
    <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/bd-p/Security-Baselines</link>
    <description>Microsoft Security Baselines topics</description>
    <pubDate>Tue, 10 Nov 2026 23:15:38 GMT</pubDate>
    <dc:creator>Security-Baselines</dc:creator>
    <dc:date>2026-11-10T23:15:38Z</dc:date>
    <item>
      <title>Cybersecurity in 2026: Is Zero Trust Enough to Defend Against AI-Powered Threats?</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/cybersecurity-in-2026-is-zero-trust-enough-to-defend-against-ai/m-p/4567850#M566</link>
      <description>&lt;P&gt;As cyber threats become more sophisticated, organizations are increasingly adopting Zero Trust architectures, identity-based security, and AI-powered threat detection. But an important question remains: Are our existing security strategies evolving fast enough to address the next generation of cyberattacks?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Microsoft has developed a comprehensive security ecosystem through Microsoft Defender XDR, Microsoft Sentinel, Microsoft Entra ID, and Microsoft Intune. These technologies provide powerful capabilities for identity protection, endpoint security, threat detection, and incident response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, attackers are also leveraging automation, generative AI, and increasingly sophisticated social engineering techniques.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd like to open a discussion around five important questions:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1. Zero Trust implementation: &lt;/STRONG&gt;Are organizations genuinely implementing Zero Trust principles, or are many simply deploying security products without changing their underlying security architecture?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2. AI-powered threats: &lt;/STRONG&gt;How prepared are Microsoft security environments to detect AI-assisted phishing, identity attacks, and automated intrusion attempts?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3. Microsoft Defender and Sentinel: &lt;/STRONG&gt;What practical improvements have security teams experienced by integrating Microsoft Defender XDR with Microsoft Sentinel?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;4. Identity as the new perimeter: &lt;/STRONG&gt;With hybrid workforces and cloud-based infrastructure, should identity security now take priority over traditional network perimeter protection?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;5. Autonomous security operations: &lt;/STRONG&gt;How much authority should AI-powered security agents have to investigate threats, isolate devices, disable accounts, or initiate incident response actions without human approval?&lt;/P&gt;&lt;P&gt;One of my biggest concerns is that organizations may invest heavily in cybersecurity tools while overlooking the fundamentals: visibility, configuration management, access governance, employee awareness, and incident response readiness.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Security is no longer just about preventing unauthorized access. It's about building resilient systems that can detect, contain, recover from, and continuously adapt to emerging threats.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd be interested to hear from security architects, SOC analysts, Microsoft MVPs, and IT administrators:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What do you consider the biggest cybersecurity challenge facing Microsoft-based enterprise environments today, and what practical steps should organizations prioritize in 2026?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looking forward to your insights and real-world experiences.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Oct 2026 20:36:20 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/cybersecurity-in-2026-is-zero-trust-enough-to-defend-against-ai/m-p/4567850#M566</guid>
      <dc:creator>faisaldadkhan</dc:creator>
      <dc:date>2026-10-26T20:36:20Z</dc:date>
    </item>
    <item>
      <title>Administrator Protection - Default Enabled?</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/administrator-protection-default-enabled/m-p/4564564#M562</link>
      <description>&lt;P&gt;We are using the 25H2 Security Baselines. After the October 2026 Patch Tuesday, Administrator Protection is active, even though the setting “User Account Control: Configure type of Admin Approval Mode” is not set or configured in the 25H2 baselines or others Policies.&lt;/P&gt;&lt;P&gt;Which other setting is causing the registry value “TypeOfAdminApprovalMode” to be set to 2?&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2026 18:22:34 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/administrator-protection-default-enabled/m-p/4564564#M562</guid>
      <dc:creator>ZEmbaxter</dc:creator>
      <dc:date>2026-10-14T18:22:34Z</dc:date>
    </item>
    <item>
      <title>Microsoft Security Compliance Toolkit</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/microsoft-security-compliance-toolkit/m-p/4563136#M558</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;This is my first time on this forum. Please can you help with the MSCT governance.&lt;/P&gt;&lt;P&gt;I have been tasked with running the MSCToolkit against our pre-prod and prod GPO's in an Enterprise setup.&lt;/P&gt;&lt;P&gt;The complete MSCToolkit has been downloaded and the policyanalyser has been installed.&lt;/P&gt;&lt;P&gt;I have copied the GPO's in Pre-Prod and Added them into the policyanalyser.exe however it's unclear to me what I need to do to ensure that these GPO policies are checked and are considered to be cleared by MS Security hardening policies. And, the lack of information of how to use the Policy Analyzer v4.0.2004.13001 tool is another source of frustration.&lt;/P&gt;&lt;P&gt;Please could someone talk me through a step by step process of how to use the Policy Analyzer and how to interpret the results so that I am able to prepare a report for consideration.&lt;/P&gt;&lt;P&gt;Hopefully someone can help with this process.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Oct 2026 08:27:53 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/microsoft-security-compliance-toolkit/m-p/4563136#M558</guid>
      <dc:creator>peterF</dc:creator>
      <dc:date>2026-10-09T08:27:53Z</dc:date>
    </item>
    <item>
      <title>Dynamic Code Setting in Version 139 Causing Printing Issues</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/dynamic-code-setting-in-version-139-causing-printing-issues/m-p/4542644#M557</link>
      <description>&lt;P&gt;Microsoft Edge security baseline version 139 via Intune sets the Dynamic Code value to 'Prevent the browser process from creating dynamic code'. The setting causes Microsoft Edge to close down / crash when trying to print. Reverting the setting value back to version 128 'Default dynamic code settings' resolves Microsoft Edge not closing down when trying to print.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jul 2026 06:57:51 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/dynamic-code-setting-in-version-139-causing-printing-issues/m-p/4542644#M557</guid>
      <dc:creator>christiansmith_nemlig</dc:creator>
      <dc:date>2026-07-31T06:57:51Z</dc:date>
    </item>
    <item>
      <title>RestrictedTrafficInstall.ps1 Fails on Windows 10 IoT Enterprise LTSC 2021 with SKU Detection Error</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/restrictedtrafficinstall-ps1-fails-on-windows-10-iot-enterprise/m-p/4540340#M554</link>
      <description>&lt;P&gt;I am encountering an issue while deploying the&amp;nbsp;&lt;STRONG&gt;Restricted Traffic Limited Functionality Baseline&lt;/STRONG&gt; on a &lt;STRONG&gt;Windows 10 IoT Enterprise LTSC 2021&lt;/STRONG&gt; device and would like to confirm whether this OS edition is supported or if this is a known issue with the baseline script.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Operating System:&lt;/STRONG&gt; Windows 10 IoT Enterprise LTSC 2021&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;EditionID:&lt;/STRONG&gt; IoTEnterpriseS&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;DisplayVersion:&lt;/STRONG&gt; 21H2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;:&lt;/P&gt;&lt;P&gt;...\RestrictedTrafficInstall.ps1 : Could not get SKU of current running OS.&lt;/P&gt;&lt;P&gt;CategoryInfo&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : NotSpecified: (:) [Write-Error], WriteErrorException&lt;/P&gt;&lt;P&gt;FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,RestrictedTrafficInstall.ps1&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jul 2026 09:27:57 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/restrictedtrafficinstall-ps1-fails-on-windows-10-iot-enterprise/m-p/4540340#M554</guid>
      <dc:creator>NiteshK</dc:creator>
      <dc:date>2026-07-24T09:27:57Z</dc:date>
    </item>
    <item>
      <title>Windows 11 24H2 Sec Baseline → Broken SSO to on‑prem (Root cause: PKINIT SHA‑1 baseline)</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/windows-11-24h2-sec-baseline-broken-sso-to-on-prem-root-cause/m-p/4528483#M550</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I ran into an issue with &lt;STRONG&gt;Entra-joined devices using Windows Hello for Business (Cloud Kerberos Trust)&lt;/STRONG&gt; that might help others working with Windows 11 24H2 security baselines.&lt;/P&gt;&lt;H2&gt;Scenario&lt;/H2&gt;&lt;UL&gt;&lt;LI&gt;Windows 11 25H2 devices&lt;/LI&gt;&lt;LI&gt;Entra-joined (not hybrid)&lt;/LI&gt;&lt;LI&gt;Intune-managed&lt;/LI&gt;&lt;LI&gt;Windows Hello for Business (WHfB) enabled&lt;/LI&gt;&lt;LI&gt;Cloud Kerberos Trust configured&lt;/LI&gt;&lt;LI&gt;On-prem AD (Windows Server 2019/2022 DCs)&lt;/LI&gt;&lt;LI&gt;Access to SMB shares / on-prem applications&lt;/LI&gt;&lt;/UL&gt;&lt;H2&gt;Symptoms&lt;/H2&gt;&lt;UL&gt;&lt;LI&gt;SSO to on-prem resources fails&lt;/LI&gt;&lt;LI&gt;Users get credential/PIN prompt instead of SSO&lt;/LI&gt;&lt;LI&gt;Error message:&lt;BR /&gt;&lt;EM&gt;“The system cannot contact a domain controller to service the authentication request”&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Client-side observations:&lt;/P&gt;&lt;P&gt;klist → no tickets (initially)&lt;/P&gt;&lt;P&gt;After enabling Cloud Kerberos Trust:&lt;/P&gt;&lt;P&gt;klist get krbtgt → works klist get cifs/server.domain → fails&lt;/P&gt;&lt;P&gt;Error:&lt;/P&gt;&lt;P&gt;0xc000a100 / 0x3bc4 Hash generation for the specified version and hash type is not enabled on server&lt;/P&gt;&lt;H2&gt;Root Cause&lt;/H2&gt;&lt;P&gt;The issue was caused by a &lt;STRONG&gt;Windows 11 24H2 security baseline setting&lt;/STRONG&gt; related to Kerberos/PKINIT.&lt;/P&gt;&lt;P&gt;The 24H2 baseline introduces a policy for &lt;STRONG&gt;configuring hash algorithms for certificate-based Kerberos authentication (PKINIT)&lt;/STRONG&gt;. This setting allows environments to &lt;STRONG&gt;disable SHA-1 and require SHA-2 algorithms&lt;/STRONG&gt;. &lt;A href="https://www.applepie.se/entra-id-joined-single-sign-on-and-24h2-security-baseline" target="_blank"&gt;[applepie.se]&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Important detail:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;This configuration &lt;STRONG&gt;only works if the domain controllers fully support PKINIT with SHA-2&lt;/STRONG&gt;, which effectively requires &lt;STRONG&gt;Windows Server 2025 domain controllers across the environment&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;If SHA-1 is disabled while running:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Windows Server 2019 or 2022 DCs&lt;/LI&gt;&lt;LI&gt;Mixed environments&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;then &lt;STRONG&gt;PKINIT authentication fails&lt;/STRONG&gt;, which directly impacts:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Windows Hello for Business&lt;/LI&gt;&lt;LI&gt;Cloud Kerberos Trust&lt;/LI&gt;&lt;LI&gt;Any passwordless Kerberos-based authentication&lt;/LI&gt;&lt;/UL&gt;&lt;H2&gt;Why this is difficult to troubleshoot&lt;/H2&gt;&lt;UL&gt;&lt;LI&gt;Cloud Kerberos Trust appears correctly configured&lt;/LI&gt;&lt;LI&gt;AzureADKerberos object exists&lt;/LI&gt;&lt;LI&gt;PRT is valid&lt;/LI&gt;&lt;LI&gt;Network connectivity is fine&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;However:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Kerberos tickets are not issued correctly&lt;/LI&gt;&lt;LI&gt;Service tickets (CIFS, HTTP, etc.) fail&lt;/LI&gt;&lt;LI&gt;Errors are misleading and point to KDC/hash issues&lt;/LI&gt;&lt;LI&gt;No explicit warning is provided in baseline guidance that mixed environments will break&lt;/LI&gt;&lt;/UL&gt;&lt;H2&gt;Resolution&lt;/H2&gt;&lt;P&gt;Revert the baseline change and &lt;STRONG&gt;allow SHA-1 for PKINIT again&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Policy location:&lt;/P&gt;&lt;P&gt;Computer Configuration → System → Kerberos / KDC → Configure hash algorithms for certificate logon&lt;/P&gt;&lt;P&gt;Ensure:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;SHA-1 is set to Allowed/Default&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;After reverting:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Kerberos ticket issuance works&lt;/LI&gt;&lt;LI&gt;SSO to on-prem resources is restored&lt;/LI&gt;&lt;/UL&gt;&lt;H2&gt;Recommendation&lt;/H2&gt;&lt;P&gt;Do not disable SHA-1 for PKINIT unless:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;All domain controllers are &lt;STRONG&gt;Windows Server 2025&lt;/STRONG&gt;, and&lt;/LI&gt;&lt;LI&gt;PKINIT SHA-2 support has been fully validated&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Treat this setting as &lt;STRONG&gt;future hardening&lt;/STRONG&gt;, not production-safe for mixed environments today.&lt;/P&gt;&lt;H2&gt;Takeaway&lt;/H2&gt;&lt;P&gt;If you experience:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;WHfB + Cloud Kerberos Trust SSO failures&lt;/LI&gt;&lt;LI&gt;klist get errors with hash generation issues&lt;/LI&gt;&lt;LI&gt;Missing or failing Kerberos service tickets&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;check the &lt;STRONG&gt;PKINIT hash configuration from the 24H2 security baseline first&lt;/STRONG&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jun 2026 09:05:48 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/windows-11-24h2-sec-baseline-broken-sso-to-on-prem-root-cause/m-p/4528483#M550</guid>
      <dc:creator>StephanGee</dc:creator>
      <dc:date>2026-06-16T09:05:48Z</dc:date>
    </item>
    <item>
      <title>Security Baseline Windows 11 25H2 in Intune</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-windows-11-25h2-in-intune/m-p/4489812#M548</link>
      <description>&lt;P&gt;Security baseline 25H2 is released in MS Security Compliance Toolkit. But in Intune, there is still 24H2. What's the reason of this delay?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to set it up by Intune.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2026 17:11:15 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-windows-11-25h2-in-intune/m-p/4489812#M548</guid>
      <dc:creator>DM-se</dc:creator>
      <dc:date>2026-01-27T17:11:15Z</dc:date>
    </item>
    <item>
      <title>TLS 1.1 is set as a recommended value in the latest security baseline</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/tls-1-1-is-set-as-a-recommended-value-in-the-latest-security/m-p/4475088#M544</link>
      <description>&lt;P data-start="0" data-end="158"&gt;In the latest security baseline for Windows 11 24H2, the following item is set to "Use TLS 1.1 and TLS 1.2," but could you please explain the reason for this?&lt;BR /&gt;&lt;A href="https://www.microsoft.com/en-us/download/details.aspx?id=55319" target="_blank"&gt;Download Microsoft Security Compliance Toolkit 1.0 from Official Microsoft Download Center&lt;/A&gt;&lt;/P&gt;
&lt;P data-start="160" data-end="302"&gt;&lt;STRONG data-start="160" data-end="302"&gt;Windows Components\Internet Explorer\Internet Control Panel\Advanced Page&lt;BR data-start="235" data-end="238" /&gt;Turn off encryption support&lt;BR data-start="265" data-end="268" data-is-only-node="" /&gt;Enabled: Use TLS 1.1 and TLS 1.2&lt;/STRONG&gt;&lt;/P&gt;
&lt;P data-start="304" data-end="439" data-is-last-node="" data-is-only-node=""&gt;Generally, I believe TLS 1.1 should no longer be used, and that using "TLS 1.2 and TLS 1.3" would be better from a security standpoint.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 06:13:58 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/tls-1-1-is-set-as-a-recommended-value-in-the-latest-security/m-p/4475088#M544</guid>
      <dc:creator>kayoda23</dc:creator>
      <dc:date>2025-12-04T06:13:58Z</dc:date>
    </item>
    <item>
      <title>Start strong with MCSB v2</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/start-strong-with-mcsb-v2/m-p/4470955#M542</link>
      <description>&lt;P class=""&gt;Cloud adoption is accelerating, but so are threats. Organizations often rush to deploy workloads without a clear security baseline, leaving critical gaps that attackers can exploit. Enter &lt;STRONG&gt;Microsoft Cloud Security Benchmark (MCSB) v2&lt;/STRONG&gt;, now in public preview, designed to help you start well-protected and evolve securely.&lt;/P&gt;
&lt;H5&gt;&lt;STRONG&gt;What Is Microsoft Cloud Security Benchmark v2?&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;MCSB v2 is a &lt;STRONG&gt;comprehensive set of best practices and controls&lt;/STRONG&gt; for securing cloud resources across &lt;STRONG&gt;Azure&lt;/STRONG&gt; and hybrid environments. It aligns with:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Industry standards&lt;/STRONG&gt;: NIST, CIS, ISO&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Microsoft Secure Future Initiative (SFI)&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Zero Trust principles&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This benchmark provides prescriptive guidance for identity, network, data, and workload security helping organizations establish a strong foundation before customizing for their unique needs.&lt;/P&gt;
&lt;H5&gt;&lt;STRONG&gt;Security Domains in MCSB v2&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;The benchmark organizes guidance into &lt;STRONG&gt;security domains&lt;/STRONG&gt;, each representing a critical area of cloud security:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;STRONG&gt;Identity Management&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;MFA enforcement, Conditional Access, privileged identity management.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Network Security&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Segmentation, firewall rules, private endpoints.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Data Protection&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Encryption at rest and in transit, key management.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Asset Management&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Resource inventory, tagging, and governance.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Logging &amp;amp; Monitoring&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Centralized logging, alerting, and SIEM integration.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Incident Response&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Playbooks, automation, and escalation workflows.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Application Security&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Secure coding practices, vulnerability scanning.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Compliance &amp;amp; Governance&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Policy enforcement, regulatory alignment.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;H5&gt;&lt;STRONG&gt;Security Control Structure&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;Each control in MCSB v2 follows a &lt;STRONG&gt;structured format&lt;/STRONG&gt; for clarity and implementation:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Control ID&lt;/STRONG&gt;: Unique identifier for tracking.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Control Name&lt;/STRONG&gt;: Descriptive title (e.g., “Enable MFA for all users”).&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Control Category&lt;/STRONG&gt;: Maps to a security domain.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Control Objective&lt;/STRONG&gt;: What the control aims to achieve.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Implementation Guidance&lt;/STRONG&gt;: Detailed steps for configuration.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Azure Policy Mapping&lt;/STRONG&gt;: Built-in policy definitions for automation.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;References&lt;/STRONG&gt;: Links to Microsoft Learn and industry standards.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This structure ensures consistency, traceability and ease of adoption across large environments.&lt;/P&gt;
&lt;img /&gt;
&lt;H5&gt;&lt;STRONG&gt;Integration with Azure Policy &amp;amp; Defender for Cloud&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;One of the most powerful aspects of MCSB v2 is its &lt;STRONG&gt;native integration with Azure governance and security tools&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Azure Policy&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Pre-built policy initiatives mapped to MCSB controls.&lt;/LI&gt;
&lt;LI&gt;Enables &lt;STRONG&gt;policy-as-code&lt;/STRONG&gt; for automated enforcement across subscriptions.&lt;/LI&gt;
&lt;LI&gt;Supports &lt;STRONG&gt;compliance dashboards&lt;/STRONG&gt; for visibility and reporting.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Microsoft Defender for Cloud&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Monitors compliance against MCSB controls in real time.&lt;/LI&gt;
&lt;LI&gt;Provides &lt;STRONG&gt;secure score&lt;/STRONG&gt; and recommendations for remediation.&lt;/LI&gt;
&lt;LI&gt;Integrates with workflows for &lt;STRONG&gt;alerting and automation&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H5&gt;&lt;STRONG&gt;How to Get Started&lt;/STRONG&gt;&lt;/H5&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;STRONG&gt;Review the Benchmark&lt;/STRONG&gt;&lt;BR /&gt;Explore the full guidance here:&lt;BR /&gt;https://learn.microsoft.com/en-us/security/benchmark/azure/overview&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Apply Built-In Policies&lt;/STRONG&gt;&lt;BR /&gt;Use &lt;STRONG&gt;Azure Policy initiatives&lt;/STRONG&gt; mapped to MCSB controls for quick enforcement.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Monitor Compliance&lt;/STRONG&gt;&lt;BR /&gt;Leverage &lt;STRONG&gt;Microsoft Defender for Cloud&lt;/STRONG&gt; to track adherence and remediate gaps.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Tune for Your Needs&lt;/STRONG&gt;&lt;BR /&gt;Start with the baseline, then customize based on workload sensitivity and business requirements.&lt;/LI&gt;
&lt;/OL&gt;
&lt;H5&gt;&lt;STRONG&gt;Best Practices for Organizations&lt;/STRONG&gt;&lt;/H5&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Enable MFA and Conditional Access&lt;/STRONG&gt; for all identities.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Segment networks&lt;/STRONG&gt; and enforce least privilege.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Encrypt data at rest and in transit&lt;/STRONG&gt; using Azure-native capabilities.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Enable Defender for Cloud&lt;/STRONG&gt; for continuous posture management.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Automate compliance&lt;/STRONG&gt; with policy-as-code.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Cloud security isn’t static. Threats evolve, and so should your defenses. MCSB v2 gives you a future-ready foundation that scales with your business and integrates with Microsoft’s security ecosystem.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Nov 2025 12:05:26 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/start-strong-with-mcsb-v2/m-p/4470955#M542</guid>
      <dc:creator>umamasurkar28</dc:creator>
      <dc:date>2025-11-18T12:05:26Z</dc:date>
    </item>
    <item>
      <title>Microsoft Zero Trust Assessment v2: Operationalizing Security with Precision</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/microsoft-zero-trust-assessment-v2-operationalizing-security/m-p/4470949#M541</link>
      <description>&lt;P&gt;In an era where cyber threats evolve faster than ever, organizations can’t afford blind spots. &lt;STRONG&gt;Zero Trust&lt;/STRONG&gt; is no longer optional it’s the foundation of modern security. With the release of the &lt;STRONG&gt;Microsoft Zero Trust Assessment v2&lt;/STRONG&gt;, enterprises now have a powerful tool to &lt;STRONG&gt;measure, prioritize, and remediate&lt;/STRONG&gt; security gaps with actionable intelligence.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG style="color: rgb(30, 30, 30); font-size: 20px;"&gt;What Is Zero Trust Assessment v2?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;The Zero Trust Assessment is a &lt;STRONG&gt;security posture evaluation tool&lt;/STRONG&gt; designed to help organizations operationalize Zero Trust principles. It automates checks across hundreds of configuration items aligned with:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Secure Future Initiative (SFI)&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Zero Trust pillars&lt;/STRONG&gt;: Identity, Devices, Applications, Data, Infrastructure and Networks&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Industry standards&lt;/STRONG&gt;: NIST, CISA, CIS&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Microsoft’s internal security baselines&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Insights from thousands of real-world customer implementations&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;H5&gt;&lt;STRONG&gt;How Does It Work?&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;The assessment follows a structured, automated workflow:&lt;/P&gt;
&lt;H6&gt;1. Data Collection &amp;amp; Configuration Analysis&lt;/H6&gt;
&lt;UL&gt;
&lt;LI&gt;Scans your &lt;STRONG&gt;Microsoft 365 environment&lt;/STRONG&gt; and connected workloads.&lt;/LI&gt;
&lt;LI&gt;Evaluates &lt;STRONG&gt;identity configurations&lt;/STRONG&gt; (e.g., MFA enforcement, conditional access policies).&lt;/LI&gt;
&lt;LI&gt;Reviews &lt;STRONG&gt;device compliance&lt;/STRONG&gt; (e.g., Intune policies, OS hardening).&lt;/LI&gt;
&lt;LI&gt;Pulls telemetry from &lt;STRONG&gt;Azure AD&lt;/STRONG&gt;, &lt;STRONG&gt;Microsoft Defender&lt;/STRONG&gt;, and other integrated services.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H6&gt;2. Automated Testing Against Standards&lt;/H6&gt;
&lt;UL&gt;
&lt;LI&gt;Runs &lt;STRONG&gt;hundreds of tests&lt;/STRONG&gt; mapped to Zero Trust principles.&lt;/LI&gt;
&lt;LI&gt;Benchmarks your settings against:
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;NIST Cybersecurity Framework&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;CISA Zero Trust Maturity Model&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Microsoft security baselines&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;Flags misconfigurations and policy gaps.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H6&gt;3. Risk Scoring &amp;amp; Prioritization&lt;/H6&gt;
&lt;UL&gt;
&lt;LI&gt;Assigns &lt;STRONG&gt;risk levels&lt;/STRONG&gt; based on:
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Impact&lt;/STRONG&gt; (how critical the gap is)&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Effort&lt;/STRONG&gt; (complexity of remediation)&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;Provides a &lt;STRONG&gt;prioritized list of actions&lt;/STRONG&gt; so you can focus on what matters most.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H6&gt;4. Actionable Recommendations&lt;/H6&gt;
&lt;UL&gt;
&lt;LI&gt;Generates &lt;STRONG&gt;clear remediation steps &lt;/STRONG&gt;not vague advice.&lt;/LI&gt;
&lt;LI&gt;Links to &lt;STRONG&gt;Microsoft Learn&lt;/STRONG&gt; and &lt;STRONG&gt;security documentation&lt;/STRONG&gt; for quick implementation.&lt;/LI&gt;
&lt;LI&gt;Suggests &lt;STRONG&gt;policy templates&lt;/STRONG&gt; and &lt;STRONG&gt;automation scripts&lt;/STRONG&gt; where applicable.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H6&gt;5. Comprehensive Reporting&lt;/H6&gt;
&lt;UL&gt;
&lt;LI&gt;Delivers a &lt;STRONG&gt;detailed report&lt;/STRONG&gt; with:
&lt;UL&gt;
&lt;LI&gt;Trends over time&lt;/LI&gt;
&lt;LI&gt;Risk heatmaps&lt;/LI&gt;
&lt;LI&gt;Compliance scores&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;Enables &lt;STRONG&gt;executive dashboards&lt;/STRONG&gt; for leadership visibility.&lt;/LI&gt;
&lt;/UL&gt;
&lt;img /&gt;&lt;img /&gt;&lt;img /&gt;
&lt;H5&gt;&lt;STRONG&gt;Integration with Microsoft Security Tools&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;Zero Trust Assessment v2 doesn’t operate in isolation it integrates seamlessly with Microsoft’s security ecosystem:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Microsoft Defender for Endpoint&lt;/STRONG&gt;&lt;BR /&gt;Detects device vulnerabilities and feeds compliance data into the assessment.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Microsoft Intune&lt;/STRONG&gt;&lt;BR /&gt;Ensures device configuration policies align with Zero Trust principles.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Microsoft Sentinel&lt;/STRONG&gt;&lt;BR /&gt;Correlates assessment findings with threat intelligence for proactive incident response.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Azure AD Conditional Access&lt;/STRONG&gt;&lt;BR /&gt;Validates identity policies like MFA and session controls.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Microsoft Purview&lt;/STRONG&gt;&lt;BR /&gt;Extends Zero Trust to data governance and compliance.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This integration ensures that remediation steps can be &lt;STRONG&gt;automated and enforced&lt;/STRONG&gt; across your environment, reducing manual effort and accelerating security posture improvement.&lt;/P&gt;
&lt;H5&gt;&lt;STRONG&gt;Sample Remediation Workflow Diagram&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;Below is a simplified view of how remediation flows after an assessment:&lt;/P&gt;
&lt;img /&gt;
&lt;P&gt;This closed-loop process ensures &lt;STRONG&gt;continuous improvement&lt;/STRONG&gt; and &lt;STRONG&gt;operationalization of Zero Trust&lt;/STRONG&gt;.&lt;/P&gt;
&lt;H5&gt;&lt;STRONG&gt;Key Benefits&lt;/STRONG&gt;&lt;/H5&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Speed&lt;/STRONG&gt;: Automates what used to take weeks of manual audits.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Accuracy&lt;/STRONG&gt;: Aligns with global standards and Microsoft’s own security posture.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Operationalization&lt;/STRONG&gt;: Moves Zero Trust from theory to practice with actionable steps.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Future-Ready&lt;/STRONG&gt;: Tests will soon be available enabling continuous improvement.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H5&gt;&lt;STRONG&gt;Why This Matters&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;Blind spots in identity or device security can lead to breaches, financial loss and reputational damage.&lt;/P&gt;
&lt;P&gt;Zero Trust Assessment v2 helps you:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Respond faster&lt;/STRONG&gt; to evolving threats.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Reduce risk&lt;/STRONG&gt; with prioritized remediation.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Build resilience&lt;/STRONG&gt; by embedding Zero Trust principles into daily operations.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Nov 2025 11:40:35 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/microsoft-zero-trust-assessment-v2-operationalizing-security/m-p/4470949#M541</guid>
      <dc:creator>umamasurkar28</dc:creator>
      <dc:date>2025-11-18T11:40:35Z</dc:date>
    </item>
    <item>
      <title>Microsoft 365 Apps for Enterprise Security Baseline 2412; when available?</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/microsoft-365-apps-for-enterprise-security-baseline-2412-when/m-p/4465964#M540</link>
      <description>&lt;P&gt;&lt;A class="lia-external-url" href="https://learn.microsoft.com/en-us/intune/intune-service/protect/security-baseline-v2-office-settings?pivots=v2306" target="_blank"&gt;Version 2306&lt;/A&gt; is currently available in Intune. Microsoft already &lt;A class="lia-internal-link lia-internal-url lia-internal-url-content-type-blog" href="https://techcommunity.microsoft.com/blog/microsoft-security-baselines/security-baseline-for-m365-apps-for-enterprise-v2412/4357320" data-lia-auto-title="released the 2412 version via the Microsoft Security Compliance Toolkit" data-lia-auto-title-active="0" target="_blank"&gt;released the 2412 version via the Microsoft Security Compliance Toolkit&lt;/A&gt;. Unfortunately, this version is not available in Intune nyet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When can we expect that version to become available in Intune?&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2025 12:49:53 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/microsoft-365-apps-for-enterprise-security-baseline-2412-when/m-p/4465964#M540</guid>
      <dc:creator>mvuem</dc:creator>
      <dc:date>2025-10-31T12:49:53Z</dc:date>
    </item>
    <item>
      <title>DSC SecurityPolicyDsc: "Could not infer CimType from the provided .NET object"</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/dsc-securitypolicydsc-quot-could-not-infer-cimtype-from-the/m-p/4404937#M523</link>
      <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;&lt;P&gt;I'm encountering a persistent issue while applying security baseline settings using the SecurityPolicyDsc module on Windows Server 2022. Despite providing valid settings (like Accounts_Limit_local_account_use_of_blank_passwords_to_console_logon_only = 'Enabled'), the DSC execution fails with the following error:&lt;/P&gt;&lt;P&gt;Could not infer CimType from the provided .NET object. The PowerShell DSC resource '[SecurityOption]LimitBlankPasswords' with SourceInfo '&amp;lt;file path&amp;gt;::SecurityOption' threw one or more non-terminating errors while running the Test-TargetResource functionality.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What I've done so far:&lt;/STRONG&gt;&lt;BR /&gt;Verified the syntax and parameters using only one setting at a time&lt;BR /&gt;Downgraded SecurityPolicyDsc to 2.9.0.0 (as 2.10.0.0 has known CimType issues)&lt;BR /&gt;Confirmed MSFT_SecurityOption.schema.mof exists in the module directory&lt;BR /&gt;Ensured no null or invalid values are passed&lt;BR /&gt;Used explicit paths in Start-DscConfiguration&lt;BR /&gt;Ran under PowerShell 5.1 on Windows Server 2022 (Azure VM, domain-joined)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Despite all this, the error persists — even for a minimal configuration like:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Configuration SecurityTest { Import-DscResource -ModuleName 'SecurityPolicyDsc' Node 'localhost' { SecurityOption LimitBlankPasswords { Name = 'LimitBlankPasswords' Accounts_Limit_local_account_use_of_blank_passwords_to_console_logon_only = 'Enabled' } } } SecurityTest -OutputPath "C:\Temp\SecurityTest" Start-DscConfiguration -Path "C:\Temp\SecurityTest" -Wait -Verbose -Force&lt;/P&gt;&lt;P&gt;Any guidance or workarounds would be greatly appreciated. If there’s a known fix or update planned for SecurityPolicyDsc, I’d be happy to test that as well.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Wed, 16 Apr 2025 16:41:23 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/dsc-securitypolicydsc-quot-could-not-infer-cimtype-from-the/m-p/4404937#M523</guid>
      <dc:creator>skybit9</dc:creator>
      <dc:date>2025-04-16T16:41:23Z</dc:date>
    </item>
    <item>
      <title>Edge Security Baseline v128 - Dynamic Code Setting</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/edge-security-baseline-v128-dynamic-code-setting/m-p/4403103#M513</link>
      <description>&lt;P&gt;Cross-posted this in the annoucement for v128 and the review of v134...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Enabling the Dynamic Code Settings "Enabled:Prevent the browser process from creating dynamic code" breaks printing to network printers in Active Directory.&amp;nbsp; Edge tries to generate the print preview page, and hangs.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2025 18:02:32 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/edge-security-baseline-v128-dynamic-code-setting/m-p/4403103#M513</guid>
      <dc:creator>Casey_S</dc:creator>
      <dc:date>2025-04-10T18:02:32Z</dc:date>
    </item>
    <item>
      <title>Microsoft Policy Analyzer 4.0 crashes after apply April updates</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/microsoft-policy-analyzer-4-0-crashes-after-apply-april-updates/m-p/4402940#M511</link>
      <description>&lt;P&gt;Good morning community !!&lt;BR /&gt;&lt;BR /&gt;After apply security/.NET patches corresponding to April, the policy analyzer is not working anymore...&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;img /&gt;&lt;P&gt;On details&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;See the end of this message for details on invoking&amp;nbsp;&lt;BR /&gt;just-in-time (JIT) debugging instead of this dialog box.&lt;/P&gt;&lt;P&gt;************** Exception Text **************&lt;BR /&gt;Deleted because system do not permit to publish it&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;************** Loaded Assemblies **************&lt;BR /&gt;mscorlib&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Assembly Version: 4.0.0.0&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Win32 Version: 4.8.9032.0 built by: NET481REL1&lt;BR /&gt;&amp;nbsp; &amp;nbsp; CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll&lt;BR /&gt;----------------------------------------&lt;BR /&gt;PolicyAnalyzer&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Assembly Version: 4.0.2004.13001&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Win32 Version: 4.0.2004.13001&lt;BR /&gt;&amp;nbsp; &amp;nbsp; CodeBase: file:///C:/Personal/PolicyAnalyzer/PolicyAnalyzer/PolicyAnalyzer_40/PolicyAnalyzer.exe&lt;BR /&gt;----------------------------------------&lt;BR /&gt;System.Windows.Forms&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Assembly Version: 4.0.0.0&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Win32 Version: 4.8.9032.0 built by: NET481REL1&lt;BR /&gt;&amp;nbsp; &amp;nbsp; CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll&lt;BR /&gt;----------------------------------------&lt;BR /&gt;System&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Assembly Version: 4.0.0.0&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Win32 Version: 4.8.9032.0 built by: NET481REL1&lt;BR /&gt;&amp;nbsp; &amp;nbsp; CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll&lt;BR /&gt;----------------------------------------&lt;BR /&gt;System.Drawing&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Assembly Version: 4.0.0.0&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Win32 Version: 4.8.9032.0 built by: NET481REL1&lt;BR /&gt;&amp;nbsp; &amp;nbsp; CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll&lt;BR /&gt;----------------------------------------&lt;BR /&gt;System.Configuration&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Assembly Version: 4.0.0.0&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Win32 Version: 4.8.9032.0 built by: NET481REL1&lt;BR /&gt;&amp;nbsp; &amp;nbsp; CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll&lt;BR /&gt;----------------------------------------&lt;BR /&gt;System.Xml&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Assembly Version: 4.0.0.0&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Win32 Version: 4.8.9032.0 built by: NET481REL1&lt;BR /&gt;&amp;nbsp; &amp;nbsp; CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll&lt;BR /&gt;----------------------------------------&lt;BR /&gt;Accessibility&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Assembly Version: 4.0.0.0&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Win32 Version: 4.8.9032.0 built by: NET481REL1&lt;BR /&gt;&amp;nbsp; &amp;nbsp; CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll&lt;BR /&gt;----------------------------------------&lt;BR /&gt;System.Core&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Assembly Version: 4.0.0.0&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Win32 Version: 4.8.9032.0 built by: NET481REL1&lt;BR /&gt;&amp;nbsp; &amp;nbsp; CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll&lt;BR /&gt;----------------------------------------&lt;/P&gt;&lt;P&gt;************** JIT Debugging **************&lt;BR /&gt;To enable just-in-time (JIT) debugging, the .config file for this&lt;BR /&gt;application or computer (machine.config) must have the&lt;BR /&gt;jitDebugging value set in the system.windows.forms section.&lt;BR /&gt;The application must also be compiled with debugging&lt;BR /&gt;enabled.&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;P&gt;&amp;lt;configuration&amp;gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;lt;system.windows.forms jitDebugging="true" /&amp;gt;&lt;BR /&gt;&amp;lt;/configuration&amp;gt;&lt;/P&gt;&lt;P&gt;When JIT debugging is enabled, any unhandled exception&lt;BR /&gt;will be sent to the JIT debugger registered on the computer&lt;BR /&gt;rather than be handled by this dialog box.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;It was working fine since patching apply.&lt;/P&gt;&lt;P&gt;I tried to uninstall patches, but the error still remains&lt;/P&gt;&lt;P&gt;Any clue to fix this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you !!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2025 11:01:57 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/microsoft-policy-analyzer-4-0-crashes-after-apply-april-updates/m-p/4402940#M511</guid>
      <dc:creator>AngelParedero23</dc:creator>
      <dc:date>2025-04-10T11:01:57Z</dc:date>
    </item>
    <item>
      <title>Edge security baseline for MS Edge management service</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/edge-security-baseline-for-ms-edge-management-service/m-p/4399049#M510</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;Do you plan and when to release directly the &lt;STRONG&gt;security baseline for Edge&lt;/STRONG&gt; as a &lt;STRONG&gt;configuration profile &lt;/STRONG&gt;to be imported into &lt;STRONG&gt;Microsoft Edge management service&lt;/STRONG&gt; ?&lt;BR /&gt;Thanks and regards&lt;/P&gt;</description>
      <pubDate>Mon, 31 Mar 2025 09:46:17 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/edge-security-baseline-for-ms-edge-management-service/m-p/4399049#M510</guid>
      <dc:creator>s_emangard</dc:creator>
      <dc:date>2025-03-31T09:46:17Z</dc:date>
    </item>
    <item>
      <title>DSC Error for 2022 Security Baseline</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/dsc-error-for-2022-security-baseline/m-p/4397752#M509</link>
      <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;&lt;P&gt;I am trying to find out more about this error but no luck.......&lt;/P&gt;&lt;P&gt;I have converted the GPOs to DSC for Windows Server 2022 - Member Server using Windows Server-2022-Security-Baseline-FINAL and have applied it to a test VM which is currently domain joined, initially I was getting too many dsc errors so I tried to narrow down and do a small batch of configurations and I still get the same error with the following message&lt;BR /&gt;&lt;BR /&gt;DSC Error : Could not infer CimType from the provided .NET object.&lt;BR /&gt;The PowerShell DSC resource '[SecurityOption]SecuritySetting(INF): LSAAnonymousNameLookup' with SourceInfo 'C:\onedsc\PasswordComplexityConfig.ps1::33::9::SecurityOption' threw one or more non-terminating errors while running the Test-TargetResource functionality. These errors are logged to the ETW channel called Microsoft-Windows-DSC/Operational. Refer to this channel for more details.&lt;BR /&gt;Could not infer CimType from the provided .NET object.&lt;BR /&gt;&lt;BR /&gt;Does anyone have any insight what could be wrong here?and how do I go about correcting it&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 27 Mar 2025 00:14:57 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/dsc-error-for-2022-security-baseline/m-p/4397752#M509</guid>
      <dc:creator>Deleted</dc:creator>
      <dc:date>2025-03-27T00:14:57Z</dc:date>
    </item>
    <item>
      <title>Security Baseline for Server 2025 is missing ADMX/ADML files?</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-for-server-2025-is-missing-admx-adml-files/m-p/4377447#M501</link>
      <description>&lt;P&gt;I imported the new "Windows Server 2025 Security Baseline" into our AD using Baseline-ADImport.ps1. Not a problem.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;From the "Templates" folder, I copied the SecGuide.admx and MSS-Legacy.admx files, along with the en-US folder to our central store in SYSVOL, as normal (backed upp the files I replace first).&lt;/P&gt;&lt;P&gt;When checking the GPOs in Group Policy Management though, I see a lot of "Extra Registry Settings" which would indicate that its missing a admx/adml file or similar. I've verified that neither of the included files i copied includes anything about the missing registry settings.&lt;BR /&gt;&lt;BR /&gt;For MSFT Windows Server 2025 - Member Server, there is a whole list of Extra Registry Settings.&lt;BR /&gt;&lt;BR /&gt;What am I missing here?&lt;BR /&gt;&lt;BR /&gt;Software\Microsoft\Windows\CurrentVersion\Policies\System\KDC\Parameters\PKINITHashAlgorithmConfigurationEnabled 1&amp;nbsp;&lt;BR /&gt;Software\Microsoft\Windows\CurrentVersion\Policies\System\KDC\Parameters\PKINITSHA1 1&amp;nbsp;&lt;BR /&gt;Software\Microsoft\Windows\CurrentVersion\Policies\System\KDC\Parameters\PKINITSHA256 3&amp;nbsp;&lt;BR /&gt;Software\Microsoft\Windows\CurrentVersion\Policies\System\KDC\Parameters\PKINITSHA384 3&amp;nbsp;&lt;BR /&gt;Software\Microsoft\Windows\CurrentVersion\Policies\System\KDC\Parameters\PKINITSHA512 3&amp;nbsp;&lt;BR /&gt;Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\PKInitHashAlgorithmConfigurationEnabled 1&amp;nbsp;&lt;BR /&gt;Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\PKInitSHA1 1&amp;nbsp;&lt;BR /&gt;Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\PKInitSHA256 3&amp;nbsp;&lt;BR /&gt;Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\PKInitSHA384 3&amp;nbsp;&lt;BR /&gt;Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\PKInitSHA512 3&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows NT\Printers\RPC\ForceKerberosForRpc 0&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows NT\Printers\RPC\RpcProtocols 5&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\Bowser\EnableMailslots 0&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\LanmanServer\AuditClientDoesNotSupportEncryption 1&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\LanmanServer\AuditClientDoesNotSupportSigning 1&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\LanmanServer\AuditInsecureGuestLogon 1&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\LanmanServer\EnableAuthRateLimiter 1&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\LanmanServer\InvalidAuthenticationDelayTimeInMs 2000&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\LanmanServer\MinSmb2Dialect 768&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\LanmanWorkstation\AuditInsecureGuestLogon 1&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\LanmanWorkstation\AuditServerDoesNotSupportEncryption 1&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\LanmanWorkstation\AuditServerDoesNotSupportSigning 1&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\LanmanWorkstation\MinSmb2Dialect 768&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\NetworkProvider\EnableMailslots 0&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\System\AllowCustomSSPsAPs 1&amp;nbsp;&lt;BR /&gt;Software\Policies\Microsoft\Windows\System\RunAsPPL 1&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2025 12:56:23 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-for-server-2025-is-missing-admx-adml-files/m-p/4377447#M501</guid>
      <dc:creator>Turranius</dc:creator>
      <dc:date>2025-02-12T12:56:23Z</dc:date>
    </item>
    <item>
      <title>Confusing Naming of Intune M365 Apps Baseline</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/confusing-naming-of-intune-m365-apps-baseline/m-p/4377288#M499</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;To which Office Apps does the exisiting ( and only)"Microsoft 365 Apps for Enterprise Security Baseline"&amp;nbsp; apply to? Its says Version 2306When I create a profile I get this information within the baseline&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;img /&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So this baseline only applies to Office 2016? If yes, how do I protect the M365 Office Apps?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2025 09:00:11 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/confusing-naming-of-intune-m365-apps-baseline/m-p/4377288#M499</guid>
      <dc:creator>heinzelrumpel</dc:creator>
      <dc:date>2025-02-12T09:00:11Z</dc:date>
    </item>
    <item>
      <title>Server 2025 Security Baseline breaks Failover Cluster</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/server-2025-security-baseline-breaks-failover-cluster/m-p/4376008#M498</link>
      <description>&lt;P&gt;Hello everyone,&amp;nbsp;&lt;/P&gt;&lt;P&gt;while testing the Server 2025 Security Baseline with our Hyper-V Hosts in a Failover Cluster, we noticed the Cluster Service (ClusSvc) was unable to start correctly. It failed with Event 7024 - "A specified authentication package is unknown". From testing and the event logs, we noticed that the .dll file "CLUSAUTHMGR.DLL" was unable to load. After setting "&lt;EM&gt;Allow Custom SSPs and APs to be loaded into LSASS&lt;/EM&gt;" to "Disabled", we were able to start the service again. I assume that the cluster auth manager .dll is not recognized as a trusted Microsoft SSP/AP and therefore blocked as "custom" when enabling this setting.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone tested this using Hyper-V clusters and/or made similar observations?&lt;BR /&gt;&lt;BR /&gt;(P.S.: Before debugging, we should have googled, since apparently we are not the only one to have this issue: &lt;A href="https://jigsolving.com/failover-cluster-service-wont-start-server-2025/" target="_blank"&gt;Failover Cluster Service won’t start on Server 2025 | Jigsolving)&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Feb 2025 15:40:16 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/server-2025-security-baseline-breaks-failover-cluster/m-p/4376008#M498</guid>
      <dc:creator>PhilippZiemke</dc:creator>
      <dc:date>2025-02-10T15:40:16Z</dc:date>
    </item>
    <item>
      <title>How to Use Baselines Correctly as a Beginner</title>
      <link>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/how-to-use-baselines-correctly-as-a-beginner/m-p/4373020#M496</link>
      <description>&lt;P&gt;Hello everyone,&lt;BR /&gt;regarding baselines I am a beginner, I downloaded them yesterday for Windows 11 pro and tried to document myself to use them in the right way but I found fragmentary information around the web.&lt;BR /&gt;First I ran the script to install them as a standalone machine : PowerShell.exe -ExecutionPolicy RemoteSigned -File .\Baseline-LocalInstall.ps1 -Win11NonDomainJoined and everything was applied at least from what I read in the logs file.&lt;BR /&gt;The first question is, if I wanted to return to the starting situation then without the applied changes should I run the Remove-EPBaselineSettings.ps1 script without specifying any parameters?&lt;BR /&gt;Then I tried using the policy analyzer by feeding it the rules xslx file for Windows 11 and comparing with the current state.&amp;nbsp;&lt;BR /&gt;Would this already be enough to verify that indeed everything has been applied?&lt;BR /&gt;However, when I do the comparison I get an error message and a warning but then it still shows me the comparison.&lt;BR /&gt;Attached is the screenshot&lt;BR /&gt;Can you tell me if there is complete and detailed documentation on both the baselines and for the policy analyzer?&lt;BR /&gt;There are several options that I don't really understand so I haven't ventured to use.&lt;/P&gt;&lt;P&gt;Thanks to all&lt;/P&gt;&lt;img /&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 02 Feb 2025 10:39:11 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/microsoft-security-baselines/how-to-use-baselines-correctly-as-a-beginner/m-p/4373020#M496</guid>
      <dc:creator>Fabio_Danzetta</dc:creator>
      <dc:date>2025-02-02T10:39:11Z</dc:date>
    </item>
  </channel>
</rss>

