> For the complete documentation index, see [llms.txt](https://helm.docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helm.docs.medcrypt.com/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/create-an-alias-to-link-unmatched-software-to-known-software.md). # Create an alias to link unmatched software to known software You can use aliases to match any dependency components in your SBOM that have multiple matches or are unmatched to known software components in the NVD. These can be created by your Administrators. ### View aliased matches To view aliases, click the **Aliases** item in the sidebar. If you have appropriate [permissions](/~/changes/KjixZskptrAaNWiTYnvj/administration/manage-users.md), you will see an **Aliases** table with the original name of the dependency component in your SBOM, the linked (aliased) name of the known software in the NVD. In the **Software Bill of Materials (Products)** page, you will see a **Matched** status with an **ALIAS** token in the **Match status** column for all aliased matches. ### Create an alias When resolving[ **Select match**](/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/resolve-match-statuses.md#resolve-select-match-or-not-found-status), [**Not found**](/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/resolve-match-statuses.md#resolve-select-match-or-not-found-status), and other [match statuses](/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/resolve-match-statuses.md), users with an [**Administrator** role ](/~/changes/KjixZskptrAaNWiTYnvj/administration/manage-users.md)can create an alias for a dependency component in your SBOM to a particular software that exists in the NVD. If you're not an **Administrator**, but have identified a likely match, contact one of your administrators to have the alias created for you. There are two ways you can create aliases: directly from the unmatched dependency component or from the **Aliases** page (detailed above). To create an alias directly from the dependency component: 1. Navigate to the **Software Bill of Materials (Products)** page, then click **Resolve i**n the **Actions** column. This will display the **Resolution options** modal. 2. Click the **Create alias** button to display the **Create alias** modal. 3. The scope is defaulted to **Organization**, which means that this alias you create for this dependency component will be linked in the future any time anyone else in your company uploads an SBOM that contains this dependency component. There isn’t another option for this currently. 4. Enter the **Dependency name** that you’re creating the alias link for, then click **Next**. You’ll then be prompted to enter the dependency name. 5. Enter all or part of your dependency name. Select the supplier/dependency combo that best matches your dependency, then click **Create**. You’ll be prompted to confirm this alias. 6. When you’re ready to confirm the alias, click **Confirm**. This will change any **Not found** or **Select match** statuses to **Matched**. Going forward, whenever you or anyone else in your organization uploads this dependency component in an SBOM, this alias will be applied. {% hint style="info" %} **IMPORTANT**: Aliases are **not applied retroactively** to SBOM dependency components that have already been uploaded, only to those created or uploaded in the future. {% endhint %} ### Remove an alias If you find that your team has added an incorrect alias, you can easily remove it if you are an **Administrator**. 1. Click the **Aliases** item in the sidebar. If you have appropriate [permissions](/~/changes/KjixZskptrAaNWiTYnvj/administration/manage-users.md), you will see an **Aliases** table with the original name of the dependency component in your SBOM, the linked (aliased) name of the known software in the NVD. 2. Click the row that you want to remove to highlight it, then click **Remove**. You'll be prompted to confirm the removal. ### Alias permissions * **Administrator:** Users with an **Administrator** role can view and edit all products, as well as create aliases and use existing aliases to link software in their SBOMs to known software in the NVD. * **User with edit permissions for a product:** Users who have edit permissions for a particular product, but are not **Administrators**, will be able to view and use existing aliases for that product to link software in their SBOM to known software in the NVD, but will not be able to create aliases unless they have an **Administrator** role. * **User with read-only permissions for a product:** These users will be able to view aliases for that product, but will not be able to use these aliases to link software. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://helm.docs.medcrypt.com/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/create-an-alias-to-link-unmatched-software-to-known-software.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.