Page 66 of At the Crossroads


Font Size:  

“Okay. Let’s start.” Clay’s voice is gravelly and impatient. He has been tapping his pen against a portfolio as we wait to start. “Has Erik made his report? Any new ideas about who’s sabotaging the software?” His voice turns deceptively soft.

“Looking at Erik’s report, I doubt we can clean it up.” I watch Jarvis clench and unclench his fists as he gives us the bad news. “I’m guessing a complete rewrite will be the only solution.”

“How long will that take?” I’m edgy, as sharp as broken glass.

“Since the upgrade planning was done, and I designed the architecture, a small team might recreate a clean version in a few months, if we’re lucky. In the meantime, I’m worried there may be a fresh attack on the current software. If that’s compromised, we’ll be at ground zero.” We all wince at the reference.

Clay explodes. “A couple of months?”

“Sorry,” Jarvis says apologetically. “I know it’s bad news, but even if we worked ’round the clock, it would take more time than you want.”

Holding up a hand, I put in, “We do have backups of the current software.”

“We do.” Jarvis verbally agrees, but shakes his head. “However, if the sabotage is internal, nothing may be safe.”

I swallow a groan. “Cleaning up infected clients will be a nightmare.”

“This only affects the upgrade—so far.” Jarvis gives a thin smile.

“Since our suspicion is it’s a Russian op, we need to find out whether it’s government sanctioned or one of the independent hacker groups. I am convinced we have an insider at GSU, presumably working with this outside group.” Metin’s remark adds to the doom and gloom that pervades the meeting.

Russian hacker groups usually have some government connection, which complicates everything. I stretch, then start moving around the cramped conference room. What I really want to do is lie on the floor to ease my aching back. Maybe do some yoga.

Metin licks her lips. “I’ve been in touch with the CIA, FBI, and NSA.” Her fingers are busy undoing and redoing her hair. “No luck so far in identifying who it is.”

Jarvis scowls. “As you know, the server has been under unusually heavy attack for a couple of days. Last night, someone opened a backdoor into the mainframe but it hasn’t been used yet. I left it alone so the hacker wouldn’t realize we’re onto him or her, but I put on an alarm, so I’ll know when they go back in. My team can set a trap ASAP to catch the perp.” Jarvis loves his TV cop lingo.

“Timeline?” Clay asks what we all want to know.

“I’ve been working on it all morning. Tonight I’ll put in the trap, and close their backdoor. We can track them while the primary system is untouched. Of course, this will only work if whoever accesses it isn’t internal. None of the team would mistake the decoy for the real thing.”

I hold up my hand. “If the plan works, it should give us a bit of breathing room. Still, there are risks. If our saboteur is internal, he or she might be tipped off by the outside entity.”

“Only if they realize it’s a dummy with fake data. We hope that might take a while.”

I shrug. “We have attacks on the server all the time.”

“Someday, one will be successful.” Jarvis’ warning is grim. “A matter of time, really.”

Metin nods. “Ransomware is a bigger and bigger threat worldwide. Whether they could blow up our server isn’t clear. It’s a possibility we need to take seriously.”

“Looks like their aim is a combination of data mining and theft.” Jarvis’ comment breaks into my thoughts. “But if we lock the door to frustrate the perpetrator, they might do something more destructive, like trying to take out the server or installing ransomware. My trap will make them think they are getting data, but none of it is real; a data set I concocted to keep them busy. I also created some fake accounts they can ‘pilfer.’”

“Are they that good?” Metin stares at me, but Clay answers.

“Probably not as good as Jarvis. But maybe they don’t need to be.” He frowns. “Working it through the security agencies takes a long time, and I’m never sure we can completely trust them. Anyway, we don’t have that kind of time.”

I lean back and put my clasped hands behind my head. “There’s no way to hurry the process.”

“Most companies can survive data leaks.” Clay tents his hands. “We are in a unique position. Our job is to make sure data leaks can’t happen. If they do, we lose our reputation, probably clients, and possibly the company.”

“You’re joking.” JL walks into the conference room. He grabs a chair and stares at the screen. A traditional security bloke, JL knows this is serious, but not how serious.

I turn to ask him why he’s here, but Clay’s growl travels through the air like a slap.

“If you started having complaints that your security guys were sleeping on the job—or sleeping with the clients—what do you think the fallout would be?”

JL’s mouth drops open, his fingers tugging at his hair. “Okay, I get it. I was kind of thinking about all these data leaks we hear about. You know, two million emails exposed, that kind of thing. Those companies are still in business.”

Source: www.allfreenovel.com