> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/security-and-data-protections/security-at-rhino-fcp.md).

# Security at Rhino FCP

Security and privacy are foundational to the **Rhino Federated Computing Platform (Rhino FCP)**. Rhino FCP is designed to enable organizations to collaborate on sensitive data while allowing data custodians to maintain control over their data and computing environments.

## Federated Approach

Unlike traditional approaches that require organizations to centralize or transfer data to a shared environment, Rhino FCP brings computation to where the data already resides.

Data is processed locally within the data custodian's environment, whether deployed on-premises or in the cloud. This allows organizations to collaborate on analytics, AI, machine learning, and other computational workloads without requiring raw data to be transferred to collaborators or centrally stored by Rhino.

This architecture allows organizations to maintain their existing security controls and data governance practices while participating in collaborative workflows.

## Defense in Depth

Rhino FCP uses multiple layers of security and privacy controls to protect data, workloads, and platform resources.

Key capabilities include:

* **Role-based access control (RBAC)** to govern access to data, workloads, and platform functionality.
* **Encryption** to protect sensitive information and platform resources.
* **Comprehensive audit logging** to provide visibility and accountability for activity within the platform.
* **Secure containerized execution**, allowing custom workloads to execute close to the data while providing an isolated environment for processing.
* **Privacy-enhancing technologies**, including support for techniques such as [differential privacy](/security-and-data-protections/differential-privacy.md), k-anonymization, and [homomorphic encryption](/security-and-data-protections/fully-homomorphic-encryption.md).

Together, these controls help organizations limit access to sensitive resources and maintain oversight of how data and workloads are used.

For more information, see [Platform Security Measures](/security-and-data-protections/platform-security-measures.md).

## Data Sovereignty and Privacy

Rhino FCP is designed around the principle that organizations should retain control of their data.

Because workloads execute where the data resides, organizations can participate in multi-site and cross-organizational projects without first moving their raw data into a centralized repository. Only the permitted outputs of a computation need to be shared between participating environments.

This approach can help organizations reduce unnecessary data movement and support data sovereignty requirements across different organizations, cloud environments, and geographic regions.

## Compliance

Rhino maintains an information security and compliance program designed to support organizations operating in highly regulated environments.

Rhino FCP adheres to security and privacy standards and frameworks including:

* **ISO 27001**
* **SOC 2 Type II**
* **HIPAA**
* **GDPR**

## Learn More

For additional information about Rhino's security practices, compliance program, and available security documentation, visit the **Rhino Federated Computing Trust Center** at [**trust.rhinofcp.com**](https://trust.rhinofcp.com).

Or contact us at <security@rhinofcp.com>&#x20;


---

# 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.rhinofcp.com/security-and-data-protections/security-at-rhino-fcp.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.