After this lesson you can explain what a log is and why it matters, describe how a SIEM collects, parses, normalises, enriches and stores log data, distinguish single-event, threshold, correlation, threat-intelligence and behaviour-based detections, explain what a use-case library is and why alert tuning matters, and identify the records that IACS UR E26 requires ships to produce.
After a collision or grounding, investigators go first to the records: the deck log, the engine log, the ECDIS track and the VDR. Without records there is only memory and opinion. In cybersecurity the records are logs, and the system that turns millions of them into something a human can act on is the SIEM.
In Lesson 16 the SIEM appeared as the centre of the SOC's tool set. This lesson opens it up: how logs get in, how they are made comparable, how rules decide what is worth an analyst's attention, and how the investigation that follows uses the same data.
Everything here applies to any SIEM product. Lessons 18 and 19 then show how two widely used platforms — Microsoft Sentinel and Splunk — put these ideas into practice.
1. What Logs Are — and Why They Matter
A log is a time-stamped record of something that happened on a system: a user logged on, a program started, a firewall blocked a connection, a setting was changed. Every computer, network device and cloud service can write logs, and most do so by default in some form.
Logs are to cybersecurity what the deck log, engine log and VDR are to a casualty investigation: the only reliable record of what happened, in what order. NIST's long-standing Guide to Computer Security Log Management (SP 800-92) was written to help organisations understand the need for sound log management, because logs that are never collected, are deleted too early or cannot be trusted are worthless when an incident happens.
Windows shows how specific logs can be. Microsoft documents security event 4625 — “An account failed to log on” — as logged for any logon failure, on the computer where the attempt was made. The event records, among other fields, the account name, the logon type (2 = interactive at the keyboard, 3 = from the network, 10 = remote desktop) and the source network address. One failed logon means nothing; fifty in a minute from one address means something.
2. The Log Pipeline
3. Detection — Rules, Correlation and Analytics
Once data is in the SIEM, it is watched by detection rules — saved searches that run automatically and raise an alert when they find a match.
A SOC keeps its rules in a use-case library: for each rule, the threat it addresses, the ATT&CK technique it maps to (Lesson 15), the log sources it needs, the expected false alarms and what the analyst should do when it fires.
4. Choosing What to Log First
Sending every log to a SIEM is expensive and slow, and on a ship it is often impossible over the satellite link. The real skill is choosing which logs matter most.
The CISA / ASD guidance package on SIEM and SOAR implementation (May 2025) includes a dedicated practitioner guide, Priority Logs for SIEM Ingestion, written to help organisations decide which logs to send to a SIEM first. A practical approach is to start with the sources that show who got in and what they changed, then grow:
This order is the author's teaching suggestion, not a ranking taken from the CISA/ASD guide; read the guide itself for its recommended priorities.
5. From Alert to Investigation
When a rule fires, the work moves from the machine to the analyst:
IACS UR E26 Rev.1 does not mention SIEM products, but several of its requirements produce exactly the records a SIEM is built to watch:
Remote access logging (4.2.6). Remote access to systems in scope must provide a logging function that records all remote access events and keeps them long enough for offline review, for example after a cyber incident has been detected.
Network monitoring records (4.3.1). Monitoring must include monitoring of network connections, monitoring and recording of device management activities, protection against connection of unauthorised devices and a bandwidth alarm. During commissioning, the test procedures include demonstrating that audit records are generated.
Inspection of audit records. In the operation phase the shipowner must describe in its cyber security and resilience programme how anomalies are detected, including inspection of security audit records.
Practical design questions. Ship OT systems often write logs in proprietary formats, or none at all, so parsing them may need custom work and help from the equipment supplier. Over a limited satellite link, a common design is to collect and filter logs on board and send only the most important records ashore, keeping the full set on board for later investigation. Whatever design is chosen, it should be agreed with the system suppliers, since E26 requires any intrusion detection to be passive and supplier-qualified.
- Logs are the time-stamped record of what happened on systems; without them there is no detection and no investigation.
- A SIEM collects logs, parses and normalises them into common fields, enriches them with context, stores them and runs detection rules.
- Detections range from single-event and threshold rules to multi-source correlation, threat-intelligence matching and behaviour analytics (UEBA).
- A use-case library links each rule to a threat, an ATT&CK technique, its data sources and an analyst procedure; tuning against alert fatigue never stops.
- Choosing which logs to send first matters more than collecting everything — CISA and ASD published dedicated guidance on priority logs in May 2025.
- IACS UR E26 requires remote access logging, recording of device management activity and inspection of audit records — natural inputs for SIEM-based monitoring.
- NIST SP 800-92 — Guide to Computer Security Log Management (2006)
- CISA — Guidance for SIEM and SOAR Implementation, incl. Priority Logs for SIEM Ingestion (May 2025)
- Microsoft — Event 4625(F): An account failed to log on
- Microsoft — What is Microsoft Sentinel SIEM? (connectors, CEF/Syslog/REST API, ASIM normalisation)
- NIST — The NIST Cybersecurity Framework (CSF) 2.0, CSWP 29
- IACS UR E26 Rev.1 (Nov 2023), Cyber resilience of ships
Regulatory and vendor statements were checked against the linked sources in November 2026. The starter log order and maritime design notes are the author's teaching examples.
Captain Paul writes the Maritime Cybersecurity Learning Roadmap on ShipPaulJobs — a step-by-step course that takes readers from security fundamentals to the cyber resilience rules that now apply to ships.
← Course Index LinkedIn⚓ Join the ShipPaulJobs Community
Join →

Comments
Post a Comment