> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/analyze-with-ox/analyzing-scan-results.md). # Analyzing Scan Results OX unifies findings from your source control, pipelines, registries, cloud accounts, and external testing tools into a single, consistent view. Each result is normalized, deduplicated, linked to its asset and owner, and refreshed on every scan. Use filters to narrow results by application, severity, status, policy, time window, and ownership. Review root cause, exploitability, affected assets, and remediation steps. Track SLAs and confirm fixes with evidence from subsequent scans. Analysis views in OX: * **Active Issues:** A cross-environment list of findings with full context and guidance. Triage, prioritize, assign, and verify fixes with links to code, builds, and assets. * **Applications:** An application-centric summary of posture. See open work, risk indicators, ownership, and progress for each product or service. * **Matching third-party projects to OX apps:** Map external project identifiers (for example, scanner “projects” or repo paths) to OX applications to consolidate results and ownership. Supports automatic suggestions with manual review and API updates. * **Importing issues from external systems:** Bring findings from other scanners or ticketing systems into OX, preserve key metadata, deduplicate against existing results, and keep status synchronized for reporting and audits. --- # 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.ox.security/analyze-with-ox/analyzing-scan-results.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.