Home » Functions » Map (RC.DM) » RC.DM-3 Service Interdependencies

Description

According to Linkov et al. ^[8], “the resilience of systems relies hugely on effectiveness of cross-domain communication and coordination at each stage of the event management cycle”. This can also be said of the interdependency of systems and services, often captured in asset inventory management databases. It is pertinent that systems and services interdependencies are well understood and articulated. Having a service interdependency map or document can help recovery analysts and an external recovery provider understand how each of the impacted systems are connected, and most importantly, on how best to administer the recovery procedure, and the sequencing of restoration. It is recommended that organisations create and maintain a complete inventory of assets, their configurations and interdependencies, or as a minimum, at least for key mission-critical assets ^[12].

See also RC.RP-1 and RC.PL-6.

Outcomes / Outputs

(Conduct / Fix / Ingest / List / Plan / Procure / Produce / Report / Review / Set / Test  / Train )

1. List detailing a  complete inventory of assets, configurations and interdependencies, or as a minimum, at least for key mission-critical assets

Reference

8. Igor Linkov, Daniel A. Eisenberg, Kenton Plourde, Thomas P. Seager, Julia Allen and Alex Kott (2013), “Resilience metrics for cyber stems”, Environmental Systems Decision Springer. DOI 10.1007/s10669-013-9485-y

12. NIST SP 800-184 (2016), “Guide for Cybersecurity Event Recovery”, NIST Special Publication 800-184. December 2016. https://doi.org/10.6028/NIST.SP.800-184