Lumension adds whitelisting solution to its management and security suite

Lumension has integrated intelligent application whitelisting into its endpoint management and security suite.

To sit alongside existing blacklisting and patching abilities, the application control module workflow is managed through a single console and deployed on a single server, single agent architecture.

The company explained that its approach extends beyond simply looking for malicious threats. Instead it determines whether change should be allowed to occur in the IT environment by providing the necessary control to define and enforce security policy without disrupting business operations.

The whitelisting solution is centred on a rules-based trust engine that can define what types of change are acceptable. According to Lumension, by setting up rules around how change can be introduced, rather than focusing solely on what kinds of change should be stopped, a balanced and more effective operational model of endpoint security management can be achieved.

Patrick Clawson, chairman and CEO at Lumension, said: “In the past, traditional application whitelisting approaches were a challenge because it was nearly impossible to anticipate and manage the changing needs of the business. This relegated traditional application whitelisting solutions to very static environments like point-of-sale or server environments where there isn't a lot of change taking place.

“As a result, companies were left with two choices: a reactive endpoint security approach that was efficient but ineffective or a proactive approach what was very effective, but not operational. Nobody was focused on how to bring the best in both approaches together, and manage change in a way that would better meet the needs of the business.”

Paul Zimski, vice president of solution marketing at Lumension, said: “Intelligent whitelisting allows IT to create and maintain a clean ecosystem through an automated, yet flexible, trust model where IT management can automate better risk-based decisions about what can be introduced into an IT environment, who is introducing it, and whether or not they should be allowed to introduce it.”

Sign up to our newsletters