STIGQter STIGQter: STIG Summary:

Microsoft DotNet Framework 4.0 Security Technical Implementation Guide

Version: 2

Release: 1 Benchmark Date: 22 Jan 2021

SV-225223r615940_ruleDigital signatures assigned to strongly named assemblies must be verified.
SV-225224r615940_ruleThe Trust Providers Software Publishing State must be set to 0x23C00.
SV-225225r615940_ruleDeveloper certificates used with the .NET Publisher Membership Condition must be approved by the IAO.
SV-225226r615940_ruleEncryption keys used for the .NET Strong Name Membership Condition must be protected.
SV-225227r615940_ruleCAS and policy configuration files must be backed up.
SV-225228r615940_ruleRemoting Services HTTP channels must utilize authentication and encryption.
SV-225229r615940_rule.Net Framework versions installed on the system must be supported.
SV-225230r615940_ruleThe .NET CLR must be configured to use FIPS approved encryption modules.
SV-225231r615940_rule.NET must be configured to validate strong names on full-trust assemblies.
SV-225232r615940_rule.Net applications that invoke NetFx40_LegacySecurityPolicy must apply previous versions of .NET STIG guidance.
SV-225233r615940_ruleTrust must be established prior to enabling the loading of remote code in .Net 4.
SV-225234r615940_rule.NET default proxy settings must be reviewed and approved.
SV-225235r615940_ruleEvent tracing for Windows (ETW) for Common Language Runtime events must be enabled.
SV-225236r615940_ruleSoftware utilizing .Net 4.0 must be identified and relevant access controls configured.
SV-225237r615940_ruleRemoting Services TCP channels must utilize authentication and encryption.
SV-225238r615940_ruleDisable TLS RC4 cipher in .Net