An end-user’s perspective on open hardware and software.
Hopefully, you have heard the news today! We couldn’t be more excited to announce the general availability of VMware AppDefense, our new security solution. AppDefense bolsters the micro-segmentations threat prevention capabilities delivered by NSX with data center endpoint threat detection and response. It’s no secret that organizations are spending more money than ever on security. It’s also no surprise that the only thing outpacing security spend are the losses due to security breaches. At VMware, we believe the struggle organizations face in gaining the upper-hand in this battle is due to a foundational architectural gap that creates misalignment between the infrastructure where security is applied and the applications that security is designed to protect.
NSX was the first step toward re-aligning network security policy with applications by leveraging the virtualization layer to enable micro-segmentation, as well as enhance the posture of other security solutions through integrations and features like service insertion and guest introspection. But applications are made up of both networks and data center endpoints like VMs. AppDefense is the other half of the puzzle. Whereas NSX prevents threats from moving freely throughout the network, AppDefense detects anything that does make it to an endpoint and can automatically Continue reading
Edge computing will require "a new kind of cloud," Michael Dell said.
AppDefense integrates with several technology partners including IBM Security, RSA, Carbon Black, SecureWorks, and Puppet.
The systems integrate Dell EMC hardware and VMware software.
Accenture, Sysco, Adidas, Medtronic, and Moody’s are early-access customers.
Last Friday, 25 August, a routing incident caused large-scale internet disruption. It hit Japanese users the hardest, slowing or blocking access to websites and online services for dozens of Japanese companies.
What happened is that Google accidentally leaked BGP prefixes it learned from peering relationships, essentially becoming a transit provider instead of simply exchanging traffic between two networks and their customers. This also exposed some internal traffic engineering that caused many of these prefixes to get de-aggregated and therefore raised their probability of getting accepted elsewhere.
Initial public cloud support is limited to AWS and Azure environments.
Conversely, Google will take advantage of Marketo's Engagement Platform.
VeloCloud's latest members include Symantec, VMware, and Forcepoint.
The post Worth Reading: The rise of info-monopolies appeared first on rule 11 reader.
At 03:22 UTC on Friday, 25 August 2017, the internet experienced the effects of another massive BGP routing leak. This time it was Google who leaked over 160,000 prefixes to Verizon, who in turn accepted these routes and passed them on. Despite the fact that the leak took place in Chicago, Illinois, it had devastating consequences for the internet in Japan, half a world away. Two of Japan’s major telecoms (KDDI and NTT’s OCN) were severely affected, posting outage notices (KDDI / OCN pictured below).
Massive routing leaks continue
In recent years, large-scale (100K+ prefix) BGP routing leaks typically fall into one of two buckets: the leaker either 1) announces the global routing table as if it is the origin (or source) of all the routes (see Indosat in 2014), or 2) takes the global routing table as learned from providers and/or peers and mistakenly announced it to another provider (see Telekom Malaysia in 2015).
This case is different because the vast majority of the routes involved in this massive routing leak were not in the global routing table at the time but instead were more-specifics of routes that were. This is an important Continue reading