> 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/readme.md).

# Medcrypt 문서

Medcrypt는 의료기기 팀이 제품 수명 주기 전반에서 사이버 보안을 구축하고, 입증하고, 유지하도록 지원합니다. 시작하려면 작업 중인 제품을 선택하세요.

<table data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>MSI</strong></td><td>AI 지원 규제 업무: 자체 증거를 기반으로 위협 모델, 제출 문서, 감사 및 성숙도 평가를 수행합니다.</td><td><a href="/ko/msi/msi.md">MSI 개요</a></td></tr><tr><td><strong>MedISAO</strong></td><td>의료기기 보안 인텔리전스 공유: CVE 및 권고문을 검색하고, 병원과 개선 조치를 공유하며, 취약점 공개를 조율합니다.</td><td><a href="/ko/medisao/medisao.md">MedISAO 개요</a></td></tr><tr><td><strong>Helm</strong></td><td>SBOM 및 취약점 관리: SBOM을 업로드하고, 구성 요소를 매칭하며, 위험의 우선순위를 정하고 개선한 뒤 FDA 제출용 보고서를 내보냅니다.</td><td><a href="/ko/helm/helm.md">Helm 개요</a></td></tr><tr><td><strong>Guardian</strong></td><td>기기 보안 라이브러리: 기기에서 프로비저닝, 보안 전송 및 암호화 작업을 수행하기 위한 C++ API입니다.</td><td><a href="/ko/guardian/guardian.md">Guardian 개요</a></td></tr></tbody></table>

### 인기 페이지

<table data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>시작하기</strong></td><td><ul><li><a href="/ko/msi/get-started/create-your-first-device.md">첫 MSI 기기 만들기</a></li><li><a href="/ko/helm/get-started-with-helm/quickstart-process.md">Helm 빠른 시작</a></li><li><a href="/ko/helm/get-started-with-helm/upload-your-first-sbom.md">첫 SBOM 업로드</a></li><li><a href="/ko/guardian/get-started/quickstart-process.md">Guardian 빠른 시작</a></li></ul></td><td></td></tr><tr><td><strong>FDA 준비</strong></td><td><ul><li><a href="/ko/helm/ensure-fda-readiness/fda-and-cisa-cybersecurity-requirements-for-medical-devices.md">FDA 및 CISA 요구사항</a></li><li><a href="/ko/msi/check-estar-readiness.md">eSTAR 준비 상태 확인</a></li><li><a href="/ko/helm/ensure-fda-readiness/fda-ready-sbom-and-vulnerability-reports.md">FDA 제출용 SBOM 및 VEX 보고서</a></li><li><a href="/ko/msi/check-estar-readiness/run-a-regulatory-audit.md">규제 감사 실행</a></li></ul></td><td></td></tr><tr><td><strong>참고 자료</strong></td><td><ul><li><a href="/ko/reference/cybersecurity-terminology.md">사이버 보안 용어</a></li><li><a href="/ko/helm/automate-and-integrate/api-sdk-documentation.md">Helm API SDK</a></li><li><a href="/ko/guardian/api-overview/api-reference.md">Guardian API 참조</a></li><li><a href="/ko/helm/changelog.md">Helm 변경 로그</a></li></ul></td><td></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 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/readme.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.