GTM Academy Sales Kit is Here!

Access the Kit

Transform Cybersecurity Sales with the Cynomi GTM Academy

Jenny-Passmore
Jenny Passmore Publication date: 31 March, 2026
Education
Common CMMC Compliance Challenges and How to Overcome Them

Bridging the Go-to-Market Gap 

The managed security services market is projected to grow from $38.31 billion in 2025 to $69.16 billion by 20301, and cybersecurity remains the fastest-growing segment of MSP services2. However, many providers are leaving significant revenue on the table because their go-to-market strategy doesn’t connect with how business leaders make decisions. 

Technical teams focus on frameworks and vulnerabilities, while business decision-makers invest in outcomes: risk reduction, successful compliance audits, and business continuity. When sales and marketing messaging fails to bridge that gap, prospects see cybersecurity as a cost center rather than a strategic priority, and deals stall. 

The structural challenges compound the problem. 77% of MSPs cite a lack of client urgency as a major sales challenge3, while 66% of SMBs identify cost as their top obstacle to adopting stronger security4. Buying decisions now involve multiple stakeholders across functions, including executives, finance, IT, and operational leaders, making alignment and clarity essential to every deal. 

The providers winning in this market have built the go-to-market discipline that matches the quality of their service delivery. Consistent execution across selling, pricing, packaging, and marketing is what converts rising market demand into scalable revenue. 

Introducing the Go-to-Market Academy 

MSP growth starts with go-to-market excellence. That’s why we created the Cynomi Go-to-Market (GTM) Academy, an enablement program designed to help MSPs and MSSPs bring cybersecurity services to market and build profitable revenue streams. 

The GTM Academy focuses on the practical side of selling, proving value, packaging, pricing, and marketing security services. It delivers operator-led training through modular kits covering the entire go-to-market lifecycle, drawing on experience from Cynomi’s leadership, trusted partners, and seasoned industry veterans. Each module is built to give you something you can use right away. 

Inside the kits, you’ll find: 

  • Guides and playbooks to provide quick-reference content that sharpens your knowledge 
  • On-demand workshops to deliver in-depth strategies from industry leaders 
  • Video series to feature short, tactical sessions covering the full go-to-market cycle 
  • Hands-on tools and templates to streamline your processes and put strategies into immediate practice 

Every resource reflects how experienced MSP operators actually think and sell, so the learning curve is short and the impact is immediate. 

The GTM Academy Sales Kit 

The first module we’ve released, The Complete Sales Kit, provides the foundation for confidently selling cybersecurity and compliance services. It helps your team close more deals and build a repeatable sales engine by covering every critical stage of the sales lifecycle. 

The Sales Kit spans guides, cheat sheets, templates, worksheets, and training videos organized around five core areas: 

  • Client targeting and engagement: Define your ideal client profile with the ICP Strategic Framework and leverage scripts and email templates to position cybersecurity as a growth driver. 
  • Revenue growth and relationship-building: Use the Upselling and Cross-Selling Guide and Getting to YES: The Anti-Sales Guide to expand existing accounts and strengthen client trust. 
  • Objection handling and deal qualification: Overcome common objections and prioritize your highest-value deals with cheat sheets and scoring worksheets focused on business impact and ROI. 
  • Sales process and pipeline optimization: Assess and improve your qualification discipline and pipeline health to build a predictable, scalable revenue engine. 
  • Sales leadership: Build a high-performing team with practical guidance on hiring, compensation, CRM best practices, and communication. 

When your team works from a shared set of tools and frameworks, execution becomes more consistent across every rep, call, and deal. Sales cycles shorten, objection handling improves, and new team members ramp faster because the playbook exists. The Complete Sales Kit gives you that foundation, built by cybersecurity leaders and experienced GTM practitioners who’ve applied these frameworks in the field. 

Go From Vendor to Strategic Advisor 

Refining your go-to-market strategy impacts more than your win rate. When your messaging aligns with actual business outcomes, client relationships shift, and you become the advisor guiding their strategy rather than the vendor pitching another tool. The GTM Academy’s frameworks give you a clear way to articulate the financial and reputational risks of inaction, helping clients make faster, better-informed decisions.  

The practices that win deals are the same ones that ensure clients adopt the protections they actually need. Your growth and their security move together. 

Join the Academy and Download the Sales Kit 

Cybersecurity growth doesn’t happen by accident. Building a profitable, scalable practice requires a deliberate approach to how you package, price, and sell your services.  

Download the GTM Academy Sales Kit to put proven sales strategies into immediate action. With a systematic sales motion, winning more deals becomes a matter of process and predictability, not luck. 

——- 

[1] Fortune Business Insights. (2024). Cyber security managed services market size, share & industry analysis. 
[2] Channel Futures. (2024). Cybersecurity dominates the 2024 MSP 501. 
[3] Infrascale. (2025). MSPs selling more cybersecurity: Statistics and trends in the U.S. 
[4] CrowdStrike. (2025). SMB cybersecurity study. 

The 30 Percent Rule: Balancing the Emotion and Math of Cybersecurity Sales

David-Primor
David Primor Publication date: 31 March, 2026
Education

Selling within the managed services industry relies heavily on relationships. The entire ecosystem functions on a foundation of trust built over years of successful service delivery. When an executive hands over the keys to their business infrastructure, they are making a deeply personal and emotional decision. 

When I started selling as a technical founder, I leaned entirely into that belief. I assumed that if I built enough trust, explained the vision clearly, and demonstrated my technical credibility, the deal would naturally close. I quickly realized that I was missing a fundamental piece of the growth equation. 

Sales is emotional and relational. But it’s also mathmatical. Understanding the balance between those two forces dictates whether your business scales predictably or stalls completely. 

The Statistical Reality of Close Rates 

Before launching Cynomi, I worked on a sophisticated privacy platform. My team had built strong technical capabilities and secured validation from highly respected investors. Through our network, we secured an introduction to a CISO at a massive enterprise organization. 

During the pitch, the executive stopped me and stated plainly that he did not think the idea was strong. 

I paused the entire operation mentally. I interpreted one strong rejection from a credible source as a final verdict on the product. Looking back at that moment with more experience, I realize I completely misunderstood sales statistics. 

Even when you possess strong product-market fit and a compelling value proposition, a healthy close rate typically hovers between 20–40%. That means 60–80% of highly qualified opportunities will not convert into paying customers. 

When a prospect declines your proposal, it does not mean your core idea is wrong. It does not mean your market positioning is broken, and it certainly does not mean your team is incapable. It simply means you are operating inside standard statistical reality. 

Moving Away from Binary Thinking 

Technical founders and engineering leaders often struggle with this statistical reality because we are trained to think in binary terms. In intelligence and government work, a solution either works or it fails. 

Sales operates entirely differently. 

You can be completely right about the prospect’s underlying business problem. You can propose the exact right solution to fix their vulnerabilities. You can approach them at the correct time in their buying cycle. Even with all those elements aligned perfectly, you will still hear the word “no” most of the time. 

When we started building the Cynomi Security Growth Platform, we initially targeted small and medium businesses directly. The operational pain was obvious in the market. These businesses were actively being attacked, they lacked internal cybersecurity leadership, and they understood their financial risk. 

Despite understanding the problem, many of those direct prospects gave us a highly specific response. They told us they needed to talk to their managed service provider before making a decision. 

A less experienced founder might have viewed that hesitation as a rejection of the platform. We recognized it as a massive market insight. If I had treated every delay as a failure, we would not have pivoted correctly. We would have missed the opportunity to empower partners with CISO Intelligence. 

Separating Emotional Experience from Data 

Relationships matter deeply when you attempt to grow your service catalog. You cannot sell complex security program management without earning the absolute trust of the client’s leadership team. However, trust does not override the fundamental statistics of business growth. 

You can build incredibly strong relationships and still maintain a 30% close rate. That conversion metric does not represent a failure of your advisory skills. It represents the structural reality of business-to-business sales. 

For founders launching a new cybersecurity package or compliance service, understanding this dynamic prevents burnout. You must separate the emotional weight of a rejected proposal from the mathematical reality of your pipeline. When you stop viewing a lost deal as a personal failure, you gain the clarity required to build scalable operational systems. 

A Practical Blueprint for Pipeline Management 

You can transition from relying purely on founder-led relationships to managing a predictable sales machine by implementing a few structural changes. Based on my experience scaling technology platforms, I recommend standardizing your approach across three specific areas. 

Target volume over comfort 

Many service providers start selling a new offering by pitching it to their friendliest clients. While this provides good early practice, it creates a false sense of your actual market conversion rate. You must step outside of your comfort zone and speak to at least 20 to 30 real prospects that match your ideal client profile (ICP). Reaching a statistically significant number of prospects allows you to see how the broader market truly reacts to your pricing and packaging. 

Track patterns instead of opinions 

When you pitch a new service to 10 qualified prospects, you should expect seven of them to decline. If seven out of 10 say no, your business is perfectly healthy. The critical data lies in why they declined. If seven out of 10 prospects raise the exact same objection regarding your implementation timeline, you have discovered a structural flaw in your offering. You can adjust your delivery model to address that specific pattern. 

Reverse engineer your revenue goals 

Hope is not a reliable sales strategy. If you know your team closes deals at a 30% rate, you must build your pipeline based on that exact math. If you need to secure three new security contracts this quarter to hit your growth targets, you must generate at least 10 highly qualified opportunities. Do not expect an unrealistic 70% conversion rate simply because you believe strongly in the value of your services. Let the math dictate your marketing spend and prospecting efforts. 

Sustaining Growth Through Disciplined Systems 

Sales in the managed services ecosystem should absolutely remain personal. The ability to form lasting, strategic relationships represents the greatest strength of this community. 

You just cannot let the emotional weight of a lost deal distract you from the mathematics of sustainable growth. The organizations that scale successfully are the ones managed by leaders who understand both the human element and the statistical requirements. 

Mastering this balance takes deliberate focus and the right operational frameworks. We have organized the most effective strategies to help you build a predictable revenue engine without losing the personal touch your clients expect. 

Download the GTM Academy Sales Kit to access the precise pipeline tracking tools, objection handling guides, and discovery templates you need to standardize your sales motion and accelerate your growth today.

Stop Selling Security and Start Advising the Business

tim coach
Tim Coach Publication date: 29 March, 2026
Education

Early in my career, I learned a difficult lesson: the key to selling cybersecurity is to advise the business, not just sell security tools. I discovered this the hard way by leading with the wrong information in too many meetings. 

I would show up to a prospect meeting excited about a new solution, a new control, or a new compliance requirement. I had the features lined up, the specifications memorized, and the value proposition polished. Almost immediately, I could feel the energy in the room shift. The client leaned back and disengaged. 

When you lead with the tool, the prospect’s gut reaction is to ask, “How much is this going to cost me?”  

That dynamic represents a fundamental sales problem. 

The Top Mistake Most Service Providers Make 

Many service providers blur the lines between marketing and sales. Marketing warms the room and generates initial interest. Sales earns the signature and secures the long-term partnership. Pitching a new security feature falls short of actual selling. 

Walking into a room and talking about your technology stack sets you up for failure. Your client does not care about the intricacies of your endpoint detection and response software, your updated firewall, or your newly designed dashboard. They view your technology as a basic utility. They expect the system to work smoothly, and they expect you to fix things rapidly when they break. 

Those baseline expectations do not drive major purchasing decisions. Any conversation that fails to connect directly to their core business operations simply creates distracting noise. 

Buyers Care About Value Over Tools 

People buy based on value, regardless of whether they are purchasing a physical product or a complex cybersecurity platform. Technical specifications do not create value. Value stems from emotional and operational impact. 

Everything changed for me when I finally understood how business owners actually think. Every executive evaluates decisions through three specific buckets: revenue, cost, and risk. 

If you fail to explain a security recommendation within the context of those three buckets, you lack a compelling business case. A recommendation outside of those parameters functions as a mere suggestion. Suggestions rarely close enterprise deals. 

When you sit down with a manufacturing executive, they care about keeping their production lines running to fulfill orders. If you propose a new security control, you must explain how that control prevents a line shutdown that would cost them thousands of dollars per hour. Connecting the technology to their revenue flow transforms your pitch into a critical business investment. 

The Advisory Move That Changes the Conversation 

The major shift in my own sales performance happened when I stopped acting like a standard vendor and started acting like a CIO. I abandoned the standard pitch deck and focused entirely on learning their business mechanics. 

Instead of presenting features, I asked executives to explain what was changing in their business that quarter. I asked them to outline their growth targets, identify their operational bottlenecks, and highlight areas where they felt financially exposed. 

Operating without any product talk or pricing discussions completely changes the posture of the meeting. When you lead with strategic advisory, the sales conversation naturally comes to you. The executive will eventually ask what it would cost to fix their exposed areas. You are no longer pushing a generic service onto a skeptical buyer. You are actively responding to an articulated business need. 

Selling the Way Your Clients Want to Buy 

Earlier in my career, I would steamroll through client conversations because I mistakenly believed that sheer confidence closed deals. Over time, the market taught me a much more valuable lesson about human psychology and decision-making. 

You must sell the way your client prefers to buy. 

Some executives require extensive data to feel comfortable moving forward. Some leaders need to view the situation through a strict risk management framework. Others demand detailed financial projections to justify the investment. Every single one of them requires absolute clarity on how your services impact their revenue, cost, and risk. 

Translating technical zeros and ones into plain business language removes the friction from the sales process. Make the conversation accessible, focus on the outcomes they care about, and demonstrate how your partnership protects their financial interests. 

A Practical Adjustment for Your Next Meeting 

You can fundamentally restructure your sales approach before your next client meeting. Leave the technical diagrams and software demonstrations for later in the engagement. 

Start the conversation by focusing on their business foundation. 

  • Identify what specific assets are at risk within the business
  • Discuss what operational changes the company is currently navigating 
  • Connect security directly to their revenue generation and cost management 

You will find the tone of the room changes immediately when you implement this structure. Executives will lean into the conversation because you are speaking their language and prioritizing their concerns. Lead with advisory, and the sales will naturally follow. 

We have always been in the business of selling trust and capability. Just ensure you are selling the outcomes that actually matter to your clients. 

If you want to equip your team with the right frameworks to consistently execute this advisory approach, we have organized the most effective resources in one place. Check out our GTM Academy Sales Kit to access the practical tools you need to elevate your client conversations and close more strategic deals. 

See you out on the road, 
Coach

How to Build a High-Performing MSP Sales Culture

Shane Deegan b&w
Shane Deegan Publication date: 28 March, 2026
Education

I’m going to say something that’ll upset a few people: most “sales culture” talk is just vibes with a nice hoodie. And listen, I am big on energy. I love momentum. But when you’re trying to build something that scales, “good vibes” won’t save you. 

A high-performing sales culture should have enforced expectations.  

It’s what you measure. 
It’s what you tolerate. 
It’s what you call out. 
It’s what you repeat until it becomes normal. 

When I joined ThreatLocker, I was employee number 30. By the time I left, my sales organization alone was around 250 people. What worked at 10 reps doesn’t work at 100 unless you build the right foundation from day one. 

What a Strong Sales Culture Looks Like 

Culture is clarity. Your reps should know: 

  • What good looks like: Meeting baseline expectations consistently. Your team hits their call counts, creates a predictable number of new deals, and maintains stable sit ratios and close rates. 
  • What great looks like: Exceeding expectations through proactive, strategic action. Call counts translate directly to a higher volume of new deals, sit ratios and close rates improve month-over-month, and the team actively identifies high-value expansion opportunities. 
  • What unacceptable looks like: Falling short of defined standards. Call counts are missed, deal creation is inconsistent, sit ratios decline, and expansion opportunities are overlooked without a clear plan for remediation. 

A successful sales culture should review pipeline on a weekly basis to dissect what’s real from what’s fantasy. Because salespeople are optimistic by nature, some over-project out of fear or under-project because they’ve been burned before. Your job as a leader isn’t to yell louder but to make the truth visible. 

Activity Creates Opportunity 

The smoothest talker in the room doesn’t always win. The hardest worker often does. 

That’s because activity creates looks, looks creates conversations, and conversations create new service engagements. 

When your service pipeline starts to dry up, it’s easy to assume you have a talent problem. But it’s rarely a talent issue. It’s almost always an activity issue. Consistent, purposeful action is the engine of any successful service-based business. It’s the daily work of reaching out, following up, and assessing client and prospect needs that keeps the pipeline full and the business moving forward. Without that steady drumbeat of activity, even the most skilled team will struggle to find opportunities. 

The Scalable Culture Checklist 

Building a sales team that scales effectively requires more than hiring the right people. It demands processes, culture, and standards that drive sustainable revenue growth.  

Here are key principles for building a high-performing, scalable sales team in your MSP: 

  • Review your sales pipeline weekly, not monthly: A weekly review keeps your team agile and proactive. Waiting a full month to assess the pipeline leads to missed opportunities and reactive selling. Weekly check-ins allow you to adapt your strategy and forecast more accurately. 
  • Remove ambiguity in key performance indicators (KPIs): Clear, measurable KPIs are essential for sales alignment and accountability. When your team knows exactly what success looks like, from lead generation to closed deals, they can focus on the metrics that grow the business. 
  • Align compensation with sustainable client outcomes: Reward your sales team for securing profitable, long-term contracts, not just for the volume of deals closed. Incentivizing high-value, quality partnerships ensures your sales efforts contribute directly to sustainable business growth. 
  • Kill the “not my job” mentality immediately: Teamwork should be the foundation of your sales culture. When salespeople hoard leads or client information, it creates silos, reduces collaboration, and hinders overall growth. Address these issues quickly and foster an environment where shared goals and communication are prioritized. 

My fundamental belief is you can’t scale vibes, but you can scale standards. Focus on building a team dynamic that thrives on accountability, innovation, and a shared commitment to client success. 

Build the culture that wins, not just the one that feels good. 

To take your sales team’s performance to the next level, check out our GTM Academy  Sales Kit  for tools and resources to effectively sell cybersecurity and compliance services. 

To your growth and success, 
Shane

How to Earn Trusted Advisor Status and Scale Your MSP

Melissa-Loehwing
Melissa Loehwing Publication date: 27 March, 2026
Education

Many managed service providers face a common frustration when trying to expand their security offerings. You build a comprehensive cybersecurity package, train your team on the latest threat detection tools, and prepare a detailed presentation. Yet, when you sit down with the client, they hesitate to sign the proposal. 

The immediate reaction is often to look inward at the sales process. If there’s one misconception I see over and over again in the MSP space, it’s this: 

“We just need the right script.” 
“We just need a better deck.” 
“We just need to explain the tech more clearly.” 

I’m going to say something that might sting a little: Your clients don’t care about your tech stack. 

They want to know a capable partner is watching out for them so they can focus on their business. When you lead with software features instead of business outcomes, you become “just another vendor.” To expand margins and scale services, you must reframe the conversation.  

Ultimately, you are looking to gain their trust.  

The Foundation of Cybersecurity Sales Is Trust 

Before entering the cybersecurity industry, I spent 10 years working in education. The core lesson I learned there translates perfectly to scaling managed services. People simply hesitate to move forward until they feel safe and confident. 

A student will avoid attempting a complex algebra problem unless they believe they have the support to succeed. Similarly, a business owner will resist expanding their security budget unless they completely trust the organization managing their risk. Confidence comes from absolute clarity. Clarity is built through strong relationships, and those relationships are forged through consistency over time. 

When you ask a client to invest more in their security posture, you are asking them to trust your judgment about risks they often do not fully understand. If your relationship is purely transactional, that leap of faith feels entirely too risky for them. 

What Trusted Advisor Behavior Looks Like 

“Trusted advisor” is a term that gets used frequently in the channel, but it is a pattern of behavior rather than a formal title. It requires a deliberate shift in how your team interacts with clients on a daily basis. 

Show up without an invoice 

Clients notice when you only reach out during renewal periods, at the end of the quarter, or when you have a new service to pitch. To build genuine trust, you need to engage with your clients when there is nothing on the table to sign. 

You can send them an article relevant to their specific market. You might congratulate them on a recent executive hire or acknowledge an industry news event that could impact their operations. These small, consistent touchpoints demonstrate that you are actively thinking about their business success, even when you are not actively billing them for a new project. 

Understand their business drivers 

You cannot position cybersecurity strategically if you do not understand your client’s overarching business goals. Security should always enable the business, which means your discovery process needs to go far beyond technical assessments. 

Ask your clients what major changes they anticipate this year. Find out what specific priorities their board of directors is focused on, and ask them how they define a successful year for their organization. If a client is planning a major acquisition, their security needs will look very different than a client who is preparing to downsize or shift to a fully remote workforce. When you align your security recommendations directly with these business drivers, your proposals transform from operational expenses into strategic investments. 

Have the hard conversations 

If you avoid uncomfortable conversations, you relegate your business to a standard vendor role. Advisors step into the difficult discussions because they know it protects the client in the long run. 

You must be willing to discuss missed calls, unexpected budget shifts, glaring security gaps, and operational friction. Addressing a failed compliance audit or a near-miss security incident requires tact and honesty. When you lead these conversations with empathy and a clear plan for remediation, you prove your value. Clients respect partners who prioritize their safety over maintaining a perfectly pleasant, surface-level relationship. 

Moving From Vendor to Strategic Partner 

Take a moment to evaluate your current client engagement model. If your quarterly business reviews consist entirely of reporting on the number of threats blocked, listing the tools you deployed, and reviewing the current invoice, you are simply reporting data. 

Strategic partners connect their technical activity directly to business outcomes. Instead of highlighting how many alerts your team processed, explain how your automated threat detection saved the client from a specific operational downtime scenario. Show them how your security program management helps them maintain compliance, which in turn allows them to win larger contracts in their own market. 

Practical Steps to Elevate Your Selling Motion 

You can begin shifting your sales motion immediately by implementing a few straightforward operational changes across your organization: 

  1. Add one non-sales touchpoint per client per month.  
  1. Document three business goals for each customer.  
  1. Ask one layered “why” question in every strategic meeting.  
  1. Never only reach out when you need a signature.  

Earning trusted advisor status requires dedication and time, but the business impact is substantial. When you focus on business outcomes and maintain consistent, proactive relationships, you not only protect your clients’ assets but also position your organization for scalable growth. 

To help you put these strategies into action, check out our GTM Academy Sales Kit. The Sales Kit is a comprehensive set of guides, tools, and templates designed to make your sales motion more repeatable, outcome-driven, and aligned with client needs. Equip your team with proven frameworks and go from vendor to strategic advisor with every client interaction. 

Introducing Cynomi’s Public API: Turning Remediation Plans into Scalable Action for Service Providers

Meha
Meha Varier Publication date: 26 March, 2026
Education

The Hidden Cost of Disconnected Security Operations 

For MSPs and MSSPs, the hardest part of delivering security services is consistent execution at scale. As service providers rely on an expanding stack of security platforms, PSAs, and execution tools, each system plays a critical role but too often operates in isolation. 

The result is familiar. Teams are forced into swivel-chair management across tools, remediation tasks are duplicated, data becomes inconsistent, and security work drifts out of sync as it moves from planning to execution. As client counts grow and security programs become more structured and proactive, this friction compounds. 

Manual task re-entry slows teams down and introduces risk. When remediation status is outdated or misaligned across systems, visibility erodes, reporting loses credibility, and service quality suffers. Fragmented workflows make remediation and compliance harder to scale, while integrations that do not reflect real operational needs stall automation and force teams into brittle workarounds. 

The result is a lack of centralized visibility into remediation and compliance progress, leaving teams to piece together the truth across disconnected systems and making security delivery harder to scale when consistency matters most. 

The Cynomi Public API: A Foundation for Scalable Security Execution 

To address these challenges, Cynomi has introduced its Public API as a foundational step in evolving the platform into an integrated operating layer for security services. Designed for operationally mature service providers that require deeper integration to streamline service delivery, the Public API extends Cynomi directly into existing operational ecosystems.  

Its first capability, task synchronization, enables secure and bi-directional integration with any PSA or ticketing system, keeping security tasks and statuses continuously aligned across tools. By eliminating manual updates and restoring clear task-to-ticket visibility, the Public API creates a reliable foundation for automation, execution, and scale, allowing MSPs and MSSPs to deliver security programs with greater confidence as operational complexity grows. 

How It Works  

The Cynomi Public API connects security planning with day-to-day execution by keeping Cynomi and operational systems continuously in sync. Security assessments and remediation roadmaps are created in Cynomi, then seamlessly surface as actionable work inside the PSA or ticketing tools teams already use. 

As remediation progresses, updates made by engineers in their service tools automatically reflect back in Cynomi. Task status, risk posture, and compliance views stay aligned without manual updates or reconciliation across systems. This creates a single, reliable view of remediation progress across clients while allowing each team to work in the tools that fit their role. 

By maintaining real-time alignment between security insight and execution, the Public API removes the gaps where visibility, accuracy, and momentum are often lost and establishes a foundation for scalable, automation-ready service delivery. 

Turning Security Insight into Action 

For service providers, the impact of task synchronization is immediate and measurable. Manual task duplication is eliminated, data stays consistent across systems, and engineers can focus on execution without leaving their primary service tools. Security leaders gain real-time visibility into remediation progress and compliance status across clients, improving confidence in reporting and service quality.  

By keeping security work continuously aligned from assessment through execution, the Public API enables faster remediation, more predictable delivery, and a scalable operating model that supports growth without adding operational overhead. 

More Than an Integration: A Platform Built for Your Operations 

Task synchronization is where you see immediate impact, but it is not the end goal. We designed the Cynomi Public API as an extensible, API-first platform capability so your integrations work for you today and continue to deliver value as your operations evolve. 

By starting with task synchronization, you get fast, tangible improvements in execution, visibility, and scale. Over time, the Public API will expand to make more Cynomi data and capabilities available to your operational systems where it meaningfully improves service delivery and customer outcomes. This approach protects your integration investments, avoids brittle one-off connectors, and removes dependency on fixed vendor roadmaps. 

Most importantly, Cynomi becomes an operating layer for your security services, supporting how you deliver today while giving you the flexibility to evolve over time. And this is just the beginning. 

CIS Controls v8: Everything You Need to Know

amie headshot
Amie Schwedock Publication date: 17 March, 2026
Compliance

When a client asks “what should we be doing for security?” they need a better answer than “it depends.” The CIS Controls are a prioritized set of 18 controls and 153 safeguards that tell organizations exactly what to protect and in what order. For MSPs delivering security services to SMBs, the framework is also practical enough to deploy across every client without reinventing the approach each time.

What makes CIS Controls different from enterprise-heavy frameworks is the Implementation Group structure. Your clients start with 56 essential safeguards and scale up as their risk profile and resources grow. That tiered approach maps directly to how you already think about service delivery. Match the engagement to the client’s maturity, then expand over time.

What Are CIS Controls v8?

CIS Controls are a prioritized set of cybersecurity best practices maintained by the Center for Internet Security. Originally developed in 2008 as the SANS Critical Security Controls, the framework has been refined over nearly two decades based on real-world attack data and input from practitioners across government, industry, and academia. The current version, v8.1 (released June 2024), contains 18 controls broken down into 153 safeguards, each specific and actionable enough to defend against the most common attack patterns observed in the field.

CIS Controls are voluntary, and that distinction matters for how you position this with clients. Organizations align with CIS Controls rather than certifying to them. This makes the framework a practical starting point for SMBs that need demonstrable security practices without the audit burden of formal certification programs. When a client’s industry eventually requires formal compliance, CIS alignment provides a documented foundation that maps to NIST CSF 2.0, ISO 27001, PCI DSS v4.0, CMMC 2.0, and SOC 2 through the CIS Controls Navigator. Several U.S. states now reference CIS Controls when defining what constitutes “reasonable” cybersecurity for government contractors and agencies.

That cross-framework mapping is where CIS Controls become especially valuable for your practice. A single assessment methodology can satisfy multiple client obligations, which means the work you do once scales across clients with different regulatory contexts. But the real operational question is where to start, and the answer is built into the framework itself.

Implementation Groups: Where Most Clients Should Start

Not every client needs all 153 safeguards. CIS Controls use Implementation Groups (IGs) to help organizations prioritize based on risk profile and available resources. The groups build cumulatively, so IG2 includes all of IG1, and IG3 includes everything.

Here’s how the groups break down:

GroupSafeguardsWho It’s For
IG156All organizations, essential cyber hygiene
IG2IG1 + additionalOrganizations with moderate cybersecurity programs
IG3All 153Regulated industries and high-risk environments

IG1 is your baseline service tier

IG1 represents the 56 safeguards every organization should implement regardless of size or industry. These address the most common attack vectors with achievable controls:

  • Maintaining inventory of devices and software
  • Configuring systems securely
  • Implementing multi-factor authentication (MFA) for all users
  • Applying patches within defined timeframes
  • Maintaining tested backups
  • Basic logging and alerting
  • Anti-malware protection
  • Security awareness training

For your SMB clients, IG1 is the structured answer to “what should we be doing?” It eliminates the low-hanging fruit that attackers exploit most frequently, and it’s achievable without dedicated security staff on the client side. If you think about this in service delivery terms, IG1 is the baseline engagement you can standardize across your entire portfolio.

IG2 and IG3: when clients outgrow the baseline

IG2 adds safeguards for organizations with more complex environments, sensitive data, or regulatory obligations. Centralized logging with SIEM correlation, EDR coverage, network segmentation, formal incident response testing, privileged access management, and phishing simulations all live in IG2. Your clients typically move from IG1 to IG2 when they acquire sensitive data, face regulatory requirements, or expand to multi-cloud environments.

IG3 covers all 153 safeguards for organizations facing sophisticated threat actors or operating in heavily regulated industries. That includes threat intelligence integration, threat hunting, application allowlisting, DLP, and red team exercises. Most SMBs will never need IG3, and that’s the point. The Implementation Group structure prevents your clients from overinvesting in controls that exceed their actual risk profile.

From a practice-building perspective, these tiers give you a natural upsell path. A client starts at IG1. As their business grows or compliance requirements kick in, you expand the engagement to IG2. Each tier is more MRR for the same client relationship, and the progression is built into the framework rather than something you have to sell from scratch. The controls themselves, though, deserve a closer look, starting with the ones that drive ongoing operational work.

The 18 CIS Controls

The controls are numbered by priority, not alphabetically. Control 1 (asset inventory) comes first because you cannot secure what you do not know exists. Control 18 (penetration testing) comes last because it validates everything else.

ControlNameWhat It Covers
1Inventory and Control of Enterprise AssetsTrack all devices connected to infrastructure
2Inventory and Control of Software AssetsManage authorized software, detect unauthorized installations
3Data ProtectionClassify, handle, and dispose of data securely
4Secure ConfigurationHarden devices and software against misconfigurations
5Account ManagementManage user and service account lifecycles
6Access Control ManagementImplement least privilege and MFA
7Continuous Vulnerability ManagementAssess and remediate vulnerabilities continuously
8Audit Log ManagementCollect, review, and retain logs for detection and investigation
9Email and Web Browser ProtectionsDefend against phishing and web-based threats
10Malware DefensesPrevent and detect malicious software
11Data RecoveryMaintain tested backup and recovery capabilities
12Network Infrastructure ManagementSecure and manage network devices
13Network Monitoring and DefenseMonitor for and respond to network threats
14Security Awareness and Skills TrainingTrain the workforce on security practices
15Service Provider ManagementEvaluate and monitor third-party security
16Application Software SecuritySecure in-house and acquired software
17Incident Response ManagementDevelop and test incident response capabilities
18Penetration TestingTest security through simulated attacks

Most of your SMB clients will not implement all 153 safeguards across 18 controls. They are starting with the 56 in IG1, and four of these controls deserve particular attention because they represent ongoing operational practices rather than one-time implementations.

Four Controls That Drive Recurring Engagements

Audit log management (Control 8)

Control 8 contains 12 safeguards focused on collecting, reviewing, and retaining logs for detection and investigation. For your clients, the work extends well beyond the initial setup. It requires defining what events to log (authentication, access changes, admin actions), determining retention periods based on regulatory and operational needs, establishing who reviews logs and how frequently, integrating with alerting systems to flag anomalies, and testing that logs are actually being captured and retained.

Organizations without dedicated security operations typically need outside help to make sense of log data. That dependency is what makes audit log management a natural fit for managed services and an ongoing engagement rather than a project.

Secure configuration (Control 4)

Default configurations are rarely secure. Out-of-the-box settings prioritize ease of use, not defense. Control 4 addresses this through hardened baseline configurations for each asset type, consistent application across the environment, detection and remediation of configuration drift, and documented exception management.

CIS Benchmarks (separate from CIS Controls) provide specific configuration recommendations for particular platforms. Controls tell your team what to do at a strategic level; Benchmarks tell your team how to configure specific systems. The ongoing challenge is configuration drift. Without continuous monitoring, systems gradually deviate from their hardened state as changes accumulate, which is why this becomes a recurring service rather than a one-time hardening project.

Access control management (Control 6)

Control 6 goes beyond “implement MFA” to address the full lifecycle of access credentials. That means creating accounts with appropriate initial permissions, reviewing and adjusting permissions as roles change, revoking access promptly when employment ends, managing privileged access separately from standard user access, and implementing MFA for all users rather than just administrators.

The principle of least privilege sounds straightforward but requires continuous attention. Permissions accumulate over time as employees change roles, creating excessive access that persists until someone audits it. For your clients, that audit is the service you provide.

Incident response management (Control 17)

Security incidents will happen. Control 17 addresses whether your client’s organization is prepared to respond effectively. That preparation includes documented policies and procedures for common incident types, defined roles and escalation paths, responder training, communication templates and protocols, and regular testing through tabletop exercises.

A plan that has not been tested is a plan that will not work under pressure. Regular exercises expose gaps in procedures and build team confidence before a real incident forces them to perform. Running those exercises is another engagement that reinforces your value as an ongoing security partner, and it connects directly to how you implement CIS Controls as a program rather than a project.

Implementing CIS Controls as an Ongoing Program

CIS Controls implementation is not a project with a completion date. It is a program that evolves as threats change, your client’s business grows, and their risk profile shifts.

Start with IG1 and prioritize within it. Every implementation should begin with the 56 IG1 safeguards. Prioritize based on current gaps. If your client has no asset inventory, start there. If backup and recovery has not been tested, that takes precedence over access management refinements. The gap analysis you run at the start of the engagement also gives your client a clear picture of where they stand and gives you the scope for everything that follows.

Assess continuously, not annually. Point-in-time assessments capture a snapshot that begins degrading immediately. Asset inventory changes, configurations drift from hardened baselines, vulnerabilities emerge, and people leave without access being revoked. Continuous assessment does not mean constant manual review. It means automated monitoring with human analysis of exceptions and trends.

Use CIS as a cross-framework foundation. Organizations pursuing multiple compliance requirements can implement CIS Controls once and demonstrate alignment across NIST CSF 2.0, ISO 27001:2022, PCI DSS v4.0, CMMC 2.0, and SOC 2. For your practice, this means a single assessment methodology that satisfies multiple client obligations without starting from scratch for each framework.

Document progress for triple-duty value. Track implementation status, responsible parties, evidence, gaps, and review dates for each control. This documentation demonstrates improvement to client stakeholders, guides resource allocation, and provides evidence of “reasonable” security practices during audits, insurance applications, and client security assessments.

For MSPs building security services at scale, platforms such as Cynomi map assessments and policies to CIS Controls v8.1, automate evidence collection, and track progress across the control set. Implementation Group alignment means you can match the right controls to each client’s maturity level and demonstrate measurable progress over time, turning security from an abstract conversation into a visible program with clear next steps.

Common CMMC Compliance Challenges and How to Overcome Them

amie headshot
Amie Schwedock Publication date: 13 March, 2026
Compliance
Common CMMC Compliance Challenges and How to Overcome Them

Your defense contractor clients probably have firewalls, endpoint protection, and backup systems already in place. Most do. When you walk into a CMMC readiness engagement, the technical controls are usually there. The governance layer is where things fall apart: documented policies, assigned ownership, and evidence trails that prove those controls actually work when a Certified Third-Party Assessment Organization (C3PAO) starts asking questions.

That governance gap becomes urgent with a deadline attached. Phase 2 enforcement begins November 2026, making Level 2 C3PAO assessments mandatory for select new Controlled Unclassified Information (CUI) contracts. The estimated 80,000 defense contractors needing Level 2 are competing for a limited pool of assessment slots, and the 110 NIST SP 800-171 requirements don’t get easier to operationalize under time pressure.

The failure patterns are well documented and predictable. For MSPs guiding defense industrial base (DIB) clients through preparation, recognizing these patterns early keeps your engagements structured rather than reactive. Every challenge below is also something your team can build a repeatable practice around.

Scope Definition Is Where CMMC Preparation Succeeds or Fails

The most expensive mistake in CMMC preparation happens before remediation even starts. Every system that stores, processes, or transmits CUI falls within the assessment boundary, along with any system connected to those assets. If you define that boundary incorrectly, costs and timelines compound downstream.

Your clients typically get this wrong in two directions. Over-scoping, declaring the entire network as in-scope because segmentation feels complicated, drives up remediation costs and creates a much larger surface for assessors to evaluate.

Under-scoping is worse. Missing a single file share where project managers occasionally store technical drawings can turn a passing assessment into a conditional one requiring rapid remediation.

The Department of Defense (DOD) publishes scoping guidelines for each level, but interpreting them correctly requires understanding how CUI actually moves through your client’s operations. A machine on the shop floor that receives technical specifications handles CUI. A laptop where an engineer reviews drawings while traveling handles CUI. The network backup that captures both handles CUI. Tracing these flows is a skill that improves with repetition, and it is where you add immediate value as a partner. A NIST 800-171 compliance checklist can serve as a reference for which requirements apply to each system you identify in scope. Once you’ve defined the boundary correctly, the next challenge is proving that every control within it actually works.

CMMC Documentation Gaps Are the Most Common Failure Point

Documentation is consistently the longest and most underestimated portion of CMMC preparation. C3PAO assessors evaluate whether controls are implemented, followed, and effective. Having a policy is not enough on its own. The policy must reflect what actually happens, and there must be evidence to prove it.

The patterns that trip contractors up are consistent. Access control policies require multi-factor authentication, but the system allows password-only access for certain user groups. Vulnerability scans run on schedule, but results are not saved in a retrievable format. Training happens, but completion records live in someone’s email rather than a system that an assessor can review. The security program works in practice but is invisible to anyone outside the organization, and that invisibility is exactly what a C3PAO will flag.

Each of the 110 NIST SP 800-171 controls has multiple assessment objectives, totaling 320 that need supporting evidence. At that scale, retroactive collection is impractical. Organizations that build evidence gathering into daily operations from the beginning produce documentation that reflects real practice. Organizations that start after scheduling a C3PAO end up pulling screenshots, exporting logs, and asking people to describe processes from memory. Assessors have seen enough of both approaches to tell the difference immediately.

A CMMC compliance checklist helps your clients track progress against each requirement and catch evidence gaps before they become assessment findings.

Resource Constraints Make CMMC Preparation Harder for Smaller Contractors

The defense industrial base ranges from major prime contractors with dedicated security teams to small machine shops with a handful of employees. CMMC applies to all of them if they handle CUI. The resource reality differs dramatically.

For small and mid-sized contractors, the constraint is the lack of security expertise they cannot easily hire for. The cybersecurity talent shortage is well-documented, and your clients compete for the same candidates as enterprises offering higher compensation. Dedicated CMMC expertise is expensive as a project cost and difficult to sustain as ongoing capability. The bulk of first-cycle spending goes to preparation and remediation rather than the formal assessment itself, which means the real cost driver is the work your clients need help with before a C3PAO ever arrives.

The skill gap extends beyond technical implementation. Your team needs to interpret what each NIST SP 800-171 requirement means for a specific business, know what assessors actually flag versus what the documentation says, prioritize which controls to tackle first when resources cannot address everything at once, and prepare staff for assessor interviews where they must explain controls in their own words. A structured cybersecurity risk assessment gives your clients a starting point for that prioritization, but the judgment call about what matters most for a specific contractor still requires hands-on experience.

That pattern recognition, built through repeated engagements, is the core of what vCISO and managed security services bring to CMMC readiness. Fractional expertise matched to actual need costs a fraction of a full-time security hire and scales with the preparation timeline. Even when your client’s internal controls are on track, though, their compliance posture depends on every organization touching CUI in their supply chain.

Supply Chain Readiness Is the CMMC Challenge Nobody Plans For

CMMC requirements do not stop at organizational boundaries. Prime contractors must ensure that every subcontractor throughout their supply chain meets the minimum CMMC level specified in the contract before award, and one unprepared subcontractor can jeopardize an entire program.

The scale is easy to underestimate. A prime with dozens of subcontractors must verify compliance status across the entire supplier base. A small machine shop receiving technical drawings to produce components handles CUI just as certainly as the engineering firm that created those drawings. Lower-tier subcontractors may not even realize CMMC applies to them, and many lack the resources or awareness to begin preparation on their own. Getting the flow-down language wrong can trigger contract termination, withheld payments, or suspension and debarment, which is why verifying subcontractor status early protects both your client and your engagement.

For MSPs, this creates a multiplier effect. One prime contractor engagement can surface five or ten subcontractors who also need CMMC readiness support. If you’re positioned as the partner who understands supply chain compliance flow-down, a single engagement becomes the entry point for a much larger book of business across the defense industrial base.

The final rule extended this to external service providers handling CUI, and that includes you. If your MSP touches client CUI, you must meet relevant CMMC requirements or demonstrate FedRAMP Moderate status. The compliance obligation flows in both directions.

That dual position is actually an advantage. You are part of your client’s assessment boundary, which gives you credibility when you lead the compliance conversation with their broader supply chain. Partners who understand how requirements flow across multiple regulatory contexts can help contractors coordinate with their subcontractors and ensure appropriate flow-down language in contracts.

Why These Challenges Compound Under Time Pressure

Each challenge above is manageable in isolation. They become dangerous when 68% of contractors report that CMMC preparation took more than one year and the Phase 2 enforcement deadline of November 2026 is already compressing timelines for contractors who haven’t started.

A scope definition error discovered during remediation resets months of documentation work. A governance gap that surfaces during a mock assessment means controls exist but nobody can explain them under interview conditions. A subcontractor that assumed CMMC didn’t apply to them can delay a prime’s entire certification timeline. With assessor wait times extending 6–12 months, a failed first attempt doesn’t just cost time. It costs competitive position.

The common thread across all of these challenges is that they reward early, structured engagement over late-stage scrambles. For MSPs, the value you bring is pattern recognition built through repeated engagements: knowing where scope typically goes wrong, which documentation gaps assessors flag most often, and how to sequence remediation so the highest-risk items close first. That expertise compounds across every client in your DIB portfolio.

For a step-by-step preparation walkthrough, see our guide to CMMC audit preparation. For MSPs building CMMC readiness into their practice, platforms like Cynomi provide the structured methodology and automation to deliver compliance readiness consistently across your client base.

Voices of Leadership: The Women Shaping the Future of Cyber Advisory

Jenny-Passmore
Jenny Passmore Publication date: 9 March, 2026
vCISO Community

Women’s History Month is an opportunity to recognize the leaders shaping industries through innovation, resilience, and vision. In cybersecurity, that leadership is especially critical. 

While women represent 22% of the global cybersecurity workforce (according to ISC2), parity remains elusive, especially at senior levels. However, a powerful wave of women leaders is driving transformation in cyber advisory, setting new standards for expertise, advocacy, and impact. 

For Women’s History Month, we are spotlighting five Cynomi partners and industry leaders who are at the forefront of this transformation. They understand that cybersecurity is a business discipline, and their insights offer a roadmap for technical excellence, strategic vision, and inclusive leadership. 

Shannan De Witt, Founder, Flex Consulting 

Bridging Operations and Security Architecture 

Shannan De Witt is the founder of FLEX Consulting, where she serves as a strategic advisor and global security lead. She manages complex digital transformations and security roadmaps for international enterprises, handling budgets exceeding $950 million. Her work focuses on bridging the gap between business operations and elite security architecture. She specializes in NIST, CMMC transitions, global identity and access management integrations, audit assurance, and the automation of governance, risk, and compliance. 

De Witt provides executive-level guidance to C-suite leadership and boards of directors, using a hands-on approach to ensure large-scale AI and SaaS platform rollouts maintain strict adherence to regulatory standards. 

Strategic advice for navigating a complex landscape 

With over 20 years of experience leading global SaaS, cybersecurity, and AI transformations, De Witt has watched the industry evolve from technical gatekeeping to strategic business enablement. Her approach relies on a core set of principles: 

  • Master the intersection: True leadership happens where AI governance and global data governance meet core security. 
  • The multi-framework mindset: Compliance is about building strategic ROI roadmaps across various compliance and regulatory frameworks, rather than just checking boxes. 
  • Forensic rigor: Lead with a data-driven approach, leveraging forensic investigations to establish authority in high-stakes environments. 
  • Continuous excellence: Elite credentials represent the gold standard for GRC expertise. 
  • Operational vision: Focus on the strategic reasoning to drive initiatives that move the business forward. 

Beyond the data center, De Witt’s background coaching football and serving as a firefighter and paramedic taught her that technical skill requires seamless teamwork. She brings that high-pressure, collaborative approach to cybersecurity, knowing that the strength of any crisis response depends on team unity. 

When it comes to women in leadership, De Witt emphasized, “While we’ve made incredible strides, we must continue pushing for progress in mentorship pipelines and representation for women in cybersecurity, infrastructure, and AI.” 

Ann Westerheim, Founder & President, Ekaru 

Strengthening the Foundation for Small Businesses 

Ann Westerheim is the founder and president of Ekaru, a technology consulting firm focused on strengthening the technology foundation and cybersecurity posture of small businesses. She helps organizations build the resilience they need to operate securely and efficiently. 

Stepping into high-impact roles 

Westerheim sees cybersecurity as one of the most interesting and high-impact careers in technology, offering far more opportunity than available talent. However, she notes a persistent gap in representation. 

When attending technical sessions at industry conferences, Westerheim observes that the rooms remain overwhelmingly male. She advocates for more women to step into both technical and leadership roles, emphasizing that cybersecurity is a field where dedicated professionals can make a tangible difference for their clients and their communities. 

Donna Gallaher, President & CEO, New Oceans Enterprises, LLC 

Translating Cyber Risk into Business Impact 

Donna Gallaher is the president and CEO of New Oceans Enterprises, a cybersecurity consulting firm specializing in data privacy and AI governance programs. Her firm provides fractional CISO services to organizations across healthcare, financial services, manufacturing, retail, energy, and education. She helps clients across healthcare, financial services, manufacturing, retail, energy, and education industries translate complex cyber and privacy risks into direct business impacts, empowering executives to make informed, strategic security decisions. 

Leading with business acumen 

Gallaher advises women entering cybersecurity leadership to focus on the broader business context. Cybersecurity is ultimately a business risk discipline, and leaders who rise quickly are those who speak the language of the boardroom. 

She encourages emerging leaders not to feel intimidated if they aren’t deeply technical in every area. Leadership centers on enabling others to achieve their goals. Gallaher emphasizes the importance of rejecting self-doubt and ignoring critics who focus on perceived shortcomings. “Don’t let anyone use your self-doubt against you, because that tactic only works if you allow it,” she said. “Nobody is an expert at everything, including those who may criticize you.” 

Instead, she recommends finding partners and collaborators who complement your strengths, building each other up, and never mistaking a knowledge gap for a leadership gap. 

Nett Lynch, CISO, Kraft & Kennedy 

Driving Strategy and Building Team Culture 

Nett Lynch serves as the CISO at Kraft Kennedy, a technology consulting firm dedicated to the legal industry. She leads the firm’s cybersecurity strategy, compliance programs, and client advisory work. She also leads Legion, their left-of-boom cybersecurity advising division built for MSP partnerships. For Lynch, building a strong team culture is an operational priority equal to the security work itself. 

Moving from mentorship to sponsorship 

Having worked in the field for 30 years, Lynch has seen significant shifts. Early in her career, women in the C-suite (let alone the CISO seat) were the exception, not the rule. Today, she sees more women leading security programs, driving compliance frameworks, and earning seats at the executive table. However, she notes that progress does not mean the work is finished. 

Lynch identifies a critical need to close the gap in sponsorship, not just mentorship. Women need advocates who will actively put their names behind new opportunities, rather than just offering guidance.  

“There isn’t just one seat at the table for women in cybersecurity, and we have to act like it,” said Lynch. 

She stresses that inclusion is not a zero-sum game. True progress requires men to act as genuine allies and women to actively champion one another and create space. That cultural shift, more than any single policy, is where she believes our next real progress lives.  

Paige Goss, Founder & CEO, Point Solutions Security 

Putting People First in Security Solutions 

Paige Goss is the founder and CEO of Point Solutions Security. She focuses on building a company that prioritizes people, supporting both her clients and her internal team. Her role centers on growing the business, strengthening relationships, and ensuring that delivered security solutions genuinely protect and support the humans behind the mission. 

Embracing vulnerability and continuous learning 

Goss advises women stepping into leadership roles to lead with confidence, curiosity, and a willingness to stay uncomfortable. The cybersecurity industry changes rapidly, and successful leaders are those who continuously learn, push their own boundaries, and step into spaces where they may not feel fully ready. 

She views vulnerability as a leadership strength. Being open about what you do not know, asking targeted questions, and surrounding yourself with people who challenge you will make you better and stronger over time. 

“Cybersecurity is about far more than technology. At its core, it is about protecting people, organizations, and communities. When you stay grounded in that mission and lead with authenticity, your impact will go much further than you think,” said Goss.  

Moving Forward: The Next Steps for Industry Inclusion 

The insights from these five leaders make one thing clear: technical expertise must be paired with business acumen, strategic vision, and a strong team culture to deliver real outcomes. To continue building a robust cybersecurity workforce, the industry must move beyond passive mentorship. 

We need active sponsorship, clear pathways to leadership, and a commitment to championing diverse voices at every maturity level. By creating space for women to lead, collaborate, and innovate, we build a future that is more secure, resilient, and ready for whatever challenges come next. 

If you know a cybersecurity advisory leader who is making a significant impact on the industry and delivering exceptional results for their clients, we encourage you to recognize their contributions. Nominate them for our Cyber Advisory Excellence Awards today.  

CMMC Audit Preparation for Defense Contractors

amie headshot
Amie Schwedock Publication date: 6 March, 2026
Compliance

If your defense industrial base (DIB) clients are asking about the Cybersecurity Maturity Model Certification (CMMC) program, they’re usually asking the same question: where do we start? You need a structured preparation process you can run consistently across every engagement. Follow the steps below once, refine them, and you have a productized CMMC readiness service you can sell repeatedly.

Most of your clients will need Level 2, which covers Controlled Unclassified Information (CUI) and requires implementation of 110 security requirements from NIST SP 800-171 across 14 control families. A Certified Third-Party Assessment Organization (C3PAO) conducts the formal assessment using document review, personnel interviews, and technical testing over 3–10 business days. But the preparation you lead determines whether your client passes on the first attempt or loses months waiting for a rescheduled slot.

Step One: Define Your Client’s CMMC Scope

The most expensive preparation mistake is implementing controls across systems that don’t handle CUI. Before configuring a single tool, map exactly which people, systems, facilities, and service providers fall within your client’s assessment boundary.

Start by tracing how CUI flows through the environment. Every system that stores, processes, or transmits CUI is in scope, along with any system connected to those assets. Many organizations find it valuable to segment their networks, creating an isolated enclave for CUI-relevant systems to shrink the assessment boundary. Tighter scope means simpler assessments and lower remediation costs.

This scoping work is where you add immediate value. Right-sizing the effort prevents both over-investment (applying Level 3 rigor when Level 2 suffices) and under-scoping, which is worse because discovering mid-assessment that additional systems are in scope can derail the entire engagement. The Department of Defense (DOD) provides scoping guidelines for each level, but interpreting them correctly requires understanding how CUI actually moves through your client’s operations.

Step Two: Run a Gap Analysis Against CMMC Requirements

With the boundary defined, you can measure your client’s current posture against every CMMC requirement. Treat this gap analysis as risk-informed prioritization, not a checklist exercise. The goal is to focus resources where they matter most.

For each of the 110 NIST SP 800-171 requirements, assess whether the control is fully implemented, partially implemented, or not implemented. Document the supporting evidence as you go, because this same evidence will be required during the C3PAO review.

CMMC uses a weighted scoring system where certain controls contribute more points based on their security importance. Some requirements are mandatory regardless of overall score. Understanding this weighting changes how you should prioritize remediation for your client: closing a high-weight gap delivers more return than closing several low-weight ones.

What you’ll find is that documentation gaps consistently surface as the top deficiency category in CMMC assessments. DOD assessment data suggests roughly 40% of organizations fail on evidence quality rather than missing controls. Your clients often have controls in place operationally, but lack the documented evidence to prove it. That distinction shapes your engagement because documentation remediation is faster, cheaper, and less disruptive than deploying new controls.

Not all gaps carry equal weight. Here’s how to categorize what you find:

Gap TypeExamplesPriority
Not implementedMissing MFA, no encryption at restHigh: blocks assessment
Partially implementedMFA enabled but not enforced for all usersMedium: requires remediation
UndocumentedControls operational but no written policyMedium: evidence gap
Scope unclearUnknown systems handling CUI, incomplete asset inventoryHigh: assessment risk

This gap analysis is also the engagement that sells the rest. A thorough assessment with honest scoring gives your client a clear picture of where they stand, gives you the scope for remediation, and produces the raw material for the documentation that assessors will actually review.

Step Three: Build Documentation for the CMMC Assessment

C3PAO assessors can tell the difference between evidence that comes from how an organization actually works and evidence compiled in the weeks before an assessment. Your documentation strategy needs to produce the operational kind.

System Security Plan (SSP): This is the foundation. It describes how your client’s information systems are secured, mapping specific controls, policies, and configurations to each of the 110 requirements. Write it early and keep it current. An SSP that describes a network architecture that changed six months ago creates unnecessary risk during assessment.

Plan of Action and Milestones (POA&M): If the gap analysis identified deficiencies, the POA&M documents the remediation plan. CMMC allows conditional assessment status if the score meets at least 80% of requirements, certain mandatory controls are satisfied, and a POA&M demonstrates how remaining gaps will close within 180 days. Organizations that don’t close within that window lose their conditional status. A CMMC compliance checklist can help your clients track progress against each requirement during this window.

Beyond the SSP and POA&M, assessors require objective proof of control implementation. This includes security policies, access control matrices, incident response documentation, configuration exports, audit logs, and training records. The key distinction is that evidence must be repeatable and auditable. Assessors verify that what you documented reflects actual practice, not a point-in-time snapshot created for the review.

Assessors evaluate evidence quality against clear benchmarks:

Assessment AreaStrong EvidenceWeak Evidence
Audit logsAutomated SIEM exports, continuousManually pulled logs from last week
Access reviewsScheduled reviews with documented outcomesA spreadsheet created for the assessment
Incident responseActual tickets, response records, lessons learnedA policy document describing what you’d do
Configuration baselinesTimestamped exports tied to change approvalsUndated screenshots of current settings
TrainingCompletion records with dates and acknowledgmentsA slide deck nobody signed off on

Build evidence collection into your client’s operations from day one. If you’re deploying SIEM as part of the engagement, align evidence exports to assessment objectives from the start. This approach produces stronger evidence and eliminates the scramble that assessors have learned to spot.

Step Four: Remediate and Rehearse Before the C3PAO

With gaps identified and documentation underway, the next phase consumes the largest portion of preparation time: closing deficiencies before you engage a C3PAO.

Prioritize remediation based on the gap analysis weighting. Address mandatory controls first, then work through high-impact items in descending order. Assign clear ownership for each task with realistic timelines, and build in buffer. Controls that look simple on paper often require coordination across teams, vendor procurement, or configuration changes that take longer than expected. Contractors who start preparation late routinely face six or more months of delays because their remediation timelines prove unrealistic.

Once remediation is substantially complete, run a mock assessment that simulates the real process: document review against all 110 requirements, interviews with personnel across organizational levels, technical testing of controls, and evidence verification for each control family. Your gap analysis confirmed that the controls exist. A mock assessment tells you something different: whether the people responsible for those controls can actually explain them when an assessor asks.

This rehearsal phase is where your experience as a partner pays off. You’ve seen what assessors flag. You know which interview questions trip people up. DOD pilot data suggests that well-prepared organizations pass at significantly higher rates on their first attempt, while organizations that skip mock assessments account for a disproportionate share of failures. Rehearsal is the variable that separates the two groups, and once your client passes, the work shifts rather than stops.

Ongoing CMMC Compliance After the Assessment

CMMC readiness doesn’t end when your client receives their assessment result. Annual affirmations require your clients to attest that controls still work, POA&M items under conditional status must close within 180 days, and evidence libraries go stale as configurations change, people leave, and processes evolve.

Every one of those ongoing requirements is a reason your client stays engaged with you month after month. The clients you help build genuine security programs, with continuous monitoring, documented processes, and clear accountability, find that maintaining assessment readiness becomes a byproduct of how they already operate. That’s the foundation of a recurring engagement.

For MSPs building CMMC readiness into their practice, platforms such as Cynomi turn CMMC readiness into a repeatable, scalable service, from initial gap analysis through assessment-ready documentation, so you can deliver it across your entire DIB portfolio without reinventing the process for each client.

Insights from the Field: Q&A with Cyber Advisory Excellence Winners

image
Erin McLean Publication date: 3 March, 2026
Education

The role of cyber advisors is evolving quickly. Today’s leading advisors and vCISOs are stepping into boardrooms, turning technical risks into practical business strategies, ensuring compliance, and building resilience to drive sustainable growth. 

To celebrate the launch of the Cyber Advisory Excellence Awards and the induction of our Founding Cohort of Transformational Cyber Leaders, we sat down with three of our winners: Chad FullertonJim Ambrosini, and Donald Monistere

Chad Fullerton
VP of Information Security at ECI 

Jim Ambrosini
Director of Cyber Advisory Services at CompassMSP  

Donald Monistere
President & CEO of General Informatics

We asked them to share their real-world experiences on the topics that matter most to service providers today. Here’s what these leaders had to say about the state of cyber advisory excellence.

Translating Technical Risk for the Board 

One of the biggest hurdles for any service provider is communication. How do you explain complex threats to a board of directors focused on revenue and growth? The consensus among our winners is clear: stop talking about packets and start talking about business impact. 

Jim Ambrosini emphasizes the need to anchor every conversation in outcomes. 

“I anchor every risk discussion in business impact—revenue, operations, client trust, and regulatory exposure. Executives don’t need packet-level detail. They need clarity on how a control gap affects strategic outcomes. By framing cyber risk as a measurable business decision, not a technical problem, leadership can prioritize with confidence and accountability.” 

Donald Monistere agrees, noting that simplicity is the ultimate sophistication when dealing with executive leadership. 

“I believe in simplifying complex ‘tech speak’ into relatable concepts. I focus on the business impact of technical risks, framing them in terms of potential financial losses, reputational damage, and operational disruptions. It’s all about vision. Half the battle is having vision into the actual risk, not the 70-page action plan. No board wants to see that. They want the dashboard and someone who can connect the dots.” 

Real-World Impact: Transforming Client Outcomes

The true measure of a cyber advisor’s success is helping their clients build a secure network that drives their business success. When security is aligned with business goals, it becomes a competitive advantage. 

Chad Fullerton shared a powerful example of how strategic advisory directly influenced a client’s financial future. 

“Our clients often have us join their board meetings, but recently a client had me join their investor due diligence call where we walked through our client’s security and compliance posture. The investor openly stated that it was some of the best representation of security and compliance they had seen amongst the client’s peers. Our client ended up securing the business.” 

For Fullerton, the value lies in making the complex actionable. 

“Our clients value our ability to translate complex technical and compliance factors into human-readable and actionable statements. My team and I focus on driving value where it matters most: focusing on AI, compliance, and operational resilience.” 

Tackling the Third-Party Risk Challenge

Third-party risk management remains a critical blind spot for many organizations. As companies rely more on external vendors and AI tools, the attack surface expands. 

Fullerton outlines a structured approach to taming this complexity, starting with a Business Impact Analysis. 

“Clients struggle with knowing where to even start. We kickoff every engagement by understanding what their third parties are and what they do. How do our clients make money, and how do they rely on third parties to do that? We then focus on evaluating controls—like MFA, SSO, and SLAs—before conducting due diligence via open-source intelligence and tailored questionnaires.” 

The Future of Cyber Advisory

The industry is at an inflection point. As technology evolves, so too must the advisor. The winners predict a shift away from policy writing toward dynamic risk ownership. 

Fullerton sees a future defined by complexity and communication. 

“It will only get more complex and demanding. There will be a shift away from being really good at writing policies, towards being really good at communicating risk in relevant terms and taking ownership of problems. Advisors will be forced into the forefront of being subject matter experts on topics that are so new nobody is even an expert yet. It will be a scary but exciting time to be in the industry.” 

Monistere highlights the necessity of continuous vigilance and adaptability. 

“Stay curious and never stop learning. The cybersecurity landscape is constantly changing, and it’s crucial to keep up with the latest trends, threats, and technologies. Cultivating a mindset of continuous improvement will set you apart.” 

Advice for Aspiring Leaders

What does it take to achieve excellence in this field? Our winners offer advice for practitioners striving to elevate their services. 

Ambrosini advises focusing on clarity over complexity. 

“Master the art of simplification without losing rigor. Clients don’t remember the technical deep-dives—they remember the advisor who made the complex understandable and the path forward actionable. If you can consistently bring structure, calm, and clarity to chaotic situations, you’ll become indispensable.” 

Monistere reminds us that true partnership sometimes means challenging the client. 

“Real talk is having the confidence to guide and sometimes disagree when your customer doesn’t properly prioritize the risk. That is when they need us most to say, ‘I know you feel the chances of this risk being exploited is low, but I can introduce you to 30 or 40 that wish they would have taken greater heed.'” 

Fullerton sums it up by urging security teams to step out of the shadows. 

“Advisors can no longer be background technical folks. It becomes more and more relevant for security teams to get out of the shadows, step into the boardroom, and learn to make security and compliance a business driver instead of a cost center.” 

The common thread here is a shift from technical execution to strategic leadership. These experts show that the future of MSPs and MSSPs lies in advisory services that connect security directly to business outcomes, building client trust and unlocking new growth opportunities. 

To learn more about the winners and the program, visit the Cyber Advisory Excellence Awards page.

100+ Cybersecurity Statistics Every MSP Should Know in 2026

amie headshot
Amie Schwedock Publication date: 2 March, 2026
Education

How do you convey the importance of cybersecurity to a client who thinks they’re too small to be targeted? Data.

The numbers tell a clear story, and it starts with targeting. SMBs are hit nearly 4x more frequently than large organizations. The financial impact is concrete: the average SMB breach costs $3.31 million, and 60% of small businesses that suffer a cyberattack close within six months. These risks are measurable, recurring, and disproportionately concentrated in the organizations least equipped to absorb them.

That financial exposure gets worse when there is no one steering the response. 64% of SMBs operate without any CISO, and a full-time hire at $250,000–$350,000+ is out of reach for most. Compliance requirements are expanding alongside the threats, with 85% of organizations reporting increased complexity and 47% failing audits two to five times in three years. The market is responding: vCISO adoption among MSPs and MSSPs jumped 319% in one year, from 21% to 67%, and providers using AI report a 68% average workload reduction.

This guide compiles over 100 statistics across six categories: threat landscape, breach costs, security leadership, compliance, what is working, and the MSP opportunity. Each section is designed to give you the data you need for client conversations, proposals, and strategic planning.

TL;DR

  • SMBs are targeted 4x more frequently than large organizations, yet 64% operate without any security leadership
  • 60% of small businesses that suffer a cyberattack close within six months
  • The average data breach costs $4.44 million globally, with SMBs averaging $3.31 million
  • vCISO adoption among MSPs jumped 319% in one year, as 96% of MSPs report high or moderate client demand
  • AI-driven security tools reduce vCISO workloads by 68% while saving organizations $1.9 million per breach
  • 47% of organizations fail compliance audits two to five times in three years, creating ongoing monitoring opportunities

The SMB Threat Landscape in 2026

The data on attack targeting, frequency, and detection times shows a pattern: smaller organizations absorb more attacks with fewer resources to respond.

SMBs are disproportionately targeted

Smaller organizations have fewer defenses and slower response times. Attackers have adjusted their targeting accordingly.

Smaller teams mean fewer eyes on alerts, and tighter budgets leave organizations running older systems with less training.

Attack frequency is accelerating

The volume of attacks continues to climb, with AI amplifying both the speed and sophistication of campaigns.

AI has changed the attacker’s playbook as much as the defender’s. Phishing emails that once required manual effort can now be generated, personalized, and deployed at scale.

Ransomware dominates SMB breaches

Ransomware has become the defining threat for smaller organizations, far more than for enterprises.

When 88% of SMB breaches involve ransomware versus 39% for enterprises, it reflects how attackers allocate resources. Smaller organizations are more likely to pay and less likely to have tested backup and recovery processes.

Detection takes too long

The time between breach and detection remains one of the biggest challenges, especially for organizations without dedicated security operations.

Attackers can compromise and exfiltrate in under an hour, while defenders often don’t notice for months. That speed gap is where breach costs concentrate.

The Cost of Breaches and Downtime

The financial impact of breaches extends well beyond the incident itself. Recovery timelines, customer attrition, and regulatory penalties compound the initial costs.

Breach costs by company size

The headline numbers get attention, but the SMB-specific data tells the more urgent story.

Most SMBs operate on margins that cannot absorb a six-figure unplanned expense.

Downtime and recovery

The breach itself is just the beginning. Recovery costs compound over months.

Every day of delayed detection and response adds cost, which is why monitoring and incident response capabilities determine outcomes more than prevention alone.

Business survival rates

Breach costs tell part of the story, but business continuity tells the rest.

These numbers reflect the reality that for many SMBs, a breach is a business-ending event.

Industry-specific costs

Some sectors carry higher risk profiles due to data sensitivity and regulatory exposure.

The costs concentrate in industries with regulatory exposure and sensitive data, often in organizations without dedicated security leadership.

The Security Leadership Gap

SMBs face enterprise-level threats without enterprise-level resources. The most critical gap is security leadership.

Most SMBs have no CISO

The majority of smaller organizations have no one responsible for security strategy.

SMBs are spending on security, but they’re spending on tools without strategy. Service providers add the most value by filling the strategic layer above the tools.

CISO salaries make in-house leadership unrealistic

Hiring a full-time CISO is not financially viable for most small and mid-sized organizations.

A $300,000 salary does not make sense for a company with $10 million in revenue, yet the consequences of having no security leadership are just as real.

The talent shortage is structural

Even organizations that want to hire cannot find qualified candidates.

The talent shortage affects providers, too. 32% of MSPs cite lack of skilled cybersecurity personnel as a barrier to offering vCISO services, while 35% cite concerns about profitability and ROI (State of the vCISO 2025). Platforms that reduce the expertise threshold for delivering security services are gaining traction as a result.

Compliance Pressure Is Mounting

Regulatory requirements are expanding faster than most organizations can adapt. For SMBs, compliance is increasingly a condition of doing business, and your clients are feeling the pressure even if they have not articulated it yet.

Framework adoption is standard practice

Organizations are not asking whether to pursue compliance. They are asking how many frameworks they need.

Compliance is now a condition of doing business. Customers, partners, and insurers increasingly require evidence of security controls before signing contracts or renewing coverage.

Audits fail more often than they succeed

Most organizations do not pass compliance audits on the first try.

Compliance requires ongoing monitoring, continuous improvement, and preparation for the next audit. For MSPs, that recurring need maps directly to a managed service.

Non-compliance has direct financial consequences

Beyond the operational burden, non-compliance increases breach costs and triggers regulatory penalties.

Defense contractors face certification deadlines

For MSPs serving defense contractors, Cybersecurity Maturity Model Certification (CMMC) compliance represents both urgency and opportunity.

How vCISO Services and AI Are Delivering Results

MSPs and MSSPs that have invested in vCISO capabilities and AI-driven tools are seeing measurable results across demand, adoption, business impact, and service delivery.

vCISO demand is surging

Client demand for strategic security leadership has reached a tipping point.

SMB clients are asking for more than break-fix IT support. They want someone who can help them navigate security strategy, compliance requirements, and risk management.

Providers are responding with vCISO offerings

The supply side is catching up to demand.

The market has moved from early adoption to mainstream, and providers without vCISO offerings are increasingly outliers.

vCISO providers report clear business benefits

For providers already delivering vCISO services, the business impact is measurable.

vCISO services position providers as trusted advisors, with the retention and expansion benefits that relationship delivers.

AI is transforming service delivery

AI and automation have moved from experimental to operational in leading vCISO practices.

A 68% workload reduction changes the operating model. vCISO services become economically viable for a broader range of clients when the delivery effort drops by two-thirds.

AI improves breach outcomes directly

AI-driven security tools also directly impact breach costs and detection times.

The MSP Opportunity

Rising threats, expanding compliance requirements, talent shortages, and maturing AI tools have created a structural market opportunity for MSPs and MSSPs. The gaps are specific and addressable, and providers are already building recurring revenue around them.

Cyber insurance is driving requirements

Insurers have become de facto regulators, requiring specific security controls as a condition of coverage.

Insurance readiness has become a service category. Clients need help meeting insurer requirements and documenting their controls, ongoing work that fits the MSP model.

The market is moving toward strategic priorities

MSPs and MSSPs are aligning their strategies with where client needs are heading.

Preparedness gaps create service opportunities

The gaps in SMB security posture represent addressable problems for providers positioned to solve them.

For MSPs, every gap on that list is a conversation starter and a potential managed service engagement.

Turning Data Into Client Conversations

The throughline across these statistics is that SMBs need security leadership, and the partners who deliver it are growing. Breach costs are climbing, compliance is getting harder to maintain, and 64% of SMBs still operate without anyone steering the security program. Every number in this piece is a conversation you can have with a client who doesn’t yet realize the gap they’re sitting on.

The shift toward AI-driven delivery makes the economics work at a scale that wasn’t possible two years ago. A 68% workload reduction means your team can serve more clients at a higher standard without adding headcount. That’s the operational reality behind the 319% growth in vCISO adoption.

For MSPs building security practices around these trends, Cynomi provides the structured methodology and built-in CISO Intelligence to deliver security program management across your full client base.