Updated:2024-09-29 SBOM Central
This page contains legal information about MAIA Software, and can be opened from the Settings menu.
Tabs:
- Licensing Information: license information from included software.
- General terms of use.
- Privacy Policy.
This chapter contains information about the web pages in SBOM Central.
This page contains legal information about MAIA Software, and can be opened from the Settings menu.
Tabs:
An API token is used to secure and authenticate access to an API.
When a valid token is provided, the API server grants the appropriate level of access. The request is rejected if the token is invalid or lacks necessary permissions.
This is a page where all tokens belonging to the user are listed. On the page, you can Create, Reveal, and Delete tokens.
Reveal can only be performed once per token.
Content:
There are two types of components:
The CWEs (Common Weakness Enumeration) menu page is an index page listing the current most dangerous software weaknesses. The list is published yearly by MITRE (external link) where each weakness type gets a score (0-100).
Priority setting.
Header | Description |
---|---|
Identifier | CWE identity and a link to detailed information at the MITRE home page. |
Score | Severity score |
Priority | A priority level is indicated with a colored thermometer (see below). |
Description | Short description. |
Environments are environment information related to SBOMs, etc, with the ability of connecting variables to tags.
The index page lists all available environments.
Heading | Description |
---|---|
Name | Identity of the environment. |
Comment | Additional information. |
Tags | Tags associated with the environment. |
Filter by | Description |
---|---|
Search | Search table info. |
Tags | Filter by tags |
An external artifact is usually a version of an open source component.
Content:
The Reports page collects various reports generated in the WebApp.
Content:
Definition: A team is a group of people who perform interdependent tasks to accomplish a common mission or specific objective.
The purpose of a team is to limit the access users have to data in WebApp so that the work of different teams can be separated from each other.
Content:
The team contains:
A user can be a member of one or more teams.
A user can switch between teams to access different subsets of information. This allows multiple teams to work in the WebApp simultaneously without creating conflicts.
The team root is a mandatory team used for administrative purposes in the WebApp. By default, the root team is granted all admin permissions.
Content:
Users are in an active state as long as they belong to a team. A user can be a member of one or more teams.
A user can switch between its teams to access different subsets of information. This allows for multiple teams to work in the SBOM Central WebApp simultaneously, without creating conflicts.