STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

Microsoft DotNet Framework 4.0 Security Technical Implementation Guide

Version

V2R8

Release Date

Feb 12, 2026

SCAP Benchmark ID

MS_Dot_Net_Framework

Total Checks

16

Tags

other
CAT I: 0CAT II: 14CAT III: 2

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSONDownload STIG ZIP

Checks (16)

V-225223MEDIUMDigital signatures assigned to strongly named assemblies must be verified.V-225224MEDIUMThe Trust Providers Software Publishing State must be set to 0x23C00.V-225225MEDIUMDeveloper certificates used with the .NET Publisher Membership Condition must be approved by the ISSO.V-225226MEDIUMEncryption keys used for the .NET Strong Name Membership Condition must be protected.V-225227MEDIUMCAS and policy configuration files must be backed up.V-225228MEDIUMRemoting Services HTTP channels must utilize authentication and encryption.V-225229MEDIUM.Net Framework versions installed on the system must be supported.V-225230MEDIUMThe .NET CLR must be configured to use FIPS approved encryption modules.V-225231MEDIUM.NET must be configured to validate strong names on full-trust assemblies.V-225232LOW.Net applications that invoke NetFx40_LegacySecurityPolicy must apply previous versions of .NET STIG guidance.V-225233MEDIUMTrust must be established prior to enabling the loading of remote code in .Net 4.V-225234LOW.NET default proxy settings must be reviewed and approved.V-225235MEDIUMEvent tracing for Windows (ETW) for Common Language Runtime events must be enabled.V-225236MEDIUMSoftware utilizing .Net 4.0 must be identified and relevant access controls configured.V-225237MEDIUMRemoting Services TCP channels must utilize authentication and encryption.V-225238MEDIUMUpdate and configure the .NET Framework to support TLS.