Differences

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

Link to this comparison view

Both sides previous revision Previous revision
public:99_annexes:annex-b-terms-and-definitions:h:hardened_image [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:h:hardened_image to public:99_annexes:annex-b-terms-and-definitions:h:hardened_image nick_didopublic: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 ====== ====== Hardened Image ======
  
-[[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
  
-A Hardened Image is a [[private:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] configured to reduce security exposure and satisfy defined security requirements or benchmarks.+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. 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.
Line 11: Line 11:
 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. 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 [[private:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]].+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 ===== ===== Definition =====
  
-//[[private:99_annexes:annex-b-terms-and-definitions:m:machine_image|machine image]] configured to reduce security exposure and satisfy defined security requirements or benchmarks//+//[[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 ===== ===== Source =====
Line 29: Line 29:
 ===== Example ===== ===== Example =====
  
-Crucible applies a DISA [[private:99_annexes:annex-b-terms-and-definitions:s:stig]] profile to a [[private: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.+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.
  
 ---- ----
  • public/99_annexes/annex-b-terms-and-definitions/h/hardened_image.1789260152.txt.gz
  • Last modified: 2026/09/12 17:42
  • by nick_dido