Known starting state
Select a named image, operating system, release, and architecture so teams can identify what entered the environment.
FRAMEWORKS / NERC CIP
AWS hardened images for NERC CIP programs.
Use maintained Linux images as controlled operating-system baselines within NERC CIP cybersecurity programs for bulk electric system environments.
PROGRAM CONTEXT
A repeatable image can strengthen the infrastructure work behind the program.
NERC CIP obligations extend across people, processes, systems, access, change control, recovery, and evidence. A hardened image addresses one bounded layer: the operating-system baseline used by an in-scope or supporting cloud workload.
Controlled change
Test image updates with the workload and keep the deployed version connected to the applicable change and recovery process.
Usable evidence
Retain product scope, configuration records, validation results, and deployment ownership alongside wider program evidence.
AUTHORITATIVE REFERENCENERC Reliability Standards ↗
IMAGE SELECTION
Carry the framework context into the catalog.
Use NERC CIP as the program context, then select the image by its actual hardening profile, operating system, release, and architecture.
- 01
Choose the product profile.
Use the named profile and product scope—not the page headline—as the description of image-level hardening.
- 02
Match the operating system.
Confirm application support, release lifecycle, package behavior, and the team's ability to maintain the platform.
- 03
Select the architecture.
Choose x86_64 or arm64 against workload compatibility, tooling, performance, and support requirements.
- 04
Validate the complete workload.
Test identity, networking, applications, monitoring, recovery, exceptions, and operating procedures before production use.
SECTOR ROUTES
Put the framework back into the operating environment.
The same program can lead to different infrastructure decisions when uptime, access, ownership, and service consequences change.
NEXT STEP