MOC COMPLIANCE
MOC COMPLIANCE
MOC COMPLIANCE
MOC COMPLIANCE
MOC COMPLIANCE

Cybersecurity Change Request (CR)

In accordance with IACS UR E26 §5.3.1 & UR E22 Section 6

Doc ID: TAG-MOC-2026-E22
Version: 1.3 (IACS E22 Compliant)

1. GENERAL INFORMATION

Vessel / Hull #:	________________	Date:	____/____/2026
Requestor / Rank:	________________	E22 Stakeholders:	[ ] OEM Agreed [ ] Owner Agreed

2. DESCRIPTION, JUSTIFICATION & ROLLBACK

CHANGE DESCRIPTION: Include KB Number, Version ID, and Reason for Change (e.g., Critical Patch for PLC Firmware).

E22 6.9 ROLLBACK PLAN: Define steps to return to known stable state if change fails (e.g., Revert to Golden Copy image).

3. SYSTEM IMPACT & RISK ASSESSMENT (E22 6.8)

IACS Category:	[ ] Cat I	[ ] Cat II	[ ] Cat III (High Criticality)
Impact Scope:	[ ] Documentation Only	[ ] Logic / Firmware	[ ] Network / Firewall

4. POST-CHANGE VERIFICATION & VALIDATION

[ ] E22 6.10 Regression Test: Verified that modification has NO negative impact on unrelated functions?
[ ] E22 6.9 Rollback Simulation: Recovery path to previous stable version confirmed?
[ ] E22 6.6 Master Files: Software master files updated and stored by Personnel Authority?
[ ] Configuration backup / “Gold Copy” successfully stored offline?
[ ] MAC Address / Asset ID updated in Master Inventory?
[ ] Functional test performed and witnessed per OEM requirements?

5. FINAL AUTHORIZATION & CLASS APPROVAL

[ ] Class Society Notified (Date: ___________) | Reference ID: ______________________

Authorized by (DPA / Master):

Signature & Date

Technical Verification (ETO / Technical Manager):

Signature & Date

Master the Management of Change (MoC)

Don’t lose your Class notation over a firmware update. Get the fillable version of this form plus the E22/E26 Workflow Guide for shipboard technical changes.

Purchase Compliance Bundle