> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation-1/integrations-and-file-imports/hcl-appscan.md).

# HCL AppScan

PlexTrac supports importing XML files from **HCL AppScan**. HCL AppScan is a security testing tool used to identify and address security vulnerabilities in web applications before deployment. It uses a combination of dynamic application security testing (DAST) and static application security testing (SAST) techniques to identify vulnerabilities.

{% hint style="info" %}
PlexTrac does not support the export format for older versions of HCL AppScan (export version <2.5).
{% endhint %}

<div align="left"><figure><img src="https://4252973360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXA6EayCcg12qfDcfXd%2Fuploads%2FED4oNhJ07FrZeUV6bxqO%2Fhcl.jpg?alt=media&amp;token=68acb283-94a7-4454-b31c-bf3ce411cdbf" alt=""><figcaption></figcaption></figure></div>

## Finding Field Mappings

Below are the mappings of fields and any reference notes to provide context. If a field is not listed, PlexTrac does not currently import it.&#x20;

<table><thead><tr><th width="223.80977988616291">Plextrac Field</th><th>HCL Path </th></tr></thead><tbody><tr><td>title</td><td><ol><li>Get the issue types: <br>issue-group/item/advisory/ref</li><li>Get the data being imported: <br>advisory-group/item/advisory/name</li></ol></td></tr><tr><td>severity</td><td>issue-group/item/severity</td></tr><tr><td>references</td><td><ol><li>Get the issue types:<br>issue-group/item/advisory/ref</li><li>Get the data being imported:<br>advisory-group/item/advisory/references</li></ol></td></tr><tr><td>recommendations</td><td><ol><li>Get the issue types:<br>issue-group/item/remediation/ref</li><li>Get the data being imported: remediation-group/item/name</li></ol></td></tr><tr><td>description</td><td><ol><li>Get the issue types: <br>issue-group/item/advisory/ref</li><li>Get the actual data being imported. All items are a concatenation of mulitple fields: <br>advisory-group/item/advisory/testDescription <br><br><em>plus</em> <br><br>advisory-group/item/advisory/testTechnicalDescription/text</li></ol></td></tr><tr><td>evidence</td><td>issue-group/item/variant-group/item/issue-information/testReportChunk</td></tr><tr><td>field: &#x3C;cwe></td><td></td></tr><tr><td>label: <strong>cwe</strong></td><td></td></tr><tr><td>value</td><td>issue-group/item/cwe</td></tr><tr><td>scores: &#x3C;cvss></td><td></td></tr><tr><td>label: <strong>cvss</strong></td><td></td></tr><tr><td>value</td><td>issue-group/item/cvss-score</td></tr><tr><td>calculation</td><td>issue-group/item/cvss-vector/base-vector</td></tr></tbody></table>

## Asset Field Mappings

| PlexTrac Field | HCL Path                                                                                                                                                  |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| asset          | <ol><li>Get the entity id:<br>issue-group/item/entity/ref</li><li>Get the data being imported: <br>entity-group/item id=(match from above)/name</li></ol> |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plextrac.com/plextrac-documentation/product-documentation-1/integrations-and-file-imports/hcl-appscan.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.