[IC] Deck 23 (forward) - Auxiliary Operations Sysytems
I've asked about the virus, but I didn't get any response to my scan, so I'm just going to make something up.
"All Starfleet systems are encoded with basic security and operations protocols hard-coded as a backup in case of computer failure. It's how the ship can function despite computer failure.
The obvious solution, and frankly, one I recommend we take once we're clear of this, would be to completely reformat the core from scratch and install a hardwired iso chip with manually entered codes. I can lock changes to the chip, so unless someone wants to steal the iso core and carve a new one, they won't be able to change the command codes. This will prevent all sorts of sabotage workarounds.
Unfortunately, this will shut down the ship for at least 6-8 hours. Possibly longer as there are security upgrades and CPU issues ongoing as well. Something to consider, however, once we avoid any minor catastrophes for more than 24 hours straight.
Grand strategies preserve him. This ship was a mess. And the science officer's idea was insane. How would dissecting a single copy of the worm help? They had infected files. They need a purge the system of the worm, not just chop up the code.
The honeypot idea.. it's quite good, actually. We might be able to reverse engineer a counter virus to infect the worm.
It's designed to resist deletion no matter what we do, but we might be easier to infect the worm with a virus of our own to stop it from doing anything.
Then we can purge the systems at our leisure when we have time to shut the computers down.
He tried considering the potential advantages and problems of the idea.