DUP – It’s child’s play!
DUP… It’s easy as 1,2 3!
Okay, that wasn’t my best line, but I hope it served its limited purpose of grabbing your attention.
Over the span of my career, I have seen toolsets come and go in our industry which promise astonishing things. Very rarely, can they deliver on some increasingly bold claims. When Forcepoint unveiled their Dynamic User Protection (DUP) as a SAAS offering, I wasn’t convinced it would be as simple as they claimed. Anyone following the world of Forcepoint can tell you that the UEBA on which DUP is based, is not a simple toolset to deploy. It requires comical levels of hardware and extremely qualified Professional Services (PS) to deploy. It’s in fact so complex, it could not be sold to clients without mandatory Forcepoint PS.
So when we at Gradian were lucky enough to get our hands on it towards the start of this year, I cleared out an afternoon, grabbed a coffee, logged into my portal and got cracking on deploying it within my lab. I knew it would be simple, but grossly overestimated the time I would need. Here’s what happened in my lab environment:
- Logged into portal
- Downloaded the NEO Agent following a pop-up telling me to (my first time login)
- Copied the agent to my lab machine (also running Forcepoint ONE Endpoint)
- Checked the status in my DUP Tenant to see “Installing” as the status for my lab machine
- Rebooted my lab machine and saw the client report into my tenant
And that was it. My coffee was still hot and my afternoon was suddenly free. The NEO Agent communicates with my ONE Agent locally. The ONE Agent feeds all relevant information back to my Forcepoint Security Manager and the NEO agent autonomously updates in the background.
Obviously there are more considerations for an enterprise deployment, such as testing, change requests and pushing the agent to all users, but the takeaway here is that the deployment process really is that simple.