scribe

Chapter 9 - THE VICE CHAIRMAN

Adrian Voss called me before I could call him.

"Claire, we need to contain this."

Not investigate.

Contain.

I was in Priya's office when his name appeared on my screen. I put the call on speaker with Leah present.

"Contain what, Adrian?"

"The reputational damage. Redhaven is a strategic vendor. Your family connection makes this look messy."

"The unauthorized access makes it messy."

"Alleged unauthorized access."

"The access is not alleged. Attribution is unresolved."

He sighed.

Adrian had spent thirty years making irritation sound like wisdom.

"This is exactly why I think you should take a temporary leave."

Priya looked at me.

I kept my voice neutral.

"On what basis?"

"Conflict of interest."

"I recused from fact-finding within hours."

"Public perception is broader than process."

"The public doesn't know about this."

"Yet."

There it was.

A threat disguised as concern.

Leah wrote on a legal pad and pushed it toward me.

DO NOT ENGAGE. ASK WHO ELSE KNOWS.

"Who have you discussed this with?" I asked.

Adrian paused.

"The appropriate board members."

"Names?"

"Claire, I am not going to be cross-examined by my own CISO."

"Then send them to counsel."

He ended the call.

Priya stared at the phone.

"That was subtle."

"For Adrian, it practically was."

Omar entered ten minutes later carrying printed access records.

"We have something."

He laid the pages down.

One of the RHC-7714 searches had targeted Adrian's own spouse.

At first glance, that made Adrian look like a victim.

Then Omar pointed to the timestamp.

"See this?"

3:04 p.m. on August 14.

"Yes."

"At 3:01, Adrian's executive assistant opened a confidential board directory. At 3:06, the vendor account searched the spouse. Same five-minute window."

"Could be coincidence," Priya said.

"Could be. Except it happened four more times with four other names. Internal directory access from Adrian's office immediately before external queries."

Leah leaned back.

"Someone in his office was feeding targets."

"Or Adrian was."

I hated saying it.

Not because I liked him.

Because a compromised vice chairman could reach far deeper than a compromised consultant.

Omar handed me another page.

"There is more. Nightglass metadata searches started twenty minutes after Adrian downloaded the latest acquisition schedule."

Priya swore under her breath.

I looked at the dates.

For weeks, our team had assumed the vendor credential was the breach point.

Now it looked more like a bridge between two compromised sides.

Inside and outside.

My phone buzzed with a text from Madison.

He finally called.

A second message followed.

He says Claire is the one being investigated now.

I read it twice.

Then a third message arrived.

He says your board thinks you leaked Nightglass and used him as cover.

Priya saw my face.

"What?"

I handed her the phone.

She read the messages and looked up.

"How would Ethan know what the board thinks?"

I already knew the answer.

He was still talking to someone inside Halcyon.

Adrian had always treated security as an obstacle that should learn manners.

He was not reckless in the obvious way. He did not email passwords or leave confidential papers on airplanes. His danger was more sophisticated: he believed seniority itself was a control. If he wanted access, he considered the desire evidence of need.

Years earlier, when I rejected his request for permanent administrator rights, he had called Helena and said I lacked "boardroom pragmatism."

Helena told me about it only after approving my decision.

"He thinks friction is disrespect," she had said.

Now, staring at access correlations tied to his office, I wondered whether we had mistaken entitlement for inconvenience.

Priya pulled historical exceptions from the governance system. Adrian's office had requested more emergency overrides than any other director suite. Most were legitimate. Some were merely impatient.

One, however, stood out.

Three months before the unauthorized searches began, Adrian had requested temporary export rights to the board relationship database for a "succession planning exercise." The export included spouse names, adult children, and outside affiliations.

The permission expired after forty-eight hours.

The file created during that window had never been formally attested as destroyed.

"Who approved it?" I asked.

Priya looked uncomfortable.

"Governance Operations. Your team flagged it, but the board office overrode."

"Which board office?"

She turned the screen.

Adrian Voss, Vice Chairman.

A legitimate approval did not prove malicious use.

May you like

But it explained how someone could build a family map without hacking anything at all.

Sometimes the most dangerous access was the access everyone had agreed to.

Related Stories

Other posts