---
sourceDocument: Yokohama IT Asset Management
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/it-asset-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Asset Management

ft:clusterId :

    - itam

bundleId :

    - itam

workflow :

    - Technology


---

# Create a custom Common Platform Enumeration (CPE) mapping for firmware in your operational technology (OT) assets

# Create a custom Common Platform Enumeration (CPE) mapping for firmware in your operational technology (OT) assets {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

If the CPE mapping for firmware that is embedded into your OT assets
isn't already represented in the Enterprise Asset Management
Content Service, create a custom CPE mapping.

## Before you begin

Important:  
You can create custom CPE mappings only using the OT Asset Workspace. To use the OT Asset Workspace, install the OT Asset Management application on your ServiceNow instance. See [Install OT Asset Management](https://www.servicenow.com/docs/jNnD1rsrsZYUDuHl1GLdFA "You can install the OT Asset Management application (com.sn_otam) if you have the admin role. The application includes demo data and installs related ServiceNow Store applications and plugins if they aren’t already installed.") for detailed instructions.

Role required: sn_eam.enterprise_admin

## About this task

CPE is a standardized naming scheme that enables you to map your information technology (IT) systems, software, and packages to corresponding vulnerability management data in the National Vulnerability Database (NVD). You can
use these mappings to identify and mitigate potential vulnerabilities across your IT infrastructure. All official CPE names are listed in the CPE Product Dictionary, which is hosted and maintained by the National Institute
of Standards and Technology (NIST).

## Procedure

1. Navigate to AllOT Asset WorkspaceNormalization.
2. Select the Custom firmware CPE tab.
3. Select New.
4. On the form, fill in the fields.  
   {#create-custom-firmware-cpe-mapping__table_j2r_3n5_4dc__entry__2}

   | Field | Description |
   |-|-|
   | Firmware product | Firmware product that you want to map to vulnerability management data in the NVD. |
   | Firmware version | Version of the firmware product that you want to map to vulnerability management data in the NVD. |
   | CPE publisher | Publisher of the firmware product, as listed in the CPE Product Dictionary. |
   | CPE product | Name of the firmware product, as listed in the CPE Product Dictionary. |
   | CPE version | Version of the firmware product, as listed in the CPE Product Dictionary. |
   [Table 1. Create New Custom firmware CPE mapping form]

   {#create-custom-firmware-cpe-mapping__table_j2r_3n5_4dc}
5. Select Save.
{#create-custom-firmware-cpe-mapping__steps_jtn_l55_4dc}

*[\>]: and then