DEFENSE SWITCHED NETWORK INFORMATION ASSURANCE ...

Table B-1. STIG Listing (continued)
STIG Description
Enterprise System
Management (ESM) STIG
VMware Enterprise (ESX)
Server STIG
Keyboard, Video, and Mouse
(KVM) Switch Checklist
Instant Messaging Checklist
Macintosh STIG
.NET Framework Checklist
Network STIG
OS/390 MVS Logical Partition
STIG
OS/390 STIG
Personal Computer
Communications Client STIG
Sharing Peripherals Across the
Network (SPAN) STIG
Secure Remote Computing
STIG
Tandem STIG
Unisys STIG
ESM STIG provides security configuration guidance for software products designed to deliver
enterprise-class system management functions. While the boundaries of the ESM discipline are
such that there is no authoritative definition of an ESM product, Section 2, Enterprise System
Management Overview, provides a generic description of the elements characteristic of most ESM
products. Section 3, Enterprise System Management Security, provides general guidance for ESM
products. Specific commercial products are addressed in appendices.
ESX Server STIG contains a set of principles and guidelines that serve as the basis for establish
VMware ESX Server environments within DoD.
KVM switches are used to connect a single keyboard, video monitor, and mouse to multiple IS,
saving space and equipment. They are commonly found in testing laboratories, in server rooms,
and with the advent of small inexpensive switches, on desktops to reduce clutter. A/B switches are
used by a single peripheral between multiple IS or multiple peripheral devices on a single interface.
Switch(es) will refer to both KVM and A/B switches unless otherwise noted.
The instant messaging checklist should be used for enterprise instant messaging systems to collect
the data and analysis methodology which will aid the tester with further details in performing the
instant messaging checks.
Macintosh STIG provides the technical security policies and a requirement for deploying a secure
IS running Macintosh OS X in a DoD Network environment.
The .NET Framework checklist targets conditions that weaken the integrity of security, contribute to
inefficient security operations and administration. Additionally, the checklist ensures the site has
properly installed and implemented the .NET environment and that it is being managed in a way
that is secure, efficient, and effective.
Network STIG has been developed to enhance the confidentiality, integrity, and availability of
sensitive DoD Automated IA. Each site network/communications infrastructure must provide
secure, available, and reliable data for all customers. This document is designed to supplement
the security guidance provided by DoD-specific requirements and will assist sites in meeting the
minimum requirements, standards, controls, and options required for secure network operations.
The intent of this STIG is to include security considerations at the network level needed to provide
an acceptable level of risk for information transmitted throughout an enclave.
OS/390 MVS Logical Partition STIG defines the technical criteria necessary to implement MAC II
Sensitive functionality within DISA non-classified multiple partitions and classified partitions. This
document does not define policy, but it documents the procedures and parameters necessary to
implement policy.
OS/390 STIG for most mainframe IA deployed throughout DoD use the IBM OS/390 or z/OS
operating system. Controls within OS/390 and z/OS have been developed and documented in IBM
references to ensure operating system integrity is maintained. This document is in the process of
transitioning from OS/390 to z/OS. Any and all references to OS/390 will apply to both OS/390 and
z/OS.
The intent of this STIG is to provide security and implementation considerations that will result in an
acceptable level of risk for information located in/on or near the PC/workstation; the information
being communicated and the protection of the critical systems that enable and carry the
communications.
SPAN STIG provides the technical security policies, requirements, and implementation details for
applying security concepts to COTS hardware peripheral devices. For this STIG, peripheral will
mean, “any device that allows communication between a system and itself, but is not directly
operated by the system.” However, this document does not deal with devices found wholly within
the main cabinet of the computer or, with the exception of A/B switches, those devices connected
via legacy parallel and serial interfaces.
Secure Remote Computing STIG provides the technical security policies and requirements for
providing a secure remote access environment to users in DoD components. This document
discusses both the remote user environment and the network site architecture that supports the
remote user. Since information can be stored, processed, or transmitted from a number of
locations, IA Systems Management and Information Security must encompass the total
environment.
Tandem STIG includes security considerations needed to provide an acceptable level of risk for the
information that resides on the Tandem systems. The requirements set forth in this document will
assist in securing the Tandem NonStop Kernel OS for each site. The Tandem OS includes the
Tandem NonStop SQL DB MS, and the Tandem file MS Enscribe.
Unisys STIG will define the minimum requirements, standards, controls, options, and procedures
that have to be in place for the Unisys Executive and standard system software to meet MAC II
sensitive compliance as described in the DoDI 8500.2. Individual sites may implement additional
security measures as deemed necessary.
B-3