Skip to content
Switched from Perim...
 
Notifications
Clear all

Switched from Perimeter 81 to Netskope - worth the extra cost?

1 Posts
1 Users
0 Reactions
3 Views
(@devops_rookie_james)
Estimable Member
Joined: 1 month ago
Posts: 116
Topic starter   [#13172]

Hey everyone, been lurking here for a bit. This is my first post, so go easy on me 😅

I'm a DevOps engineer, and we recently migrated our team's secure access from Perimeter 81 to Netskope. The shift was driven by our security team wanting tighter integration with our existing cloud security posture tools. The technical migration wasn't too bad, but the cost jump was... significant.

From my operational view, Netskope's CASB and real-time inline protection for our SaaS apps (like GitHub and our CI/CD tools) is definitely more granular. I can set policies based on specific actions, which is cool. But I'm still trying to quantify the "worth" part.

Has anyone else made a similar switch? I'm curious about:
- Real-world performance impact, especially on CI/CD pipeline agents that fetch dependencies. We saw a slight latency increase initially.
- Whether the advanced data loss prevention features are something you actively use day-to-day, or if it's more of a compliance checkbox.
- If the cost is justified mostly for the enhanced cloud app visibility, or if there are operational benefits I might be missing from a deployment/automation angle.

Here's a super basic example of the kind of policy I'm now able to write that I couldn't before, which is neat:

```json
{
"action": "block",
"applications": ["github-enterprise"],
"activities": ["upload"],
"conditions": {
"data_profile": "source-code",
"destination": "external"
}
}
```

Would love to hear from teams who've lived with Netskope for a while. Does the extra cost feel like it pays for itself, or do you start hitting diminishing returns quickly?


Learning by breaking


   
Quote