> 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/medcrypt-documentation/guardian/get-started.md).

# Get started

Medcrypt's Guardian Platform provides PKI-based cryptographic security for medical devices, ensuring device authentication, secure communication, and regulatory compliance without disrupting performance. [Learn more about PKI and why it matters for medical devices](/medcrypt-documentation/guardian/get-started/what-is-public-key-infrastructure-pki.md).

## **Guardian components**

Guardian consists of two main components:

* **Guardian Library**: Guardian Library runs on your devices to parse configuration profiles, request certificates from Guardian Cloud, and enable cryptographic functions like signing and encryption. Available for C++, C, Java, and more.
* **Guardian Cloud**: Cloud-based platform that processes certificate requests, enrolls devices into trust hierarchies, and generates certificates. This is the part of the Guardian platform formerly known as Overwatch.

## **Guardian core principles**

* All connections between devices should be secured
* Keys generated on the device never leave the device (including protection against data exfiltration methods)
* Keys should be rotatable as frequently as needed
* Key usage should be specific and isolated to particular operational contexts
* Security policy should be codified in signed configuration that drives operational usage

## **What Guardian provides:**

* Rapid deployment and seamless integration into new and existing systems
* Self-serve management through an intuitive web interface
* Device cryptographic identities with certificate-based authentication and automated lifecycle management
* Automated compliance reporting for FDA and other regulatory requirements
* Support for diverse hardware platforms, operating systems, and cryptographic libraries

## **What Guardian does:**

* Automated cryptographic key generation and management with unique keys for each device. Keys are FIPS 140-2 and FIPS 140-3 Level 3 compliant.
* Secure device-to-device communication (East-West protection)
* Secure device-to-cloud communication (North-South protection)
* Provisioning lifecycle management
* Support for memory-constrained and connectivity-limited devices
* Zero-trust security architecture implementation
* Legacy system protection without code modification
* Certificate lifecycle management (coming soon!)
* PKI operations

## **Common use cases:**

* Create segmented security zones across multi-device ecosystems
* Protect sensitive assets throughout the manufacturing process
* Establish trusted connections to cloud services
* Meet FDA cybersecurity requirements
* Implement zero-trust security architectures
* Manage cryptographic keys throughout device lifecycle
* Provide legacy system security without code modification


---

# 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/medcrypt-documentation/guardian/get-started.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.