---
title: "Discussion on \"Risk Acceptance: How to Document a Vulnerability Your Client Won't Fix\" | Hashnode"
description: "Discussion on \"Risk Acceptance: How to Document a Vulnerability Your Client Won't Fix\". What to write down, who signs it, and when to ask again"
url: "https://hashnode.com/posts/vulnerability-risk-acceptance/6ad95d8d0c9ccb04a2f55a8a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Risk Acceptance: How to Document a Vulnerability Your Client Won't Fix](https://varaxontech.hashnode.dev/vulnerability-risk-acceptance?utm_source=hashnode&utm_medium=feed)

What to write down, who signs it, and when to ask again

Oct 22 · 4 min read · varaxontech.hashnode.dev  
Updated 21h ago  
Read the article

-   [#cybersecurity](https://hashnode.com/tag/cybersecurity)
-   [#security](https://hashnode.com/tag/security)
-   [#msp](https://hashnode.com/tag/msp)
-   [#vulnerability-management](https://hashnode.com/tag/vulnerability-management)
-   [#compliance](https://hashnode.com/tag/compliance)

## Written by

[Brandon Sooknanan](https://hashnode.com/@varaxonceo)

@varaxonceo

  
[View profile](https://hashnode.com/@varaxonceo)

AI vulnerability reports for MSPs and security teams

Varaxon turns exports from the scanners you already use into clear, prioritized client reports, with tickets in your PSA after review. Practical writing on vulnerability management for MSPs, MSSPs and security consultants. Try it free at varaxontech.com

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
