It took only a moment for Vreta to realize what was happening, and his implant was already working to contain the detected threat. [i]Someone[/i] was being exceptionally bold, and at least at first, Vreta had a mind to show them who they were dealing with. However, he soon realized that there was something more to this virus. Normal Human malware likely would have been dealt with before Vreta was even aware of it, but there was something different about this one. His implant started dedicating a surprising amount of resources to adapting to the malicious code, so as quickly as he could, Vreta himself stepped into action. 

From the start, Vreta disabled all outgoing signaling from his implant to prevent any outbound transmissions. Without that, there would be no connection from his implant to any external server. Naturally, he also ceased his ongoing tactical support to his team so that his implant could dedicate its full processing power to the task ahead. 

Despite the surprising sophistication of the virus, Vreta might have been able to have it dealt with swiftly, had that been the path he chose. There was clearly Cradle tech involved with the program, but his own implant was top-of-the-line by Rothian standards. It had immense computational capacity compared to anything of Human creation, and this virus was at least still partially Human-made. Vreta, however, was not merely interested in stopping it. This presented new opportunities beyond just the outcome of a combat simulation. 

Vreta, of course, did nothing to hamper his implant’s ability to fight back and protect himself. He stopped his own digital assistance towards his team so that his implant would have the resources for the kind of record-keeping he required. Like a ship sealing off compromised compartments, his implant first quarantined various sections of his internal network from one another. Some sections, by their core design architecture, were inaccessible. Implant subsystems connected to most vital organ systems were isolated, with their own processors and core programming. They were disconnected from his neural implant, except for a specialized interface that allowed the subsystems to view directives without allowing the direct transmission of code. The virus could not spread to them, but other systems, such as his sensory and motor functions, did have a direct, low-latency connection to his neural implant. As such, his implant did have to work to protect them. 

Instead of outright deletion, Vreta directed his implant to create an quarantined partition with “write once read many” write protection. Any well-made virus would be able to erase part or all of itself if needed, but his implant was more than capable of dealing with that issue. It issued a root-level override to [i]all[/i] deletion operations, or indeed any form of code modification, to instead copy into the quarantined partition. In effect, that partition would serve as an immutable record of everything happening within Vreta’s internal network in order to guarantee that he could save a copy of the virus in its entirety. Of course, Vreta had stopped giving any manner of assistance to his team during all of this, but at this point, his goals had changed.