# Who should use Guardian?

Guardian is ideal for medical device manufacturers who need to:

**You need Guardian if you have:**

* Devices with technical constraints, including limited connectivity, memory, or processing power (e.g.,  pacemakers, insulin pumps, surgical instruments)
* Legacy systems that can't be easily modified
* Multiple devices that need to communicate securely
* Limited resources for managing PKI infrastructure
* Need to meet FDA cybersecurity requirements

**Common use cases:**

* Eliminate security vulnerabilities in device-to-device communication
* Streamline FDA compliance with automated reporting and documentation
* Establish trusted connections to cloud services
* Implement zero-trust security architectures
* Manage cryptographic keys throughout device lifecycle

## Teams

All of your teams benefit from using Guardian, as in these example initiatives.

* Product security engineers: Implementing zero-trust architectures.
* Software developers: Integrating security with minimal code changes.
* Product owners: Planning compliant security implementations
* Manufacturing teams: Implementing and streamlining device provisioning workflows

## Role and industry-specific solutions

No matter your role, Guardian has you covered.

#### Healthcare Delivery Organizations (HDOs) 

* **Inventory management:** Automatically detect and authenticate connected medical devices.
* **Vulnerability assessment:** Identify devices with security weaknesses.
* **Segmentation enforcement:** Ensure devices only connect to authorized systems.

#### Medical device manufacturers (MDMs)

* **FDA premarket requirements:** Meet FDA cybersecurity documentation requirements with automated reporting.
* **Secure design practices:** Build security into new devices from inception.
* **Legacy device management:** Secure already-cleared products without code modification.

#### Third-party service providers

* **Safe security updates in the field:** Simplified safe security updates by technicians
* **Remote monitoring:** Establish secure connections for remote service capabilities
* **Security validation:** Verify security measures without disrupting device operation