# Clause 4.2.1: General

When setting up the BCMS, identify which interested parties matter to it and record the requirements each of them has.

Cloud: Keep the view general enough to cover new services and specific enough to be useful during an incident. A list that only names the provider misses the subproviders and the regions that decide whether a failure is survivable.

Evidence: Interested party register, dated and owned; The specific requirement captured for each listed party; Method note showing how relevance to the BCMS was decided.

Test: Check that the list is reviewed when a service is added, moved or retired.

Citation: ISO 22301:2019, clause 4.2.1. Source: https://compliance.theartofservice.com/frameworks/iso-22301-2019. Last updated: 2026-10-20.