Skip to content

Microsoft DotNet Framework 4.0 Security Technical Implementation Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • 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 i...
    Rule Medium Severity
  • 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 t...
    Rule Medium Severity
  • 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 po...
    Rule Medium Severity
  • .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...
    Rule Medium Severity
  • The .NET CLR must be configured to use FIPS approved encryption modules.

    FIPS encryption is configured via .NET configuration files. There are numerous configuration files that affect different aspects of .Net behavior. The .NET config files are described below. Mac...
    Rule Medium Severity

The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.

Capacity
Modules