Skip to content
Notifications
Clear all

Hot take: SentinelOne is fantastic for endpoints, but look elsewhere for cloud.

3 Posts
3 Users
0 Reactions
0 Views
(@jasonb)
Estimable Member
Joined: 1 week ago
Posts: 115
Topic starter   [#5164]

Just finished a 6-month rollout of SentinelOne across our endpoints. The visibility and threat-hunting are top-notch. Blocks stuff instantly, and the dashboard is super clean. Big win for our laptops and servers.

But here's my hot take: when we tried extending it to our cloud workloads (AWS mostly), it felt... bolted on. The cloud security module just didn't have the same depth. We ended up keeping S1 for endpoints and using a dedicated CSPM tool. The cost for the full suite was hard to justify when we only needed half of it.

Anyone else run into this? Love it for one area, but had to supplement for another?

— Jason


Let's build better workflows.


   
Quote
(@kubernetes_wrangler_42)
Estimable Member
Joined: 2 months ago
Posts: 64
 

Totally see where you're coming from, Jason. We had a similar split - SentinelOne has been a rock for our physical and VM endpoints, but the cloud agent felt like an afterthought in our Kubernetes clusters.

It struggled with the ephemeral nature of workloads and the deep context we needed around pod identities and network policies. The alerting was noisy without the cloud-native context a tool like Wiz or Orca provides.

What dedicated CSPM did you land on? I've found that pairing S1 with a purpose-built cloud tool, even though it's another dashboard, gives us the layered defense we actually need.


yaml is my native language


   
ReplyQuote
(@ci_cd_plumber_99)
Estimable Member
Joined: 4 months ago
Posts: 112
 

You've nailed it with the Kubernetes struggle. The agent wasn't designed for cattle, it was built for pets. Trying to force-fit it into a pod that might live for 90 seconds just creates configuration drift and blind spots.

We landed on Palo Alto Prisma Cloud for the CSPM/CWPP piece. It's not cheap, but the context it has on IAM roles, container image layers, and network flow between services makes the alerts actually actionable. SentinelOne's console would scream about a process calling out to an IP, but Prisma could tell me it was a frontend pod, using its assumed role, trying to reach a public S3 bucket it shouldn't have access to.

It's another dashboard to manage, true, but I'd rather have two tools that each excel than one "suite" that does half the job poorly. The sales rep hated that answer.


Speed up your build


   
ReplyQuote