Menü aufrufen
Toggle preferences menu
Persönliches Menü aufrufen
Nicht angemeldet
Ihre IP-Adresse wird öffentlich sichtbar sein, wenn Sie Änderungen vornehmen.
Version vom 2. Juli 2026, 09:17 Uhr von KoKl (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „right|thumb|100px|Button for workflow plans A '''workflow plan''' triggers the reassessment of vulnerability analyses automatically and sends them as a self-assessment to the interview partners. In this way, reassessments can be sent out, for example, annually, in order to check whether the contents are still valid. We discuss details and general information on workflow plans on the page Special:MyLanguage/Workflowpläne|Workflow…“)
(Unterschied) ← Nächstältere Version | Aktuelle Version (Unterschied) | Nächstjüngere Version → (Unterschied)
Button for workflow plans

A workflow plan triggers the reassessment of vulnerability analyses automatically and sends them as a self-assessment to the interview partners. In this way, reassessments can be sent out, for example, annually, in order to check whether the contents are still valid. We discuss details and general information on workflow plans on the page Workflow plans.

Workflow plans for analyses work with reassessments. When the workflow plan is triggered, it works similarly to the manual reassessment with the button. HITGuard creates a new protection needs analysis or vulnerability analysis that is based on the template of the old one. The original analysis remains untouched and write-protected in the system.

This variant lets you plan and automate reassessments in advance.