52% of ASIC Cyber Resilience Good Practices you already have
BIMCO Cyber Security already covers about 52% of ASIC Cyber Resilience Good Practices, leaving
14 of 29 controls as genuinely new work.
Already covered 0
Likely covered 15
New work 14
No control in BIMCO Cyber Security
maps directly to one in ASIC Cyber Resilience Good Practices. Everything counted as covered is covered because both
map to the same third standard, which is what a crosswalk is, but it is an inference rather
than a lookup.
What is genuinely new work
Nothing in BIMCO Cyber Security reaches these. This is the list to scope.
ASIC-CR-AT-2Continuous development
ASIC-CR-DE-2Data analytics for threat integration
ASIC-CR-GOV-2Treat cyber resilience as a management and investment tool
ASIC-CR-GOV-4End-to-end assurance processes
ASIC-CR-GOV-5Responsive, event-driven governance
ASIC-CR-GOV-6Align cyber governance with enterprise governance
ASIC-CR-PR-2Security Development Lifecycle
ASIC-CR-PR-3Encryption of data at rest and in transit
ASIC-CR-PR-4Outbound email filtering and monitoring
ASIC-CR-PR-5Restricted removable media / USB access
ASIC-CR-RM-3Third-party and supply chain risk management
ASIC-CR-RR-3Proactive board reporting during incidents
ASIC-CR-RR-4Customer and breach notification
ASIC-CR-RR-5Stakeholder communication plan
Show the 15 you already have
ASIC-CR-AM-1Centralised asset management system
ASIC-CR-AM-2Configuration management
ASIC-CR-AT-1Staff awareness and training
ASIC-CR-AT-3Random staff testing
ASIC-CR-CO-1Confidential information sharing
ASIC-CR-CO-2Specialist threat-intelligence providers
ASIC-CR-DE-1Continuous monitoring with SIEM
ASIC-CR-GOV-1Board engagement and periodic review of cyber strategy
ASIC-CR-GOV-3Board cyber fluency
ASIC-CR-PR-1Implement the ASD Essential Eight
ASIC-CR-RM-1Intelligence-led cyber risk management
ASIC-CR-RM-2Fusion centres for real-time monitoring
ASIC-CR-RR-1Scenario planning and response exercising
How this is calculated
Already covered means a mapping runs from a control in BIMCO Cyber Security to that control. Likely
covered means no direct mapping exists but both frameworks map to the same control in a third
standard. New work means neither. We keep those separate rather than adding them into one
friendlier number, because blending them would present a two-hop inference as a verified
fact.
Coverage is not symmetric.
Run it the other way and you will get a
different number; both are correct.
From 332,959 cross-framework control
mappings across 723 frameworks, 531 of them verified against
their source documents. It does not tell you that you are compliant: a mapped control means
the two standards ask for the same thing, not that you have done it.
Try another pair ยท
Today's edition