> For the complete documentation index, see [llms.txt](https://docs.aquilax.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquilax.ai/blog/ai/ai-driven-vulnerability-triage.md).

# AI-Driven Vulnerability Triage

<figure><img src="/files/viCFsjbXPJBdrCJDVrPm" alt=""><figcaption><p>AI-Driven Accuracy in Security Reviews</p></figcaption></figure>

\
Traditional Static Application Security Testing (SAST) tools generate excessive noise, overwhelming security teams with false positives. The AquilaX AI-powered Findings Review Model transforms this process by automating vulnerability classification with high accuracy and efficiency. Using machine learning and real-world security insights, it significantly reduces false positives, streamlines triage, and enhances DevSecOps workflows. This cutting-edge AI solution ensures that security teams focus on critical threats, eliminating the manual burden of reviewing low-risk findings.

Download the white-paper here: <https://aquilax.ai/ai-driven-accuracy-in-security-reviews>


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aquilax.ai/blog/ai/ai-driven-vulnerability-triage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.