Worm
What is Worm?
A type of malware that self-replicates and spreads across networks without requiring user interaction or a host programme. Worms can consume bandwidth, overload systems, and deliver additional malicious payloads.
Terms that appear alongside worm
Each of these is named in at least one of the same controls as worm. The number is how many controls name both.
- audit 7 shared controls
- integrity 6 shared controls
- nist 6 shared controls
- audit trail 5 shared controls
- availability 5 shared controls
- baseline 4 shared controls
- hipaa 3 shared controls
- chain of custody 3 shared controls
Frameworks that govern worm
What the standards actually require on worm
Requirements naming worm across 6 standards, quoted from the control text.
Threats are untargeted (the ship or company is one of many victims or collateral damage, as with NotPetya, using tools freely available online) or targeted (the company or ship is chosen, often after reconnaissance, with tailored tools).
BIMCO-2.2 · Types of cyber threats →Security Dimension 3 Non-Repudiation per X.805 Clause 6.3: Non-repudiation stops a person or entity from credibly denying that it carried out a given action on data, by keeping evidence of network-related actions available (for example evidence of an obligatio...
X805-Dim3-Non-Repudiation-Proof-Origin-Delivery-Sender-Receiver-Denial-Prevention · ITU-T X.805 Security Dimension 3 - Non-Repudiation + Proof of Origin + Proof of Delivery + Sender + Receiver Denial Prevention + Digital Signatures + Timestamping + Audit Logs + Forensic Evidence + Court-Admissible Records →Malicious Code Controls. Controls to detect and block malicious code (or suitable mitigating controls) must be deployed at both endpoint and network level, covering viruses, ransomware, spyware, worms and trojans (para 53).
BMA-20 · Malicious Code Controls →Measures that prevent, detect and correct, above all current security patches and virus control, are put in place and kept up throughout the enterprise to shield information systems and technology from malware, ransomware, viruses, worms, spyware and spam: pro...
cobit-2019::DSS05.01 · DSS05.01 Protect against malicious software →CBSs and networks in scope must support timely, complete and safe backup and restore, with backups regularly maintained and tested, so the ship can regain navigation and operation from a secure copy or image, with sufficient information and facilities, backup...
iacs-unified-requirements-e26e27-cyber-resilience-of-ships-and-on-board-systems::E26-4.5.2 · E26 4.5.2 Backup and restore capability →ISMAP Cloud Operations covers the day-to-day security operations of cloud services. (1) Cloud Security Monitoring and Logging: 24x7 Security Operations Center (SOC) + SIEM Security Information and Event Management + UEBA User and Entity Behaviour Analytics + S...
ISMAP-CloudOperations-Monitoring-Logging-IncidentResponse-NISC-Reporting-Vulnerability-Change-SLA · ISMAP Cloud Operations - Security Monitoring + SIEM + Logging + Incident Response + NISC Reporting + Vulnerability Management + Penetration Testing + Change Management + SLA Management →Questions people ask about worm
What is Worm?
Why is Worm important for compliance?
Which compliance frameworks address Worm?
Where can I learn more about Worm?
See how Worm applies across compliance frameworks
Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.