> For the complete documentation index, see [llms.txt](https://docs.catchify.sa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catchify.sa/portal-guide/findings-management/scoring-explained.md).
# Scoring Explained
In Catchify, each finding is scored based on **Risk** and **Criticality** to help you prioritize what matters most. These scores are set by our assigned pentester, aligned with your organization’s risk profile.
### 🔍 Scoring Breakdown
* **Severity** – Reflects the urgency of the issue based on its potential impact
* **Impact** – Describes how serious the consequences would be if exploited
* **Likelihood** – How likely the vulnerability is to be successfully exploited
* **CVSS** – A standardized score (0–10) that combines impact and likelihood into a single risk number
> **CVSS**: A higher score means the issue is more critical and should be prioritized for remediation.
These scores are visualized in the Risk Matrix inside your Catchify portal, giving you a clear view of which vulnerabilities need urgent attention.
---
# 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.catchify.sa/portal-guide/findings-management/scoring-explained.md?ask=&goal=
```
`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.