| Vuln ID | Severity | Asset | STIG | Title | Status | Doc Status | Assigned To | Actions |
|---|---|---|---|---|---|---|---|---|
| V-225223 | CAT II | MONT-WS-92040 | Microsoft DotNet Framework 4.0 Security ... | Digital signatures assigned to strongly named asse... | - | |||
Check TextUse regedit to review the Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. If the StrongName\Verification key does not exist, this is not a finding. If there are assemblies or hash values listed in this key, each value represents a distinct application assembly that does not have the application strong name verified. If any assemblies are listed as omitting strong name verification in a production environment, this is a finding. If any assemblies are listed as omitting strong name verification in a development or test environment and the IAO has not provided documented approvals, this is a finding. Fix TextUse regedit to remove the values stored in Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. All assemblies must require strong name verification in a production environment. Strong name assemblies that do not require verification in a development or test environment must have documented approvals from the IAO. Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT A FINDING on 10/23/2025 ResultHash: 540AD243F46DB5DD820AEE05A8F5EADCA3474F69 ~~~~~ HKLM:\SOFTWARE\Microsoft\StrongName\Verification does not exist
Source: _Reviewed/MONT-WS-92040/Checklist/MONT-WS-92040_DotNET4_V2R7_20251023-142306.ckl
Scan Date: 2026-01-14T12:57:25.530570
Technology Area: Windows Operating System
|
||||||||
| V-225223 | CAT II | MONT-WS-92010 | Microsoft DotNet Framework 4.0 Security ... | Digital signatures assigned to strongly named asse... | - | |||
Check TextUse regedit to review the Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. If the StrongName\Verification key does not exist, this is not a finding. If there are assemblies or hash values listed in this key, each value represents a distinct application assembly that does not have the application strong name verified. If any assemblies are listed as omitting strong name verification in a production environment, this is a finding. If any assemblies are listed as omitting strong name verification in a development or test environment and the IAO has not provided documented approvals, this is a finding. Fix TextUse regedit to remove the values stored in Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. All assemblies must require strong name verification in a production environment. Strong name assemblies that do not require verification in a development or test environment must have documented approvals from the IAO. Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT A FINDING on 10/23/2025 ResultHash: 540AD243F46DB5DD820AEE05A8F5EADCA3474F69 ~~~~~ HKLM:\SOFTWARE\Microsoft\StrongName\Verification does not exist
Source: _Reviewed/MONT-WS-92010/Checklist/MONT-WS-92010_DotNET4_V2R7_20251023-141005.ckl
Scan Date: 2026-01-14T12:57:27.786540
Technology Area: Windows Operating System
|
||||||||
| V-225223 | CAT II | MONT-VSF-004 | Microsoft DotNet Framework 4.0 Security ... | Digital signatures assigned to strongly named asse... | - | |||
Check TextUse regedit to review the Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. If the StrongName\Verification key does not exist, this is not a finding. If there are assemblies or hash values listed in this key, each value represents a distinct application assembly that does not have the application strong name verified. If any assemblies are listed as omitting strong name verification in a production environment, this is a finding. If any assemblies are listed as omitting strong name verification in a development or test environment and the IAO has not provided documented approvals, this is a finding. Fix TextUse regedit to remove the values stored in Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. All assemblies must require strong name verification in a production environment. Strong name assemblies that do not require verification in a development or test environment must have documented approvals from the IAO. Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT A FINDING on 10/23/2025 ResultHash: 540AD243F46DB5DD820AEE05A8F5EADCA3474F69 ~~~~~ HKLM:\SOFTWARE\Microsoft\StrongName\Verification does not exist
Source: _Reviewed/MONT-VSF-004/Checklist/MONT-VSF-004_DotNET4_V2R7_20251023-143711.ckl
Scan Date: 2026-01-14T12:57:29.485524
Technology Area: Windows Operating System
|
||||||||
| V-225223 | CAT II | MONT-VSF-003 | Microsoft DotNet Framework 4.0 Security ... | Digital signatures assigned to strongly named asse... | - | |||
Check TextUse regedit to review the Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. If the StrongName\Verification key does not exist, this is not a finding. If there are assemblies or hash values listed in this key, each value represents a distinct application assembly that does not have the application strong name verified. If any assemblies are listed as omitting strong name verification in a production environment, this is a finding. If any assemblies are listed as omitting strong name verification in a development or test environment and the IAO has not provided documented approvals, this is a finding. Fix TextUse regedit to remove the values stored in Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. All assemblies must require strong name verification in a production environment. Strong name assemblies that do not require verification in a development or test environment must have documented approvals from the IAO. Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT A FINDING on 10/23/2025 ResultHash: 540AD243F46DB5DD820AEE05A8F5EADCA3474F69 ~~~~~ HKLM:\SOFTWARE\Microsoft\StrongName\Verification does not exist
Source: _Reviewed/MONT-VSF-003/Checklist/MONT-VSF-003_DotNET4_V2R7_20251023-143732.ckl
Scan Date: 2026-01-14T12:57:30.918773
Technology Area: Windows Operating System
|
||||||||
| V-225223 | CAT II | MONT-MB-002 | Microsoft DotNet Framework 4.0 Security ... | Digital signatures assigned to strongly named asse... | - | |||
Check TextUse regedit to review the Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. If the StrongName\Verification key does not exist, this is not a finding. If there are assemblies or hash values listed in this key, each value represents a distinct application assembly that does not have the application strong name verified. If any assemblies are listed as omitting strong name verification in a production environment, this is a finding. If any assemblies are listed as omitting strong name verification in a development or test environment and the IAO has not provided documented approvals, this is a finding. Fix TextUse regedit to remove the values stored in Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. All assemblies must require strong name verification in a production environment. Strong name assemblies that do not require verification in a development or test environment must have documented approvals from the IAO. Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT A FINDING on 10/23/2025 ResultHash: B3CB706A6ADDE1748C32DB756BC478CBF6005E4B ~~~~~ HKLM:\SOFTWARE\Microsoft\StrongName\Verification exists but no values were found within.
Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_DotNET4_V2R7_20251023-152339.ckl
Scan Date: 2026-01-14T12:57:32.355929
Technology Area: Windows Operating System
|
||||||||
| V-225223 | CAT II | MONT-DP-001 | Microsoft DotNet Framework 4.0 Security ... | Digital signatures assigned to strongly named asse... | - | |||
Check TextUse regedit to review the Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. If the StrongName\Verification key does not exist, this is not a finding. If there are assemblies or hash values listed in this key, each value represents a distinct application assembly that does not have the application strong name verified. If any assemblies are listed as omitting strong name verification in a production environment, this is a finding. If any assemblies are listed as omitting strong name verification in a development or test environment and the IAO has not provided documented approvals, this is a finding. Fix TextUse regedit to remove the values stored in Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. All assemblies must require strong name verification in a production environment. Strong name assemblies that do not require verification in a development or test environment must have documented approvals from the IAO. Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT A FINDING on 10/23/2025 ResultHash: 540AD243F46DB5DD820AEE05A8F5EADCA3474F69 ~~~~~ HKLM:\SOFTWARE\Microsoft\StrongName\Verification does not exist
Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_DotNET4_V2R7_20251023-143731.ckl
Scan Date: 2026-01-14T12:57:34.683670
Technology Area: Windows Operating System
|
||||||||
| V-225223 | CAT II | MONT-DC-003 | Microsoft DotNet Framework 4.0 Security ... | Digital signatures assigned to strongly named asse... | - | |||
Check TextUse regedit to review the Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. If the StrongName\Verification key does not exist, this is not a finding. If there are assemblies or hash values listed in this key, each value represents a distinct application assembly that does not have the application strong name verified. If any assemblies are listed as omitting strong name verification in a production environment, this is a finding. If any assemblies are listed as omitting strong name verification in a development or test environment and the IAO has not provided documented approvals, this is a finding. Fix TextUse regedit to remove the values stored in Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. All assemblies must require strong name verification in a production environment. Strong name assemblies that do not require verification in a development or test environment must have documented approvals from the IAO. Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT A FINDING on 10/23/2025 ResultHash: 540AD243F46DB5DD820AEE05A8F5EADCA3474F69 ~~~~~ HKLM:\SOFTWARE\Microsoft\StrongName\Verification does not exist
Source: _Reviewed/MONT-DC-003/Checklist/MONT-DC-003_DotNET4_V2R7_20251023-171946.ckl
Scan Date: 2026-01-14T12:57:36.663331
Technology Area: Windows Operating System
|
||||||||
| V-225223 | CAT II | MONT-DB-002 | Microsoft DotNet Framework 4.0 Security ... | Digital signatures assigned to strongly named asse... | - | |||
Check TextUse regedit to review the Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. If the StrongName\Verification key does not exist, this is not a finding. If there are assemblies or hash values listed in this key, each value represents a distinct application assembly that does not have the application strong name verified. If any assemblies are listed as omitting strong name verification in a production environment, this is a finding. If any assemblies are listed as omitting strong name verification in a development or test environment and the IAO has not provided documented approvals, this is a finding. Fix TextUse regedit to remove the values stored in Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. All assemblies must require strong name verification in a production environment. Strong name assemblies that do not require verification in a development or test environment must have documented approvals from the IAO. Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT A FINDING on 10/23/2025 ResultHash: 540AD243F46DB5DD820AEE05A8F5EADCA3474F69 ~~~~~ HKLM:\SOFTWARE\Microsoft\StrongName\Verification does not exist
Source: _Reviewed/MONT-DB-002/Checklist/MONT-DB-002_DotNET4_V2R7_20251023-143930.ckl
Scan Date: 2026-01-14T12:57:38.504147
Technology Area: Windows Operating System
|
||||||||
| V-225223 | CAT II | MONT-BE-002 | Microsoft DotNet Framework 4.0 Security ... | Digital signatures assigned to strongly named asse... | - | |||
Check TextUse regedit to review the Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. If the StrongName\Verification key does not exist, this is not a finding. If there are assemblies or hash values listed in this key, each value represents a distinct application assembly that does not have the application strong name verified. If any assemblies are listed as omitting strong name verification in a production environment, this is a finding. If any assemblies are listed as omitting strong name verification in a development or test environment and the IAO has not provided documented approvals, this is a finding. Fix TextUse regedit to remove the values stored in Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. All assemblies must require strong name verification in a production environment. Strong name assemblies that do not require verification in a development or test environment must have documented approvals from the IAO. Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT A FINDING on 10/23/2025 ResultHash: 540AD243F46DB5DD820AEE05A8F5EADCA3474F69 ~~~~~ HKLM:\SOFTWARE\Microsoft\StrongName\Verification does not exist
Source: _Reviewed/MONT-BE-002/Checklist/MONT-BE-002_DotNET4_V2R7_20251023-143746.ckl
Scan Date: 2026-01-14T12:57:39.853926
Technology Area: Windows Operating System
|
||||||||
| V-225223 | CAT II | MONT-AP-002 | Microsoft DotNet Framework 4.0 Security ... | Digital signatures assigned to strongly named asse... | - | |||
Check TextUse regedit to review the Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. If the StrongName\Verification key does not exist, this is not a finding. If there are assemblies or hash values listed in this key, each value represents a distinct application assembly that does not have the application strong name verified. If any assemblies are listed as omitting strong name verification in a production environment, this is a finding. If any assemblies are listed as omitting strong name verification in a development or test environment and the IAO has not provided documented approvals, this is a finding. Fix TextUse regedit to remove the values stored in Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. All assemblies must require strong name verification in a production environment. Strong name assemblies that do not require verification in a development or test environment must have documented approvals from the IAO. Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT A FINDING on 10/23/2025 ResultHash: 540AD243F46DB5DD820AEE05A8F5EADCA3474F69 ~~~~~ HKLM:\SOFTWARE\Microsoft\StrongName\Verification does not exist
Source: _Reviewed/MONT-AP-002/Checklist/MONT-AP-002_DotNET4_V2R7_20251023-144010.ckl
Scan Date: 2026-01-14T12:57:42.156893
Technology Area: Windows Operating System
|
||||||||
| V-225223 | CAT II | MONT-SW-89108 | Microsoft DotNet Framework 4.0 Security ... | Digital signatures assigned to strongly named asse... | - | |||
Check TextUse regedit to review the Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. If the StrongName\Verification key does not exist, this is not a finding. If there are assemblies or hash values listed in this key, each value represents a distinct application assembly that does not have the application strong name verified. If any assemblies are listed as omitting strong name verification in a production environment, this is a finding. If any assemblies are listed as omitting strong name verification in a development or test environment and the IAO has not provided documented approvals, this is a finding. Fix TextUse regedit to remove the values stored in Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. All assemblies must require strong name verification in a production environment. Strong name assemblies that do not require verification in a development or test environment must have documented approvals from the IAO. Finding DetailsEvaluate-STIG 1.2510.0 (Scan-NETFramework4_Checks) found this to be NOT A FINDING on 12/17/2025 ResultHash: 540AD243F46DB5DD820AEE05A8F5EADCA3474F69 ~~~~~ HKLM:\SOFTWARE\Microsoft\StrongName\Verification does not exist
Source: MONT-SW-89108_DotNET4_V2R7_20251217-202821.ckl
Scan Date: 2026-03-04T15:25:15.828600
Technology Area: Windows Operating System
|
||||||||
| V-225223 | CAT II | MONT-SW-89134 | Microsoft DotNet Framework 4.0 Security ... | Digital signatures assigned to strongly named asse... | - | |||
Check TextUse regedit to review the Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. If the StrongName\Verification key does not exist, this is not a finding. If there are assemblies or hash values listed in this key, each value represents a distinct application assembly that does not have the application strong name verified. If any assemblies are listed as omitting strong name verification in a production environment, this is a finding. If any assemblies are listed as omitting strong name verification in a development or test environment and the IAO has not provided documented approvals, this is a finding. Fix TextUse regedit to remove the values stored in Windows registry key HKLM\Software\Microsoft\StrongName\Verification. There should be no assemblies or hash values listed under this registry key. All assemblies must require strong name verification in a production environment. Strong name assemblies that do not require verification in a development or test environment must have documented approvals from the IAO. Finding DetailsEvaluate-STIG 1.2510.0 (Scan-NETFramework4_Checks) found this to be NOT A FINDING on 12/17/2025 ResultHash: 540AD243F46DB5DD820AEE05A8F5EADCA3474F69 ~~~~~ HKLM:\SOFTWARE\Microsoft\StrongName\Verification does not exist
Source: MONT-SW-89134_DotNET4_V2R7_20251217-201000.ckl
Scan Date: 2026-03-04T15:25:41.864254
Technology Area: Windows Operating System
|
||||||||