THE BOARDROOM TRAP
By Monday morning, Secure Core Systems had become the center of a crisis its executives could no longer control.
The banking outage had been contained.
Customer transactions were being reconciled.
Financial losses were still being calculated.
But the security investigation had uncovered enough irregularities to trigger urgent questions about privileged access and vendor oversight.
I arrived at Manhattan Trust shortly after seven.
Daniel met me in the lobby.
He looked even more exhausted than he had on Saturday.
“We have a problem,” he said.
“What kind?”
“Secure Core wants an emergency executive meeting.”
I stopped walking.
“With whom?”
“Richard Halston, our legal department, and the heads of technology.”
“About the outage?”
“Officially.”
“And unofficially?”
Daniel handed me a printed email.
Secure Core had accused me of misappropriating confidential technical information and interfering with its contractual relationships.
The letter demanded that Manhattan Trust terminate my consulting agreement.
It also threatened legal action if the bank continued using my services.
I read it twice.
Then laughed quietly.
Daniel raised an eyebrow.
“Something funny?”
“They fired me while I was responding to an emergency.”
“Then they admitted they couldn't provide a replacement.”
“Then the bank hired me under the emergency provisions.”
“And now they're accusing me of interfering with their business.”
Daniel shrugged.
“Corporate lawyers can be very creative.”
We entered the elevator.
“There's more,” he said.
“What?”
“Howard is attending the meeting.”
I stared at him.
“Personally?”
“Yes.”
“Interesting.”
“Gerald Thompson too.”
I looked toward the rising floor numbers.
For twenty-four years, Howard and Gerald had held all the power in our professional relationship.
They controlled promotions.
Assignments.
Salary increases.
Performance reviews.
They decided who received recognition and who stayed invisible.
Now they were coming into a building where I was an authorized independent consultant.
And where their own company's conduct was under investigation.
I wondered whether either man understood how completely the situation had changed.
At 9:30 a.m., the boardroom doors opened.
Howard Bennett entered first.
He wore a tailored navy suit and an expression of practiced confidence.
Gerald followed him.
Two attorneys walked behind them.
Howard saw me sitting beside Daniel.
His expression changed immediately.
“Carl.”
“Howard.”
He looked toward the bank's executives.
“I wasn't aware he would be participating.”
Richard Halston folded his hands.
“Mr. Rodriguez is our technical adviser.”
Howard's jaw tightened.
Gerald sat down without speaking.
Their lead attorney began the meeting.
She argued that Secure Core retained contractual rights over the banking software and that my independent engagement threatened proprietary information.
Richard listened politely.
Then asked a simple question.
“Can Secure Core currently provide a qualified engineer to support these legacy systems?”
Gerald cleared his throat.
“We are actively evaluating staffing solutions.”
“That wasn't my question.”
“We expect to have a plan shortly.”
Richard nodded.
“Then I understand your answer is no.”
Howard leaned forward.
“Our company has supported this institution for decades.”
Richard's expression remained calm.
“And Mr. Rodriguez has apparently performed much of that support personally.”
Howard looked at me.
“Carl has been a valued member of our team.”
I almost laughed.
A valued member.
Three days earlier, he had fired me without asking what I was working on.
Now I was suddenly valuable again.
Richard opened another folder.
“Let's discuss the emergency response.”
He summarized Secure Core's failure to provide a timely replacement.
Then he turned toward me.
“Carl, did Secure Core authorize you to continue working after your termination?”
“No.”
“Did you complete additional technical work for Secure Core after receiving that termination?”
“No.”
“Did Manhattan Trust independently authorize your subsequent consulting work?”
“Yes.”
Richard turned back to the attorneys.
“Our position is straightforward.”
He paused.
“We will not allow a service provider to compromise our recovery efforts because of its own staffing decisions.”
Howard's face reddened.
“You're oversimplifying this.”
Richard raised one finger.
“I'm not finished.”
The room became silent.
Richard looked toward Daniel.
“Please explain the security findings.”
Daniel opened his laptop.
He displayed a timeline.
The maintenance interface.
The dormant administrator credential.
The reactivation record.
The attack.
Then Howard's termination call.
Howard stared at the screen.
His face changed.
Not dramatically.
But enough.
I had known him for twenty-four years.
I recognized the precise moment when confidence turned into fear.
Daniel spoke carefully.
“We have preserved records indicating that privileged access associated with a retired administrator account was reactivated shortly before the incident.”
He looked toward Howard.
“The authorization record identifies your administrative account.”
Howard shook his head.
“That's impossible.”
Daniel continued.
“We are not suggesting that the record alone establishes responsibility.”
“But we need an explanation.”
Howard turned toward Gerald.
For a fraction of a second, Gerald's expression hardened.
Then Howard looked back at the screen.
“My account could have been compromised.”
Daniel nodded.
“That's one possibility.”
“Then why am I being questioned?”
“Because your account appears in the record.”
Howard leaned backward.
Gerald finally spoke.
“We should move this discussion into a privileged legal setting.”
Richard nodded.
“Our counsel will coordinate appropriately.”
The meeting might have ended there.
But Howard made a mistake.
He turned toward me.
And smiled.
A cold, unpleasant smile.
“Carl, you've always been a talented technician.”
I said nothing.
“But business decisions require a broader perspective.”
I waited.
“You may have misunderstood the reasons for your termination.”
Something inside me finally shifted.
For twenty-four years, I'd swallowed comments like that.
I'd nodded.
Accepted.
Moved on.
Not this time.
“Howard,” I said quietly.
“Did you know I was responding to a major banking emergency when you fired me?”
He hesitated.
“That's not relevant.”
“Did you know?”
Gerald looked at him.
Howard's eyes narrowed.
“No.”
“Did you review my active assignment before terminating my employment?”
Silence.
“Did you arrange for a qualified replacement?”
Howard's face reddened.
“Carl, this isn't a performance review.”
“No,” I replied.
“It isn't.”
I leaned forward.
“It's a discussion about the consequences of decisions made without understanding the systems your company was responsible for protecting.”
Nobody spoke.
Then Richard closed his folder.
“I believe we have enough for today.”
Howard stood abruptly.
Gerald followed.
The attorneys began gathering their documents.
But as Howard reached the door, he turned toward me.
His expression was no longer confident.
It was angry.
“You think you've won?”
I looked at him.
“I wasn't aware we were competing.”
He stepped closer.
“Be careful, Carl.”
Daniel immediately stood.
Richard's voice became sharp.
“Mr. Bennett.”
Howard stopped.
Then left without another word.
I watched the door close.
For a moment, I felt satisfied.
But the feeling disappeared when Daniel approached me.
“We need to talk.”
“What happened?”
He lowered his voice.
“The investigators confirmed something about Martin Voss.”
My stomach tightened.
“What?”
“His supposed death was never properly documented in the records we've checked.”
I stared at him.
Daniel continued.
“And we found another connection.”
He handed me a document.
It listed a private technology investment company.
Blackstone Meridian Holdings.
The name meant nothing to me.
Until I saw the second page.
The company had acquired a substantial ownership interest in Secure Core Systems shortly before Martin's disappearance.
I looked at Daniel.
“Who owns it?”
He shook his head.
“That's what we're trying to determine.”
Then he pointed toward a highlighted transaction.
“Carl, someone connected to that company transferred twelve million dollars into an offshore entity two days before the banking attack.”
I felt my chest tighten.
Daniel lowered his voice.
“And the transfer authorization used a legacy processing signature associated with your original software.”
I stared at the page.
“That's impossible.”
“Why?”
“Because that signature was retired years ago.”
Daniel watched me.
Then asked the question that transformed an employment dispute into something much darker.
“Who besides you would know how to recreate it?”