Chapter 6 #2
"Your patch is solid. Better than the original.
" I keep my eyes on my own screen. The compliment costs me nothing and buys goodwill, and if it also happens to be true, that's incidental.
"But you reinforced the north-facing handshake protocol with a redundancy loop that adds latency.
Over sustained traffic, that compounds."
"Over sustained traffic from, say, a coordinated multi-vector cyber weapon?"
"Over sustained traffic from anything. Sloppy is sloppy."
He takes a long drink of coffee, swallows, and adjusts his glasses with his ring finger. "How much latency?"
"Twelve point three milliseconds per cycle. More if the secondary relay is under load."
"You measured."
"I measure everything."
The silence that follows should be combative, but it isn't. His mouth twitches at one corner, and he turns back to his screen, and the twelve point three milliseconds hang between us like a shared joke that neither of us is willing to laugh at yet.
His mouth, when it does that, creates a problem I don't have a variable for.
I notice the shape of it. I notice that I notice.
I force both observations into the box that won't close and go back to work.
We work.
The Committee's weapon is more sophisticated than the targeting data suggested, and every layer I peel back reveals another layer beneath it with a design philosophy I recognize.
Distributed nodes, redundant pathways, modular deployment capability.
Whoever built this didn't just study offensive cyber operations.
They studied elegant offensive cyber operations.
The weapon's a surgical instrument, and the precision of its design tells me something about its creator that the targeting data alone never could: this person cares about craft.
I hate that I admire it.
"I need you to walk me through your defense matrix.
" The words come out flatter than I intend.
Asking for help doesn't come naturally. Asking Tommy for help, specifically, feels like conceding ground I can't afford to lose.
But the weapon's delivery mechanism targets the intersection between his internal systems and the external communications channels, and I can't map the attack surface without understanding what he built.
Tommy rolls his chair sideways until our stations overlap, close enough that I can smell coffee and dark chocolate and something underneath both, something warm and clean and distinctly him.
My body registers the scent with the efficiency of a system that's decided this information is mission-critical despite receiving no such instruction.
He pulls up a schematic on his center monitor and starts talking.
Rapidly. In layers. With tangential observations that seem irrelevant until they circle back three sentences later and land with the precision of a scalpel. He talks the way he codes: dense, efficient, and threaded with a structural logic that makes my fingers itch to diagram it.
"The primary defense operates on a rotating cipher with a randomization seed generated from environmental data.
Temperature readings from the server room, ambient sound levels, barometric pressure from the exterior sensors.
Nothing digital, nothing predictable, nothing someone could brute-force without physically being inside the mountain.
Secondary layer is behavioral analysis. The system learns normal traffic patterns and flags deviations, but I tuned the sensitivity so it doesn't cry wolf every time Sarah runs a high-volume signals sweep in the middle of the night. "
"Behavioral analysis can be spoofed."
"By someone who knows what normal looks like from the inside.
Which is why the tertiary layer exists." He taps a section of the schematic, and his hand passes close enough to mine that I feel the warmth radiating off his skin.
"Custom protocol. I wrote it from scratch when Kane started running field operations that required real-time intelligence support.
It monitors the handshake between internal systems and outbound communications and verifies integrity at the packet level. "
"That's the layer I came through."
His fingers stop on the keyboard for a beat, then resume. "Yeah. That's the layer you came through."
"Your custom protocol has a vulnerability in the timing verification during high-load operations.
When the system's processing multiple outbound streams simultaneously, the integrity check deprioritizes to maintain throughput.
The window's small, fractions of a second, but fractions of a second is all I needed. "
Tommy's quiet for long enough that I glance sideways.
His expression isn't defensive. He's looking at the schematic with the intensity of a man who's just been shown a flaw in something he built with his own hands, and the flaw is real, and he already knows how to fix it, and the fact that someone else found it first is eating him alive.
The intensity changes his face, sharpens it, and his jaw and cheekbones do something that has no business registering on my threat assessment but does anyway.
"Show me."
I lean forward. My chair rolls closer to his.
The workspace is already tight, two stations crammed into a space designed for one because Kane wanted us working within arm's reach, and my elbow brushes his forearm as I reach for his keyboard.
The contact is brief, but his skin is warm from hours at the keys, and my fingers are cold because they always are, and the temperature differential sends a jolt through my wrist that has nothing to do with thermoregulation.
He doesn't pull away. Neither do I.
I type the exploit pathway, each keystroke laying out the exact route I used to deliver the warning.
Tommy watches my hands on his keyboard, and the proprietary quality of that observation, the attention he pays to the movement of my fingers on his hardware, creates a tension in the air between our chairs that smells like ozone and tastes like a bad idea.
"There." I pull back. "The reprioritization during high-load creates a window where the integrity check drops to passive monitoring. I routed my message through that gap by triggering a synthetic load spike on three of your outbound channels simultaneously."
"You created a distraction."
"I created a precisely calibrated load distribution that exploited a design trade-off between security and performance. A distraction is throwing a rock through a window. This was threading a needle while the needle was moving."
"I can fix it."
"I know. But that's not the point." I pull the Committee's weapon analysis onto my own screen and rotate it so he can see.
"The point is that whoever designed this weapon found the same vulnerability, or one functionally identical to it.
The delivery mechanism targets the same intersection between internal and external systems, exploiting the same kind of design trade-off. "
The implication lands. I watch him process it, watch the color of his understanding shift as the pieces connect.
"They studied my system."
"They studied your system the way I studied it. Structurally. Over time. With patience and technical fluency. They found the same seams I found."
Tommy pushes his glasses up with his thumb, takes them off entirely, and cleans them on the hem of his shirt with a deliberation that suggests the gesture has nothing to do with dirty lenses.
Without the glasses, his face is exposed in a way that the barrier usually prevents.
His eyes are brown and unguarded, and they carry the quiet devastation of a man realizing he's not as good as he thought he was.
I've worn that expression. I recognize it the way you recognize your own handwriting.
"We need to go to the server room." His voice is even, controlled, and the humor's gone.
The absence changes the shape of the air between us.
"I need to run a physical audit of the communication relays.
If the weapon's targeting the interface between internal and external systems, I need to know if there's hardware-level compromise I haven't detected. "
I grab the diagnostic tablet and follow him through the corridor without argument, which is notable because I argue about everything.
The walk is short, two turns and a security door that opens to his biometric scan, and neither of us speaks.
The silence isn't hostile. It's the focused quiet of two people who've just agreed on something important and don't need to fill the space with noise.
The server room is cold, the deep structural chill of a climate-controlled environment designed to keep machines alive at the expense of human comfort. The air tastes like metal and ozone, and the hum is louder here, lower in frequency, vibrating in my molars.
Tommy works the hardware with a competence I didn't expect.
He moves through the server racks with physical confidence, hands finding connections by feel, his body navigating the narrow aisles between equipment with the ease of someone who's spent years in this room.
He's the man who built what the screens display, who crawled under desks and ran cables through solid rock and soldered connections in the dark because the infrastructure of this place didn't exist until he made it.
I watch his hands on the relay housings, precise and fast and certain.
Then I stop watching his hands because my gaze has tracked up his forearms to his shoulders, which are broader than his usual posture advertises, and the muscles in his back shift under his shirt when he reaches for a high connection.
I'm standing in a cold room surrounded by servers watching a man I've known for days with an intensity of attention that I normally reserve for code I'm about to exploit.