Although vendor-written, this contributed piece does not advocate a position that is particular to the author’s employer and has been edited and approved by Network World editors.
It’s a cliché, but “change is the only constant.” Every company periodically reviews and makes changes to their applications, processes and solutions they use to conduct business. And nowhere is this rationalization more important than in the ever-shifting and increasingly perilous arena of cyber security.
Companies often begin the security rationalization process after accumulating a portfolio of tools over the years (i.e. penetration testers, web-application, and code scanners) or through mergers and acquisitions or shifting business strategies.
To read this article in full or to leave a comment, please click here
Traditional perimeter-based approaches to security are not enough to protect against increasingly sophisticated attacks that engineer their way into internal networks. Juniper introduces software-defined secure networks, a new model that integrates adaptive policy detection and enforcement into the entire network.
In today's WAN, network administrators need to complement traditional SNMP-based tools with active monitoring. NetBeez lets administrators constantly monitor end-to-end connectivity and performance for every site.
The post Simplifying WAN Complexity With Active Monitoring appeared first on Packet Pushers.
In today's WAN, network administrators need to complement traditional SNMP-based tools with active monitoring. NetBeez lets administrators constantly monitor end-to-end connectivity and performance for every site.
The post Simplifying WAN Complexity With Active Monitoring appeared first on Packet Pushers.
Here he comes to save the day! Serving, protecting, and troubleshooting -- 24-7-365.
This post was written by Marek Vavruša and Jaime Cochran, who found out they were both independently working on the same glibc vulnerability attack vectors at 3am last Tuesday.
A buffer overflow error in GNU libc DNS stub resolver code was announced last week as CVE-2015-7547. While it doesn't have any nickname yet (last year's Ghost was more catchy), it is potentially disastrous as it affects any platform with recent GNU libc—CPEs, load balancers, servers and personal computers alike. The big question is: how exploitable is it in the real world?
It turns out that the only mitigation that works is patching. Please patch your systems now, then come back and read this blog post to understand why attempting to mitigate this attack by limiting DNS response sizes does not work.
But first, patch!
Let's start with the PoC from Google, it uses the first attack vector described in the vulnerability announcement. First, a 2048-byte UDP response forces buffer allocation, then a failure response forces a retry, and finally the last two answers smash the stack.
$ echo "nameserver 127.0.0.1" | sudo tee /etc/resolv.conf
$ sudo python poc. Continue reading
A look at the vendor-neutral WiFi certifications offered by the Certified Wireless Network Professional program.
Hopes run high for 5G at Mobile World Congress as the industry awaits a standard for the emerging technology.