Skip to main content

itemis SECURE 23.2.1

Overview​

The patch 23.2.1 of itemis SECURE addresses several minor issues and makes targeted improvements to enhance your experience and workflow with our software.

In this document, you will find detailed information about the changes, bug fixes, and enhancements we did compared to the 23.2 release. These updates are designed to further enhance the stability and functionality of itemis SECURE.

For an overview of the changes introduced in itemis SECURE 23.2, we encourage you to review the 23.2 release notes.

Reduced Model Checker Information Results​

Checklist items that haven't been assessed yet won't show model checker hints for an empty rationale field. This is done to reduce the number of hints for new and empty projects. Only after you assessed a checklist item will the model checker suggest adding a rationale for traceability reasons.

Bugfixes​

Removed Broken Completion Menus​

When clicking on non-editable links, you will no longer encounter completion menus. Clicking on an entry on one of those menus could break the model by replacing an existing element.

Removed Checkbox Completion Menus​

Clicking on checkboxes will no longer activate completion menus, as checkboxes already auto-toggle on click as expected, preventing any confusion or errors.

Fixed a Report Generation Issue​

Limiting the number of attack steps for calculated attack paths can no longer cause the Threat Scenarios and Attack Paths report item to break.

We've resolved an error that occurred when selecting Zipped Composition as the method configuration and catalog while creating a new project.

UX Improvements​

Related to controls and control groups, we've made several user experience improvements.

Fixed Indicators for Disabled Controls​

Controls now accurately indicate whether they are active by means of the default Control Scenario, providing users with immediate feedback on their configuration.

Clarified Editor for References to Control Groups​

References now refer to Control Groups as such, making it easier to identify and manage them within your projects.

Fixed In-line Control Group Creation​

Whenever you create a new control group in-line (when you specify the groups of a control or the controls or control groups of a scenario), any newly created group will always get a name assigned even if the user didn't specify one. This helps to prevent situations where newly created groups would end up without a proper name or two groups would be assigned the same name.

Added Default Control Scenarios​

We've added default scenarios for "all" and "no" controls, improving the ease of use and reducing the need for manual configurations whenever you create a new project.

Reduced Number of Warnings for Controls​

You will no longer receive warnings for unassigned controls and a missing "all" scenario, reducing unnecessary alerts. If you intentionally decide to delete the new default scenarios you will no longer be prompted to create such a scenario, as you have demonstrated your intention by removing the given one.

Version Mapping​

The following table can be used to determine the itemis SECURE version based on the internal plugin version com.moraad.core stored in the .msd file of every solution:

<language slang="l:2bca1aa3-c113-4542-8ac2-2a6a30636981:com.moraad.core" version="<com-moraad-core-version>" />
com.moraad.core versionitemis SECURE version
8923.2, 23.2.1
8823.1.1
8723.1
8622.4
8122.3
8022.2
7822.1
7421.3