Trusted Traffic: A Classification of Six Recorded Compromises of the Borg Collective's Network into Four Paths of Entry, 2367–2378
Abstract
We find that every recorded compromise of the Borg Collective's network reached it as traffic which the Collective took for its own, and that no compromise has been followed by a recorded defence that closed its path of entry. Six compromises are on record between 2367 and 2378. We classify them into four paths, with one case each on the first three and three on the last: a command injected through a privileged node, a contagious idea brought back by a drone, a concealed network within the network, and a payload accepted through assimilation. We reconstruct each from Starfleet incident files, the engagement registry and the mission records of the USS Voyager, returned in 2378, and we write from 2379, using the pathogen of 2378. None of the six was stopped before it took effect. In the first, the vessel that received the command was destroyed but the Collective survived; the next four left it years or months of record in which to respond, and the sixth, of 2378, is too recent to judge. In the five assessable cases the Collective purged carriers once, possibly quarantined one ship and left a ruined cube unrecovered, and closed no path. By contrast, its personal shields adapted to phaser fire within about three discharges against a standard setting, and within about ten even against randomised modulation. We argue that the Collective's adaptive defences look outward, and that the six compromises are one class of hole entered four ways.
1. Introduction
We find that every recorded compromise of the Borg Collective's network came in as traffic which the Collective accepted as its own, and that none has been followed by a recorded defence that closed the path it used. Establishing how an intruder reached a network is an important task, and it serves several purposes, for example: deciding which of the network's own processes to distrust, judging whether the intruder's success can be repeated, and telling a planner whether the opponent has learned from it. No matter the goal, the path of entry has to be known before anything else.
Most studies treat the Collective as an opponent that adapts. At first contact in 2365 a phaser discharge felled one drone and the next was already shielded, and later measurement by the present author and colleagues (Strelnik et al.) showed that a change of phaser frequency buys only a few discharges before the shields follow. Starfleet doctrine has absorbed this lesson thoroughly, whereas a second lesson has been absorbed much less well, which is that the Collective has been compromised from within as well, and has never been compromised in the way that doctrine prepares a boarding party to expect.
Writers have described these compromises one at a time, each as an episode in the career of a person or a ship. Here they are treated as a set, which we classify by path of entry. We ask what each path had in common with the others, and compare the Collective's response to them with its response to physical attack. We write from 2379, after the return of USS Voyager in 2378, and we use the neurolytic pathogen of that year as the last case.
2. Sources and Method
We worked from three bodies of record. The Starfleet incident files hold the debriefings and sensor logs of the Locutus episode and of the Hugh episode (Veshlan, 2368; Maroudis, 2371). The Starfleet Tactical Engagement Registry holds the engagements with Borg vessels from 2365 (Starfleet Tactical Engagement Registry, 2377). The mission records of Voyager, transferred to Starfleet in 2378, cover the Delta Quadrant encounters, including the vinculum virus, the child carrying a pathogen, the hidden network and the pathogen of 2378 (Tavenhall, 2378; Dessarin, 2379). Each case rests on one or two primary files read against the registry, and we cite compilers, not the persons whose accounts the files preserve.
A compromise was counted when an outside party caused the Collective's network to carry an effect which the Collective did not intend and could not have prevented by physical means. Three events were considered and excluded. First, in 2373 a former drone, hearing the Collective through a residual link, directed Starfleet fire to a point of a cube that appeared non-critical. That event extracted information, however, and no command or payload entered the network, and the damage was done by conventional weapons. The severance of Seven of Nine in 2374 removed one drone from the network and changed nothing within it (Halvard-Ng, 2375). The drones disconnected in 2369 and 2370 belong to the Hugh case and are not counted separately. These choices determine the count, and we state them in order that a reader may argue with them. Had the 2373 event been admitted, the count would be seven, and had the severance of 2374 been admitted as well, eight, but neither event meets the rule, because in neither did anything enter the network and take effect inside it.
For each case we coded four attributes: the vehicle by which the effect entered, whether the Collective survived to respond, what response is recorded, and whether that response closed the path. A response that closed the path is one that removed the possibility of a second entry by the same vehicle, such as a check on that vehicle. The coding is qualitative and the sample is six. For that reason, we report counts and no statistics, and thus no interval. The dates of the Voyager records are less firm than the others, because the ship kept its own reckoning for seven years in the Delta Quadrant, and we give the years of the hidden network with a margin of one.
3. Entry Through a Privileged Node
The first case is the command sent through Locutus in 2367. A cube had taken Captain Jean-Luc Picard in 2366 and made him its spokesman, which meant that his link to the Collective was kept open and was given a standing that no ordinary drone enjoyed (Veshlan, 2368). When Starfleet recovered him, Lieutenant Commander Data used that link, reached the Collective's network through the connection which the Collective itself had provided, and planted a command which put the drones into regeneration, and the cube was destroyed while they lay in that state.
Nothing had to be broken, and no barrier was passed, because the link was a legitimate channel and the traffic it carried, which we read as marked as coming from a node of high standing, needed no further credential. In this sense, the Collective had therefore handed its enemy a key, and had done so for its own purpose. Data chose a low-level command because it was the least likely to be challenged, and whatever notice the Collective took of the intrusion, it did not stop the command.
The cube did not survive, but the Collective did, and it had from 2367 to the end of our record to close the path. We record the case as one in which the opportunity to respond existed at the level of the Collective and not of the vessel. That the former captive could still hear the Collective in 2373 shows that the link through which the command of 2367 entered had not been closed. A further limit is that the file says nothing of the years between, and therefore a closure which later reopened would not appear in it.
4. Entry Through a Carried Idea and Through a Hidden Network
The second case began in 2368, when Starfleet returned an injured drone, whom the crew had named Hugh, to the Collective. He carried no weapon, and the only thing he took back was a sense of himself as an individual. The mission was planned on the understanding that his return would carry a destructive instruction, which the crew declined to install. What spread was the idea, and by 2369 and 2370 the drones of a ship had been disconnected from the Collective by it, and a faction of them followed another leader away, until Hugh himself led the survivors (Maroudis, 2371).
Thus the vehicle was a drone in good standing, who was accepted without examination and who then spoke to others over the ordinary links, attesting that the Collective had no means of treating a thought as an attack. The Collective survived the episode. However, the files show no change in how it admitted returned drones. Whether the ship was cut off by the Collective or lost its link through the disorder itself, the record does not settle. If the former, it was a quarantine of the carrier and not a defence against the path. Its later vessels went on taking in new members by assimilation, and nothing in the engagements of the Registry suggests that they screened them (Starfleet Tactical Engagement Registry, 2377).
The third case is the hidden network, which Voyager met in the Delta Quadrant in 2376 and 2377, a pair of years which the ship's own reckoning fixes only loosely.
Within it, a minority of drones with a genetic mutation met one another as individuals in a shared virtual space during regeneration, and returned to the Collective each time they woke. Their meeting place sat inside the network and used its regeneration cycle for transport, with the result that a drone entering it was, to every observer in the Collective, simply regenerating (Tavenhall, 2378). The Queen knew of the space before Voyager found it, though it had not been able to locate it.
Voyager helped these drones keep their individuality after they were reconnected, and the Collective did respond: the Queen searched for the space and destroyed drones, and whole vessels, that carried the mutation. What the record does not show is a defence against the class of path, such as a check on what any drone does in regeneration. The response was a purge of the carriers, not a change to the cycle they used.
5. Entry Through Willing Assimilation
The fourth case belongs to 2375. A virus was carried into a cube by aliens whom the record calls Species 6339, who allowed themselves to be assimilated for the purpose, and it was found in the vinculum of the wrecked cube, the device which interlinks the minds of a cube's drones (Tavenhall, 2378). The details are thin and we hold them cautiously: the record does not show how far the virus spread, and Voyager removed the vinculum before it could be carried further. We count the case because the payload was admitted by the Collective's own act of assimilation and was designed to take effect inside the network.
A fifth case is recorded in 2376. A pathogen had been engineered into a child of another species, who was later assimilated by the Collective, and on the Brunali account it killed the adult drones of the cube that took him in; the record shows no attempt by the Collective to recover that cube (Tavenhall, 2378). We hold the details of the child's origin cautiously, and the date of his assimilation is less firm than the date of the record. The path is plain, since the payload was carried into the network by the Collective's own act of assimilation, and the response on record is a failure to recover the cube, not a screening of what assimilation brought in. No such screening appears between 2376 and 2378, which is the whole of the interval that our record covers.
Our sixth case belongs to 2378 and to the Voyager record. An older Voyager officer, who came to the ship from a later timeline and whom the record identifies as Admiral Janeway, carried a neurolytic pathogen and allowed the Borg Queen to assimilate her. The pathogen travelled through the Collective by the Collective's own assimilation process, which gave it the standing of a new member joining the network, and it spread to the drones by the links through which the Collective shares what each one knows (Dessarin, 2379).
This path stands opposite the first. The command in 2367 used a key that the Collective had given to a captive. The payload in 2378 used the Collective's own appetite, since assimilation is the process that it examines least. A defence which examined what assimilation brought in would have taken the Collective against its own purpose, and the record shows that none existed. Consequently the sixth case, like the first, is classed by its path and not by its weapon.
The transwarp hub was destroyed in the same operation, and our record, which ends in 2378, is too short to show how the Collective answered.
Table 1 sets the six cases side by side.
6. Discussion
The central finding is an asymmetry. Against physical threats the Collective adapts within a few shots: in the earlier study of 214 firing sequences (Strelnik et al.), a preset phaser setting gave about three effective discharges before the shields followed, randomised modulation gave about ten, and a deflection of one drone was repeated for a fresh drone in 91% of cases. Against the six compromises it closed no path, in the sense that no response that closed the path is recorded in any of the five cases where it had time to make one. Of six compromises, none was stopped before it took effect. By path, one used a privileged node, one a carried idea, one a hidden network and three willing assimilation. In five the Collective had time to respond, and it purged carriers once, possibly quarantined one ship once, and left a ruined cube unrecovered once. The contrast does not depend on how finely the adaptations are timed, because the shield figures count discharges and the compromise figures count years. A Collective able to learn the frequency of a phaser within an engagement could, by the same capacity, have learned in the eleven years after 2367 or the ten after 2368 to examine its links to captives and its returned drones. The records show that it did neither, and they show no sign that it tried.
For that reason, the six compromises should be treated as one class. Each reached the Collective as internal traffic: a link given to a captive, a drone accepted back, a cycle used by its own members, and an assimilation completed as designed. The adaptive defences of the Collective, which we know from the shield measurements, face outward. They react to a weapon, a frequency or a hull. Consequently they have nothing to react to when the offending input comes from a node, and no node is ever treated as an adversary. This is the design question taken up in the companion paper by Dr. Sorvan, who argues from the timing of adaptation that acting on internal traffic without verification is the efficient choice for a collective of the kind. The present paper does not repeat that argument. It supplies the record of compromises against which such a design can be judged.
The classification stands or falls on mechanism, since the record is too small for anything else. The mechanism is the same each time, because entry did not require defeating the Collective's defences, and no defence was in a position to notice an admission. We state this as established for the record we hold. Whether the Collective could close these paths without changing what it is remains a design question, and we leave it to the companion paper.
Some advantages of this classification are: it can be applied by a team with no more than the incident files, it tells a boarding party which of the Collective's own processes to treat as a door, and it can be refuted by a single structural defence appearing in the record. A future compromise is likely to use whichever vehicle the Collective cannot distinguish from its own members, which now includes the returned drone, the mutated minority and the assimilated visitor.
7. Limitations of the Record
Six cases is a small number, and each case has its own narrow base of record. The classification rests on the mechanism they share, not on counts. Absence of a recorded response is not proof of absence, particularly for the hidden network, where the file ends with the departure of the ship, and for the vinculum virus and the child, whose details are thin. The Voyager records were kept by one crew and have been read here only through Starfleet's own transfer.
The finding is narrower than it may appear, and it does not entail that the Collective is easy to attack. It entails that the Collective's defences look outward, and that a compromise has to date required a vehicle which only a rare circumstance supplies. It also leaves open whether the Collective has altered its design since 2378, because our records end with the destruction of the hub. The full case files accompany this report as a restricted supplement, released by the Division to fleet planners. We hope that their release will encourage debate on testing the classification against the next compromise, and on correcting it.
References
- Veshlan, T. (2368). Link record of the Locutus episode, reconstruction of the command path and the destruction of the cube. Starfleet Tactical Analysis Reports, TAR-68-17.
- Maroudis, K. (2371). The returned drone, assessment of the loss of a Borg vessel's link and its aftermath, 2368–2370. Starfleet Incident Records, SIR-71-044.
- Tavenhall, J. (2378). USS Voyager mission records, the Borg encounters of 2375–2377, the vinculum virus, the child carrying a pathogen and the hidden network. Starfleet Delta Quadrant Mission Records, NCC-74656, Borg series.
- Dessarin, R. (2379). USS Voyager mission records, the pathogen of 2378 and the destruction of the transwarp hub. Starfleet Delta Quadrant Mission Records, NCC-74656, return series.
- Halvard-Ng, I. (2375). Severance of a drone and the links that remain, notes on the Sector 001 engagement and the case of 2374. Starfleet Tactical Analysis Reports, TAR-75-40.
- Starfleet Tactical Engagement Registry (2377). Engagements with Borg drones on Federation vessels and installations, 2365–2377. Starfleet Tactical Engagement Registry, series B-4.
- Strelnik, O., Sorvan, & Ishikawa-Moreau, H. (2026). How Many Shots Before the Collective Adapts? Borg Personal-Shield Adaptation to Phaser Fire and the Diminishing Return of Frequency Rotation in 214 Firing Sequences, 2365–2378. Uncited Press.
- Sorvan (2026). Why a Hive Trusts Itself: A Relay-Depth Model of Unverified Internal Traffic in the Borg Collective, Validated Against 41 Timed Adaptation Events, 2365–2378. Uncited Press.
Open in Uncited Press →