USS Sentinel
Main Sim: Stellar Cartography Lab - ATTN: Chief Engineer, Chief of Security, XO
Posted by Gamemaster Pelican (GM) in Main Sim: Stellar Cartography Lab - ATTN: Chief Engineer, Chief of Security, XO
Posted by Master Chief Petty Officer Karl Johansson (Chief Engineer) in Main Sim: Stellar Cartography Lab - ATTN: Chief Engineer, Chief of Security, XO
Posted by Gamemaster Pelican (GM) in Main Sim: Stellar Cartography Lab - ATTN: Chief Engineer, Chief of Security, XO
Posted by… suppressed (3) by the Post Ghost! 👻
OOC: This is the GM, trying to finish the sim.Posted by… suppressed (14) by the Post Ghost! 👻
SNIP
Roman turned to the NE. “What exactly happened here?”
~ Cmdr Alden, XO/CSO
NE Whistle looked around and said, “Commander, I don’t have enough information to answer that question. I haven’t even come in here until now.”
He looked over at the computer station and saw that the side was opened, and the connection ports were exposed. “Looks like someone hard-connected an external device to the ship’s computer systems, or at least tried to. Beyond that open panel, though…”
Whistle stopped looking around the room; his specialties were astronomy and computer science, not forensics, so he would likely miss details that the Security personnel would notice.
“I was coming to my duty shift at Stellar Cartography - trying to be a few minutes early so I didn’t lose a bet some of us junior officers have about shift punctuality - when someone in a services uniform with a weird-looking satchel - I think it was a satchel, since it was slung on his hip, but I’m not actually sure - bumped into me as I rounded the corner. I saw Ensign Piccolo slumped against a wall in the corridor. She was unconscious, and had a gash in her head. I called Medical, they showed up, then I called Security. From what I saw, Betsy - sorry, Ensign Piccolo - hadn’t been attacked in the hallway, but I couldn’t be sure.”
Whistle looked over to the other senior officers. “I’m not going to tell you how to do your jobs, but I would guess the attack happened in here, and you might be able to tell how whoever did this connected to the computer. I’ve rewired enough Starfleet computer terminals in my day because of crazy Academy professors - er, detail-oriented instruction; sorry for the lack of decorum, Commander - to know that that doesn’t look normal.”
Pelican, GM
USS SentinelKarl looked over the console the Officer mentioned and nodded walking to it and examining it curiously.
Master Chief Karl - CE
Bumping for Security and Science to respond
Cpt. Asam, CO
Rende tapped her comms and sent a message to Lt. Anders to have someone meet En. ch’Sirhc at comm control.
Cpt. Asam, CO
Bump for GM
OOC: Going back and highlighting information to be responded to. There is plenty here for Science, Security, and Engineering to respond. Once they do I will add more.
EvilJen, DDoSFEO
[O] Asam to security, medical, and Alden. Deck 8, junction 29. Our quarry is there now. Attempting to bypass the comm lock down. He’s wearing an environmental suit.[C]
Cpt. Asam, CO
Hearing the comm call, Alden turned and raced down the hall, towards Deck 8.
~ Cmdr Alden, XO/CSO
Karl looked up as the first officer ran down the corridor “I’ll finish up here” He called after the first officer, he wanted to finish checking out how the spy got through their system before going blind against a more recent attempt. He took out his diagnostic tool and attached it to the terminal that had been tampered with.
Master Chief Karl - CE
Marcus bolted to stay in step with the XO, ‘On your right Commander,’ he said quickly, tightening the grip on his phaser.
-Lieutenant Junior Grade Marcus Anders: Chief of Security-
OOC: Cross Posted Anders to this thread:
https://www.star-fleet.com/core/stf5/sentinel/posts/251276/Bump
The diagnostics came back with a lot of what would normally be expected for a forced access of this nature - a couple of damaged processing boards, some reconfigured connection route instructions. However, it seemed that the intruder had managed to place a secondary operating system layer underneath the existing software. It wasn’t placed maliciously, on its face; nothing happened when Johansson discovered it, other than that Karl could suddenly access it (if he was able to read Romulan, at any rate). But it was clear that this operating system layer had allowed the intruder to bypass many standard security and access restrictions that the standard Starfleet operating system included.
Pelican, GM
USS SentinelKarl frowned at the alien lettering. He’d some basic knowledge of Vulcan and was familiar with some of their different written language but that wasn’t nearly enough to have passing familiarity with Romulan writing. He flipped open his communicator unwilling to mess around without knowing what he was doing [O]Chief K to bridge, I need a translator down at Stellar Cart, someone who can read and translate Romulan.[O]
Master Chief Karl - CE
Rende punched her comm on the chair, [O]I’ll have someone down there immediately, Chief.[C]
Cpt. Asam, CO
While Jahonsson was waiting, the Romulan operating system suddenly came alive. It scrolled automatically, displaying about 50 lines in as many seconds, then displaying a block of the Romulan text about four lines long. Then another two lines displayed - and the whole screen went blank. Come to that, all of the displays in Stellar Cartography went blank. They reactivated almost immediately, but it seemed that, unlike the standard Starfleet operating system, the hidden Romulan OS had not turned back on - or was no longer in the system at all.
Pelican, GM
USS SentinelKarl cursed a few colorful Icelandic curses mostly related to devils, hell, and some unsavory comparisons to a really ugly fish as he tapped through attempting to retrieve any of the information he’d lost.
Master Chief Karl - CE
He wasn’t able to retrieve live data, but the data wipe that had apparently occurred had failed to erase display image copies. It was one of the benefits of Starfleet redundancy - in the event that work data was lost, it was possible to recover it by taking a look at screen captures. It was somewhat time intensive - but it meant that the Chief Engineer, while not being able to actively work with the hidden Romulan operating system, could still look at what the OS was doing before the whole system did a rapid reset.
Pelican, GM
USS Sentinel
Karl immediately went to work looking at what was happening, making sure to record his progress onto his tricorder incase the redundancy failed. A tertiary fail system was a Starfleet Engineers saving grace.
Master Chief Karl - CE