It was 12:06 p.m.
The anonymous sender had warned him not to let the test run at noon.
He had tried to stop it.
Yet the validation had completed anyway.
And somewhere inside Westbridge Airport, a system that should have remained inactive for three years had just come back to life.
At 12:09 p.m., Jonathan Reed ordered the investigation team to preserve every available record connected to Project Horizon. The name had appeared only once in the recovered logs, but it was enough to suggest that the airport's security breach had roots far deeper than the suspicious maintenance device discovered that morning.
Priya worked at the terminal while Elena examined the authentication records remotely. Andrew contacted the independent compliance team and arranged for an external specialist to join the investigation. Nobody was permitted to alter the dormant account, reset its credentials, or attempt to access its contents without first creating a verified forensic copy.
The decision frustrated several people in the room, especially Martin Hale, who had returned to demand an explanation.
"You have an unknown privileged account inside the airport network," Martin said. "The obvious response is to disable it immediately."
"The account has already been activated," Jonathan replied. "We need to understand what it accessed before we decide how to contain it."
"And while you investigate, someone could use it again."
"Which is why we've restricted the relevant network routes and are monitoring the account's activity."
Martin shook his head.
"You're treating this like a paperwork problem."
"No. I'm treating it like a security incident in which careless action could destroy evidence or interrupt essential operations."
Martin turned toward Priya.
"Can you tell us what Project Horizon was designed to do?"
Priya searched the historical archive. The first reference appeared in a technical planning document dated three years earlier, shortly before Flight 608 experienced its unexplained departure delay.
The project had originally been described as an initiative to unify authorization across airport systems. Under the proposal, an authorized administrator would be able to verify permissions across passenger processing, maintenance management, emergency access controls, and departure coordination through a single validation process.
The stated goal was efficiency. Instead of maintaining separate authorization rules across multiple systems, the airport would use a central authority to verify that each system recognized the correct permissions.
Jonathan read the proposal carefully.
"That could simplify administration," he said. "But a central authority also creates a single point of failure."
"Exactly," Priya replied. "If the central identity is compromised, the attacker might gain access to several systems at once."
"Was that risk documented?"
"Yes. The original design required separate approvals for sensitive operations. No single identity was supposed to be able to grant itself unrestricted access."
Jonathan pointed to a paragraph.
"Then why does the current record say my clearance was transferred?"
Priya opened the later revisions.
"Because someone changed the authorization model after the first trial."
The revised proposal introduced a temporary recovery mechanism. It was intended to allow airport administrators to restore access if the central authorization service became unavailable. Instead of requiring separate approval from each system, the recovery mechanism could issue a temporary privileged identity to restore essential operations.
The revised model still required independent verification, but the approval process had been simplified.
Jonathan examined the revision date.
"Who requested the change?"
The document listed a project steering committee, but the individual approval fields were incomplete. A note indicated that the revision had been discussed during an emergency meeting following Flight 608.
Martin folded his arms.
"I remember that meeting. The airport was facing serious delays, and the technology team needed a way to restore service more quickly."
"Who proposed the recovery mechanism?" Jonathan asked.
"I don't remember the exact details."
"Was the system ever approved for live operations?"
"It was approved for limited testing."
"Was Project Horizon officially closed?"
Martin looked toward Priya.
"That's a technical question."
Priya shook her head.
"The project was marked inactive, but the underlying service account was never deleted. It was placed in a dormant state."
"Why?"
"The official note says it was retained for compatibility with legacy systems."
Jonathan looked at the historical authorization record.
"Who could reactivate it?"
Priya opened the access list.
"At least three administrative roles could initiate the process. The chief security officer, the technology director, and the executive recovery service."
"And what does the executive recovery service do?"
"It verifies that a privileged account is eligible for emergency restoration."
"Does it verify the identity of the person requesting restoration?"
"It should."
"Did it verify mine today?"
Priya searched the validation logs.
"The system verified a valid executive identity. But it did not establish that you personally approved the request."
The distinction was critical.
Someone had presented the system with a credential that appeared valid, and the system had treated that credential as sufficient proof of authorization.
Jonathan looked at Elena's latest message. She had found the same weakness from the remote side.
"The recovery service is trusting an authorization package generated by the legacy gateway," she said over the phone. "If that package was copied or recreated, the system could accept it without checking the original hardware token."
"Can we determine when the package was created?"
"We have a partial timestamp. The first record goes back to the night Flight 608 was delayed. The package was refreshed this morning."
"By whom?"
"An internal service account. We're still tracing the underlying session."
Jonathan turned to Andrew.
"Pull the original Project Horizon approval records. I want the committee minutes, contractor agreements, and every revision to the recovery mechanism."
Andrew nodded and left the room.
At 12:24, Priya discovered a connection between Project Horizon and the missing network module. The module's serial number appeared in the equipment inventory for the original trial, but its description had been changed after Flight 608.
Originally, it was listed as a temporary authorization bridge.
In the later inventory, it was described as a network diagnostics component.
"That is not a normal inventory update," Priya said.
"Could the equipment have been repurposed?" Jonathan asked.
"Possibly, but the change should have been supported by a new work order. There isn't one."
Jonathan studied the two records.
"Someone changed the equipment's description to make it appear ordinary."
"That's what it looks like."
"Can we identify who made the change?"
Priya opened the revision history.
The update had been made using an administrative account assigned to the central service desk. The employee field was blank, and the change had been approved by a shared security credential.
Martin stepped closer.
"Shared credentials were used during the original project because the team needed access around the clock."
"That may explain why the account existed," Jonathan replied. "It doesn't explain why the equipment description changed without a work order."
Martin's expression tightened.
"You keep treating every administrative shortcut as evidence of wrongdoing."
"I'm treating unexplained changes to a security device as evidence that needs to be investigated."
Before Martin could answer, Jonathan received a message from Elena.
WE FOUND A SECONDARY ACCOUNT ASSOCIATED WITH PROJECT HORIZON. IT IS CURRENTLY ACTIVE.
Jonathan called her immediately.
"Where is it operating?"
"The account is communicating through a legacy administrative interface. We can see its requests, but its user profile is masked."
"Can you identify the permissions?"