scribe

Chapter 26 - AFTER THE DEAL

Project Nightglass closed on a gray Monday morning in March.

There were no champagne bottles in my office.

No victory photographs.

Ardent Microgrid became a Halcyon company at 9:02 a.m., after months of renewed due diligence, regulatory review, independent board oversight, and one final weekend in which forty-seven lawyers discovered new reasons to hate one another.

At 9:07, Priya walked into my office and placed a paper cup on my desk.

"Celebration coffee."

"This tastes exactly like normal coffee."

"Budget cuts."

We looked through the glass at the operations center.

The people working there had rotated credentials, rebuilt vendor access, reviewed millions of authentication events, and answered questions from regulators, auditors, directors, and journalists. Most of them would never appear in a press release.

That felt right.

"How many Redhaven accounts remain?" I asked.

"Zero. Contract terminated. Transition complete."

"Third-party privileged sessions?"

"Hardware-bound, time-limited, recorded."

"Family-background queries?"

Priya gave me a look.

"If anyone searches your mother, an alarm now sounds in three states."

I laughed.

It was the first easy laugh I had had at work in months.

Halcyon's annual meeting came two weeks later.

Shareholders asked angry questions.

They should have.

The company had failed to detect abuse of legitimate vendor access early enough. A vice chairman had exploited governance weaknesses. Sensitive transaction metadata had been exposed. The recovery was not evidence that the original controls had been good.

Helena said so publicly.

So did I.

A reporter asked whether I considered myself vindicated.

"The investigation found no evidence that I participated in the scheme," I said. "But cybersecurity is not a courtroom where personal vindication is the objective. Our responsibility is to reduce the chance that the same failures happen again."

The quote appeared everywhere.

My mother sent me six links.

My father sent one text.

You sounded boring. Proud of you.

I laughed when I read it.

That evening, Helena invited me to her office.

She poured tea and slid a folder across the desk.

"Before you say no, read it."

"That sentence guarantees I want to say no."

The folder described a new enterprise role overseeing information security, operational resilience, third-party risk, and certain governance reforms.

Expanded authority.

Expanded responsibility.

A larger compensation package I did not discuss with Madison.

"Why me?" I asked.

Helena raised an eyebrow.

"Do not become falsely modest now. It doesn't suit you."

"I'm asking about timing."

"Because the board spent six months discovering that cyber risk, vendor risk, and governance risk are not separate planets. You have been saying that for years."

I read the first page again.

"I want Priya promoted."

"Expected."

"Independent reporting for the third-party risk team."

"Already included."

"Board cyber education twice a year. Mandatory."

"You enjoy pain."

"Only educational pain."

Helena smiled.

"Anything else?"

I thought about it.

"No announcement that frames this as a reward for surviving scandal."

Her expression softened.

"Agreed."

I signed the acceptance a week later.

Not because my family would finally understand what I did.

Not because Ethan once said he could outrank me.

I had stopped measuring my life against people who needed a hierarchy to recognize value.

I accepted because the work mattered.

That difference felt like freedom.

The weeks after Nightglass closed were quieter than the months before it, which made certain lessons easier to see.

We had improved technical controls, but the deeper repair was cultural. Executives stopped treating third-party risk as a procurement checkbox. Board members asked different questions. Vendor managers learned that "trusted partner" was not a permanent category but a relationship requiring evidence, limits, and renewal.

I also changed.

Before the case, I believed privacy meant needing very little from other people. Afterward, I understood that secrecy and independence were not the same thing. Priya had challenged me when I wanted control. Leah had protected process when anger tempted shortcuts. Madison had corrected the public record without turning me into a hero. Even my parents, eventually, had learned to ask instead of assume.

Resilience was not the absence of dependence.

It was choosing dependable connections.

When I reviewed the new role Helena offered, that was the idea I kept returning to. I did not want more authority simply to accumulate it. I wanted systems where no single person's authority could become invisible risk.

So I added one last condition to the job description before signing.

My own privileged decisions would receive independent quarterly review.

Helena read the clause and smiled.

"You really don't trust anyone."

"I trust controls."

"Including controls on you?"

"Especially those."

She signed beneath my change.

The new role changed my calendar more than my identity.

I spent fewer mornings inside security operations and more inside rooms where people argued about supply chains, insurance, acquisitions, physical facilities, and regulatory exposure. At first I missed the clarity of incident work. Systems either authenticated or they didn't. Governance lived in sentences such as "material enough" and "reasonable under the circumstances."

Then I realized the same discipline applied.

Define assumptions.

Name owners.

Make exceptions visible.

Plan for failure.

Most organizations did not collapse because no one cared. They collapsed because everyone cared about a narrow piece and assumed someone else owned the gaps.

The Voss scheme had lived in those gaps.

So I built my new team around overlap. Security sat with procurement. Finance sat with operational resilience. Legal sat in vendor-risk reviews before emergencies, not only after them.

Priya accused me of trying to turn the company into one enormous incident-response exercise.

"Only the useful parts," I said.

"You say that now."

We argued, adjusted, and built something better than either of us would have designed alone.

May you like

That became another quiet correction in my life: collaboration was not the opposite of control.

Done well, it was control distributed intelligently.

Related Stories

Other posts