# Adding Assets to a Client Assets within PlexTrac are stored outside of reports at the client level within the platform. An asset can exist as a standalone file in the Clients module or associated with a finding, referred to as an affected asset. Organizations can efficiently manage and track their cybersecurity resources by organizing and storing assets in PlexTrac. This centralized approach ensures that important files and information are readily accessible when necessary, facilitating collaboration, efficient vulnerability management, and streamlined remediation efforts. ## Creating an Asset Step 1: From the **Clients** module home page, click the client's row or **View** under the "Actions" column.
Step 2: Click the **Assets** tab. Step 3: Click the **Add assets** pulldown menu and select **Create asset**.
Step 4: The "New Asset" modal appears. Enter the desired information into the appropriate fields. {% hint style="info" %} Asset Name is the only required field. {% endhint %}
Step 5: Click **Save** at the bottom of the modal.
The asset now appears in the **Assets** tab. ## Adding Assets via Bulk Paste Step 1: From the **Clients** module home page, click the client's row or **View** under the "Actions" column.
Step 2: Click the **Assets** tab. Step 3: Click **Add assets**, then select **Bulk paste assets** from the pulldown menu.
Step 4: Paste asset information into the provided box as a return- or comma-separated list. PlexTrac will parse the assets and add them to the finding. URLs with paths (i.e., [www.plextrac.com/test/](http://www.plextrac.com/test/)) will be separated into parent and child assets.
{% hint style="info" %} Check "Preserve pasted assets" to treat the pasted content as a monolithic asset. The parser will **not** attempt to break down the asset into its constituent parts (child assets) or identify potentially vulnerable parameters.\ \ ![](https://4252973360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXA6EayCcg12qfDcfXd%2Fuploads%2FeA5Zyr4XOFBZnK1TS2HA%2Fimage.png?alt=media\&token=d7eeea09-a2c7-4976-b290-e3d6d287d18c) {% endhint %} Step 5: Click **Next**. Step 6: PlexTrac will search for assets in the bulk paste that match existing assets and identify them separately from new assets on the **Review** tab. This provides the option to deselect any assets before import.
Step 7: Click **Next**. Step 8: Add any tags (optional). Click **Add X assets**.
A message confirming the import and assets are viewable from the **Assets** tab will appear. ## Importing Assets to Clients PlexTrac supports asset imports using an NMAP file or a CSV template: * **NMAP files**: Network Mapper is a [free, open-source ](https://nmap.org/)network discovery and security auditing utility. More information on NMAP can be found on PlexTrac's [Integrations](https://docs.plextrac.com/plextrac-documentation/product-documentation-1/integrations-and-file-imports) section of this site. * **CSV**: PlexTrac provides a template for uploading assets to a client. Click the file below to download the template: {% file src="" %} updated 4-20-2023 {% endfile %} ### CSV Asset Template Rules The template is prepopulated with all permitted fields and sample values. {% hint style="danger" %} Do not add additional columns or some data may not be imported. {% endhint %} | Column Header | Description | Sample Value | Comments | | ----------------- | ---------------------------------------------------- | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | name | Asset Name | temp-asset-1 | | | ip addresses | IP address of the asset | 10.0.0.10 | | | criticality | Importance level of the asset | High | | | data owner | Person responsible for the data | Jane Pentester | | | physical location | Geographic location of the asset | Boise | | | system owner | Person responsible for the system | John | | | ports | Open/closed ports and associated services | 22/open/tcp//ssh//OpenSSH 4.3 (protocol 2.0)/ | Each port can have up to eight values, separated by a slash. See the Ports section below after the table for more information. | | tags | Categorization tags | Karbo | | | description | Brief description of the asset | csv-desc1 | | | parent | Hierarchical relationship | Child 1 | | | type | Asset type | Workstation |

The value for this field must be one of the following: Workstation, Server, Network Device, Application, or General. If another value is used, it will be ignored, and the Asset Type value will display in PlexTrac as "Not Set."

This field is not case-sensitive.

| | host fqdn | Fully Qualified Domain Name | [www.plextrac.com](http://www.plextrac.com/) | | | hostname | Name of the host | temp-asset-1 | | | host rdns | Reverse DNS lookup | 4.3.2.1.in-addr.arpa | | | dns name | DNS name associated with the asset | 192.0.2.44 | | | mac address | Media Access Control address | 00-B0-D0-63-C2-26 | | | netbios name | NetBIOS name of the asset | temp-asset-1 | | | total cves | Total number of Common Vulnerabilities and Exposures | 8 | | | pci status | Payment Card Industry compliance status | Fail |

The value for this field must be blank, Passor Fail. If another value is used, it will be ignored, and the Asset Type value will display in PlexTrac as "Not Set."

This field is not case-sensitive.

| | operating system | OS running on the asset | Windows 11 | | #### Ports Column G ingests port information imported and found in the asset's **Notes/Description** tab.
Multiple values for the ports cell are separated by commas, such as: `22/open/tcp//ssh//OpenSSH 4.3 (protocol 2.0)/, 25/open/tcp//smtp///, 53/closed/tcp//domain///, 70/open/tcp//gopher///, 80/open/tcp//http//Apache http 2.2.3 ((CentOS))/, 113/open/tcp//auth///, 31337/open/tcp//Elite///` Each port can have up to eight values, separated by a slash. This means there must be seven slash characters (/) for each port ingested, even if no data exists within the slashes. If the correct number of slashes is not used, an import error will appear, and the file will not be accepted. Examples of valid data values for the ports field: * 80/////// * 80/open////// * 80/open/tcp///// * 80/closed/tcp/auth//// * 80/open/tcp/auth/ssh/// * 80/open/tcp/auth/ssh/test 6// * 80/open/tcp/auth/ssh/test 6/Apache http 2.2.3 (CentOS)/ The first value captures the port number. The second value captures the port status (any ports with a status of `Closed` will not be imported). The third value captures the protocol. The fifth value captures the service, and the seventh value captures the version. {% hint style="info" %} If the port has a defined closed status, the cell is left blank entirely (the field is optional), or just one value is entered (such as `15.22.161.22`), then it is not necessary to include all seven slashes. {% endhint %} ### Importing Assets Step 1: From the **Clients** module home page, click the report row or **View** under the "Actions" column.
Step 2: Click the **Assets** tab. Step 3: Click **Add assets**, then select **Bulk paste assets** from the pulldown menu.
Step 4: Drag a file into the modal or click the box to navigate to the file on the computer.
Step 5: Click **Import**.
A message will appear confirming import. The new assets are displayed on the **Assets** tab. To view imported values, click **View** of the imported asset.
To view imported port information, click **Notes/Descriptions**.