[SAIN\\MOD\\SAMIA\\IS\s_rtPL_984155\\_communications]
SAIN Terminal Access System v3.85665
Accessing IP 9845.66885.445211.55416
April 5th, 2232
SYSTEM ALLIANCE MILITARY INTELLIGENCE AGENCY
INTERNAL SECURITY DIVISION
INTERNAL COMMUNICATIONS ARCHIVE - DIRECTOR TAIMEI KUBOTA
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
EYES ONLY DEEP EYES SENTIENT AND ABOVE
UNAUTHORIZED SYSTEM ACCESS CARRIES IMMEDIATE LETHAL ICE PENALTIES
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
CASE FILE #988445112-BRTEEV-0065412567
SUBJECT: Attempted Information Leak from OMIS by OMIS Official Juan Carlo Martinez
Subsection: Review, Investigation and Analysis
PUBLIC KEY 984555112-PHDBAPAOKDHHG-9887455112545-ODJDHSLSAOAPAODFDJABFDBDGS
TIMESTAMP: MARCH 29th, 2232 | 1035 Hours
FROM: Senior Operations Supervisor Itaki Reindorf
TO: Director of Counterintelligence Operations Taimei Kubota
SUBJECT: Initial Review Case #988445112-BRTEEV-0065412567
Director Kobuta,
We have concluded the initial review of the attempted information leak by OMIS official Commodore Juan Carlo Martinez. At this point in time we can assemble the first comprehensive picture of the entire case and the actions taken by our government agencies, and what has been ascertained about Martinez actions and those of the hostile party that had and potentially has penetrated the OMIS at the highest level.
Frankly, Sir, the level of penetration the enemy achieved is worrying in the extreme, and so is the enemy party's target. We have confirmed Martinez carried 56 terabytes of ASI codelines and operation logs, including a copy of specific parts of the SAIN YGGDRASIL data backbone architecture, on an implanted storage system. Thankfully, the Black Ops to neutralize Martinez thoroughly slagged the storage device; we are certain none of this data could be transmitted to the Salarian courrier. Penetration this deep is worrying; no enemy party should have enough intelligence on us to specify to Martinez what parts of the YGGDRASIL code it wants to obtain. This either means specifications of YGGDRASIL were leaked beyond the awareness of the alphabet soup, or another party has reverse-engineered enough of YGGDRASILs internals to ascertain important code segments and name them to Martinez. Analysis in that part is still ongoing.
In my recommendation, we have to begin a serious sweep of our counterintelligence capabilities, especially ONIs TREE ROOT initiative and the SASAs ECHELON WOOD system; frankly Martinez leak points towards what I have to start calling laziness within our intelligence community, and overconfidence that our infosupremacy will deflect enemy penetration attempts. This is obviously not the case anymore, and unacceptable. Leaks of our ASI architecture, especially TITAN or WARMIND, and of YGGDRASIL would place the SA and the SAAF at strategic weaknesses and in the case of war, disadvantages, we would need years if not decades to correct, and would ensure the loss of one of our greatest force multipliers.
With that said, the attached master file where we compressed the events until now, and SI actions post-Data denial operation.
Itaki Reindorf
Senior Operations Supervisor
[ 1 Attached File: 2232_03_29_SICase_988445112-BRTEEV-0065412567_Master_ ]
[ ▼ 2232_03_29_SICase_988445112-BRTEEV-0065412567_Master_ ▼ ]
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
THIS IS A DEEP EYES SAPIENT RED FILE
YOUR ACCESS ATTEMPT HAS BEEN LOGGED
AUTHENTICATING USER ID... [ ACCEPTED ]
DISARMING ICE AND MEMETIC PAYLOADS... [ DONE ]
DECRRYING FILE... [ DONE ]
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
SYSTEM ALLIANCE MILITARY INTELLIGENCE AGENCY
INTERNAL SECURITY DIVISION
CASE #988445112-BRTEEV-0065412567
Attempted Information Leak from OMIS by OMIS High Official Juan Carlo Martinez
Master Case and Operations File
Glossary of Terms
Bodyloss: The loss of an Egos Shell due to heavy damage, potentially including loss of Ego Execution capability.
Codelines: AI-specific executive code and associated data files. Can refer to both the entire general executive code and code architecture of one AI series (such as the Type 552 AI of a Kamachida Household Android) or the executive code and data of a singular specific AI. (A/N: TachikomaAIOS_v2.065.1_Tachikoma-0056_cdl_ is one example of an AI-specific Codeline)
Echelon Trust Rating: The Echelon Trust Rating is a "trigger sensitivity" for internal surveillance systems and projects like DEEP SENTINEL. It decides when a person is marked for review, surveillance, or other actions
Ego: The wholesome complex neuronal and/or information landscape of a person, including the Ghost. AGIs and ASIs possess an Ego as well, though of a different format than (trans)humans that run on a Homo Sapiens neuroarchitecture.
Ego Execution Capability: Egos require an executive medium to run; the ability of a medium, whether it may be a brain, augmented brain, or artificial brain, to execute an Ego is referred to as Ego Execution Capability. Loss of EEC means the Ego is frozen as static data, potentially in a back-up system, or has been lost.
Ghost: The core of the Ego, the Ghost are identifying aspects and information clusters that make a person a person and unique; it can also be seen as the "soul". Whereas other aspects of the Ego can be altered without major consequences, alterations to the Ghost carry major personality and behavior changes and can indeed be used to override one person with another, more desired one.
Instance-kill: An instance kill, in contrast with a bodyloss, means that the instance state of a particular Ego was irreversibly lost. For an Ego without backups, Instance-kill means real death, with no possibility to create a new instance of the Ego.
ONI: Office of Naval Intelligence - The System Alliance Space Force-specific Intelligence Agency.
RISS: Resleeve Identity Stress Syndrome - A psychological condition that Egos initiated from Backup can often experience after their previous Instance has died with loss of the Ego. Common symptoms are feelings or sentiments of "being just a clone of the original" and "not being oneself".
Psychosurgery: Special "surgery" conducted on the Ego or, if necessary, the Ghost, with the goal of changing parts of either from an undesired into a desired shape. Psychosurgery can be used to remove (or add) psychological conditions, add compulsory triggers, add or remove skills or memories especially when associated with the Ghost, or perform deep-intrusion memory and personality alterations. Differs from a Ghosthack insofar as that Psychosurgery can also only influence the Ego, and is in any way conducted less in a subversive manner. Can also be seen as consensual ghosthacking.
Resleeving: The act of transmitting an Ego from static data storage onto an Ego-executive medium.
SASA: System Alliance Security Agency - Intelligence Agency responsible for communication interception, analysis, and network-based intelligence
(Cortical) Stack: A reinforced Ego Storage system that creates a continuous backup of the Ego. If Ego Execution capability is lost or a person suffers bodiless any other way, the Stack enables a secure backup of the last Egostate to be retrieved and resleeved in a new Shell. Destruction of the Stack means, in lack of any other Shell-side Ego storage systems, an Instance-kill.
Simulspace: "Simulated Space" - An Ego-hosting Virtual Reality environment. Contrast with Virs (Virtual Reality.)
PDS: Personal Digital Sphere - The whole of a person's individual data and software, attached to that person.
DEEP SENTINEL: Counter Penetration Surveillance AI system that monitors System Alliance personnel for enemy intelligence penetration
ECHELON WOOD: SASA system for monitoring Extranet traffic
TREE ROOT: ONI Initiative to monitor extranet traffic at the borders of human space.
YGGDRASIL: Codename for the AIs and communication, server and networking architectures that merge all aspects of the System Alliance communication, networking and information infrastructure from government over intelligence to the military into the System Alliance Information Network.
Case History - Recent timeframe
On the eve of March 20th, OMIS-assigned DEEP SENTINEL AIs registered a major behavior and biometrics deviation on Commodore Juan Carlo Martinez, sufficiently to trigger the Echelon Trust Override and alarm SI to a possible breach. Subsequently, DEEP SENTINEL switched Martinez status to Surveilled, and documented as Martinez transferred unknown data from an external OMIS-issue 500-Tb storage device into his PAN using a hardwired connection. Subsequently, the IS was alerted to a likely data security breach in progress, as Martinez had logged no such activity beforehand.
SAMIA SI Counterintelligence Division 6 Team 45 was alarmed and tasked with ascertaining the nature of the breach, as Martinez left OMIS HQ and returned to his home, scheduled to depart for Earth the next day via an interplanetary shuttle departing from the New Armstrong spaceport for Singapore Highport. Martinez was supposed to spend a night at Singapore Groundport before departing via Hypersonic to Japan for a meeting with Kenbishi Heavy Industries and Bostom-Akamashu Japan officials, talking about the introduction of a new series of AI into SAAF service.
At 0855 Hours March 21st, S6T45 officially reported that Martinez had accessed the OMIS Codeline stores, and used his credentials to authorize a codeline download for OMIS-stored ASI software from the DEEP MIND 4 archives; at 1122 Hours it was certain Martinez had transfered 56 terabytes of ASI codelines, including parts of the TITAN network and the System Alliance Information Network YGGDRASIL Backbone, as well as operations logs to his external storage device and then into his PAN. This activity was not discovered earlier because Martinez had released a sophisticated Counter-Intrusion Detection program into the DEEP MIND 4 servers, which covered and erased his traces; remaining early-warning points did not trigger warnings due to the Echelon Trust rating of Martinez.
Subsequently, Internal Security Leadership was alerted to a high-profile security breach in progress; political deliberations delayed a quick response however, and Martinez departed from New Armstrong spaceport without intervention by IS units. Section 6 forces at Singapore groundport were alerted to a potential intelligence breach and prepared to engage.
At 1430 Hours, IS teams scrutinizing Martinez home on Luna and his digital sphere discovered an enemy program that will be elaborated on further; Martinez contact was ID'ed as Hendal Wim, possible STG-affiliate, officially with the Citadel Economic Development Foundation in Malaysia as a Citadel Alliance Representative. Subsequently, the breach rating was updated, and Internal Security leadership briefed at 1550 Hours.
At 1810 Hours Director of Counterintelligence Operations Taimei Kubota called in external assistance after deliberation with the IS council, requesting an external IS-unaffiliated Black Ops Force to neutralize Martinez.
This neutralisation took place on the following day, March 22nd 2232, at 1856 Hours local time in the Penthouse suite 0632 of the Singapore Groundport Hilton Megaplex Tower 4. Martinez and Wim were both, together with three guards Wim had brought to the location, instance-killed, with loss of stack in all five instances via total destruction of the cranial cases followed by a nanothermobatic explosive used to destroy bodies and carried storage devices. The Black Ops force subsequently exfiltrated without issues, and Section 6 units moved in to assess the situation and secure the now-crime scene. At 2032 hours, IS units arrived on-site from the Los Angeles division to take over the site from Section 6 and SGPD.
Post-Incident IS review of Subject Commodore Juan Carlo Martinez
Martinez Ego present at Singapore Groundport was instance-killed, with total loss of the Ego. As soon as total bodyloss and destruction of the Ego was officialy confirmed by police authorities, the Office of military Medicine and Augmentations was contacted and the pull of Martinez back-up, updated on the night from the 19th to the 20th of March 2232, was requested for post-incident interviews as per standard IS policy. During this interview done in Simulspace on March 23rd, Martinez did not disclose any dealings and indicated major distress at the thoughts of being "just a copy" and "the real Martinez having died", showing major Post-resleeve distress and Resleeve Identity Stress Syndrome. After the interview which was conducted with some difficulty and cut short on medical concerns, he was transferred, on consent, for medical psychosurgery to help with stress relief.
However, before being subject to Psychosurgery, Martinez ego was again sleeved in a Simulspace environment and subjected to more thorough interrogation by IS personnel; he was confronted with the actions of his other instance and asked how and when he had been contacted by whom. At first, Martinez made clean denials, but gave IS psychosurgeons enough neural activity pointers to subsequently extract and confront Martinez with a relationship with an unknown, potentially STG-affiliated party for the past 2 years, based on incriminating information the other party threatened to release into the wider public, killing Martinez carrier and his position at the OMIS. The alternative was for him to hand over information to the party; at first irrelevant reports but soon followed by more important information, including AI codelines.
The backup of Martinez was, however, definitely and confirmed not aware of his other instances actions during the 21st and 22nd of March. In conclusion, Martinez neutralized instance was only commanded to retrieve the information destroyed on the 22nd on the 21st of March; fitting with his actions triggering DEEP SENTINEL. Martinez was most likely aware that he would trigger DEEP SENTINEL or other overwatch routines, but apparently saw no alternative.
After this second interrogation session, Martinez was transferred to psychosurgery and treated for RISS; furthermore Ghost editing was performed and Guild Locks inserted to neutralize Martinez awareness of his past actions and the honey pot that had been used to pressure him. This should ensure a solid integrity going forward, though Martinez will remain under IS watch for the year going forward, pending future evaluation of his status.
A new Shell for Martinez is provided at this time, and he will return to active duty with the OMIS only a few days from now.
Martinez home and digital sphere
While Martinez home and personal digital sphere was already subject to preliminary review during the events of the 21st and 22nd of March, the analysis of the hostile software took several days, in part due to counter-analysis measures and the heavy encryption.
The software was a special contact and communications software installed directly into the OS of Martinez home system and his primary terminals. Based on digital forensics, the software was uploaded there by a digital intrusion delivered via a regular OS update two years ago. The intrusion was definitely guided and not conducted by an independent attack program; Martinez update was intercepted and altered in transit. The exact means are still under investigation.
Once installed, the program nested itself deep within the OS architecture and established several encrypted ports into the human Extranet; it received periodic instructions through some of these ports. After an "incubation" period, the program activated for a first time a month after insertion on April of 2230, confronting Martinez with the evidence and recruiting him for the unknown party; during this time Port 02 was active, transmitting to and from a Virverse server.
Over the subsequent months the program became active whenever Martinez was contacted by the unknown party; the software kept parts of the old messages in storage, interestingly, buffering them for potential replay under heavy encryption. Why this decision was made is unknown but pointers are that the messages were split and buffered inside the software over weeks, seeking to bypass security measures with miniscule, seemingly unrelated data packages send to Martinez. Thanks to this, we were able to retrieve parts of the messages, and document two security breaches of significance - Once a Synthetic Insights AGI program of the ATTS-9800 series, an another time a Battlefield Control Software package used for the mass control and coordination of robotic infantry.
Detailed analysis of the software reveals a surprising mixture of code from all over Citadel space; large amounts of the software were batarian coding associated with the SIU and the Black Guard, including past penetration attempts. Only parts of the code were definitive STG packages; including the encryption and stealth software used to hide the software inside Martinez OS. As such, the responsible party cannot be identified per the code and programming style; we could not identify any STG programming teams in this software, unlike in other cases.
Nature of the hostile party
The nature of the hostile party that caused the Martinez breach is unknown; while the depth of the penetration and the involvement might point towards the STG, the nature of the breach, the data leaked by Martinez and the message style do not support this conclusion. The Shadow Broker network, the Batarian Hegemony intelligence community or one of the larger hacker networks could also be responsible. Investigating Wims background and affiliation might yield deeper answers to this question, but as of this time IS cannot ascertain the hostile party.
Nonetheless we recommend that investigation into this case continue and are branched out to the AIS for deeper investigation in Citadel space. Reactions by the STG going forward may also supply clues as to the nature of the party.
[\\log_out]
[\\access_terminate]
A/N(Sevoris): A little non-optional Interlude more heavy on the worldbuilding before it goes into Chapter 1, looking a bit more into what happened around the events of the Prologue on the side of the MIAs Internal Security division.
A/N:(Nick): Question for readers: Want a chapter for Codex Entries here or a dedicated documents?