Uncategorized

THE WOMAN HE CALLED A CIVILIAN — UNTIL THE COLONEL REVEALED HER TRUE RANK

Chapter 10

Theme:
Font Size:
24px

The aircraft availability figures were inconsistent with the maintenance summaries she had received the previous evening.

She enlarged the document.

"Daniel, where did these numbers come from?"

"Central readiness database, ma'am."

"Who uploaded them?"

"I'll check."

He began typing.

A moment later, his expression changed.

"Ma'am, the report was uploaded through an external support account."

Evelyn looked at him.

"Which account?"

Daniel hesitated.

"An account previously associated with Ironclad Strategic Solutions."

The room became very quiet.

Evelyn placed the tablet on her desk.

"Don't approve the schedule."

"Yes, ma'am."

"Preserve the report. Notify information security. And do not attempt to modify the original file."

"Understood."

Daniel left immediately.

Evelyn leaned back in her chair.

Ironclad had supposedly been removed from the relevant support assignment months earlier.

Its access credentials had been suspended.

The investigation had concluded that the company had violated several security requirements.

Yet somehow, an account associated with the company had appeared in a new readiness report.

She picked up her phone.

"Colonel Vance's office."

A familiar voice answered.

"Vance."

"Sir, it's Carter."

"Good morning. What's happening?"

"I've found a possible unauthorized access issue involving the readiness database."

His tone changed immediately.

"Explain."

She described the report, the external account, and the discrepancy in the aircraft availability figures.

Vance was silent for several seconds.

"Don't touch anything else. I'll be there in five minutes."


At 6:15 a.m., Colonel Vance entered Evelyn's office with Captain Daniel Brooks from military investigations.

Brooks had handled the airport investigation and was now assigned to the command's security review team.

He placed a laptop on the desk.

"Lieutenant Commander, I need the original report."

Evelyn handed him the tablet.

He examined the file.

"Interesting."

"What?"

"The account wasn't used directly. Someone appears to have routed the upload through a legacy authentication gateway."

Vance frowned.

"Can that happen?"

"Not under the current configuration."

"Then how?"

Brooks looked at Evelyn.

"Someone may have retained access through an older integration system."

Evelyn crossed her arms.

"Which means the account suspension didn't eliminate every possible connection."

"Correct."

Vance moved closer to the screen.

"Can we determine who used it?"

"Not immediately. But we can identify the access path."

Brooks opened another window.

A series of timestamps appeared.

He scrolled through them.

Then stopped.

"Colonel, there's another issue."

"What now?"

"The report contains information that hasn't been officially released to all participating units."

Evelyn leaned forward.

"What information?"

"Aircraft availability projections for the next thirty days."

Vance's expression hardened.

"Those figures are restricted."

"Yes, sir."

Evelyn looked at the document.

The uploaded report had not simply contained inaccurate information.

It contained operational details that could reveal weaknesses in the upcoming deployment schedule.

Someone had deliberately introduced false readiness data into the system.

If the command had approved the report without checking its source, aircraft and personnel could have been allocated incorrectly.

The consequences could have been serious.

"How long has this been happening?" Evelyn asked.

Brooks shook his head.

"We don't know yet."

Vance turned toward him.

"Find out."


By noon, the investigation had expanded.

A cybersecurity team isolated the affected database gateway.

Several accounts were temporarily restricted.

The aviation operations staff were instructed to verify every readiness figure against original maintenance records.

Evelyn spent most of the afternoon coordinating the verification process.

At 2:30 p.m., a young systems specialist named Aaron Mitchell entered her office.

He looked exhausted.

"Ma'am, we found something."

Evelyn looked up.

"Go ahead."

"The external account was accessed from a location associated with a private logistics facility in Virginia."

"Can you identify the user?"

"Not yet. But the authentication request was generated through a device previously registered to Ironclad."

Evelyn stood.

"Is the device still active?"

"Apparently."

"Who owns it?"

Aaron looked at his notes.

"According to the original registration record, the device belonged to Melissa Grant."

Evelyn stared at him.

"Melissa Grant?"

"Yes, ma'am."

She walked toward the window.

Grant had resigned from her regional position after the previous investigation.

Her involvement had been referred to the appropriate authorities.

But the appearance of her device in a new security incident suggested that the matter had not ended.

"Have you notified Colonel Vance?"

"Not yet."

"Do that immediately."

Aaron nodded.

As he turned to leave, Evelyn stopped him.

"One more thing."

"Ma'am?"

"Did you find any evidence that the false readiness figures were actually used?"

"Yes."

Her expression tightened.

"Where?"

"In a draft deployment allocation file."

Evelyn slowly turned around.

"Who prepared it?"

Aaron looked uncomfortable.

"That's the problem, ma'am. It was submitted under your authorization code."

For a moment, Evelyn said nothing.


At 3:05 p.m., Colonel Vance called an emergency meeting.

The room contained representatives from operations, cybersecurity, military investigations, and legal compliance.

Evelyn sat beside Vance.

Captain Brooks displayed the evidence on a large screen.

"The false readiness report was uploaded using a compromised legacy authentication pathway. The resulting data was then copied into a draft deployment allocation file."

He changed the screen.

"The file appears to have been prepared under Lieutenant Commander Carter's authorization credentials."

Several people looked toward Evelyn.

She remained composed.

"Those credentials were never used by me."

Brooks nodded.

"We have no evidence suggesting that you personally accessed or submitted the file."

News in the same category

THE WOMAN HE CALLED A CIVILIAN — UNTIL THE COLONEL REVEALED HER TRUE RANK

15 Part