top of page

One Lockout, a Pile of SOC Tickets: How One MSP Cut the Noise

3 hours ago
5 min read

The video uses a digital avatar of Erick Grau, CEO of Chibitek.

Your SOC sent a pile of tickets for one lockout. That is not more security. That is noise.

Every MSP that has added a SOC or an MDR service knows the feeling. The tool did its job and locked down an account. Then the tickets start stacking up, three techs grab the same problem, and the user who just got locked out is sitting there waiting. I want to walk through how another MSP described this exact problem in public, what they say they changed, and what I would take from it for our own shops.

What Net Friends shared at FLOW 2026

On November 17, 2026, Rewst posted a session from its FLOW 2026 conference featuring John Snyder, CEO, and Joel Abney, COO, of Net Friends. Net Friends is a managed IT provider in North Carolina, founded in 1997.

Card from the Short: At Rewst's FLOW 2026, an MSP walked through this exact problem. Net Friends, managed IT provider, North Carolina. John Snyder, CEO. Joel Abney, COO. Session posted by Rewst, Nov 17, 2026.

John opened with the part every one of us lives with. Security tools create alerts and noise, and the job is to get the signal inside that noise to the right people at the right time. When they lock down a user or a device, he said, a lot of people in their organization tend to get mobilized. "Meanwhile, the user is sitting there ... waiting on us to get them back to work."

How one lockout turns into a pile of tickets

Joel explained that Net Friends ran its own in-house SOC for a long time and now uses an outsourced SOC. Then he described what a single user lockout looked like on their side:

  • The SOC locks the user out and sends a ticket, "as they should."

  • The user realizes they cannot get into much of anything and calls or emails, "maybe both."

  • The SOC has "more than one channel of communication" to them, so its outreach arrives from more than one place.

Rewst's own description of the session confirms the pattern: duplicate tickets from their outsourced SOC for a single lockout, which Net Friends now merges into one.

None of that is anyone doing their job badly. The SOC is doing what it should. The user is doing what they should. The problem is that the systems do not know the tickets belong together. That is a workflow problem, not a people problem.

What they say they changed

Net Friends built a Rewst workflow that looks at tickets as they come in and keys off specific details to recognize the duplicates. Rewst's session summary describes it as merging duplicate tickets from their outsourced SOC into one, and as connecting their security tools "without adding a SOAR platform."

Joel described the result in operational terms: fewer people engaged, "less pressure on dispatch," and "a core ticket that we're working from that's our source of knowledge."

Card from the Short: What Net Friends says they did. Merge the duplicates into one ticket. No SOAR added. One core ticket. Up to 75% less lockout time. Their number, not ours.

About that 75 percent

Here is the number, and I want to be careful with it because it is Net Friends' number, not ours.

  • In the talk, Joel said, "this is a 50 to 75% reduction in lockout time."

  • Rewst's description of the session says Net Friends "cut user lockout time by up to 75%."

  • Net Friends' own site, in a post about an interview from the same conference, describes "a 75% improvement in incident response times" after automating a critical workflow.

So the honest version is: Net Friends reports cutting lockout time by 50 to 75 percent, up to 75 percent, with this workflow. In what I reviewed, they did not explain how they measured it or over what period. That does not make it wrong. It means you should treat it as one MSP's reported result and measure your own before and after.

Four ways to cut the noise on your own security tickets

Card from the Short: 4 ways to cut security ticket noise. 1. One parent ticket per event: link or merge the SOC alert, the call, the email. 2. Match on user or device, short window: let automation catch them, not a tired tech. 3. One owner per lockout: fewer people touch it, the user hears from one person. 4. Ask frontline techs first: automate the tedious steps that slow them down.

These are my steps, not Net Friends'. Their story is the example that prompted them.

1. Pick one parent ticket for each security event. Decide that the SOC alert is the parent, and link or merge the call, the email and any follow-up from the SOC into it. The tech who picks it up should see the whole story in one place, not hunt across a stack of tickets.

2. Match duplicates on the same user or device inside a short time window. A lockout has a user and usually a device. If a new ticket names the same user or device within minutes of a SOC alert, it is almost certainly the same event. Let automation make that match, not a tired tech at the end of a shift.

3. Give every lockout one owner. Fewer people touch it, and the user hears from one person instead of three. That is better for the user and cheaper for you.

4. Ask your frontline techs which tedious steps slow them down, and automate those first. They know where the duplicates come from because they are the ones closing them. Start there, not with the automation that looks best in a slide deck.

Key Points

  • At Rewst's FLOW 2026, Net Friends described how one user lockout from their outsourced SOC could produce duplicate tickets for the same event.

  • The tickets come from good behavior: the SOC's alert, the user's call or email, and the SOC reaching out on more than one channel.

  • Net Friends says a Rewst workflow now merges those into one core ticket, without adding a SOAR platform.

  • Net Friends reports 50 to 75 percent less lockout time. That is their number, and how it was measured was not stated in what I reviewed.

  • Any MSP can start with one parent ticket per event, matching on user or device, one owner per lockout, and asking frontline techs what to automate first.

Frequently Asked Questions

Do I need a SOAR platform to fix duplicate security tickets? Not necessarily. Net Friends' example is a workflow that reads tickets as they arrive and merges the duplicates, built on the automation platform they already used. Start with the rules: what makes two tickets the same event.

Is the 75 percent a Chibitek result? No. It is Net Friends' own reported figure. In the talk, Joel put it at 50 to 75 percent less lockout time.

What should I match duplicates on? The user and the device involved, inside a short time window after the SOC alert. Keep the window short so you do not merge unrelated tickets.

Merge or link? Linking keeps every ticket and shows they belong together. Merging leaves you with one. Either way, the goal is one ticket a tech works from and one person the user hears from.

Where do I start? Pull your last few lockouts and count the tickets each one produced. That gives you your own baseline before you automate anything.

Let's Compare Notes

At Chibitek, we are an MSP talking to MSPs, and alert noise is something every one of us fights. Credit to Net Friends and Rewst for walking through this one in public. If you want to compare notes on how your SOC alerts, calls and emails land in your PSA, we are happy to. Contact us at hello@chibitek.com.

We make IT effortless so you can create, disrupt, and grow!

Follow Chibitek on YouTube at @chibitekmsp, and follow Chibitek on LinkedIn.

Sources

Comments


bottom of page