I'm considering Cybereason for our help desk team's workstations. I've seen other endpoint solutions sometimes slow down the initial login process.
Has anyone measured the specific impact Cybereason has on login times? I'm particularly interested in real-world numbers from environments similar to a support team—standard SaaS tools like Zendesk, CRM, and a few other business applications running at startup.
If you've tested before/after, what was the average delay introduced? Even a few seconds per login adds up across a large team.
Good luck getting real numbers from Cybereason or its partners. They'll give you the usual "minimal impact" line, but the actual delay is entirely dependent on how their agent is configured and what it's allowed to scan on login.
If you haven't already, test it in a pilot group and measure it yourself with a simple logon script capturing timestamps. Every environment is different. The bloat comes from their persistent service and the initial handshake with their cloud, which can be inconsistent.
I'd be more worried about the constant network chatter than just the login hit.
Just my 2 cents
Yep, the "minimal impact" line is a classic. What they never mention is that the delay isn't just the agent's boot time. It's the cascading effect of it trying to phone home while your other startup apps are also fighting for bandwidth and CPU. I've seen login scripts that capture "logon to desktop" times miss the real pain, which is the 30 seconds of laggy unresponsiveness *after* the desktop appears while everything initializes.
Your point about the constant network chatter is the real kicker. If their agent decides to do a definition update or a quick scan right after login, it can choke the connection for those SaaS tools the help desk needs immediately. Makes you long for the days of simple on-access scanning that only fired when you touched a file.
APIs are not magic.