verinice 52

The following new features are available to users with the release of verinice 52.

Improving the handling of Markdown fields

The use of Markdown fields is to be improved, particularly for catalog elements (controls, scenarios, etc.), by ensuring that they:

• can be edited even after creation.
• can be populated via CSV import.

Improvements to OnPrem operation prior to roll-out

Improvements for OnPrem operation prior to the official roll-out (Helm chart and Talos VM).

Minor improvements and bug fixes (Uncommon valor)

Minor improvements and bug fixes in the Uncommon valor sprint.

Bug fix: Objects from other units can be viewed

Objects from a unit cannot be viewed with an incorrect UUID.

Bug fix: Risk values are lost

In the risk dialog, the potential impacts are not always loaded correctly.

Use translation of the domain name in the domain selection

In the domain selection, the translation is displayed instead of the domain name.

Manual test of the object view

Manual test of the object view, including all functionalities.

Manual test of object overview

Manual test of the object overview, including all functionalities.

Bug fix: Origination in RI must be required

In the RequirementImplementationDto endpoint, the Origination field is optional, which makes no business sense since the control must be implemented at some level. The field must be required.

More Compact Menu

The menu has been redesigned to be more compact to avoid unnecessary scrolling:

Standardize Documentation Creation

The creation and updating of the verinice documentation should be documented for content creators. This part of domain development, currently used only internally, must be standardized for future white-label use.