> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases.md).

# Playbooks

Complete walkthroughs showing how Heeler's parts combine to resolve one security problem, from start to finish.

The rest of the docs explain features one at a time. A **playbook** shows how they **work together** to solve a real problem — start from a goal you recognize ("is this CVE actually exploitable?", "prove our posture to an auditor"), and follow it through every part of the product that's involved, end to end.

Each playbook names the capabilities it draws on, walks the steps in order with realistic examples, and ends with how to confirm it worked — linking out to the feature docs when you need deeper configuration detail.

## Investigate and respond to risk

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Determine Exploitability in Production</strong></td><td>Narrow a CVE across your estate to the instances that are reachable, running and internet-exposed.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/determine-exploitability-in-production.md">Determine Exploitability in Production</a></td></tr><tr><td><strong>Contain a Leaked Secret</strong></td><td>From detection to a rotated, revoked credential that can't come back.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/contain-a-leaked-secret.md">Contain a Leaked Secret</a></td></tr></tbody></table>

## Remediate and verify

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Fix a Vulnerable Dependency and Verify It's Deployed</strong></td><td>Route it to the right team, auto-generate a validated fix, and confirm it deployed.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/fix-and-verify-in-production.md">Fix a Vulnerable Dependency and Verify It's Deployed</a></td></tr><tr><td><strong>Run Unattended Dependency Remediation</strong></td><td>The same loop at program scale — critical and high dependency findings driven to zero with no operator dispatching the work.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/run-unattended-dependency-remediation.md">Run Unattended Dependency Remediation</a></td></tr></tbody></table>

## Secure your software supply chain

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Build a Supply Chain Security Program</strong></td><td>Stop malicious and immature packages at the door, and fix the rest in priority order.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/building-a-proactive-supply-chain-security-program.md">Build a Supply Chain Security Program</a></td></tr><tr><td><strong>Secure AI Coding Agents</strong></td><td>Discover, score, and govern the skills, MCP servers, and agent files running with your developers' access.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/secure-your-ai-coding-agents.md">Secure AI Coding Agents</a></td></tr><tr><td><strong>Secure Deployments on Vercel</strong></td><td>Bring your Vercel estate under one model — coverage, findings, data, AI surface, and prevention.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/secure-what-you-ship-on-vercel.md">Secure Deployments on Vercel</a></td></tr></tbody></table>

## Run and prove your program

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Run an SLO-Driven AppSec Program</strong></td><td>Every finding owned, on a clock, with new risk gated out at the pull request.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/run-an-slo-driven-appsec-program.md">Run an SLO-Driven AppSec Program</a></td></tr><tr><td><strong>Vulnerability Jail</strong></td><td>Attach a real consequence to overdue remediation — a team past its SLO can open pull requests, but not merge them.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/vulnerability-jail.md">Vulnerability Jail</a></td></tr><tr><td><strong>Evidence for a Security Audit</strong></td><td>Pull posture, SLO attainment, license compliance, SBOMs, and a change log into one evidence pack.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/prove-your-security-posture.md">Evidence for a Security Audit</a></td></tr></tbody></table>

## Design securely

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Threat-model a service from what's actually running</strong></td><td>Export a runtime-informed model of a service and drive a STRIDE assessment from real data.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/threat-modeling-with-service-decomposition.md">Threat-Model a Service</a></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, and the optional `goal` query parameter:

```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases.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.
