Checklist Summary:

The Innoslate 4.x Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DoD) information systems. This document is meant for use in conjunction with other STIGs, such as the Apache STIG and appropriate operating system STIGs. Innoslate has been developed for use with Department of Defense Architecture Framework (DoDAF) projects. The DoDAF Version 2.0 is the overarching, comprehensive framework and conceptual model enabling the development of architectures to facilitate the ability of DoD managers at all levels to make key decisions more effectively through organized information sharing across the department, Joint Capability Areas (JCAs), mission, component, and program boundaries. Innoslate offers full lifecycle software for model-based systems engineering, requirements management, verification, and validation in support of DoDAF.

Checklist Role:

• Server

Known Issues:

Not provided.

Target Audience:

Parties within the DoD and federal government’s computing environments can obtain the applicable STIG from the DoD Cyber Exchange website at https://cyber.mil/. This site contains the latest copies of STIGs, SRGs, and other related security information. Those without a Common Access Card (CAC) that has DoD Certificates can obtain the STIG from https://public.cyber.mil/.

Target Operational Environment:

• Managed
• Specialized Security-Limited Functionality (SSLF)

Testing Information:

Not provided.

Regulatory Compliance:

This document is provided under the authority of DoDI 8500.01.

Comments/Warnings/Miscellaneous:

Not provided.

Disclaimer:

DISA accepts no liability for the consequences of applying specific configuration settings made on the basis of the SRGs/STIGs. It must be noted that the configuration settings specified should be evaluated in a local, representative test environment before implementation in a production environment, especially within large user populations. The extensive variety of environments makes it impossible to test these configuration settings for all potential software configurations. For some production environments, failure to test before implementation may lead to a loss of required functionality. Evaluating the risks and benefits to a system’s particular circumstances and requirements is the system owner’s responsibility. The evaluated risks resulting from not applying specified configuration settings must be approved by the responsible AO. Furthermore, DISA implies no warranty that the application of all specified configurations will make a system 100 percent secure.

Product Support:

Not provided.

Point of Contact:

disa.stig_spt@mail.mil

Sponsor:

Not provided.

Licensing:

Not provided.

Change History:

updated to FINAL - 11/14/2022

Dependency/Requirements:

URL	Description

References:

Reference URL	Description

NIST checklist record last modified on 11/15/2022