Ensuring Robustness of SOC Operations

BUILD Robustness

Open

Build Robustness

Based on the Regular scenario, procedures for the SOC Operator are defined.

Based on the Anticipated scenario, plans are developed for how each Operator will contribute, and the benefit from each tool is anticipated, in a manner that reflect the maturity of the organisation related to the anticipated potential for transformation (Transformative Effects on Basic SOC Processes) or strategic leverage of SOC performance (Strategic Leverage for Improved Performance of the SOC as a Whole).

VALIDATE Robustness

Open

Validate Robustness

The SOC should recurrently validate that Robustness is maintained. Revisons of the Regular and Anticipated scenarios should be done periodically.

STRESS-TEST Robustness

The SOC should periodically stress-test the validated Robustness through a relevant Surprise scenario, encompassing the SOC as a whole. Surprise scenarios should evolve based on prior results.

STRESS-TEST Degraded Modes

A special case of stress-testing should periodically be conducted on degraded modes. The degradation should be based on updated status of tools, their inter-connectivity, and their dependency on joint platforms (see Degraded Modes).