Part of the IDENTIFY Playbook ← Return to Hub

Deep Dive: Protocol Intelligence

Looking for detailed risk analysis and hardening guides for NMEA, Modbus, and AIS?

VIEW INTELLIGENCE LIBRARY

Execution: To enforce Conduits (Step 03), you must map the “Language” of the assets to technical ports. This module provides the configuration data needed for firewall Access Control Lists (ACLs) as required by UR E26 §4.2.

1. Intelligence: Gateway Logic

Bridging the Serial Gap

Most maritime assets (Engines, GPS, AIS) use serial RS-422/485. When using Serial-to-IP Gateways, they become network-visible. Ensure your Conduit (Firewall) only allows the specific IP and Port of the gateway.

Firewall Rule Concept: ALLOW TCP [Bridge_Workstation] [NMEA_Gateway_IP] PORT [Protocol_Port]

2. Port & Service Mapping for Firewalls

To enforce Conduits (Step 03), you must map the “Language” of the assets to technical ports. This data is the foundation for your firewall Access Control Lists (ACLs).

Tactical Member Access Required
Missing from this Module:
  • Technical Port Mapping
  • S7 & Modbus DPI Actions
  • Safe OT-Scanning Checklist
  • Nmap Discovery Scripts

Technical Implementation Locked

Unlock IACS UR E26 compliance checklists and bridge-specific diagnostic procedures.

Upgrade to Unlock

Next Section

OT Traffic Baselining Procedures

OT Traffic Baselining Procedures Objective: Capture the "Normal" state of communication to create a blueprint for Firewa...

Scroll to Top