Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:s:stig [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:s:stig [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Security Technical Implementation Guide (STIG) ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Security Technical Implementation Guide (STIG) specifies security configuration requirements for an information technology product, system, service, platform, or technology. | ||
| + | |||
| + | The Defense Information Systems Agency (DISA) publishes STIGs for the United States Department of Defense information systems. A STIG translates applicable security controls and risk-management expectations into product-specific or technology-specific configuration requirements and assessment checks. | ||
| + | |||
| + | A STIG may identify required settings, prohibited configurations, | ||
| + | |||
| + | STIGs may be distributed in human-readable and machine-processable forms. Machine-processable content may support automated assessment through technologies such as the Security Content Automation Protocol (SCAP) and tools such as OpenSCAP. | ||
| + | |||
| + | Within Crucible, a STIG may form part of a [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //security configuration guide that specifies implementation and assessment requirements for an information technology product, system, service, platform, or technology// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Generalised from the Security Technical Implementation Guides published by the United States Department of Defense and the Defense Information Systems Agency, and specialized for the Crucible architecture and operational model. | ||
| + | |||
| + | DISA identifies STIGs as security guidance for Department of Defense information technology systems and describes them as a bridge between NIST SP 800-53 and the Risk Management Framework. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A STIG applies to a defined product, technology, version, or operating context. The applicable STIG and release should therefore be identified explicitly. | ||
| + | |||
| + | For example, a STIG for [[public: | ||
| + | |||
| + | Applying a STIG does not by itself grant accreditation or an [[public: | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A Crucible Image Baseline identifies a DISA STIG for [[public: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||