> For the complete documentation index, see [llms.txt](https://knowledge.flyability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.flyability.com/policy-and-security/cybersecurity.md).

# Cybersecurity

Learn how Flyability protects inspection data through offline operation, encrypted communications, local storage, and optional cloud collaboration.

## Cybersecurity for Flyability drones and products

Inspection data can contain proprietary infrastructure information, operational details, and safety-critical insights. Flyability systems help operators protect this data through local storage, offline operation, and encrypted drone communications.

This page describes data handling, system connectivity, and recommended security practices.

### Security principles

Flyability's cybersecurity approach follows three principles:

* **Data control:** Operators retain ownership and control of their data.
* **Operational independence:** Inspections and reviews can be completed offline.
* **Defense in depth:** Hardware, software, and workflows provide multiple protection layers.

### Drone system architecture and data flow

Flyability drones support inspections in signal-denied environments. During a flight, the drone communicates only with its Ground Control System (GCS).

* The system has no inherent internet connection during flight.
* Inspection data remains on local storage.
* Data is not transmitted externally unless the user initiates it.

Inspection video, images, and logs are stored on the drone's SD cards and SSD. Optional backup recordings can be stored on the controller tablet.

### Air-gapped operation and network isolation

Flyability systems can operate in air-gapped environments. They do not need an internet connection for normal operation.<sup>1</sup> Firmware updates can also be installed offline.<sup>2</sup>

The tablet is the only component that can access the internet. It does so only when an operator manually connects it to a network. Without that connection, the system has no network path to external infrastructure.

{% hint style="info" %} <sup>1</sup> The tablet requires an internet connection for first activation. Premium software licenses require an internet connection every 30 days.

<sup>2</sup> While offline updates are possible, software and firmware updates must be downloaded from the Internet. For a smoother experience we recommend automatic online update
{% endhint %}

### Encrypted drone communications

The drone and GCS communicate through the CubePilot HereLink transmission system. Uplink and downlink streams use AES-128-CTR encryption over the 2.4 GHz band.

Access requires manual pairing with the drone.

### Local data storage and handling

Flyability systems use a local-first data model.

* Flight logs, telemetry, and sensor data are stored onboard.
* Video and inspection data are recorded to SD cards and SSDs.
* Optional backup recordings can be stored temporarily on the tablet.

No automatic cloud transfer occurs. Data remains under operator control and is exposed only through physical access to the devices or storage media.

Delete data from the drone and tablet after a secure transfer when required by your data-governance policy.

{% hint style="warning" %}
Data stored on the drone is not encrypted. Protect the drone and storage media from unauthorized physical access.
{% endhint %}

### Inspector Online security

Inspector Online is an optional cloud platform for collaboration and data sharing. Organizations can continue to operate entirely offline.

Inspector Online provides:

* Encryption for data in transit and at rest
* Multi-factor authentication (MFA)
* Regular security testing, including penetration testing and vulnerability scanning

### Operational data shared with Flyability

Flyability collects limited operational data only when Inspector runs on an internet-connected computer and the user opts in. This data includes:

* An encrypted unit identifier
* Flight duration
* Firmware version

Operators can opt out. Data shared with Flyability is handled securely and used only for troubleshooting.

### Security compliance and standards

Flyability aligns its security practices with recognized standards and regulations, including:

* ISO 9001 certification
* SOC 2 certification
* GDPR compliance

Flyability also follows practices informed by ISO/IEC 27001 and the NIST Cybersecurity Framework.

### Secure inspection practices

Use the following practices to reduce the risk of data loss or unauthorized access.

#### Secure devices and storage

* Keep drones, controllers, and storage media physically secure.
* Lock equipment during transport.
* Empty drone storage before each mission.

#### Manage inspection data

* Transfer data immediately after the inspection.
* Securely store the transferred data.
* Delete data from devices after transfer, when appropriate.

#### Protect network access

* Avoid public or unsecured Wi-Fi networks.
* Disable Wi-Fi and Bluetooth when they are not required.
* Use air-gapped workflows for sensitive environments.

#### Control operational access

* Follow your organization's IT and cybersecurity policies.
* Limit device and data access to authorized personnel.

### Shared responsibilities

Cybersecurity is a shared responsibility.

Flyability provides secure system architecture, controlled data flows, and secure firmware and software design. Operators secure their environment, manage access to devices and data, and follow internal security policies.

### Frequently asked questions

#### Does the system require internet access?

No. Flyability systems can operate offline, subject to the activation and license requirements described above.

#### Where is inspection data stored?

Inspection data is stored locally on the drone's SD cards and SSD. Optional backup recordings can be stored on the controller tablet.

#### Is data automatically shared with Flyability?

No. Limited operational data is shared only when Inspector runs on an internet-connected computer and the user opts in.

#### Can the system be used in secure or classified environments?

Yes. Its offline architecture supports air-gapped and high-security inspection workflows.

#### Is Inspector Online required?

No. Cloud features are optional and remain under operator control.


---

# 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://knowledge.flyability.com/policy-and-security/cybersecurity.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.
