Crew Changeover & Identity Handover
This guide provides a structured process for revoking departing crew credentials and provisioning new identities during crew rotation, preventing account accumulation and maintaining a clean audit trail.
In the maritime industry, the rotation of crew is a constant. However, if digital identities are not managed during these transitions, the vessel’s security posture degrades rapidly. “Account Pollution”—where dozens of old accounts remain active—is a primary target for attackers and a major “Critical Finding” during Class Surveys.
The Changeover Risk: Shared Identities
The biggest risk during a crew change is the temptation to pass over a single “Chief Eng” or “ETO” login. While this seems efficient, it creates a blind spot in the vessel’s safety management. Without unique identities, you lose the ability to verify who performed a specific action, which is a requirement for both security and insurance liability.
The “Ghost” Admin
Departing officers who retain remote access credentials (ZTNA/VPN) or hardware tokens pose a significant risk. If their home computer is compromised months later, an attacker has a direct, valid “identity” to enter your ship’s engine room.
Audit Trail Collapse
When multiple people use one ‘Admin’ account, forensic logs become legally useless. In the event of an accident, you cannot prove if a change was made by the current ETO, the one who left last week, or a remote vendor.
The Formal Handover Protocol
To satisfy E26/E27 requirements, the digital handover must be documented in the ship’s Safety Management System (SMS).
Access Revocation Checklist
Execute these steps to ensure IACS compliance before the signing-off officer leaves the vessel:
- Step 1: Edge Gateway (ZTNA/VPN) — Revoke the officer’s unique certificate in the shore portal.
- Step 2: Windows OT Workstations — Disable user accounts in
Local Users & Groups. - Step 3: HMI / SCADA Systems — Remove the user from ‘Admin/Engineer’ groups in the AMS console.
- Step 4: Network Switches — Rotate SSH/Console credentials if unique accounts aren’t used.
- Step 5: Physical Assets — Collect hardware tokens and verify “Break-Glass” seals are intact.
Compliance Documentation Previews
Standardized templates and technical logs. View watermarked previews below; All fillable forms and SOPs are free with a registered account.
The specific regulatory requirements this playbook satisfies. Use these references when preparing for Class survey or responding to a surveyor's checklist.
