Digital signatures assigned to strongly named assemblies must be verified.
An XCCDF Rule
Description
A strong name consists of the assembly's identity, simple text name, version number, and culture information (if provided)—plus a public key and a digital signature. Strong names serve to identify the author of the code. If digital signatures used to sign strong name assemblies are not verified, any self signed code can be impersonated. This can lead to a loss of system integrity.
- ID
- SV-225223r961038_rule
- Version
- APPNET0031
- Severity
- Medium
- References
- Updated
Remediation Templates
A Manual Procedure
Use 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.