Keep security with an in-house IT person only when someone senior checks their work and the basics are written down. A managed IT or security provider fits when you need tools watched and patches applied, but it runs what is in its contract, not your whole risk. When an insurer or a large customer is asking for proof and nobody inside can answer, a fractional security lead with a monthly program usually fits best: one accountable person, a written record of what is protected, and a plan for the day something goes wrong. At MarkCMO that starts with a one-time foundation fee of $4,500 to $15,000, then $3,000 to $9,000 a month, month to month.
In most owner-led firms nobody ever decided who owns security. It landed with whoever set up the computers: an office manager who is good with technology, a part-time IT contractor, a managed IT provider on a support contract, or a relative who helped years ago. That person resets passwords and keeps the email working. Security is assumed to be part of the job, but it was never written down what they are responsible for.
The gap shows up when someone outside asks for proof. A cyber insurance renewal asks whether every account uses two-factor sign-in. A large customer sends a security questionnaire before signing. A bank asks how payment details are protected. The owner forwards it to the IT person, and the honest answers turn out to be "I think so" and "I would have to check". Nobody has tested whether the backups restore. Nobody knows how many former staff still have a working login.
That is the real question behind in-house versus outsourced. It is less about who does the work and more about who is accountable for the risk, and whether anyone can show what is protected.
| Question | In-house IT person or hire | Managed IT or security provider | Fractional security lead plus a monthly program |
|---|---|---|---|
| Cost shape | Part of a salary, plus the tools they buy | A monthly contract, often per user or per device | A foundation fee, then a monthly fee you can resize or end |
| Who is accountable for the risk | The person, though it is rarely written down | The provider, for what its contract names and nothing more | The security lead, against a written plan you approve |
| What gets written down | Usually whatever lives in that person's head | Tickets and tool reports, in the provider's systems | An access list, a ranked findings list and an incident plan, in your name |
| Who checks the work | Often nobody | The provider checks itself | The lead checks the work, including the provider's |
| On the day of an incident | One person, who may be on vacation | The provider follows its own playbook for its own tools | A plan agreed in advance: who decides, who calls the insurer, where the backups are |
| Proof for an insurer or customer | Hard to produce | Reports on the tools it runs | Answers backed by the record, with gaps fixed before you sign |
| Best when | There is a full week of security work and a senior reviewer | You need devices patched and a help desk answered | Someone outside is asking for proof and nobody inside can answer |
For how each of these is priced, the cybersecurity cost page sets out the numbers. This page is about who owns what.
Security can live inside the business when it is a real part of someone's job, not an extra on top of the help desk. Three signs point that way:
If the first sign is missing, a security hire spends much of the week on other work. If the second or third is missing, the firm depends on one person's memory, which is the situation most owners are trying to get out of.
A provider is the right call for the daily operational work: keeping laptops patched, running the help desk, managing email and the network, and watching the alerts its tools raise. It does this at a scale and a level of process a small firm cannot build alone.
The limit is the contract. A provider protects what it was asked to protect. Your website, your cloud accounts, a payment tool someone signed up for, or the old file share a former partner still has access to may sit outside it. Before relying on a provider for security, ask it to list in writing which of these it covers: access reviews across every account, email authentication on your domain, restore tests of your backups, website and cloud settings, and a written incident plan. Whatever it does not list is still yours. The managed IT services vs a head of IT comparison covers the wider question of who runs IT day to day.
This fits the firm that has a provider or an IT person doing the daily work but no one who owns the risk. Usually the trigger is outside pressure: an insurance renewal, a customer questionnaire, a contract that mentions security controls, or a scare such as a convincing fake invoice that nearly got paid.
A fractional security lead gives you that ownership for part of the week. The work starts with an authorized review of what is exposed, who can sign in to what, and how email and backups are set up. The critical and high findings are fixed first and checked live. From then on, scheduled checks and alerts run, and a short monthly note says what changed. The daily IT work stays with your provider or your own person. The lead directs it, checks it, and keeps the record current. This is not a 24/7 operations center, and it does not issue a SOC 2 report or a CMMC certification, which only an accredited auditor or assessor can do. It prepares you for both. What the work covers is on the cybersecurity services page.
If you cannot produce these today, that is the place to start, before choosing who does the work next. They are also most of what an insurer or a large customer will ask to see.
MarkCMO is a marketing and technology company. Mark Gabrielli has spent 15 years leading marketing and operations, and he secures the websites, payment flows, email domains and cloud accounts of his own portfolio of companies with the same routine: written authorization, findings ranked by risk, fixes checked live, and everything recorded in the owner's name. A standalone assessment is scoped and priced in writing before it starts. Ongoing work runs as a one-time foundation fee of $4,500 to $15,000 covering the first month, then $3,000 to $9,000 a month, month to month, with larger scopes priced on a call inside $2,500 to $50,000 a month. If your real question is a head of IT or a managed provider, the answer do we need a head of IT or a managed IT provider covers it. Every service is on the services hub.
For most firms of 5 to 30 people, neither on its own. An in-house IT person knows your systems but rarely has the time or the second pair of eyes that security needs. A provider brings tools and process but only covers what its contract names. The setup that works is usually one accountable owner of the risk, inside or outside, who directs whoever does the daily work and keeps a written record of what is protected.
They can do much of the daily work: patching, resetting passwords, removing old accounts. The problem is that nobody is checking it, and security is the one area where a gap stays invisible until it is used. If your IT person handles security, give them a written list of what they own, a second person with admin access, and an outside review at least once a year.
A managed IT provider keeps computers, email and networks running and answers the help desk. A managed security provider watches for threats with monitoring tools and responds to alerts. Many firms buy one and assume it covers the other. Ask each provider, in writing, which of these they do: access reviews, email authentication, backup restore tests, website and cloud settings, and incident response.
Someone who can prove each answer, not just tick it. Questionnaires usually ask about two-factor sign-in, backups, who has admin access, how devices are updated and what happens after an incident. If the honest answer to any of these is that you are not sure, fix the gap first, then answer. A wrong answer on an insurance application can cause trouble later if you ever need to make a claim.
That depends entirely on what was agreed before. Without a written plan, the first hours go to finding out who to call and who has the logins. With one, everyone knows who decides, who contacts the insurer and your attorney, how accounts get locked, and where the clean backups are. Whoever owns security for you should write that plan and walk you through it before it is needed.
No. MarkCMO is not a help desk and not a 24/7 security operations center. It owns the security plan, closes the gaps found in the assessment, checks the work your provider does, and sets up alerts for what matters most. Your provider keeps doing the daily IT work. If you have no provider, Mark can help you choose one and write down what it must cover.
MarkCMO provides the strategy and the roadmap, and then delivers it across three tiers, so you get direction and execution from one team instead of handing a deck to someone else to build.
Fractional CMO and COO leadership: strategy, positioning, go-to-market, and the roadmap that sets the direction.
Running the function day to day: managing teams, vendors, budgets, and the operating cadence that keeps the plan on track.
Hands-on delivery: marketing execution, software development, tech-stack build and integration, plus finance and operations support, everything a business needs to scale.
From tech to marketing to finance, strategy through execution, MarkCMO can lead it, manage it, and build it.

Free. 30 minutes. With Mark, not a salesperson.
Book a free 30-minute call with Mark Gabrielli. Bring the insurance renewal, the customer questionnaire, or your provider's contract. You will leave knowing who should own the risk, which gaps to close first, and what to have in writing before you answer anyone.
Book a free 30-minute call →Related services