"That is impossible. My credentials weren't activated until the verification you just completed."
Andrew shook his head.
"The system says the session was authenticated using your executive identity before you entered the terminal."
Jonathan looked toward the restricted corridor again.
For the first time that morning, he wondered whether the anonymous message had been a warning—or an invitation.
Someone had known he would come.
And someone had been waiting for him.
Andrew Collins led Jonathan through a staff-only door into a narrow administrative office behind the check-in counters. The room contained two computer terminals, a wall-mounted display showing departure information, and a small table covered with maintenance reports. It was not impressive, but it was secure enough for preliminary incident reviews.
Jonathan closed the door himself.
"First, tell me who had access to my executive credentials before this morning."
Andrew sat at the computer.
"Normally, nobody can use them without your physical authentication token and a secondary verification code. Your account is also restricted to approved devices."
"Normally isn't an answer."
Andrew hesitated.
"The airport technology team has a small number of emergency recovery procedures. The chief security officer can authorize a temporary administrative session if the primary account holder is unavailable."
"Can that procedure be activated without notifying me?"
"Not under the current policy."
"Who can override the notification?"
Andrew opened another window. "The chief security officer, the network director, and two members of the executive emergency committee."
"Names."
Andrew brought up the authorization list. Four names appeared, each accompanied by a department and access level.
Jonathan read them carefully. He recognized all four. One belonged to his own cybersecurity director, Elena Morris. Another belonged to Martin Hale, Westbridge Airport's chief security officer. The remaining two belonged to senior administrators responsible for infrastructure and emergency response.
"Have any of them reported a lost device or compromised account?"
"No."
"Have any of them requested emergency access this week?"
Andrew searched the audit history.
"Not through the normal procedure."
Jonathan leaned against the table.
"Then either someone has stolen a credential, someone has discovered a weakness in our authentication process, or an authorized employee is hiding a session."
Andrew looked troubled.
"Could it be a system error?"
"It could. We will verify that possibility before accusing anyone."
Jonathan had learned that investigations often failed because people decided too early what they wanted the evidence to prove. He had no intention of repeating that mistake.
He took out his phone and called Elena Morris directly.
She answered after two rings.
"Jonathan? I thought you were visiting the regional office today."
"I'm at Westbridge."
There was a short silence.
"You're at the airport?"
"Yes. I need you to check an executive authentication alert. Someone appears to be using my credentials from a second location."
Elena's voice immediately changed.
"Don't access any more restricted screens. Don't disconnect anything. Tell me the alert code and the time it first appeared."
Jonathan gave her the information.
"All right," she said. "I'm opening the audit records now. I'll contact you through the secure channel in five minutes."
"One more thing. Keep this limited to people you personally trust."
"Understood."
The call ended.
Andrew was watching him.
"Should we notify Martin Hale?"
"Not yet."
"But he's responsible for airport security."
"Which is why we need to know whether the session originated from a security-controlled device before involving him."
Andrew appeared uncomfortable with the implication.
"Martin has worked here for fourteen years."
"That makes him experienced. It doesn't make him immune to investigation."
Jonathan returned to the computer. "Show me the original reservation problem."
Andrew opened the airline's booking interface and entered Jonathan's reference number. The system displayed a confirmed ticket, a completed payment, and a valid seat assignment.
"There," Andrew said. "The reservation is fine."
"Then why did Counter 12 reject it?"
He checked the transaction history. A status change had occurred at 8:11 that morning, five minutes before Jonathan reached the counter.
The booking had not been canceled. Instead, a restriction had been added to the check-in record.
MANUAL REVIEW REQUIRED. AUTHORIZATION LEVEL: SUPERVISOR.
Andrew frowned.
"That's a legitimate restriction code."
"Who added it?"
He clicked the audit details.
The system returned a username, but the employee identification field was blank.
"That isn't normal," Andrew said.
"Can the restriction be applied automatically?"
"Yes, in certain cases. A payment dispute, a document discrepancy, a security flag, or an irregularity in the passenger record."
"Did any of those conditions exist?"
Andrew checked the payment history and document status. Both were clean.
"No."
"Then someone added the restriction manually."
Andrew's expression grew tense.
"The account used to apply it belongs to the airport's central service desk."
"Who was logged into that account?"
"That's what I need to establish."
Jonathan pointed at the audit trail.
"Preserve this record. Make a copy that cannot be altered by the same administrative account. If someone has compromised the system, the original history may not be reliable."
Andrew nodded and initiated a secure export.
At that moment, Jonathan's phone vibrated. Elena had sent a message through the encrypted channel.
I FOUND A SECOND SESSION. AUTHENTICATION METHOD IS UNUSUAL. CALL ME.
Jonathan stepped toward the far end of the room and called her.
Elena spoke quickly.
"The second session isn't using a normal login. It is presenting a valid executive token signature, but the device fingerprint doesn't match your registered equipment."
"Could someone have cloned the token?"
"Not easily. The token contains hardware-based protections. But someone could have copied an earlier authorization package or exploited a trusted service that validates your identity on behalf of the airport."
"Would that explain the blank employee ID on the reservation restriction?"
"Possibly. If the same service account is involved, the restriction might have been created by a process rather than a person. We need the complete audit trail."
"Can you identify the device?"
"I'm trying. The session is routing through a local operations gateway, but the gateway logs show an internal address that doesn't belong to any currently registered workstation."
Jonathan looked at Andrew.
"How many unregistered workstations are connected to this terminal?"