Airline Agent Tore Passenger's Ticket at Check-In—Then the Airport System Displayed His Clearance

Chapter 4

Theme:
Font Size:
24px

Andrew shook his head. "None should be."

"Check maintenance systems. Temporary equipment. Contractor laptops. Anything connected during the last thirty days."

Elena interrupted.

"Jonathan, there's something more concerning. The session isn't just reading information. It has requested permission to modify access-control rules."

Jonathan went still.

"Has the request been approved?"

"One validation stage has passed. The next stage requires authorization from the airport's operations controller."

"Who is the controller this morning?"

Andrew answered before Elena could.

"Martin Hale."

Jonathan closed his eyes briefly.

There were innocent explanations. A routine test might have been scheduled without the correct paperwork. A technician might have used an emergency recovery account. The system might have incorrectly associated an ordinary operation with Jonathan's identity.

But the timing was too precise to ignore.

"Elena," he said, "I want you to monitor the session without alerting whoever created it. Do not attempt to take control remotely."

"Agreed. If we touch the wrong process, we could destroy evidence or trigger an automatic response."

The call ended.

Andrew rubbed his forehead.

"If someone is inside the security network, shouldn't we close the airport?"

"Not without evidence that passenger safety is immediately at risk. Closing an airport affects thousands of people and can create new safety problems. We need a controlled response."

"How do we know the system isn't already compromised?"

"We don't. That's why we preserve evidence, verify the source, and restrict unnecessary privileges without interrupting essential operations."

Andrew looked at the monitor.

A new message had appeared.

ACCESS CONTROL REQUEST: PENDING AUTHORIZATION.

Beneath it was a list of restricted functions, including staff credentials, maintenance access, and emergency door controls.

Jonathan's face hardened.

"That request must not be approved."

"I can reject it," Andrew said.

"Can you do so without notifying the requester?"

Andrew checked the interface.

"I can place it in a review queue."

"Do that. Do not delete it."

He moved the request into the queue. The screen briefly flashed, then displayed a confirmation.

For several seconds, nothing happened.

Then a second request appeared.

This one did not come from the same gateway.

It originated from a workstation registered to the central service desk.

Jonathan and Andrew exchanged a glance.

"Someone is trying another route," Andrew said.

"Or a separate process is operating independently. We cannot assume it's the same person."

Andrew opened the details.

The request carried the same executive identity, but the authorization time was different. It had been generated less than a minute after the first request was placed under review.

Then a message appeared in a small notification window.

PLEASE STOP INTERFERING WITH THE VALIDATION PROCESS.

Andrew stared at it.

"Who sent that?"

Jonathan leaned closer.

"Can we trace the message source?"

"Not without opening the full diagnostic record."

"Then preserve the message and its metadata."

Andrew did so.

A moment later, another message appeared.

YOU WERE NOT SUPPOSED TO ARRIVE TODAY.

Jonathan felt a chill move through him.

The message could have been intended for the legitimate account holder. It could have been a crude attempt to intimidate whoever was investigating the session. Either way, the sender knew that someone was monitoring the access request.

Jonathan took a photograph of the message using a separate device.

"Andrew, who knew I was coming here today?"

"Nobody at the airport, as far as I know."

"Check the visitor records. Check any appointment requests associated with my name. Then find out whether anyone accessed my travel reservation."

Andrew began typing.

A knock sounded at the office door.

Both men turned.

"Who is it?" Andrew called.

"Martin Hale. Open the door."

Jonathan did not move.

Andrew looked at him questioningly.

Jonathan gestured toward the computer. "Save the current state."

Andrew completed the export before unlocking the door.

Martin entered wearing a dark security uniform. He was tall, broad-shouldered, and composed, with the practiced expression of someone accustomed to being obeyed. His gaze moved from Andrew to Jonathan, then to the screen.

"What's going on here?" he asked.

Andrew answered carefully.

"We detected an unauthorized executive session and a request to modify access-control permissions."

Martin's eyes narrowed.

"Why wasn't I notified immediately?"

"We were verifying the event before escalating it."

"That is my responsibility. Show me the records."

Jonathan stepped forward.

"Before we do that, I have a question. Did you authorize any emergency authentication tests this morning?"

Martin looked at him for a moment.

"No."

"Did anyone on your team request temporary access to the executive recovery service?"

"No."

"Has a contractor connected any temporary equipment to the operations network this week?"

Martin's expression became defensive.

"I don't see why you're asking me questions as if I'm under investigation."

"Because your department controls the systems involved."

"And who are you to question my department?"

Andrew inhaled sharply.

Martin had apparently not yet connected Jonathan's name with the secure clearance displayed on the screen.

Jonathan took his identification card from his pocket and placed it on the table.

Martin looked down.

His expression changed.

"Mr. Reed."

"Good morning, Mr. Hale."

News in the same category

Airline Agent Tore Passenger's Ticket at Check-In—Then the Airport System Displayed His Clearance

30 Part