Guide · 8 min read

Security checklist for aerial inspection data: utilities, airports and defense work

Drone imagery of substations, runways and military sites is sensitive. What these clients usually ask, where inspection data is exposed between capture and delivery, and the questions to put to any file transfer or sharing tool before it carries their data.

Author
Ripton Cloud team, Product editorial
Updated

Key takeaways

  • Ask the client which rules apply to their data before the first flight. Utility, airport and defense contracts can each set their own storage, access and records requirements.
  • Inspection data is exposed in five places: the aircraft and cards, the field laptop, the transfer, storage, and the delivery to the client.
  • Ask any transfer or sharing tool where the data is stored, whether encryption can be switched off, who can access it, and what record it keeps.
  • A vendor's own controls are not a certification. Check which certifications the client actually requires and whether the vendor holds them.

Why inspection data is sensitive

Aerial inspection data shows the exact location, layout and condition of infrastructure: substations and lines, runways and airfield lighting, towers, pipelines and, on some contracts, military installations. In the wrong hands it is a map of where things are weak. Clients in these sectors increasingly put data-handling terms into their contracts, and the questions arrive before the first job, not after.

What these clients usually ask

Client typeQuestions to expect
Electric and gas utilitiesWhere is our data stored and in which country? Who at your company and your vendors can access it? Some utility data falls under grid security rules such as NERC CIP; does any of ours?
AirportsWho receives airfield imagery and how is it shared? How long do you keep it? Does it need to stay within the airport's security programme?
Defense and governmentIs any of this controlled unclassified information? Which contract clauses apply, for example DFARS requirements or CMMC? Does the data have to stay on systems you control, in the United States?
Telecom and engineering firmsHow is data delivered to us and to pole owners or subcontractors? Can we see who downloaded it?

Where inspection data is exposed

StageRiskControl
Aircraft and cardsLost or stolen cards; data left on aircraftClear cards only after the office confirms receipt; keep a chain of custody
Field laptopLost laptop, shared accounts, unencrypted diskFull-disk encryption, individual logins, no personal cloud sync of project folders
Transfer homeInterception on public or hotel networks; uploads into services the client has not approvedEncryption that cannot be switched off, and a destination the client has approved
StorageData held by a third party, in an unknown region, with unclear accessStorage on systems you or the client control, with named access
Delivery to the clientLinks that never expire, forwarded links, no record of who downloadedNamed recipients, expiry, passcodes and a download record

Questions to ask any transfer or sharing tool

  1. 1Where is the data stored, and does it ever pass through the vendor's servers or another country?
  2. 2Is every transfer encrypted, with which algorithms, and can an administrator or user switch encryption off?
  3. 3Does each session use its own key, and is tampering with data in transit detected?
  4. 4Who can access the data: individual accounts with multi-factor sign-in, single sign-on, and roles?
  5. 5What does the audit log record, can entries be edited or deleted, and can it be exported to your security monitoring?
  6. 6Can delivery links be limited to named people, expire, and be withdrawn?
  7. 7Which certifications does the vendor hold today, and which does your client require?
  8. 8Can it run on infrastructure you control, including a network with no internet connection if a contract requires it?

Field habits that matter as much as the software

  • Give each pilot and analyst their own login; never share one account across a crew.
  • Encrypt laptop disks and portable SSDs, and lock screens when unattended.
  • Keep project data out of personal cloud drives and messaging apps.
  • Delete working copies on laptops once the office confirms receipt, following the client's retention terms.
  • Record who handled each capture from flight to delivery, so you can answer the client's questions with facts.

How Ripton Cloud answers these questions

QuestionRipton Cloud
Where is the data stored?On the Ripton node you run on your own servers or cloud account. Files do not pass through Ripton Cloud's servers.
Can encryption be switched off?No. The transfer protocol always encrypts with AES-256-GCM or ChaCha20-Poly1305; there is no plaintext mode.
Session keys and tamperingA new forward-secret key for each session, with authenticated packets and replay protection.
Who can access it?Individual accounts with MFA from Starter; SAML single sign-on and roles from Professional.
Audit logFull append-only audit log from Professional: recorded events cannot be edited. A basic admin and transfer log on Free and Starter; SIEM export on Enterprise.
Delivery linksNamed recipients, passcodes, expiry and revocation, with views and downloads recorded.
No internet connectionAir-gapped activation on Enterprise.

Related

Bring your client's data-handling requirements. We will walk through the deployment, encryption, access and audit controls against them.

Review it with your security team