Aegis / Brightpath Commerce - Competitive Evaluation

Yeah, that's — that's probably a good idea. Because honestly Aisha, I'll just be upfront with you, we've been doing a broader security vendor evaluation over the last six weeks or so and it's been... eye-opening.

Sure. So we've been talking to SentinelShield, we've had a couple of pretty deep demo sessions with them, and their threat monitoring story is — I mean, it's compelling. Especially after, you know, what happened in March.

-1Kendra says SentinelShield's threat monitoring is compelling after the March outage. · competitive alternative

Right. And I — I want to address that directly because I know the March incident is something we need to own. That was not acceptable and I understand why it's still top of mind for you.

I mean, six hours, Aisha. Six hours where we had zero threat monitoring visibility. We're a retail company, we process transactions around the clock, and we had no idea what was happening on our infrastructure for six hours. That's — that's really hard to just move past.

-1Kendra describes six hours without threat monitoring visibility as very hard to move past. · service reliability

And it should be hard to move past, I'm not going to sit here and tell you to forget about it. What I can tell you is what we did about it — the root cause was a single point of failure in the event ingestion layer, and the engineering team has since implemented redundant processing nodes and a circuit breaker pattern so that kind of cascading failure literally cannot happen the same way again.

I saw the post-mortem doc your team sent over. And look, the transparency was appreciated, I'll give you that. But a post-mortem doesn't help me if my board is asking why we're still with a vendor that had a six-hour outage two months ago.

-1Kendra says a post-mortem doesn't help her answer her board about remaining with Aegis. · support experience

Honestly? It accelerated it. We had some low-level grumblings about Aegis Detect before March — the alert fatigue issue I mentioned back in, I think it was January — but the outage kind of pushed us to actually go out and look at alternatives. So yeah, SentinelShield is now a serious contender where a few months ago they wouldn't have been.

-1Kendra says the outage accelerated the evaluation and SentinelShield is now a serious contender. · competitive alternative

Okay, and I — I want to come back to the alert fatigue piece because that's something I want to make sure we've addressed properly. But on SentinelShield specifically, what's resonating with you? Like what are they showing you that's landing well?

Their detection accuracy demos have been solid. They're showing us this, uh, behavioral baselining thing where it learns what normal looks like for your specific environment over time and reduces false positives significantly. And for us that's huge because our team is small, we can't have people chasing ghost alerts all day.

-1Kendra says SentinelShield's behavioral baselining would cut false positives, which matters because her team can't chase ghost alerts. · product capability

Yeah, and that behavioral baselining is — I mean, Aegis Detect does have adaptive thresholding that works similarly, but I hear you that we haven't done a great job of demonstrating that or helping you configure it for your environment. That's on us.

I guess what I'd say is — it's not just about features at this point, Aisha. It's about confidence. And right now my confidence in Aegis Detect specifically is pretty low. The other modules, honestly, less so.

-1Kendra says her confidence in Aegis Detect specifically is pretty low. · service reliability

That's a really important distinction. Can you say more about that? Because I want to understand which pieces of the platform still feel solid to you.

Yeah, so Aegis Protect has been fine — backup and recovery has done what it's supposed to do. And actually, your Comply v2 launch, the one that just happened a couple weeks ago — we actually pulled our first on-demand SOC 2 report through it last week and that was... genuinely impressive. Saved my compliance team probably two days of work.

+1Kendra calls Comply v2 genuinely impressive and says it saved her compliance team about two days. · compliance reporting

Oh, that's great to hear — I'm really glad that landed well. The Comply v2 team worked really hard on that launch. Were you able to use any of the other frameworks, or was it primarily SOC 2 for now?

Okay. So help me understand — if we could demonstrate, concretely, that the reliability issues with Detect are resolved and we could do a proper optimization session to address the alert tuning, is that enough to keep you from switching, or is there something more fundamental going on here?

That's a hard question to answer right now. I think — look, we're not trying to blow up our entire security stack. Switching vendors is painful and expensive and my team doesn't have bandwidth for a big rip-and-replace. So if Aegis can get its act together on Detect, yeah, there's a path. But I need to see it, not just hear about it.

That's fair. And I think show-don't-tell is the right framing here. What if we set up a dedicated technical session — I'm thinking bring in our Detect product team directly, not just a CS overlay — and we go through your specific environment, your alert configuration, and do a live walkthrough of what the redundancy architecture looks like now post-March?

Yeah, I'd be open to that. I just — I don't want it to be a sales demo. My team has sat through enough of those. I want it to be a real technical conversation where my engineers can ask hard questions.

Completely understood. I'll make sure it's the right people in the room — we'll bring the engineering lead who actually implemented the circuit breaker changes. No slides, just architecture diagrams and your real config.

Okay. That would help. And Aisha, I do want to be honest — SentinelShield is probably going to come back to us with a pricing proposal in the next week or two. So we're not in a wait-forever situation here.

-1Kendra warns SentinelShield may bring a pricing proposal soon and that Brightpath is not in a wait-forever situation. · competitive alternative

I'd say we need to have a clearer picture by mid-May. Our current Aegis contract comes up for renewal in July and I don't want to be scrambling at the last minute either way.

Okay, that's helpful. Mid-May gives us enough time to do this right if we move quickly. Can we target the technical session for sometime in the next two weeks? I'm thinking early May at the latest.

Yeah, early May works. Let me check with my lead engineer — her name's Priya — and I'll have her connect with you directly to get something on the calendar. She'll know better than me what questions she wants to dig into.

Perfect. And honestly, Kendra, I just want to say — I understand the frustration. What happened in March was serious and you're right to hold us accountable. I'm glad you're still willing to have this conversation rather than just, you know, walking away.

I mean, we've had a decent working relationship for two years and I'm not trying to blow that up for no reason. But I have to make the right call for Brightpath. So — yeah. Let's see what the technical session looks like.

Absolutely. I'll send you a follow-up email today summarizing what we talked about — the technical session plan, who we'll bring from our side, and the timeline. And I'll loop in Priya's contact info too.

Absolutely, I'll get the engineering post-mortem and the architecture change doc — the real ones — and include those in the follow-up. No marketing fluff.