The contract was signed. The champagne was poured. Then someone read Appendix C — and Meridian Group had 30 days to prove a security posture they’d never documented.
There are two kinds of good news in business.
The first kind arrives and simply is what it is: a deal closes, a milestone hits, a number beats plan. You celebrate, you move on.
The second kind arrives with an appendix.
In April, Meridian Group signed the largest client contract in company history — a multi-year agreement with a national healthcare services organization that Xavier had been pursuing, in one form or another, since his second month at the company. The sales effort had taken months. The negotiation had taken weeks. The legal review had taken longer than anyone expected.
The celebration in the office on signing day was genuine and well-earned. Renata gave a short speech. Sandra opened the good sparkling wine instead of the regular sparkling wine, which at Meridian was a meaningful distinction.
It was Renata, two days later, who walked into Xavier’s office holding a printed copy of the contract with a sticky note on page 47.
“We may have a situation,” she said.
Xavier had learned by now that when Renata used that phrase, she meant it literally.
Appendix C
Buried in the contract’s security requirements — Appendix C, Section 4, a paragraph that had survived three rounds of legal review without anyone at Meridian fully absorbing its implications — was a condition of the engagement:
Contractor shall maintain and demonstrate compliance with SOC 2 security criteria, with documentation of readiness to be provided within thirty (30) days of execution.
SOC 2.
Xavier had heard the term. He knew, in the general way most executives know it, that it was some kind of security framework — something that lived in the world of auditors and control matrices and things that big companies had and smaller companies didn’t worry about.
Meridian had never been through a SOC 2 audit. Meridian had never formally documented its security controls. Meridian had, until eleven months ago, been a company where the entire security posture could be summarized as: we hope for the best.
The healthcare client — being in healthcare, being subject to its own regulatory universe, being a large organization with vendor risk management requirements — needed assurance that Meridian’s environment met a recognized security standard. And they needed the documentation in thirty days.
Xavier read the paragraph twice, then called Xpert.
“Hypothetically,” he said, “how hard is SOC 2?”
What SOC 2 Actually Is
The Xpert team’s answer was more encouraging than Xavier expected — but not immediately.
SOC 2, they explained, is an auditing framework built around what are called the Trust Services Criteria — security, availability, processing integrity, confidentiality, and privacy. For Meridian’s purposes, the relevant scope was SOC 2 Type 1: an audit of the design of their security controls at a point in time, as opposed to Type 2, which examines operating effectiveness over a period of months.
The framework itself wasn’t exotic. It asked reasonable questions: Do you have access controls? Is data encrypted? Do you have an incident response plan? Are employees trained on security? Are backups tested? Is vendor access managed? Are changes to systems documented?
Here’s what Xavier realized, as the Xpert team walked him through the criteria one by one: Meridian could answer yes to almost every question.
Not because Meridian had set out to build a compliant environment. But because over the past eleven months, in response to a series of incidents that had felt, at the time, like one crisis after another, they had built one anyway.
- Access controls and least privilege? Implemented after the vendor access audit.
- MFA and credential management? Deployed after the password incident.
- Endpoint protection and device encryption? In place after the laptop at Gate B14.
- Incident response? Proven, documented, and battle-tested at 2:14 AM.
- Backup and recovery? Rebuilt, verified, and demonstrated during the ransomware event.
- Employee security training? Rolled out with the phishing awareness program.
- Vendor access management? Formalized with a register and lifecycle process.
- Offboarding and access revocation? Automated after the HR-IT integration.
- Communication and data governance? Established after Eleanor’s boardroom question.
Every incident in Meridian’s recent history — every uncomfortable phone call, every late-night alert, every audit that found something nobody wanted to find — had left behind a control, a process, or a piece of infrastructure. None of it had been built for compliance. All of it, it turned out, counted.
What Meridian didn’t have was the paperwork. The controls existed. The documentation of the controls did not. And an audit, as the Xpert team gently explained, cannot audit what has not been written down.
The Thirty Days
What followed was the most intense month of Xavier’s tenure — busier than the ransomware week, in its own way, because this one had a countdown attached from the start.
Xpert ran the engagement like a project, because it was one:
Week one: Readiness assessment. Xpert performed a gap analysis against the SOC 2 criteria — mapping every required control to Meridian’s actual environment, identifying what existed, what was documented, and what was missing. The findings were better than anyone had expected: the technical controls were largely in place. The gaps were almost entirely documentary — policies that existed in practice but had never been written, processes that were followed but never formalized, and a handful of smaller technical items.
Week two: Documentation. This was the heavy lift. Xpert’s team drafted the formal policy set — information security policy, access control policy, incident response plan, change management procedure, business continuity plan, vendor management policy, acceptable use policy. Each one was a written version of something Meridian was already doing. Each one went through review with Xavier, Sandra, and legal to confirm it reflected reality rather than aspiration. “A policy that describes what you actually do,” the Xpert lead explained, “is worth ten that describe what you wish you did.”
Week three: Closing the technical gaps. The remaining items were small but necessary — a formal asset inventory, a documented patching cadence, a couple of configuration standards, and a logging retention adjustment. Xpert handled the technical work directly. The asset inventory, in particular, was the kind of unglamorous foundational item that auditors care about deeply and companies never build voluntarily.
Week four: Evidence and audit support. Xpert coordinated with the external auditing firm engaged for the assessment, served as the primary point of contact for evidence requests, and sat in on the audit interviews alongside Meridian’s team. When the auditor asked how incident response worked, the answer wasn’t a policy document — it was the ransomware timeline, with timestamps.
On day twenty-nine, the audit was complete.
Meridian passed.
The Debrief
Xavier got the formal report on a Friday afternoon. He read it at his desk, then walked down the hall to Sandra’s office and set it on her desk without a word.
She read the summary, looked up, and said: “So the champagne was justified after all.”
“Justified twice,” Xavier said.
Later that week, in the debrief with the Xpert team, Xavier asked the question that had been sitting with him since the readiness assessment: “If we’d gotten this contract a year ago — before you were here — what would have happened?”
The Xpert lead didn’t sugarcoat it. “You’d have had the controls for maybe a third of the criteria, no documentation for any of it, and thirty days to build both. Some companies in that position lose the contract. Some sign a remediation extension and spend six months and a lot of money catching up. And some discover, mid-audit, that their environment doesn’t match what they thought it was.”
Xavier nodded slowly.
“And instead?”
“Instead, you spent a year fixing things one incident at a time, and the audit was mostly a matter of writing down what you’d already done.”
The Point Nobody Makes About Compliance
Compliance has a reputation problem. In most companies, it’s experienced as an imposition — a bureaucratic hurdle, a cost center, a checklist that exists because someone somewhere requires it. Something you do after the real work, when a client or a regulator forces your hand.
Xavier had thought about it that way too, before April.
What the SOC 2 process actually revealed was something different: compliance done right isn’t a project you start when a contract demands it. It’s the natural byproduct of running your technology environment properly over time. Every control the auditor asked about, Meridian already had — not because anyone had set out to become compliant, but because every incident of the past year had ended with Xpert asking the same question: how do we make sure this never happens again?
Answer that question enough times, across enough incidents, and eventually you have a security posture. Write it down, and you have compliance.
If a major client dropped a 30-day compliance requirement on your desk tomorrow morning — could your company pass?
For most growing businesses, the honest answer depends less on what they’ve built than on whether anyone wrote it down. And the gap between “we’re probably fine” and “we can prove it” is exactly the gap that costs companies contracts.
Meridian closed it in thirty days because they’d spent a year earning the right to.
Coming up in the next installment of The Xavier Chronicles: A major client proposal goes out with last quarter’s pricing, the wrong company name, and two sections that contradict each other. Five people edited five versions of the same file — and nobody was working on the real one.
Meridian Group is a fictional company. SOC 2 readiness is increasingly a hard requirement for mid-sized businesses selling into healthcare, finance, and enterprise markets — and companies that build security properly over time find audits dramatically easier than those that scramble to comply on a deadline. Xpert Technologies helps growing companies in Metro Detroit build security environments that are audit-ready because they’re genuinely secure — not the other way around.
Could you pass a compliance audit next month? If your answer is anything but a resounding, “Yes”, let’s chat.
#SOC2 #Compliance #CyberSecurity #AuditReadiness #RiskManagement #MetroDetroit #XpertTechnologies