Configuration
🚧 Work in progress
Each project needs a configuration. Projects can use either the default configuration provided by the tool or a customized configuration. The chosen configuration is copied at project creation and saved as part of the project file. Therefore, changing the configuration of a project has no influence on the original configuration.
Important
After changing the configuration of a project, the project needs to be saved and reloaded in order to work properly.
It is recommended to create a complete configuration first and then create the project. However, if the configuration of a project needs to be adjusted, it is recommended to only add new objects and not to delete existing ones.
Caution
Changing the configuration of a project may lead to undefined behavior.
Table of Contents
- Analysis Fields
- Assumptions & Constraints
- Assets (coming soon)
- Stencils (coming soon)
- Software & Process Components
- Checklists
- Risk Assessment
- Protection Goals
- Threat Categories (coming soon)
- Threat Sources (coming soon)
- Attack Vectors (coming soon)
- Threat Rules (coming soon)
- Controls (coming soon)
Localization
The configuration file includes a dictionary for translations. This dictionary can be used to provide translations for texts that are part of the configuration. The feature is currently only available for selected settings but may be extended on request.
The localization of a text can be opened via the "language" button (see blue circle). In the localization dialog, there are three options:
- No translation: The text is always shown as entered in the text field.
- Existing entry: An existing translation can be reused. This can be achieved by searching for a translation key and then clicking on the check icon at the beginning of the row.
- Custom entry: Create a new translation by defining the key and the translations for each language.