26 controls
2 frameworks share controls with it
International
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
BIMCO Maritime Cyber Security Evidence & Implementation Kit
26 controls is the documentation set somebody has to write. This is that set,
already written: an adopt-ready artifact for every control in policy and procedure text you
edit rather than draft, and the evidence checklist an auditor asks for against each.
See what is in it, $249
The same set every buyer of this kit receives. Nothing here is produced on request.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
Every control
| Code | Control | Also in |
|---|
BIMCO-1.2 | Senior management involvement | 1 |
BIMCO-1.3 | Roles, responsibilities and tasks | 1 |
BIMCO-1.4 | Differences between IT and OT systems | 1 |
BIMCO-1.5 | Plans and procedures | 1 |
BIMCO-1.8 | Relationship with vendors and other external parties | 1 |
BIMCO-10.2 | The four phases of incident response | 1 |
BIMCO-10.3 | Recovery plan | 1 |
BIMCO-10.4 | Data recovery capability | 1 |
BIMCO-10.5 | Investigating cyber incidents | 1 |
BIMCO-2.1 | Threat actors | 1 |
BIMCO-2.2 | Types of cyber threats | 1 |
BIMCO-3.1 | Common vulnerabilities | 1 |
BIMCO-3.3 | Typical vulnerable systems | 1 |
BIMCO-3.4 | Ship to shore interface | 1 |
BIMCO-3.6 | Remote access | 1 |
BIMCO-3.7 | System and software maintenance | 1 |
BIMCO-4 | Assessing the likelihood | 2 |
BIMCO-5.1 | Impact assessment (CIA model) | 1 |
BIMCO-6.2 | The four phases of a risk assessment | 1 |
BIMCO-6.3 | Third party risk assessments | 1 |
BIMCO-7.1 | Defence in depth and in breadth | 1 |
BIMCO-7.2 | Technical protection measures | 1 |
BIMCO-7.3 | Procedural protection measures | 1 |
BIMCO-8.1 | Detection, logging, blocking and alerts | 1 |
BIMCO-8.2 | Malware detection | 1 |
BIMCO-9 | Establish contingency plans | 1 |
Tell me when BIMCO Cyber Security files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What an auditor will ask you to produce
The artefacts named on the failure modes this framework speaks to.
- Incident response plan
- Incident response plan and playbooks
- Incident records, post-incident reviews and reporting to authorities
- Exercises/drills (including OT scenarios)
- Incident response plan following the four phases
- Ship-shore coordination and escalation procedures
- Monitoring configuration and alert rules
- Anomaly detection logs
- Security event evaluation records
- Incident response playbooks
How programmes fail on this
Failure modes named by this framework and others. Each opens the full record.
What this page is
A control-level reference for BIMCO Cyber Security, drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition