Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
.NET must be configured to validate strong names on full-trust assemblies.
Description
Discussion Text
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 time but at the expense of performing certificate validation.
Full trust assemblies are .Net applications launched from the local host. Strong names are digital signatures tied to .Net applications/assemblies. .Net 4 considers applications installed locally to be fully trusted by default and grants these applications full permissions to access host resources.
The bypass feature applies to any assembly signed with a strong name and having the following characteristics:
Fully trusted without the StrongName evidence (for example, has MyComputer zone evidence).
Loaded into a fully trusted AppDomain.
Loaded from a location under the ApplicationBase property of that AppDomain.
Not delay-signed.
Not validating the certificates used to sign strong name assemblies will provide a faster application load time, but falsely assumes that signatures used to sign the application are to be implicitly trusted. Not validating strong name certificates introduces an integrity risk to the system.
Full trust assemblies are .Net applications launched from the local host. Strong names are digital signatures tied to .Net applications/assemblies. .Net 4 considers applications installed locally to be fully trusted by default and grants these applications full permissions to access host resources.
The bypass feature applies to any assembly signed with a strong name and having the following characteristics:
Fully trusted without the StrongName evidence (for example, has MyComputer zone evidence).
Loaded into a fully trusted AppDomain.
Loaded from a location under the ApplicationBase property of that AppDomain.
Not delay-signed.
Not validating the certificates used to sign strong name assemblies will provide a faster application load time, but falsely assumes that signatures used to sign the application are to be implicitly trusted. Not validating strong name certificates introduces an integrity risk to the system.
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.