> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/vulnerabilities/glossary.md).

# Glossary

This glossary defines key terms used throughout the *Vulnerabilities* section in Sprinto. Use it as a reference to better understand the terminology related to vulnerability management, compliance, and evidence tracking.

<table><thead><tr><th width="238.75390625">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Vulnerability</strong></td><td>A flaw or weakness in a system that could be exploited to compromise security, such as unpatched code, misconfigurations, or exposed endpoints.</td></tr><tr><td><strong>Pentest</strong> (Penetration Test)</td><td>A security test conducted by a certified external party to identify vulnerabilities in a product or infrastructure.</td></tr><tr><td><strong>Monitoring Source</strong></td><td>An integrated tool or service that detects vulnerabilities and sends findings to Sprinto (e.g. AWS Inspector, GitLab, SonarCloud).</td></tr><tr><td><strong>System-status Check</strong></td><td>An automatic compliance check triggered when a vulnerability is detected by an integrated source. It is resolved automatically when the vulnerability is closed at the source.</td></tr><tr><td><strong>Workflow Check</strong></td><td>A manual compliance check that must be configured by the user. It requires periodic action and evidence submission.</td></tr><tr><td><strong>SLA (Service Level Agreement)</strong></td><td>A predefined time window within which a vulnerability must be resolved. SLA tracking ensures timely remediation and compliance.</td></tr><tr><td><strong>Evidence</strong></td><td>Documentation (such as scan reports, screenshots, or logs) uploaded to confirm completion of a workflow check or remediation activity.</td></tr><tr><td><strong>Special Case</strong></td><td>A designation for vulnerabilities that are not applicable or cannot be resolved. Marking a special case prevents check failure while retaining audit visibility.</td></tr><tr><td><strong>Due/Critical/Failing</strong></td><td>Status indicators for system or workflow checks. A check becomes <em>Critical</em> as the SLA approaches expiry and <em>Failing</em> once overdue.</td></tr><tr><td><strong>Passing</strong></td><td>Indicates that a vulnerability has been resolved or a check has been successfully completed with valid evidence.</td></tr><tr><td><strong>VPAT</strong></td><td>Vulnerability and Penetration Assessment Test. A certified pentest report uploaded to Sprinto as part of regular compliance.</td></tr></tbody></table>


---

# 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:

```
GET https://docs.sprinto.com/data-library/vulnerabilities/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.