This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:safeav:as:cybersec [2025/10/29 07:40] – pczekalski | en:safeav:as:cybersec [2025/10/29 07:53] (current) – ToDo checked: pczekalski | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| {{: | {{: | ||
| - | <todo @pczekalski></ | + | <todo @pczekalski |
| Drones' | Drones' | ||
| Line 26: | Line 26: | ||
| </ | </ | ||
| + | Cybersecurity for drones includes all their components (hardware and software), procedures, and operations. Below is in a table {{ref> | ||
| - | <todo @Pczekalski> | + | <table table2> |
| - | Cybersecurity for drones includes all their components (hardware and software), procedures, and operations. Below is in a table {{ref>table2}} there is a short list of those components with characteristics: | + | |
| - | + | ||
| - | <table tab_label> | + | |
| < | < | ||
| ^ Area ^ Short Explanation ^ | ^ Area ^ Short Explanation ^ | ||
| Line 51: | Line 49: | ||
| </ | </ | ||
| + | Technically, | ||
| - | + | <table table3> | |
| - | + | < | |
| - | + | ^ **Category** | |
| - | + | | **Communication & Control Links** | |
| - | + | | ::: | |
| - | Domain-specific | + | | ::: |
| - | + | | ::: | |
| - | ^ **Category** ^ **Attack / Threat Type** ^ **Impact** ^ **Mitigation Strategies** ^ | + | | **Data Security** |
| - | | **Communication & Control Links** | Jamming (RF denial) | Loss of command/ | + | | ::: |
| - | | | Spoofing (GPS/ | + | | **Software & Firmware Integrity** |
| - | | | Eavesdropping | Leakage of telemetry or video | End-to-end encryption (AES, TLS), mutual authentication | | + | | ::: |
| - | | | Man-in-the-Middle (MitM) | Command alteration or injection | Digital signatures, certificate-based identity, integrity verification | | + | | ::: |
| - | | **Data Security** | Unencrypted transmission | Theft of mission data, privacy violation | Use of VPNs or secure links (TLS/DTLS), data minimization | + | | **Navigation Systems** |
| - | | | Compromised onboard storage | Exposure of sensitive data after capture | Encrypted storage, self-wiping memory, tamper detection | | + | | ::: |
| - | | **Software & Firmware Integrity** | Malicious firmware updates | Persistent compromise, backdoors | Signed updates, secure boot, trusted update servers | | + | | **Hardware & Supply Chain** |
| - | | | Outdated software | Exploitable vulnerabilities | Regular patching, vulnerability scanning | | + | | ::: |
| - | | | Malware infection | Unauthorized control or data theft | Air-gapped maintenance, | + | | **Network & Cloud Systems** |
| - | | **Navigation Systems** | GPS spoofing | False navigation, crash, or theft | Multi-sensor fusion (INS + GNSS + vision), anomaly detection | | + | | ::: |
| - | | | GPS jamming | Position loss, uncontrolled drift | Anti-jam antennas, inertial backup navigation | | + | | ::: |
| - | | **Hardware & Supply Chain** | Hardware backdoors | Hidden persistent access | Supply chain vetting, component attestation, | + | | **AI & Autonomy** |
| - | | | Physical capture | Reverse engineering, | + | | ::: |
| - | | **Network & Cloud Systems** | Ground control compromise | Full UAV fleet takeover | Network segmentation, | + | | **System Resilience** |
| - | | | Cloud data breach | Exposure of telemetry or missions | Strong access control, encryption at rest/in transit, audit logs | | + | | ::: |
| - | | | API abuse | Unauthorized remote commands | API authentication, | + | | **Regulatory & Standards** |
| - | | **AI & Autonomy** | Adversarial AI input | Misclassification, | + | | ::: |
| - | | | Model poisoning | Manipulated learning behavior | Secure dataset curation, signed models, anomaly detection | | + | | **Human Factors** |
| - | | **System Resilience** | Single points of failure | System-wide outage | Distributed control, redundant communication paths | | + | | ::: |
| - | | | Poor fail-safe design | Crashes during disruption | Secure failover modes, autonomous return-to-base logic | | + | </ |
| - | | **Regulatory & Standards** | Lack of standards | Inconsistent security posture | Adoption of DO-326A / NIST frameworks, international harmonization | | + | |
| - | | | Weak certification | Deployment of insecure UAVs | Third-party audits, mandatory penetration testing | | + | |
| - | | **Human Factors** | Operator credential theft | Unauthorized UAV access | Multi-factor authentication, | + | |
| - | | | Insider threats | Intentional sabotage or leakage | Role-based access, behavior monitoring, background checks | | + | |
| - | + | ||
| - | + | ||
| - | Good practices. | + | |