public:99_annexes:annex-b-terms-and-definitions:h:hardened_image

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:h:hardened_image [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:h:hardened_image [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Hardened Image ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Hardened Image is a [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] configured to reduce security exposure and satisfy defined security requirements or benchmarks.
 +
 +The hardening process may remove or disable unnecessary services, restrict access, strengthen authentication, configure auditing, apply security policies, update packages, enforce secure defaults, and remediate identified findings.
 +
 +A Hardened Image reflects a defined security configuration at the time of its build. Continued security depends on controlled updates, vulnerability management, configuration management, monitoring, and operation within an appropriate environment.
 +
 +Within Crucible, hardening and compliance scanning occur as controlled image-build activities, and the resulting findings and evidence remain associated with the image and its [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]].
 +
 +===== Definition =====
 +
 +//[[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|machine image]] configured to reduce security exposure and satisfy defined security requirements or benchmarks//
 +
 +===== Source =====
 +
 +Generalized from cybersecurity, operating-system hardening, secure configuration, compliance engineering, and machine-image usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +A Hardened Image is not necessarily accredited, authorized, vulnerability-free, or suitable for every operating context.
 +
 +The applicable hardening criteria depend on the operating system, threat model, compliance baseline, workload, and target environment.
 +
 +===== Example =====
 +
 +Crucible applies a DISA [[public:99_annexes:annex-b-terms-and-definitions:s:stig]] profile to a [[public:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 Guest Image, remediates applicable findings, disables unnecessary services, configures auditing, and produces a Hardened Image with associated compliance evidence.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>