· cyber security · 5 min read

An Incident Response Plan for Co-Managed Teams: Who Calls Whom

When something goes wrong, the first hour is about phone calls. This post lays out call order, decision rights, outside obligations, evidence preservation, and a sample responsibility split for co-managed IT teams.

When something goes wrong, the first hour is about phone calls. This post lays out call order, decision rights, outside obligations, evidence preservation, and a sample responsibility split for co-managed IT teams.

Say it is a Monday morning in March and staff at an accounting firm can’t open client files on the shared drive. Tax season is in full swing. The IT manager is on the way in. The MSP’s alert has already fired. The managing partner is at a client meeting.

Everyone is competent, and nobody knows who is supposed to call whom. In a co-managed IT arrangement, that confusion is fixable before anything happens. It takes a plan that fits on a few pages.

Decide the call order ahead of time

The order below is a starting point. Adjust it with your insurance carrier and your attorney.

  1. Internal IT and the MSP connect first and start containment.
  2. The IT manager or MSP tells the owner or managing partner.
  3. The owner calls the cyber insurance carrier.
  4. The owner or carrier brings in legal counsel.
  5. The carrier’s approved vendors, such as forensic investigators, are engaged.
  6. Affected vendors are told, including the supplier of your main business application.

Call the carrier early. Many cyber policies require prompt notice, and many direct you to a panel of approved response firms. Hiring your own investigator before the call can create coverage questions you don’t want in the middle of an incident. Read your policy now and put the carrier’s claim line on the contact list.

Decision rights

During an incident, the slowest thing is waiting for permission. Settle in advance who can:

  • shut down a server
  • disconnect an office from the internet
  • isolate a workstation or lock an account
  • authorize spending on outside help
  • decide whether and when to notify customers or clients

A workable rule is that the MSP and IT manager can contain, meaning isolate a device or lock an account, without asking. Anything that stops the business, such as taking a core application offline or cutting the internet to an office, needs the owner or an operations lead. Write it down and have both sides sign it.

Know your outside obligations

Depending on your business, an incident can start clocks that have nothing to do with IT. Read these before you need them:

  • Contract notification duties. Customer agreements often require you to tell the customer within a set time if their data may be involved.
  • Cyber insurance carrier requirements, including notice timing and approved vendors.
  • Incident reporting for defense contractors. DFARS clauses in federal contracts can require reporting certain incidents, often on short deadlines, so check your contract language.
  • Breach notification laws. Most states have them, and healthcare organizations also face HIPAA’s Breach Notification Rule, which sets its own deadlines.

Counsel should tell you which of these apply to you. The point of listing them now is that someone on your team already knows where the contracts and the policy live.

Keep the contact list on paper

If email, phones, or the file server are down, a contact list stored on them is useless. Print it. Keep copies at the main office, in the IT manager’s bag, and at the owner’s home.

Include names, mobile numbers, and backup contacts for:

  • internal IT and the MSP’s emergency line
  • the cyber insurance claim line and policy number
  • legal counsel
  • the vendor that supports your main business application
  • the internet provider, the phone provider, and the building manager
  • the owner and the operations lead

Preserve evidence before you fix things

The urge is to wipe the machine and get back to work. Hold off until someone says it is safe. Reimaging a computer can destroy what the investigators need to learn how the attacker got in.

Practical steps:

  • Photograph ransom notes and error screens
  • Keep a running log of what was done, by whom, and at what time
  • Don’t delete accounts, logs, or suspicious files
  • Isolate affected machines from the network, and leave them powered on unless your response team tells you otherwise
  • Ask the investigators before restoring from backup

Good backup and recovery matters here, because a clean restore is the way out. The timing of that restore should still be coordinated.

A sample responsibility split

  • Owner or managing partner: approves major decisions, talks to the carrier and counsel, signs off on customer notices
  • Operations lead: runs manual workarounds, tells clients about delays, handles staff questions
  • Internal IT: first technical responder, knows the systems, controls physical access, works with application vendors
  • MSP: containment, investigation support, evidence handling, and restoration
  • Carrier and counsel: bring in forensics and guide the notification analysis

Communication to clients and staff should go through one person. Agree on who that is, and have a short holding statement ready. For more on the compliance side, see our compliance and regulatory services.

How Kayak Cyber helps

We help co-managed teams write this plan with their actual names and numbers in it, then test it. Our analysts watch alerts around the clock and can isolate a compromised device or disable a compromised Microsoft 365 account while your IT manager is reached. We also keep backups, including immutable copies, and test restores. Your IT manager keeps authority over the environment. See how we work with in-house teams in our co-managed IT services.

Call us at 405-253-5101 or schedule a discovery call to get on the calendar.

  • co-managed-it
  • incident-response
  • cyber-insurance
Share:
Back to Blog