> 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/openvas.md). # OpenVAS PlexTrac supports importing XML files from **OpenVAS**. OpenVAS (Open Vulnerability Assessment System) is a network security scanner and vulnerability management solution designed to identify and assess vulnerabilities in network infrastructure and web applications. It performs scans of networks and hosts to identify open ports, running services, and potential vulnerabilities. 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.
## Finding Field Mappings | PlexTrac Field | OpenVAS Path | Notes | | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | title | \\\ | | | | severity | \\ | | | | references |

\\\
\\\\
\\\
\\\

|

A combination of:
\: we ignore "NOXREF" if populated in the \ element and

\: we take the id and type from all cert\_ref tags in the \ element and

\: we ignore "NOCVE" if populated in the \ element and

\: we ignore "NOBID" if populated in the \ element

| | | recommendations | \\\ |

PlexTrac parses the element into separate items based on the | delimiter that creates an array of key value pairs. Then we evaluate the array to compose description. Description is composed of the following values, if the key exists:

  • summary
  • impact
  • insight
  • affected
  • vuldetect
| | description | \\\ |

PlexTrac parses the \ element into separate items based on the | delimiter that is used to create an array of key value pairs. Then we evaluate the array and compose recommendations from the following values, if the key exists:

  • solution
  • solution\_type

If solution is not in the array, we populate the solution with the phrase: "A solution was not provided by the scan source"

| | score: \ | | | | | label: cvss | | | | | value | \\\ | | | | calculation | \\\ |

PlexTrac parses the element into separate items based on the | delimiter that creates an array of key value pairs. Then we evaluate the array and compose cvss calculation: Calculation is composed of the following values, if the key exists:

  • cvss\_base\_vector
| ## Asset Field Mappings | PlexTrac Field | OpenVAS Path | | -------------- | ---------------- | | asset | \\ | --- # 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/openvas.md?ask=&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.