> 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/nodezero.md). # NodeZero PlexTrac supports importing the ***weaknesses.csv*** from **NodeZero.** NodeZero includes a wide range of penetration testing and security auditing tools, such as network scanners, vulnerability scanners, password cracking tools, and exploit frameworks.

## Finding Field Mappings Below are the mappings of fields and any reference notes to provide context. All data flows from NodeZero to PlexTrac. If a field is not listed, PlexTrac does not currently import it.

NodeZero Field	Direction	PlexTrac Field
NodeZero	-->	Finding Source
Title	-->	Finding Title
Description	-->	Finding Description
Score		Finding Severity
1 - 3.9	-->	Low
4 - 6.9	-->	Medium
7 - 8.9	-->	High
9 - 10	-->	Critical
Finding Status	-->	Open
ProvenEntityEid	-->	Finding Tags
Root Cause	-->	Finding Tags
Confirmed/Unconfirmed		Custom Field
Potential	-->	Custom Field Value
Confirmed	-->	Custom Field Value
Root Cause or Type		Custom Field: "Root Cause"
Security Misconfiguration	-->	Custom Field Value
Vulnerability	-->	Custom Field Value
Context Score		Custom Field: "Context Score"
Context Score Number	-->	Custom Field Value Numeric
Impact	-->	Custom Field
Mitigations	-->	Recommendations
References	-->	References

## Asset Field Mappings Below are the mappings of fields and any reference notes to provide context. All data flows from NodeZero to PlexTrac. If a field is not listed, PlexTrac does not currently import it.

NodeZero Field	Direction	PlexTrac Field
IP or Host Name	->	Child Asset Name
IP or Host Name	->	Affected Asset - Child Asset Name
Hostname	->	Hostname
IP	->	Known Ips (Array)
OS	->	Operating System (Common Delimited)
Port	->	Number
Protocol	->	Protocol
Service	->	Service
Service Type	->	Version
First Seen	->	First Found

--- # 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/nodezero.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.