Principle Name
Business Continuity
Statement
University activities should be maintained, despite system interruptions.
Rationale
As system operations become more inherent, we become more dependent of them. Therefore, we should consider the reliability of such systems throughout their entire conception and application. Business areas throughout the entire University should be able to continue conducting their normal activities, regardless of external events. Hardware failures, natural disasters, and lack of data integrity should not interrupt business activities. Business activities should be able to employ alternative mechanisms to convey information.
Implications
- Dependence on shared applications implies that business interruption risks should be expected and managed in advance. Management includes, but is not limited to, periodic revisions,vulnerability and exposure tests, or designing mission-critical services to ensure continuity through redundancies or alternative resources.
- Recoverability, redundancy, and maintenance should be approached at inception.
- Applications should be assessed regarding criticality and impact on the University’s mission to determine which continuity level is required and which corresponding recovery plan should be implemented.
Architecture Domains
- Business