The Dissolving Network Perimeter - And What You Can Do About It!

This should come as no surprise, but the network perimeter is disappearing – or at least it’s getting very blurry. If this is a surprise there’s a chance you’ve been living in a cave or in a coma for the past couple years.
IT security needs to find ways to protect its data while employees are on the move. It’s estimated that about a third of employees have the need or the access to work remotely instead of within the confines of the “traditional office”. Long gone are the days of employees coming into the office to gain access to the data they need.
Today we have employees connecting to the network at customer sites, at home, in coffee shops, etc. Just like the quote from Jurassic Park “Life will find a way”, users will always find a way to get the data they want. Not only are employees connecting to the network from a variety of locations, but they’re doing so on a multitude of different devices like smart phones, tablets and laptops.

 Read the rest at: http://blog.algosec.com/2012/04/the-dissolving-network-perimeter-and-what-you-can-do-about-it.html

State of Network Security 2012

The “State of Network Security 2012” survey was conducted by Algosec.com to analyze security risks and operational challenges, and gauge the effects that next-generation firewalls (NGFWs) are having upon IT security professionals’ workload.

While malware attacks continue to make headlines, today’s security teams are more concerned with the risk from poor internal security processes and insider threats. Adding to this challenge of managing security policies is the adoption of NGFWs, which is adding even more scale and complexity. As NGFWs are adopted more widely, IT Security and Operations teams will need to carefully evaluate the costs and benefits, and plan improvements to their firewall management policies, to avoid increasing security risks and the costs of preventing them. Click to read more on Algosec.com research:

http://www.algosec.com/en/resources/network_security_2012 

Same old, same old from Verizon Breach Report