4.2.2 Legal and regulatory requirements
Run and maintain a process that finds, obtains access to and assesses the legal and regulatory requirements applying to the continuity of the organization's products, services, activities and resources, ensure those requ
4
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Current obligations register with source, applicability and assessment date · Policy repository / GRC workspace
- Evidence of horizon scanning or subscription to a legal update source · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Documented process for identifying and assessing continuity related legal and regulatory requirements · Document repository
- Traceability from an obligation to the BCMS element that satisfies it · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Obligations register held by legal and never reconciled against the BCMS
- No assessment step, so the register lists laws without saying what they demand of continuity
- Regime changes in new operating jurisdictions missed because the process has no trigger
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet4.2.1 General · 4.3 Determining the scope of the business continuity management system