Operational fit
Confirm that the baseline, services, and update approach are compatible with the workload's performance and availability requirements.
FRAMEWORKS / NIST SP 800-82 REV. 3
Choose supported Linux baselines for cloud workloads around operational technology while preserving the performance, reliability, and safety constraints that make OT distinct.
PROGRAM CONTEXT
NIST SP 800-82 Rev. 3 addresses operational technology across a broad range of systems that interact with the physical environment. Image selection should therefore be tested against operating consequences, not treated as an isolated configuration exercise.
Confirm that the baseline, services, and update approach are compatible with the workload's performance and availability requirements.
Place the image inside the intended network, identity, monitoring, remote-access, and recovery design before judging the result.
Document exceptions and test behavior under representative operating conditions before the workload enters service.
IMAGE SELECTION
Use the OT environment as the selection context, then compare real image profiles, OS families, releases, and architectures in the catalog.
Use the named profile and product scope—not the page headline—as the description of image-level hardening.
Confirm application support, release lifecycle, package behavior, and the team's ability to maintain the platform.
Choose x86_64 or arm64 against workload compatibility, tooling, performance, and support requirements.
Test identity, networking, applications, monitoring, recovery, exceptions, and operating procedures before production use.
SECTOR ROUTES
The same program can lead to different infrastructure decisions when uptime, access, ownership, and service consequences change.
NEXT STEP