Price of Duty
Page 19
As the seconds ticked down, the blinking red icons drew ever nearer to Moscow.
“All surface-to-air missile batteries report they are standing by. They are ready to fire on command,” the first voice said again, sounding more excited now. “Handoff to 96L6E complete! Hostile altitude is two hundred meters! Formation size is ten-plus hostiles. Types unknown. Enemy formation now increasing speed to one thousand kilometers per hour.”
The assembled officers and officials tensed. At any second now, salvos of long-range missiles would begin rippling skyward, reaching out to destroy enemy aircraft with relative ease.
“Second Battery, 210th Air Defense Regiment reports solid lock on hostiles. Ready to attack!”
Suddenly the red icons speeding toward Moscow vanished.
“What the hell?” someone exclaimed.
“Contact lost,” the first voice reported, seconds behind the situation shown on the map. “Radars are attempting to reacquire.”
Minutes later, the icons representing the incoming enemy air strike blinked back on. But they were in a different location now, well to the north of their previous plotted position and fifty kilometers closer to Moscow.
Again, the longer-range SAM acquisition radars cycled through the process of handing off data to their batteries’ target-tracking and missile-guidance radars. And again, as soon as the defenders were ready to fire, their radars mysteriously lost all contact with the hostile aircraft. Now, though, the green symbols representing several different SAM units flashed orange. Some went black.
“Our forces are under missile attack!” a panicked voice yelled over the speakers. “They report multiple impacts which have destroyed many radars and SAM launchers!”
The hostile icons reappeared suddenly on the map. But this time they displayed the enemy attack formation far south of its earlier reported position and scarcely a hundred kilometers from the center of Moscow.
“I think we’ve seen quite enough, Doctor,” Colonel General Valentin Maksimov, the tall and powerfully built commander of Russia’s Aerospace Forces, muttered to the much shorter man sitting next to him.
Dr. Nikolai Obolensky nodded. “Indeed, General,” he said in a dry, precise voice.
Everything about Obolensky, from his close-cropped gray hair and tortoiseshell eyeglasses to his unfashionable black suit and drab brown tie, marked him as an old-fashioned academic. Some would have gone further, pegging him as a washed-up professor of mathematics from some minor university. That would have been both unkind and inaccurate.
In reality, he ran the Nizhny Novgorod Research Institute of Radio Engineering (NNIIRT)’s software lab—overseeing the development of the target acquisition and identification programs used by Russia’s most advanced and lethal SAM systems. Though it had been years since he had done any serious software development himself, Obolensky had proved his managerial talents by successfully shepherding a number of vital projects to completion, and doing so on budget and on time.
“End simulation, Anya,” the NNIIRT lab chief said into the wireless mic attached to his lapel. Behind him, in the projection room at the back of the auditorium, his assistant obeyed.
The digital map display froze, still showing the appalling hole torn in Moscow’s outer air-defense network. It also showed that the enemy strike force was now well within air-launched missile range of Russia’s capital. The lights came up, revealing a sea of unhappy faces.
Obolensky moved to the front of the auditorium. “This was a computer-generated simulation of what might happen if the Poles and their Iron Wolf mercenary allies conduct an all-out attack on Moscow. It represents our best estimate of the tactical advantages conferred by their use of netrusion technology and an array of stealth drones.” He smiled thinly. “As you have seen, they are considerable.”
Maksimov nodded bitterly. During last year’s short war with Poland and its hired high-tech warriors, he’d watched in horror while several of his most advanced fighter squadrons and SAM battalions were savaged—often without being able to even fire a shot in reply, let alone score any kills. The sensor data they’d gathered on the enemy’s netrusion systems and drones represented the only silver lining in that black cloud of slaughter and humiliation . . . and that was a very slender thread to which to cling for solace.
“Now let me show you what will happen once we deploy the software upgrades developed by my lab here at NNIIRT,” Obolensky told them. He moved to the side, away from the screen and looked up toward the projection booth. “Reboot the simulation, Anya,” he ordered. “Run FAVORIT/TRIUMF variation 19 point 17c.”
The lights dimmed again.
For a time, the sequence of events played out just as it had earlier. Enemy aircraft were detected and then vanished almost as soon as firing solutions were first achieved. But that was the end of any similarity. Now the icons showing the attacking force reappeared much faster, and they were much closer to their earlier estimated positions. Halfway through the war game, Russia’s S-400 and S-300 SAM batteries were in action—firing missiles at confirmed enemy targets. Most missed, lured astray by the array of close-in defenses employed by the Poles and their hirelings. But, ultimately, as almost always in war, quantity proved to be a quality all its own. The equation was simple: if you fired enough missiles at a given number of targets, you were bound to score hits.
Colonel General Maksimov sat enthralled, watching computer-generated Polish and Iron Wolf bombers, fighters, and drones disappear. Now, though, instead of vanishing behind their technological cloak, they were blinking off the display as they were shot down by Russian surface-to-air missiles. His SAM units took casualties too, but the fight this time was far more even. In the end, the whole enemy air formation was wiped out. Best of all, they were blown out of the sky before they could launch any of their own offensive weapons toward Moscow.
When the lights came up, he stood to applaud Obolensky, a move slavishly imitated by his subordinates and by the other defense-industry officials who depended on the weapons contracts he approved.
“You have worked wonders, Doctor,” Maksimov boomed. “For years, we have been at the mercy of this vaunted netrusion technology of the Americans. Their planes, and now those of the Poles, have flown unchallenged over our beloved Motherland. But now you have uncovered their secrets, and learned how to defeat our enemies.”
Precise as always, Obolensky shook his head. “Short of capturing one of the aircraft employing this technology, I’m afraid its innermost secrets will remain outside our grasp.”
Annoyed at being contradicted, Maksimov scowled down at the shorter man. He waved at the images shown on the screen. “Then what have you shown us? A lie? A wishful computer fabrication?”
“Not in the least, General,” the lab chief assured him. He smiled. “The new upgrade we’ve just demonstrated represents a significant improvement over our existing defenses. In the past, once the enemy blinded or spoofed our radars, it could take as long as two or three minutes to regain an accurate picture of the air battlefield.”
“Which is a lifetime in combat,” Maksimov growled. “In two minutes, a modern fighter-bomber might be as far as fifty kilometers away from where it was last detected.”
Obolensky nodded. “To address this problem, my team identified two separate approaches. First, we’ve greatly speeded up the rate at which our target acquisition and identification software comes back online after suffering a so-called netrusion attack. And second, our upgrade significantly enhances the software’s ability to sort out decoy drones from actual combat aircraft and air-launched weapons.”
“How much faster? And in plain Russian, please,” Maksimov asked. He shrugged his massive shoulders. “Remember that I am an old war-horse, not a computer scientist.”
“The enemy can still blind our radars or launch waves of decoy drones to cloud the radar picture,” Obolensky explained. “But now we can pierce this concealing cloak in as little as thirty to fifty seconds.”
“To what effect
?” Maksimov asked bluntly. “In the real world.”
“We estimate this software upgrade will increase our Pk, the probability of kill, for S-300 and S-400 missile launches by up to thirty percent,” Obolensky said with serene confidence. He turned and pointed at the situation now shown on the screen. “And that increase in combat efficiency, Colonel General, represents the margin between watching Moscow battered into burning, bomb-gutted ruins . . . and victory.”
Maksimov lowered his head briefly, conceding the point. Much as he disliked appearing uninformed in front of others, he admired the little man’s willingness to stand up to him, and the self-assurance he exhibited. “Then I gladly stand corrected, Doctor,” he said with a forced smile. “But that leaves me with one last question.”
Obolensky raised an eyebrow. “Yes, General?”
“How soon can this program upgrade of yours be deployed to my surface-to-air missile regiments?”
“We should be able to transmit a final, completely debugged version to your headquarters in Moscow within forty-eight hours,” the NNIIRT lab chief assured him. He shrugged. “After that, its final distribution to the appropriate air-defense units will be up to your staff.”
Maksimov nodded. He shot an inquiring glance at his senior military aide, Major General Viktor Polichev. “Well, Viktor?”
Polichev pursed his lips, pondering the logistics involved. “Once we get our hands on this NNIIRT software update, our headquarters IT specialists should be able to make the necessary copies in short order. And we can send them out to every S-300 and S-400 regiment by special courier.”
“You suggest we use courier delivery?” Maksimov asked, unable to hide his surprise. “Wouldn’t it be faster to distribute this update online, using our data links to each regimental headquarters?”
“Perhaps, sir,” his aide said. Then he shrugged. “But in light of recent events, I think it might be wiser to avoid relying too much on electronic communication.”
Maksimov nodded slowly, thinking about the tidal wave of computer-caused havoc currently sweeping across Eastern and central Europe. Polichev was right. If nothing else, President Gryzlov’s cyberwar campaign showed the dangers involved in trusting vital information to the vagaries of the Internet.
“An excellent point, Viktor,” he said at length. “Organize your courier chain at once. Sooner or later, the Poles and their Iron Wolf pirates are bound to strike back at us. And when that day finally comes, I want to be sure our SAM regiments are ready, willing, and able to swat them out of the sky!”
As the assembled military officers and defense-industry officials filed out, Dr. Nikolai Obolensky stood near the auditorium’s exit, gravely acknowledging their congratulations. His briefing had been a triumph, both of showmanship and of substance, and he knew it.
The NNIIRT lab chief was well aware that many of the computer engineers who worked under him had little understanding of, or respect for, his skills as an administrator. Sometimes they even furtively passed around copies of the subversive American comic strip Dilbert, slyly identifying him with the comic strip’s imbecile, pointy-headed boss. In their insular world, a man who no longer wrote lines of code himself was nothing but an officious, interfering bureaucrat.
Today’s success should shake that ignorant view, he thought smugly.
Not one of his technically adept computer geniuses could possibly have “sold” their work so easily to an old Soviet-era dinosaur like Maksimov. Any briefing they put together would have opened with deadly dull PowerPoint slides and ended with a mind-numbing, jargon-filled recitation of intricate technical detail. By that time, the NNIIRT auditorium would either have been packed with snoozing generals or completely abandoned after the audience fled. Using a battle simulation to show off the upgrade’s features had been his idea. And it had worked perfectly. Nothing so delighted men of Maksimov’s kind as seeing enemy planes—even computer-generated ones—blown to pieces.
The crowd of officers and officials thinned and then vanished. Later in the day, they would meet again at one of Nizhny Novgorod’s most expensive restaurants. The Research Institute’s top brass had organized an elaborate lunch for their distinguished guests and customers. And there, celebratory toasts would ratify yet another programming triumph for Nikolai Obolensky and his software-development team.
He smiled to himself, imagining the paeans of praise and new perks his superiors were sure to shower on him.
Suddenly aware that he was under observation, Obolensky looked up. A striking redhead in uniform had stayed behind the rest. Her shoulder boards bore the three stars of a colonel. She stood a few feet away, eyeing him with a wry smile of her own.
He blushed, feeling slightly awkward at having been caught so obviously daydreaming. Embarrassed, he cleared his throat. “May I help you with something, Colonel . . .” His voice trailed off as he realized he did not know her name.
“Nechaeva. Tatiana Nechaeva,” the redhead said crisply. “And I think you will find that I am the one who can help you, Dr. Obolensky.” Seeing his confusion, she handed him her identity card.
Obolensky stared down at the card. It declared that Colonel Tatiana Nechaeva was an officer in the FSB’s counterintelligence service. His eyes widened a bit in surprise. He had always pictured secret-police agents as hulking, unsmiling brutes. Meeting one who was a shapely, extremely attractive woman came as something of a shock. Still puzzled, he handed her ID back. “I’m afraid I don’t quite understand,” he admitted. “How is it that you can help me?”
Nechaeva shook her head. “Not here, Doctor. Not in public.” Her gaze was cooler now. “This is a matter of urgent state security.”
He froze briefly. “A matter of state security? But—” Seeing her mouth tighten in annoyance, he stopped talking.
“I won’t remind you again, Doctor,” Nechaeva said sharply. “I strongly suggest we move this conversation to your office.”
Obolensky bobbed his head in hurried agreement. “Of course, Colonel. At once.” He gestured toward the hallway. “Please, follow me.”
Somehow, his small office looked messier than he remembered. It also smelled strongly of both dust and pipe tobacco. With a murmured apology, he cleared away the stacks of file folders and manuals piled up on his only other chair.
Primly, Nechaeva sat down. She waited to speak until he closed the door and uneasily took his own seat. “First, you must understand that everything I am about to tell you stays in this room,” she said sternly. “This information is classified at the highest level. Revealing it to anyone else is punishable by life imprisonment or execution. Is that clear?”
Obolensky swallowed hard and nodded. “Yes, Colonel. I understand.”
“Good,” she said, suddenly relaxing. “I apologize for all the theatrics, Doctor. But I’m afraid they are necessary.”
“Why is that?” he asked nervously.
“Because it appears that foreign spies have targeted NNIIRT and especially your section,” Nechaeva told him.
His eyes widened again. “Spies? Here? Trying to penetrate my lab?”
“Apparently, your good work is appreciated far beyond our Motherland’s borders,” Nechaeva said.
“My God,” he murmured shakily. He looked at her. “But how do you know this, Colonel? Have these spies been trying to break into our facility? Or bribing some of my staff?”
“Nothing so old-fashioned,” she replied.
“Then how—”
“We have observed several attempts to break through the security firewall guarding your lab’s computer system,” Nechaeva said flatly.
“Our firewall?” Obolensky shook his head. “Excuse me, Colonel, but that is not possible. The institute’s information-technology specialists would have informed me at once of any such hacking efforts.”
“You think it impossible?” Nechaeva said coolly. She nodded toward the computer on his desk. “Then I will show you what we have discovered, Doctor. You have system administrator privileges for the l
ab’s computer network, do you not?”
He nodded slowly. “Yes, of course, but I . . . well, I almost never use them. Having such access is a formality, mostly. Because of my rank.”
“Naturally,” she agreed. Then she shrugged. “I suppose I should not expect the head of a computer software lab to pay close attention to the security of his own systems.”
Obolensky flushed at her obvious sarcasm. Recovering, he fumbled around in one of his desk drawers until he found the laminated card with the necessary password and user-ID information. He showed it to her.
“Very good, Doctor. Now sign in as an administrator and bring up your denied-access log for the following times,” Nechaeva commanded, rattling off a succession of specific days, hours, and minutes.
He obeyed, bringing up a dense wall of text showing that several different attempts had been made to penetrate the lab’s firewall at those moments. He glanced through the data and then shrugged his shoulders. “This is not evidence of any hacking, Colonel,” he said confidently. “Even a cursory look reveals these are simply instances where the computer systems the institute uses for routine day-to-day business accidentally contacted our lab’s secure network. This happens quite often, usually when someone hits ‘reply all’ to an e-mail which contains one of our secured addresses. Or occasionally when one of the administrative staff sends out a general memo to all departments, including ours, without first obtaining the necessary permissions.”
Nechaeva smiled thinly. “I suggest you examine those supposedly ‘internal’ IP addresses more closely.”
Nettled, Obolensky did as she suggested. What was she driving at? he wondered. His eyes moved from IP address to IP address, now paying careful attention to every detail. This time he saw the problem. The blood drained from his face. He looked away from the screen in horror. “Those are not genuine internal IP addresses,” he sputtered. “Those queries are coming from the outside, camouflaged as one or another of our business-side computers.”