Competitive Response Strategy

No worries. Okay, so, the reason I called this is — we've had three deals in the last two weeks where SentinelShield came up pretty aggressively in late-stage conversations, and I want to make sure we're all aligned on how we're positioning against them going forward.

Is this primarily on the Detect side or is it across the board?

Mostly Detect, honestly. Which is — and I'll be candid here — not a surprise given what happened in March.

Exactly. SentinelShield's reps are apparently going into these late-stage conversations with specific talking points about platform reliability, and at least one prospect — Hartfield Manufacturing — mentioned it directly. They said something like, 'we heard Aegis had some significant downtime recently.'

Sure, yeah. So — the root cause was a single point of failure in the event ingestion pipeline. When the primary node went down, the failover didn't trigger the way it was supposed to, and that created a cascading failure across the processing layer. Total visibility loss was roughly six hours.

Six hours is a long time in threat monitoring.

It is. I'm not going to sugarcoat it. But — and this is important — what we've done since then is we've implemented redundant processing nodes across all three availability zones, and we've added a circuit breaker pattern that will isolate a failing component before it can cascade. So the architecture is fundamentally different now.

Yes, it went into production — I want to say March 29th? March 30th. Kevin, you were closer to that, do you remember the exact date?

March 28th, I think. I can double-check but yeah, it's been in production for a couple weeks now.

Good, okay. So we have a real story to tell there. The question is how do we tell it without it coming across as defensive.

Okay. Let me shift gears slightly — Jordan, you've been doing some work on how Comply v2 fits into the competitive picture. Since we literally just launched three days ago, I'm curious what you're seeing.

Yeah, so — Comply v2 is actually a pretty strong differentiator right now because SentinelShield and VaultEdge both have compliance features but they're more of a bolt-on. Like you can tell they didn't design around compliance workflows from the ground up. What we launched on April 7th — the on-demand reporting for SOC 2, PCI DSS, HIPAA, ISO 27001 — that's all native, it's integrated directly with the detection and identity layers.

Right, and from a design standpoint the report generation flow — you can go from selecting a framework to a full exportable report in, um, something like four clicks. That's not an accident, we spent a lot of time on that. CyberNova, for comparison, their compliance workflow requires like three separate configuration steps just to set up a report template.

Internal, at least for now. We don't have it in any sanctioned competitive collateral yet. But I'm working with marketing to get a competitive battlecard updated — hopefully by end of next week.

That would be really useful. Right now I'm kind of winging it when prospects bring up CyberNova.

Okay so let me just capture some action items here. Tom — is there any chance we can get a one-pager or some kind of technical summary of the March remediation that we can share with prospects? Not a post-mortem, more of a... forward-looking architecture overview?

I can put something together. Give me until end of next week. I'll keep it high-level enough that it's accessible but specific enough that it's credible.

Perfect. And Rachel, for Hartfield specifically — do you think there's still a path there or did SentinelShield lock that one up?

I think there's still a path. Their procurement timeline got pushed to May so we have some runway. I'd want to get Kevin in on a technical call with their infrastructure team and lean into the Comply v2 story since they're mid-SOC 2 audit right now.

Oh that's — yeah, that's actually a really good angle. If they're mid-audit and we can show them on-demand SOC 2 reporting, that's not abstract, that's an immediate pain point.

Exactly. I'll set something up for next week if Kevin you're available.

Yeah, put something on my calendar, I'll make it work.

Okay, I think that's a solid foundation. Jordan, ping me when the battlecard is closer to done. Tom, I'll watch for that architecture doc. And Rachel and Kevin — let me know how the Hartfield call goes. Anything else before we drop?