Digital Fortress Chapter 9

Systems security technician Phil Chartrukian had only intended to be deep down Crypto a minute-just bulky enough to grab some paperwork hed forgotten the day before. scarcely it was non to be.After making his way across the Crypto floor and stepping into the Sys-Sec research lab, he at present knew some topic was not right. The computer terminal that perpetu each(prenominal)y monitored TRANSLTRs internal workings was enervate and the monitor was switched off.Chartrukian called out, Hello?There was no reply. The lab was spotless-as if no virtuoso had been there for hours.Although Chartrukian was only twenty-three and relatively new to the Sys-Sec squad, hed been trained well, and he knew the drill There was always a Sys-Sec on duty in Crypto especially on Saturdays when no cryptographers were around.He immediately powered up the monitor and turned to the duty board on the wall. Whos on observation post? he demanded aloud, scanning the tend of names. According to the schedule, a young greenhorn named Seidenberg was supposed to have started a double shift at mid night the night before. Chartrukian glanced around the empty lab and frowned. So where the hell is he?As he watched the monitor power up, Chartrukian wondered if Strathmore knew the Sys-Sec lab was unmanned. He had noticed on his way in that the curtains of Strathmores workstation were closed, which meant the boss was in-not at all uncommon for a Saturday Strathmore, despite requesting his cryptographers take Saturdays off, seemed to work 365 days a year.There was i thing Chartrukian knew for certain-if Strathmore found out the Sys-Sec lab was unmanned, it would cost the absent laddie his job. Chartrukian eyed the phone, wondering if he should call the young techie and adherence him out there was an unspoken rule among Sys-Sec that they would watch each others backs. In Crypto, Sys-Secs were second-class citizens, constantly at odds with the lords of the manor. It was no secret that the crypto graphers control this multibillion-dollar roost Sys-Secs were tolerated only because they kept the toys running smoothly.Chartrukian made his decision. He grabbed the phone. only if the receiver never reached his ear. He stopped short, his eyes transfixed on the monitor now coming into focus before him. As if in slow motion, he set down the phone and stared in open-mouthed wonder.In eight months as a Sys-Sec, Phil Chartrukian had never seen TRANSLTRs Run-Monitor post anything other than a double zero in the hours field. Today was a first.TIME pass on 151721 Fifteen hours and seventeen minutes? he choked. ImpossibleHe rebooted the screen, praying it hadnt refreshed properly. But when the monitor came back to life, it looked the same.Chartrukian tangle a chill. Cryptos Sys-Secs had only one responsibility Keep TRANSLTR clean-virus free.Chartrukian knew that a xv-hour run could only mean one thing-infection. An impure level had gotten inside TRANSLTR and was corrupting the progra mming. Instantly his training kicked in it no longer mattered that the Sys-Sec lab had been unmanned or the monitors switched off. He focused on the matter at hand-TRANSLTR. He immediately called up a log of all the blames that had entered TRANSLTR in the last forty-eight hours. He began scanning the list.Did an infected file shake up through? he wondered. Could the security filters have missed something?As a precaution, every file entering TRANSLTR had to pass through what was known as Gauntlet-a series of powerful circuit-level gateways, packet filters, and disinfectant programs that scanned inbound files for computer viruses and potentially dangerous subroutines. Files containing programming unknown to Gauntlet were immediately rejected. They had to be check up on by hand. Occasionally Gauntlet rejected entirely harmless files on the basis that they contained programming the filters had never seen before. In that case, the Sys-Secs did a scrupulous manual inspection, and only then, on confirmation that the file was clean, did they bypass Gauntlets filters and send the file into TRANSLTR.Computer viruses were as varied as bacterial viruses. Like their physiological counterparts, computer viruses had one goal-to attach themselves to a host system and replicate. In this case, the host was TRANSLTR.Chartrukian was amazed the NSA hadnt had problems with viruses before. Gauntlet was a potent sentry, but still, the NSA was a bottom feeder, sucking in massive amounts of digital information from systems all over the world. Snooping data was a lot like having indiscriminate sex-protection or no protection, sooner or later you caught something.Chartrukian finished examining the file list before him. He was now more puzzled than before. Every file checked out. Gauntlet had seen nothing out of the ordinary, which meant the file in TRANSLTR was solely clean.So what the hells taking so long? he demanded of the empty room. Chartrukian felt up himself break a sweat. He wondered if he should go disturb Strathmore with the news.A virus probe, Chartrukian said firmly, trying to calm himself down. I should run a virus probe.Chartrukian knew that a virus probe would be the first thing Strathmore would request anyway. Glancing out at the deserted Crypto floor, Chartrukian made his decision. He sozzled the viral probe software and launched it. The run would take about fifteen minutes.Come back clean, he whispered. Squeaky clean. Tell Daddy its nothing.But Chartrukian sensed it was not nothing. Instinct told him something very unusual was going on inside the great decoding beast.