APPNET0052 - Encryption keys used for the .NET Strong Name Membership Condition must be protected.


The Strong Name Membership condition requires that member assemblies be defined with Strong Names. 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. If assemblies do not have a strong name assigned, the assembly cannot be unique and the author of the code cannot be uniquely identified. In order to create the strong name, the developer must use a cryptographic key pair to sign the assembly. If the developer does not protect the key, the key can be stolen and used to sign any application, including malware applications. This could adversely affect application integrity and confidentiality.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.


Ask the Systems Programmer how the private keys used to sign the assembly are protected.

Private keys are simply values stored as strings of data. Keys can be stored in files on the file system or in a centralized data repository.

Adequate protection methods include, but are not limited to:

- utilizing centralized key management;
- using strict file permissions to limit access; and
- tying strong pass phrases to the key.

The private key(s) used to sign the assembly must be protected. Utilize centralized key management or strict file permissions along with strong pass phrases and/or other well established industry practices for managing and controlling access to private keys.

See Also

Item Details


References: 800-53|IA-5(2)(b), CAT|II, CCI|CCI-000186, Rule-ID|SV-225226r615940_rule, STIG-ID|APPNET0052, STIG-Legacy|SV-7450, STIG-Legacy|V-7067, Vuln-ID|V-225226

Plugin: Windows

Control ID: a762a61e06b9ebf9d2d519d6784bec958cc1f799fcd377dec065cae1f6616cb0