Cloud Cover, a flat-fee managed IT provider in Worthington, Ohio, offers both fully managed and co-managed IT, so we see how each model works in practice. This post compares the two through a compliance lens: who owns which controls, where responsibility gaps tend to appear, and how to match the model to your staffing and risk profile.
Fully managed IT means an outside provider runs your day-to-day IT and security: help desk, patching, monitoring, backups, user accounts, and security tools. Your leadership still makes business decisions and owns policies, but the provider does most of the operational work. Co-managed IT means your internal IT staff and an outside provider share the work. A common split is that your team handles users, applications, and on-site needs, while the provider supplies security tooling, monitoring, after-hours coverage, and specialized projects. For a deeper look, see our complete guide to co-managed IT responsibilities.
Before deciding who owns what, it helps to know what the rules actually ask for. Each one focuses on safeguards and documentation, not on which support model you use.
The HIPAA Security Rule applies to covered entities, such as healthcare providers and health plans, and to their business associates. It requires administrative, physical, and technical safeguards for electronic protected health information (ePHI). That includes a required risk analysis, access controls, audit controls that record and examine system activity, and written policies and procedures kept for six years. An IT provider that handles ePHI is generally a business associate and needs a signed business associate agreement (BAA).
PCI DSS applies to businesses that store, process, or transmit payment card data. Version 4.0, now maintained as v4.0.1, expects you to protect systems from known vulnerabilities, log and review activity, restrict and authenticate access, and maintain an incident response plan. As of March 31, 2025, requirements such as MFA for all access into the cardholder data environment are mandatory. PCI DSS also expects you to track which requirements each third-party service provider manages and which you manage yourself.
Ohio's Data Protection Act (S.B. 220, effective 2018) gives businesses an affirmative defense against certain data-breach tort claims if they maintain a written cybersecurity program that reasonably conforms to a recognized framework, such as the NIST Cybersecurity Framework or, for regulated businesses, HIPAA's security requirements. PCI DSS can qualify when paired with another listed framework. Separately, ORC 1349.19 generally requires notifying affected Ohio residents in the most expedient time possible, and no later than 45 days after discovering a breach of computerized personal information.
In both models, leadership owns the big decisions: accepting risk, approving policies, signing vendor agreements, and deciding when to notify customers or regulators after an incident. What changes is who does the technical work and keeps the evidence.
The provider typically owns patching, endpoint protection, monitoring, backups, MFA enforcement, and account provisioning. It also keeps the reports that show those controls are working. Your team's role is to approve changes, follow policies, complete training, and tell the provider about new hires, departures, and new systems. This model fits businesses with little or no internal IT staff.
Ownership is split, so it must be written down. Your internal team might own user accounts, line-of-business applications, and local hardware, while the provider owns security tooling, alert monitoring, backup oversight, and after-hours response. Each side keeps evidence for the controls it owns. This model fits businesses that have capable internal staff but need more depth, coverage, or security tools.
The table below shows a typical split. Every engagement is different, so treat this as a template for your own responsibility matrix, not a standard.
| Control or task | Fully managed IT | Co-managed IT (typical split) |
|---|---|---|
| Risk analysis (HIPAA) and risk acceptance | Provider supports the analysis; leadership owns decisions | Shared input; leadership owns decisions |
| Security policies and procedures | Provider helps draft and review; business approves | Internal team maintains; provider reviews |
| Patching and vulnerability management | Provider | Provider for operating systems; internal team for line-of-business apps, or as agreed |
| Endpoint protection and monitoring | Provider | Provider |
| Logging and alert review | Provider | Provider monitors; internal team investigates local issues |
| User accounts and access reviews | Provider, based on business requests | Internal team, with provider support for reviews |
| MFA enforcement | Provider | Shared: provider configures, internal team handles user exceptions |
| Backup and restore testing | Provider | Provider oversees; internal team confirms critical data is included |
| Security awareness and phish testing | Provider runs; staff participate | Provider runs; internal team follows up |
| Incident response | Provider leads technical response; leadership owns notification decisions | Joint response under a written plan; leadership owns notification decisions |
| Vendor agreements (BAA, PCI service provider list) | Business signs; provider supplies its information | Business signs; both sides document their scope |
Fully managed IT can create a false sense that "the IT company handles compliance." The provider can run controls and keep records, but your business still owns policies, training follow-through, vendor agreements, and notification decisions. If leadership is not involved, gaps appear in the non-technical parts of the program. Co-managed IT has a different risk: shared controls that nobody owns. Access reviews, offboarding, and patching of specialty applications are common examples. When an auditor asks who reviewed admin access last quarter, both sides may point at each other. A written responsibility matrix, reviewed at least once a year, is the simplest fix. If an incident does happen, clear roles also make the first hours easier. Our guide on what to do after a cyberattack covers those first steps.
Cloud Cover offers both fully managed IT services and co-managed IT services for Central Ohio businesses, at a flat fee. In either model, we help clients prepare for HIPAA and PCI audits with compliance logs, security hardening, and policy reviews. Cloud Cover's layered security includes endpoint protection, phish testing and training, MFA enforcement, dark web scanning, and Huntress and ThreatLocker. We also provide backup and disaster recovery, Microsoft 365 management, and vCIO reviews where we walk through risks and responsibilities with leadership. Learn more about our cybersecurity as a service. For Columbus metro clients, same-day on-site support is available when an issue needs hands-on attention. This article is general information, not legal advice. Please confirm your specific obligations with your compliance advisor or attorney.
If you have no internal IT staff, or your team is stretched thin, fully managed IT usually gives the clearest ownership of technical controls. If you have capable internal staff who need more security depth, monitoring, or coverage, co-managed IT can work well, as long as responsibilities are written down. Either way, the goal is the same: every control has an owner, and every owner keeps evidence. Cloud Cover can help you map your current responsibilities and recommend the model that fits your staffing and risk. Schedule a consultation, or use our instant pricing calculator to see flat-fee pricing for your business.
Either can support HIPAA compliance. Fully managed IT gives clearer ownership if you lack IT staff. Co-managed IT works if your team is capable and responsibilities are documented. In both cases, a signed BAA is generally required.
If the provider creates, receives, maintains, or transmits ePHI on your behalf, it is generally a business associate under HIPAA and should sign a BAA. Confirm the details with your compliance advisor.
PCI DSS expects you to maintain a list of service providers and know which requirements each one manages and which you manage. Using a provider does not transfer your responsibility for protecting card data.
No. Ohio's Data Protection Act (S.B. 220) is voluntary. It offers an affirmative defense against certain breach-related tort claims for businesses whose written cybersecurity program reasonably conforms to a recognized framework.
It is a written list of IT and security tasks showing who owns each one: your internal team, the provider, or both. It helps prevent gaps and gives auditors a clear answer about ownership.
Tell us a little about your business and a Cloud Cover team member will follow up with answers, not a sales pitch.