Business Continuity Management (BCM) Program Maintenance Evaluation
Business Continuity Management (BCM) Program Maintenance Evaluation : "Some techniques to evaluate the maintenance of BC include: (1) Evaluating the document change history to determine whether updates to the document are recorded. (2) Reviewing maintenance requirements to ensure component maintenance is assigned to specific individuals and management provides guidance to enable the individuals to be effective at maintaining BC capabilities. (3) Reviewing BC assumptions to ensure they align well with current operating requirements. BC assumptions should change to address new issues such as additional locations, new concentrations of risk (e.g., a new disaster scenario becomes credible), reliance on new/different third parties, or operations in new countries. (4) Reviewing changes in BC assumptions to ensure each change has a basis. (5) Reviewing the date of the BIA to ensure the foundation for the BC plans is current enough to provide adequate direction. (6) Contacting people responsible for tasks in the plan to determine their understanding of the requirements and confidence that they can perform well. In many cases, people named in plans (especially plans that have existed for several years) are simply replacements for their predecessors in name only and have not been provided the same training as when the BCM program and/or BC plan was initially introduced. (7) Reviewing the BC document structure/setup to determine how accurately it reflects the current organizational model and structure. (8) Scanning for words such as "current" and "today's" and evaluating whether the associated content is truly keeping pace with the organization, especially if a document is available electronically. (9) Reviewing exercise/test results and associated action reports for exceptions (e.g., gaps) requiring remediation. (10) Assessing the BCM program and BC recovery capabilities to ensure they have been updated to correct necessary gaps and have been implemented effectively". (IIA, Business Continuity Management, 2008. pp. 14-15)
No records Found