This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| policies:security:develandmaint [2018/01/10 12:23] – [33. Additional risk analysis] deul | policies:security:develandmaint [2018/01/10 13:32] (current) – [39. Calamity procedures] deul | ||
|---|---|---|---|
| Line 28: | Line 28: | ||
| The Security manager as defined by the [[policies: | The Security manager as defined by the [[policies: | ||
| ====39. Calamity procedures===== | ====39. Calamity procedures===== | ||
| - | There is no true calamity procedure and each case is handled ad hoc, with teh following requirements in mind: | + | There is no true calamity procedure, |
| * Minimize downtime of critical services | * Minimize downtime of critical services | ||
| * Communicate the calamity to all users/ | * Communicate the calamity to all users/ | ||
| * Maximize the collaborative effort within the IT Department team | * Maximize the collaborative effort within the IT Department team | ||
| * Strive to full resolution of the calamity | * Strive to full resolution of the calamity | ||