See the trust boundary behind the process.
Plant security goes beyond a device list. Review inventory, access paths and decision authority together at Harbor, keeping physical consequences visible throughout.
Open the plant dossierSelect a boundary. Find the question behind it.
This map describes declared dependencies. Arrows are not actual reachability or firewall validation.
Were all routes reviewed; is there a connection bypassing the DMZ?
- Declared relationship
- Jump point → engineering station
- Review owner
- Access owner
The safety zone is shown separately. Neither absence of a connection nor presence of a reference establishes process safety.
Study sequence for your role
- 1OT asset inventory and process context
- 2Zones, conduits and trust boundaries
- 3Engineering stations and project integrity
- 4Vendor and remote-access management
- 5OT vulnerability, patch and change management
- 6Passive OT monitoring and anomaly review
- 7Safety-led industrial incident response
- 8Validated OT recovery and return to operations
A learning recommendation; choices stay on this page. No account progress, points, field authority or certificate is created.
8 topics, 24 explained scenarios
8 modules
OT asset inventory and process context
Move from an IP list to an inventory with process, ownership, dependencies and evidence provenance. Investigate why a Harbor plant asset is absent from observations.
Beginner → intermediate → advancedZones, conduits and trust boundaries
Review a fictional plant diagram using an actual local JSON model. Distinguish what DMZ, control and safety boundaries establish and what remains unproven.
Beginner → intermediate → advancedVendor and remote-access management
Evaluate identity, target, duration, local sponsorship and session evidence rather than treating a VPN as sufficient.
Beginner → intermediate → advancedEngineering stations and project integrity
Manage project files, revisions, removable media and legacy-system risks with process context; a running workstation is not a validated system.
Beginner → intermediate → advancedOT vulnerability, patch and change management
Assess CVE scores alongside process impact. Connect vendor validation, representative testing, maintenance windows and rollback evidence.
Beginner → intermediate → advancedPassive OT monitoring and anomaly review
Avoid premature conclusions from a new flow or quiet sensor. Interpret observations through coverage, maintenance, time and process context.
Beginner → intermediate → advancedSafety-led industrial incident response
Do not blindly transfer IT isolation reflexes to OT. Keep process authority, physical impact, communications and evidence visible in the same decision.
Beginner → intermediate → advancedValidated OT recovery and return to operations
Identify dependencies from file backups to accepted process functionality; distinguish a booted computer from validated production.
Beginner → intermediate → advancedQuestion the drawing. Review the path.
Use two synthetic JSON models to find declared shortest paths, a DMZ bypass and missing review records. The Node.js kit needs no package installation or network connection; results do not validate equipment, SL/SIL or safety.
Open the browser plant deskDownload the Harbor Plant kit