Menü aufrufen
Toggle preferences menu
Persönliches Menü aufrufen
Nicht angemeldet
Ihre IP-Adresse wird öffentlich sichtbar sein, wenn Sie Änderungen vornehmen.

Translations:Schwachstellen/45/en: Unterschied zwischen den Versionen

Aus HITGuard User Guide
Sala (Diskussion | Beiträge)
Die Seite wurde neu angelegt: „To avoid having to perform a new check every time a measure is implemented, HITGuard offers the option of subjecting these marked test objects to a semi-automa…“
 
Faha (Diskussion | Beiträge)
Keine Bearbeitungszusammenfassung
Zeile 1: Zeile 1:
To avoid having to perform a new check every time a measure is implemented, HITGuard offers the option of subjecting these marked test objects to a semi-automatic re-evaluation. This means that HITGuard automatically updates the deviation of the respective test questions of the test objects. In this process, the test questions that are affected by the implementation of measures are set to the "after" value of the vulnerability reduction.
To avoid having to perform a new check every time a measure is implemented, HITGuard offers the option of subjecting these marked review objects to a semi-automatic re-evaluation. This means that HITGuard automatically updates the deviation of the respective test questions of the review objects. In this process, the test questions that are affected by the implementation of measures are set to the "after" value of the vulnerability reduction.

Version vom 8. August 2022, 10:47 Uhr

To avoid having to perform a new check every time a measure is implemented, HITGuard offers the option of subjecting these marked review objects to a semi-automatic re-evaluation. This means that HITGuard automatically updates the deviation of the respective test questions of the review objects. In this process, the test questions that are affected by the implementation of measures are set to the "after" value of the vulnerability reduction.