Explain secure OT architectural principles
Network topology and access decisions are represented; a dedicated architecture design task remains.
Meridian crosswalk
OTC-01OTCY-02DOMAIN 4.0 · 18% draft
OT Cybersecurity Architecture, Design, and Engineering
Design defensible zones, conduits, access paths, monitoring, and compensating controls without losing the process.
Paraphrased, versioned draft mapping from CompTIA SecOT+ SOT-001 V1 draft objectives v1.3. This independent page is not CompTIA content.
Summarize physical security concepts
Physical walkdown, cabinet, surveillance, and perimeter controls are not yet a released primary lab.
Meridian crosswalkNo released scenario mapped yet.
Given a scenario, determine the applicable hardware security controls and settings
PLC modes, firmware, Secure Boot, removable media, and tamper controls need a dedicated lab.
Meridian crosswalkNo released scenario mapped yet.
Given a scenario, apply appropriate host and application security practices
Host hardening, EDR, code signing, and patch controls are curriculum topics without a released primary lab.
Meridian crosswalkNo released scenario mapped yet.
Given a scenario, recommend appropriate network security controls and designs
Zones, conduits, monitoring, and access tradeoffs are present; design validation remains partial.
Meridian crosswalk
OTC-01OTCY-02Given a scenario, recommend the appropriate identification, authentication, and authorization controls
Role authority and secure access are modeled; PKI, RADIUS/TACACS+, and PAM depth is a gap.
Meridian crosswalk
OTCY-03robot-comms-001Turn this domain into a decision.
The free R8 incident exposes evidence, safety, coordination, and recovery behavior through the canonical OT-Praxis runtime.
Practice in Meridian →