| Finding ID |
Severity |
Title |
Description |
|
V-225238
|
Medium |
Disable TLS RC4 cipher in .Net |
Use of the RC4 cipher in TLS could allow an attacker to perform man-in-the-middle attacks and recover plaintext from encrypted sessions. Applications that target .Net version 4.x running on multiple Windows versions could be vulnerable to these types of attacks. The registry settings in this requirement will prevent .Net applications... |
|
V-225237
|
Medium |
Remoting Services TCP channels must utilize authentication and encryption. |
Note: Microsoft recommends using the Windows Communication Framework (WCF) rather than .Net remoting. New development projects should refrain from using .Net remoting capabilities whenever possible.
.NET remoting provides the capability to build widely distributed applications. The application components may reside all on one computer or they may be spread out... |
|
V-225236
|
Medium |
Software utilizing .Net 4.0 must be identified and relevant access controls configured. |
With the advent of .Net 4.0, the .Net framework no longer directly configures or enforces security policy for .Net applications. This task is now relegated to the operating system layer and the security protections built-in to .Net application "runtime hosts" that run on the O.S.
Examples of these .Net "runtime... |
|
V-225235
|
Medium |
Event tracing for Windows (ETW) for Common Language Runtime events must be enabled. |
Event tracing captures information about applications utilizing the .NET CLR and the .NET CLR itself. This includes security oriented information, such as Strong Name and Authenticode verification.
Beginning with Windows Vista, ETW is enabled by default however, the .Net CLR and .Net applications can be configured to not utilize Event... |
|
V-225233
|
Medium |
Trust must be established prior to enabling the loading of remote code in .Net 4. |
|
|
V-225231
|
Medium |
.NET must be configured to validate strong names on full-trust assemblies. |
The "bypassTrustedAppStrongNames" setting specifies whether the bypass feature that avoids validating strong names for full-trust assemblies is enabled. By default the bypass feature is enabled in .Net 4, therefore strong names are not validated for correctness when the assembly/program is loaded. Not validating strong names provides a faster application load... |
|
V-225230
|
Medium |
The .NET CLR must be configured to use FIPS approved encryption modules. |
|
|
V-225229
|
Medium |
.Net Framework versions installed on the system must be supported. |
Unsupported software introduces risks and violates DoD policy. Applications utilizing unsupported versions of .NET introduce substantial risk to the host, network, and the enclave by virtue of the fact they leverage an architecture that is no longer updated by the vendor. This introduces potential application integrity, availability, or confidentiality issues. |
|
V-225228
|
Medium |
Remoting Services HTTP channels must utilize authentication and encryption. |
Note: Microsoft recommends using the Windows Communication Framework (WCF) rather than using .Net remoting. New development projects should refrain from using .Net remoting capabilities whenever possible.
.NET remoting provides the capability to build widely distributed applications. The application components may reside all on one computer or they may be spread... |
|
V-225227
|
Medium |
CAS and policy configuration files must be backed up. |
A successful disaster recovery plan requires that CAS policy and CAS policy configuration files are identified and included in systems disaster backup and recovery events. Documentation regarding the location of system and application specific CAS policy configuration files and the frequency in which backups occur is required. If these files... |
|
V-225226
|
Medium |
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,... |
|
V-225225
|
Medium |
Developer certificates used with the .NET Publisher Membership Condition must be approved by the ISSO. |
A .Net assembly will satisfy the Publisher Membership Condition if it is signed with a software publisher’s Authenticode X.509v3 digital certificate that can be verified by the Windows operating system as having a chain of trust that leads to a trusted root certificate stored in the user’s certificate store. The... |
|
V-225224
|
Medium |
The Trust Providers Software Publishing State must be set to 0x23C00. |
Microsoft Windows operating systems provide a feature called Authenticode. Authenticode technology and its underlying code signing mechanisms serve to provide a structure to identify software publishers and ensure that software applications have not been tampered with. Authenticode technology relies on digital certificates and is based on Public Key Cryptography Standards... |
|
V-225223
|
Medium |
Digital signatures assigned to strongly named assemblies must be verified. |
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... |
|
V-225234
|
Low |
.NET default proxy settings must be reviewed and approved. |
The .Net framework can be configured to utilize a different proxy or altogether bypass the default proxy settings in the client's browser. This may lead to the framework using a proxy that is not approved for use. If the proxy is malicious, this could lead to a loss of application... |
|
V-225232
|
Low |
.Net applications that invoke NetFx40_LegacySecurityPolicy must apply previous versions of .NET STIG guidance. |
CAS policy is .NET runtime version-specific. In .NET Framework version 4, CAS policy is disabled by default however; it can be re-enabled by using the NetFx40_LegacySecurityPolicy setting on a per application basis. Caspol.exe is provided by Microsoft to set security policy on .Net applications prior to version 4.0. This requirement... |
