Translations:Schutzbedarf/52/en: Unterschied zwischen den Versionen
Weitere Optionen
Isan (Diskussion | Beiträge) Keine Bearbeitungszusammenfassung |
Isan (Diskussion | Beiträge) Keine Bearbeitungszusammenfassung |
||
Zeile 4: | Zeile 4: | ||
It makes sense to spread protection needs analyses across multiple workflow plans so they can be reassessed throughout the year, e.g., some in the spring and some in autumn. If, for example, you have created a workflow plan for the spring and one for the fall and those repeat annually, and you have an especially sensitive organizational unit that needs to be reassessed twice a year (in the spring and the fall), you can add the protection needs analysis to both the workflow plans.<p> | It makes sense to spread protection needs analyses across multiple workflow plans so they can be reassessed throughout the year, e.g., some in the spring and some in autumn. If, for example, you have created a workflow plan for the spring and one for the fall and those repeat annually, and you have an especially sensitive organizational unit that needs to be reassessed twice a year (in the spring and the fall), you can add the protection needs analysis to both the workflow plans.<p> | ||
If the circle of participants for a protection needs analysis changes, if many new resources/data categories are adde4d, or if there hasn't been a personal interview in a longer while, then we also recommend a manual reassessment as an interview.<p> | If the circle of participants for a protection needs analysis changes, if many new resources/data categories are adde4d, or if there hasn't been a personal interview in a longer while, then we also recommend a manual reassessment as an interview.<p> | ||
If a protection needs analysis is assigned to a workflow plan and a reassessment is triggered manually (via the revaluate button), then this new protection needs analysis is assigned as the basis for the next workflow in the linked protection needs analyses. If the reassessment is deleted, the link is reset to the original protection needs analysis. Caution: if a new protection needs analysis revaluating resources/data categories was created with the plus button, this link is not established and it may cause conflicts.<br clear=all> | |||
<br clear=all> |
Version vom 25. August 2025, 09:12 Uhr
Tips, tricks & best practice

Relationships in the structural analysis generally lead to the highest protection need. These dependences can be reduced with a protection needs analysis. One should therefore start with the analysis of those assets/resources/services that are most important to the organization and evaluate them regarding the requirements of the management system first.
It makes sense to spread protection needs analyses across multiple workflow plans so they can be reassessed throughout the year, e.g., some in the spring and some in autumn. If, for example, you have created a workflow plan for the spring and one for the fall and those repeat annually, and you have an especially sensitive organizational unit that needs to be reassessed twice a year (in the spring and the fall), you can add the protection needs analysis to both the workflow plans.
If the circle of participants for a protection needs analysis changes, if many new resources/data categories are adde4d, or if there hasn't been a personal interview in a longer while, then we also recommend a manual reassessment as an interview.
If a protection needs analysis is assigned to a workflow plan and a reassessment is triggered manually (via the revaluate button), then this new protection needs analysis is assigned as the basis for the next workflow in the linked protection needs analyses. If the reassessment is deleted, the link is reset to the original protection needs analysis. Caution: if a new protection needs analysis revaluating resources/data categories was created with the plus button, this link is not established and it may cause conflicts.