A Review and Analysis of Attack Vectors on MIL-STD-1553 Communication Bus
Bibliographic record
Abstract
MIL-STD-1553 has been used for the past four decades by the military as a standardized, reliable, and fault-tolerant communication bus to provide connectivity between different embedded components in mission-critical military vehicles. The bus was designed with a great focus on reliability, responsiveness, and fault tolerance. However, its security aspects were an afterthought. Indeed, in the early 1970s, the notion of cyberattacks was not ubiquitous as it is today. Attacking computerized systems located at very high altitudes was an inconceivable scenario for many people, including security engineers. With current developments in cybersecurity and telecommunication networks, the security analysis of the MIL-STD-1553 bus reveals that the system is not immune from cyberattacks. The bus is vulnerable to many attacks that could seriously damage the entire system. Rebuilding the security of MIL-STD-1553 from scratch is cost prohibitive and a very complex, not scalable, and inflexible approach. A common alternative to embedding security to the existing system is the development of an intrusion detection system that can be added to the MIL-STD-1553 bus with minimal cost. In this article, we review and discuss some possible attack vectors on the MIL-STD-1553 bus. Then, we analyze the risk and consequences of each attack vector on a fighter jet. This review and analysis will provide security engineers with a holistic overview of possible attacks and their related risk on MIL-STD-1553 to better design an effective intrusion detection system.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.003 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".