PNPC Lieutenant Neshala: In for a Penny...
Isara Aleron
Neshala: There is the SigInt array. We could piggyback on that. Lieutenant Seleya is off ship and her replacement hasn’t arrived yet. But what’s the point here?
Is’Kah: Social engineering has been a flaw among networked computer systems since the invention. Therefore, the subsequent step is to identify all locations where an individual is currently logged in. If an individual accesses the computer from multiple locations or from a user known to be planet-side, this information can be utilized to narrow the scope of the investigation. Conversely, if no individual is active in multiple locations simultaneously, a password reset can be implemented after logging out all users.
Neshala: Okay, I can see that. I thought about a password reset earlier, but without knowing what system, or systems, have been accessed, it would be fairly pointless.
Hughes: ::Examining the small teams working simulation thoughtfully:: Hmmmm, that’s true, BUT currently, whoever is behind this signal, has to keep relaying it through systems just to stay ahead of us. If we begin resetting passwords system by system under the pretense of standard maintenance protocols, it would help us herd them towards the systems we can monitor more directly.
Is’Kah: The issue is that if a day-zero exploit has been utilized, compelling all users to log out would be ineffective. The vessel is six months away from Spacedock, and it is entirely plausible that there exists a security breach of which we are unaware.
Neshala: Goddess, let’s hope not. We’d better find this thing fast and seal it up.
Hughes: ::Pinching the bridge of his nose with frustration:: Let's take it one problem at a time. First we have to find the leak, then we can plug it.
She nodded in agreement to that. She’d been trying for hours to do exactly that.
Is’Kah: It is entirely possible that one of the individuals we granted asylum from Stillwater has unlawfully accessed the computer and is illicitly transferring data to Cazimir or the Concordance. Ensign, could you please verify that all connected devices are equipped with Starfleet public-private key authentication?
Neshala: Now that is an interesting thought. Maybe we should alert the Chief of Security.
She threw Is’Kah a teasing wink and turned back to watch Hughes working.
Neshala: Any progress?
Hughes: Working on it Lieutenant, there’re a lot of interactions to check. We’re starting to narrow it down, I have a list of Non-Starfleet signatures. But this is still a long list. Perhaps we could design an algorithm to help detect whether the signature is authorized or not? ::He looked towards Is’Kah seeking her expertise in this situation::
Is’Kah: I believe there is one we could use, Ensign. ::To Neshala:: Perhaps we should have less levity at the moment and take this seriously, Lieutenant?
Neshala: I do take it seriously, Chief. But right now, I am more focused on this signal because that’s my job. We can take a look at our guests once we have this stopped.
Hughes: ::watching as a stream of data scrolls by on the access panel:: Here it is again Lieutenants! Look at this, the relay jumps are getting shorter. I think they’re running out of places to hide. Each time the signal jumps it avoids the same three maintenance relays. I’m thinking one of these relays must be the signals ACTUAL location.
Is’Kah: Use Is’Kah-pkpalgorithmtest_final-v2final-did_I_fix_that_bug-true-this_time_its_final.exe
Neshala: Well, let’s hope this works, then.
She called up the executable that Is’Kah had referenced and initiated it.
Hughes: ::Grinning maniacally:: Perfect timing Lieutenant Is’Kah. Computer, initiate a crosscheck using Chief of Security Is’Kah’s algorithm against all non-starfleet access points….
Is’Kah: It should work.
Neshala: Yes, it seems to be working. We should have it momentarily.
Hughes: I think I’ve got something ma’am. The good news is that the signal appears to be originating from Lower Cargo Bay 3, Deck 15.
Neshala looked at him in confusion. There wasn’t anything of value down there.
oO Why would they choose that one? Oo
Is’Kah: That is an out-of-the-way Cargo Bay.
Neshala: Indeed. But I think you have more news for us, don’t you?
Hughes: The bad news is…. it appears to be Cardassian.
Is’Kah: A Cardassian? Our only Cardassian that I am aware of transferred months ago. Are you aware of anyone, Neshala?
She shook her head, not recalling anyone since Soria had left.
Neshala: I can’t think of any.
Is’Kah: I didn’t think so. Could it be a Caraadian and the hack caused a computer error?
Neshala: I don’t know. But why the Cardassians? The Cardassian Union is literally on the other side of the galaxy from us? What could they possibly hope to gain?
Hughes: Response
Is’Kah: Can you bring up a video feed of that cargo bay? I’d like to confirm what we’re walking into.
Neshala: Yes, one moment.
She quickly called up the feed, but the database indicated there were no records available for the indicated timeframe.
Neshala: Computer, what happened to the records for Cargo Bay 3?
Computer: There are no records for the time of your inquiry, Lieutenant Neshala.
Neshala: Why not?
Computer: It was taken offline at fourteen-twenty-one hours two days ago for maintenance.
Neshala: That can’t be right. I would have had a record of any maintenance requests.
Hughes: Response
Is’Kah: Of course, it’s been hacked and is offline. Ensign, can you bring it online without alerting the attacker? If you can, once we verify what's going on, we’ll shut off all outgoing subspace relays for ten minutes. With people on the planet, we can’t risk being offline for longer.
Hughes: Response
Neshala: Understood, Chief. Should I alert the command team that comms will be down?
It was standard SOP for anytime communications were going to be offline, but the problem was that if they followed those SOPs, it might alert their hacker.
Is’Kah: Response
Hughes: Response
Neshala: Understood, Lieutenant. I’m already in it deep. Might as well keep piling it on.
Is’Kah: Response
Hughes: Response
–
PNPC Lieutenant Neshala
Helm, Communications, Operations Officer
USS Valkyrie, NCC-76418-A
A239412S10