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

# 취약점 내보내기

다음 **취약점** 페이지에서는 특정 제품의 모든 취약점과 각 취약점이 조직에 미치는 위험을 식별하는 과정에서 팀이 작성한 모든 메모를 내보낼 수 있습니다.

취약점을 내보내는 방법은 두 가지입니다.  **Reports** 페이지에서 내보내거나,  **취약점** 테이블에서 직접 내보낼 수 있습니다.

**Reports에서 취약점 내보내기**

1. 다음을 클릭합니다 **보고서** 사이드바에서 항목을 선택하여 **보고서** 페이지를 표시합니다.
2. 다음의 **Export vulnerabilities** 버튼을 **Vulnerabilities CSV** 카드에서 클릭합니다.

**Vulnerabilities 페이지에서 취약점 내보내기**

1. 에서 **취약점**, 제품 이름과 모든 버전 또는 특정 버전을 선택합니다.
2. 클릭 **Export vulnerabilities**. 이렇게 하면 별도로 필터링하지 않은 모든 취약점이 내보내집니다.


---

# 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.medcrypt.com/ko/helm/manage-vulnerabilities/export-vulnerabilities.md?ask=<question>&goal=<user_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.