An aviation certificate may remain checkable during a cyberattack if your team has kept both the document and the evidence needed to verify it outside the affected systems. For a maintenance, training or quality team, the useful next step is a controlled exercise: give a colleague an exported test record and see what they can establish without the original platform.
A saved PDF lets you read the certificate. It does not necessarily let you confirm who issued it or whether it matches the issued version. If its QR code only opens the supplier's website, that part of the check still depends on the website working.
What the August 2026 alert establishes
On August 10, 2026, the UAE Cybersecurity Council reported through the state news agency WAM that it had detected and repelled attacks targeting aviation, energy and education. The council said it contained the attempts before the attackers achieved their objectives or affected the continuity of vital systems and services.
The announcement describes attempts against systems, accounts and operational data, including phishing, which tries to trick users into helping an attacker gain access. It does not establish that aviation certificate records were altered. For teams holding such records, it is a reason to examine their own recovery arrangements, not evidence that their particular archive was compromised.
Keep the file and the means to check it
A digital proof can help compare a document with an earlier reference. One building block is a hash, a fingerprint calculated from the file's exact data. A changed file is expected to produce a different fingerprint. That comparison needs a trusted reference: calculating a new hash of today's file does not prove what it contained years ago.
A timestamp adds evidence about when data existed. For example, the RFC 3161 timestamp protocol uses a signed response from a time-stamping authority for a data fingerprint. The signature and the authority's certificate must also be checked. A date printed on a PDF is not the same evidence.
Some systems record a fingerprint on a blockchain, a shared transaction record. That can reduce dependence on the issuer's database, but a future checker still needs the matching file, the proof format, a usable verification tool and the information that makes the reference trustworthy. Access to public network data may also be necessary. A timestamp obtained today supports a claim about today; it cannot establish an unrecorded history of the file.
Ask the supplier to identify the complete export for your system. Keep it in an archive your organization can recover independently of the platform being tested. Our guide to verifying certificates without their platform explains how to inspect that export and its remaining dependencies.
A fictional training record during an outage
Consider a fictional maintenance training school whose records platform becomes unavailable after ransomware, malicious software that blocks access to files. A maintenance employer needs to check a course certificate the school issued earlier. This example illustrates a recovery exercise, not a reported incident or product test.
The employer has retained the original certificate file and an associated signed timestamp package. A colleague uses the supplied instructions and a separate verification tool. If the necessary evidence and trust information are present, they can check whether the file matches the timestamped data without logging into the school's platform.
The colleague records exactly what succeeded. If a required certificate, tool or network connection is missing, the check remains incomplete. That failure alone does not show that the document was forged. A deliberately changed disposable copy provides a useful second test: it should not be reported as matching the original evidence.
Even a successful result leaves the employer's personnel check to complete. Under the European rules, Part-147 covers approved maintenance training organizations; a training certificate alone does not authorize its holder to certify maintenance. In a Part-145 maintenance organization, authorization to sign a release to service comes from that organization within the applicable personnel requirements. A release to service is the certification made after maintenance within the authorized scope.
Continuing airworthiness management is a separate function: it organizes and follows the work needed to keep an aircraft airworthy. A Part-CAMO approval covers that management role and does not, by itself, confer maintenance approval. These distinctions follow Regulation (EU) No 1321/2014, points 147.A.145, 145.A.35 and CAMO.A.315. The recovered training record supports one part of the employer's review.
Run one exercise before the real outage
Use a harmless test document and an isolated test environment. Do not disable live operational systems to find out whether a supplier's claim holds.
- Export and preserve the evidence. Ask which exact file is covered, which supporting files are needed and where the instructions are kept. Store an original separately from working copies.
- Test without the services you may lose. Have a colleague check the package with access to the issuer's and platform vendor's services blocked in the test environment. Record any separate tool or network they still need.
- Compare the original and a changed copy. Keep the original intact. If both copies appear to match the same proof, establish what the tool actually checked before relying on the result.
- Leave a usable review note. Name the file, tool version, test date, result, missing evidence and person responsible for resolving any gap. Retest when relevant software, export formats or trust information change.
These are suggested purchasing and recovery checks, not a regulatory checklist. They give a supplier a concrete question to answer: can someone outside the platform repeat this check with what we retain?
Keep recovery, confidentiality and authority separate
Independent evidence does not restore lost documents or stop attacks. Backups and incident response still matter. Retaining a hash elsewhere also does not make the whole process confidential: the exported documents, verification links, keys and shared records each need appropriate handling.
Finally, a matching file may contain an original error, and an issuer or certificate may have changed status since issuance. Check the authority and current status required for the intended use alongside the historical proof. Our guide to checking certificate status today covers that next question.
See how AeroCert verification works, then ask for a demonstration using your own retention and recovery requirements. Judge the result by what a colleague can actually verify with the exported material.
Frequently asked questions
Can a certificate be checked when its issuer's systems are down?
It may be possible if you have retained the exact document, its supporting proof and a way to check them without those systems. Test that arrangement before relying on it, and record any remaining network or trust dependencies.
Is a PDF and its QR code enough?
Not necessarily. The QR code may only open a page on the unavailable platform. Ask what files and instructions another person needs to check the evidence independently, then retain and test that package.
Does recording a document's hash on a blockchain prevent cyberattacks?
No. A hash is a fingerprint of data. Recording it elsewhere can provide a reference for checking a retained file, but it does not stop an intrusion, restore lost files or guarantee access to the network used for verification.
Does an unchanged training certificate authorize someone to release an aircraft to service?
No. The certificate must be assessed for what it records. Training, a maintenance license and an organization's authorization to certify maintenance answer different questions under the applicable rules.