From 581f3613bad2411bd122bdf22019f3a7625a321a Mon Sep 17 00:00:00 2001
From: mit-da <102551711+mit-da@users.noreply.github.com>
Date: Sun, 22 Feb 2026 00:57:14 -0500
Subject: [PATCH] Update security_policy.rb to fix casing issue breaking
 idempotency

It seems having having the incorrect casing for `LanManServer` in the `Microsoft network server: Server SPN target name validation level` policy is causing this policy to apply repeatedly even though it is set correctly. Specifically the name is currently `'MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\SmbServerNameHardeningLevel'` when it should be `'MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\SmbServerNameHardeningLevel'` like the rest of the values.

Verified this in our setup where before, it would show up during each puppet run, even though a quick pass at the registry value and secpol.msc showed it was set correctly. After this case change it now longer shows up.
---
 lib/puppet_x/lsp/security_policy.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/puppet_x/lsp/security_policy.rb b/lib/puppet_x/lsp/security_policy.rb
index e60c8ec..160bb7a 100644
--- a/lib/puppet_x/lsp/security_policy.rb
+++ b/lib/puppet_x/lsp/security_policy.rb
@@ -707,7 +707,7 @@ def self.lsp_mapping
         policy_type: 'Registry Values',
       },
       'Microsoft network server: Server SPN target name validation level' => {
-        name: 'MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\SmbServerNameHardeningLevel',
+        name: 'MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\SmbServerNameHardeningLevel',
         reg_type: '4',
         policy_type: 'Registry Values',
       },