{'fraction_non_alphanumeric': 0.022010271460014674, 'fraction_numerical': 0.01760821716801174, 'mean_word_length': 5.888888888888889, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Shared responsibility for forensic readiness-related security controls: Prerequisite for critical infrastructure maintenance and supplier relationships

New regulation on cybersecurity for critical infrastructure mandates the implementation of a minimum set of security measures to achieve satisfactory security posture for the respective business domain. The organization responsible for operation of a given critical infrastructure may have some flexibilities in selecting recommended or mandatory national or international standards used for compliance. No matter which set of standards and guidelines are selected, security incident response will be one of the key security requirements to be met, e.g. according to ISO/IEC 27002:2013, §16, ISO/IEC 27035, ISO/IEC 27041 or NIST SP 53Rev4. This paper focuses on the business needs and practical approaches on shared responsibility with regard to the enforcement of selected security controls. The topics and case studies addressed in this paper include shared responsibility of contractors with service providers (e.g. application providers and cloud service providers) and shared responsibility related to maintenance services (site-local maintenance, remote maintenance, and preventive maintenance). As of today there is no agreed upon semi-formal representation for expressing these shared responsibilities.