> 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/guardian/guardian.md). # Guardian overview Guardian provides PKI-based cryptographic security for medical devices: device authentication, secure communication, and regulatory compliance without disrupting performance. The Guardian library abstracts away cryptography-related tasks so your team can focus on the clinical features that are core to your device, rather than building and maintaining a security layer from scratch. ### Set up Guardian and provision devices


Get started	What is Guardian Who should use Guardian? Get familiar with the Guardian UI Quickstart process Provision your first device Download Guardian library Guardian terminology Guardian file types and extensions
Manage systems	Create new system Manage systems Manage certificate trust chain
Manage provisioning	Understand device provisioning Begin device provisioning Provisioning methods Manage device provisioning Export provisioning report
Provision devices via UI	Connected device provisioning Disconnected device provisioning
Manage certificates	Manage device certificates Manage Root of Trust certificates Extract certificates from provisioned devices
Secure your deployment	Security best practices What is PKI?

### Integrate the Guardian library


Provision devices via API	API overview Connected device provisioning Disconnected device provisioning Proxy device provisioning
Provision via command line	Connected device provisioning Disconnected device provisioning Proxy device provisioning
Code examples	Connected device provisioning Disconnected device provisioning Proxy device provisioning
API reference	API overview API reference Guardian class Classes Namespaces Status codes

### Updates and administration


Check out the latest updates!	Changelog
Administration	User roles and permissions Modify your organization's name

## Why an integrated library Learning the basics of how to use crypto libraries such as libsodium or OpenSSL to perform key generation, data signing and encryption, or certificate verification is fairly straightforward. Integrating those operations into a complete security solution is not. A production solution has to address: * Configuration-driven key generation and storage * Certificate management * Security layer and code abstraction, and patching * Security library inventory and version tracking * Vulnerability tracking and reporting Getting all of this right requires an expert team and significant, ongoing effort. Guardian provides it as a service, so you can secure your product without reinventing the security wheel. ## Capabilities * C/C++ library, cross-compilable to targets including ARM and x86, on Linux, QNX, BSD, macOS, Windows, Android, and iOS * Available as a ready-to-build source package or as native library binaries, with bridges to the native library for Java (via JNI) and NodeJS (via pre-gyp and gyp) * Support for popular open-source cryptography libraries * Options for root-of-trust control * Configuration-driven security guided by a best-practices policy * Data security configurations signed by the root of trust These capabilities are designed to cover the [FDA's recommendations for data security in medical devices](https://www.fda.gov/downloads/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/UCM623529.pdf), which place particular emphasis on data encryption, signature verification, intrusion detection, and vulnerability monitoring. Tell us what we've done well and how we can improve: [reach out to us](mailto:support@medcrypt.com).