month, park it where everyone can see, and suddenly they think they’re
Marcus Cole.”
Marcus Cole was the bank’s chief executive and majority shareholder, a
famously hard negotiator whose decisions could move markets. To Andrew,
working at Harrington & Cole felt like standing just outside the gates
of power. He had started confusing proximity to wealth with possession
of it.
While Andrew had been judging watches, Elena had spent the morning
reviewing a security report from a European banking consortium. The $4.8
million draft was the final payment under a licensing agreement for one
of Aegis Protocol’s security systems. The company had earned the money
by solving a problem that much larger institutions had failed to
contain.
Elena had not inherited her success. Fifteen years earlier, she had
founded Aegis in a cramped garage with a refurbished laptop, a
secondhand server, and almost no money. She worked late into the night,
wrote code until her eyes burned, and rejected investors who wanted to
dilute her ownership or weaken the safeguards she was building into the
system.
Her goal was to create an encryption and data-routing architecture that
could recognize hostile access even when an intruder possessed
apparently valid credentials. Most conventional security systems watched
for obvious attacks: repeated failed logins, suspicious locations, or
traffic that exceeded known limits. Elena wanted a system that could
recognize when a legitimate-looking request behaved in a way no
legitimate request should.
She called the core architecture Aegis Lattice.
Three years earlier, a coordinated group of state-sponsored hackers had
begun targeting major financial institutions. Banks suffered data
breaches, trading systems were compromised, and confidential customer
records appeared on criminal markets. Boards of directors searched for a
solution while security vendors offered expensive patches that failed to
address the underlying weaknesses.
Aegis helped several institutions contain the attacks. Its system
identified unusual data routes and isolated compromised credentials
before the intruders could reach protected records. The results drew
attention from regulators, insurers, and bank executives around the
world.
Harrington & Cole had been among the institutions that requested a
demonstration. Marcus Cole wanted an exclusive license, but Elena
refused. She believed a security system protecting customers’ money
should not be locked inside a single bank’s private walls, and she would
not allow a client to override the independent audits she required.
The bank chose a cheaper vendor instead: Palisade Systems.
Elena warned Harrington & Cole that Palisade’s BridgeKey compatibility
module created a dangerous maintenance route. The route could allow a
support account to reach systems that should have been isolated.
Palisade insisted the feature was necessary for older infrastructure,
and Harrington & Cole’s technology division accepted the explanation.
Elena documented her concerns and withdrew from the negotiation.
She did not forget the decision, but she moved on. Aegis grew, its
clients expanded, and the company remained independent. Harrington &
Cole continued using Palisade’s software.
Then, two days before Elena’s visit, the bank’s security director sent
her a short, urgent message.
The bank had detected unusual activity inside its transaction network.
Its security team could not determine whether the activity was a failed
test, an internal configuration error, or the beginning of a breach. The
message asked Elena to attend a confidential meeting with Marcus Cole
and the bank’s executive team at ten-thirty that morning.
Elena agreed to come, but she set a condition: no one would ask her to
approve a system she had not been allowed to inspect, and no one would
ask her to conceal a problem from regulators or customers.
She had arrived early to deposit the consortium’s payment before the
meeting. She expected the transaction to take a few minutes, followed by
a difficult technical discussion upstairs.
She had not expected to be laughed at before she could even present her
identification.
------------------------------------------------------------------------
The branch manager, Olivia Grant, arrived at Counter Seven less than
three minutes after Andrew’s call. She was in her early fifties, with a
measured manner and the habit of listening before speaking. She glanced
at the check, the legal folder, and Elena’s face, then recognized the
name on the corporate documents.
“Ms. Brooks,” Olivia said, stepping around the counter. “I’m sorry
you’ve had to wait. We were expecting you upstairs.”
Andrew looked between them. “You know her?”
Olivia gave him a brief, unmistakably disapproving glance. “Yes, Andrew.
Ms. Brooks is the founder and chief executive of Aegis Protocol. She has
an appointment with Mr. Cole.”
Andrew stood so quickly that his chair rolled backward and struck the
cabinet behind him.
Elena closed the folder. “I don’t need special treatment, Ms. Grant. I
need the same professional handling any customer should receive.”
“Of course,” Olivia said. “And you should have received it from the
beginning.”
Andrew opened his mouth, but no apology came out. He was still trying to
understand how the woman he had dismissed as a suspicious walk-in had an
appointment with the chief executive.
Before Olivia could escort Elena upstairs, the phone at the manager’s
station rang. She answered, listened, and became very still.
“Understood,” she said. “I’ll bring her immediately.”
She replaced the receiver and looked at Elena.
“The executive team has escalated the security incident. Mr. Cole needs
you now.”
Elena picked up her folder. “Then let’s go.”
As she turned away, Andrew finally found his voice.
“Ms. Brooks, I—”
She looked back.
“I’m sorry,” he said, but the words came out thin and unfinished.
“I heard what you said to me,” Elena replied. “I’ll decide what I think
of your apology after I see what you do next.”
Then she followed Olivia through the private corridor.
------------------------------------------------------------------------
The executive floor was quieter than the lobby, but the atmosphere was
anything but calm. Assistants moved quickly between glass-walled
offices, security staff spoke into earpieces, and several senior
executives stood around a monitor displaying a map of the bank’s
internal network.
Marcus Cole waited in the boardroom with the chief technology officer,
Victor Hale, and the head of information security, Martin Vale. At
sixty-three, Cole had silver hair, a precise voice, and the reputation
of a man who rarely admitted uncertainty. That morning, however, his
usual composure had begun to crack.
“Elena,” he said as she entered. “Thank you for coming.”
“You said the network was behaving strangely. Tell me exactly what
happened.”
Victor Hale took over. At 6:40 a.m., the bank’s monitoring system had
detected unusual traffic from a maintenance account associated with
Palisade Systems. The account was supposed to be dormant except during
scheduled service windows, but it had initiated several connections to
transaction-processing systems before dawn.
At first, the security team had treated the activity as a configuration
problem. Then a batch of outbound instructions appeared in a settlement
queue, and the team discovered that a portion of the bank’s audit logs