Network Dictionary – Security Blanket Failure
Define "Security Blanket Failure"
The post Network Dictionary – Security Blanket Failure appeared first on EtherealMind.
Define "Security Blanket Failure"
The post Network Dictionary – Security Blanket Failure appeared first on EtherealMind.
One of my kids recently asked me whether I plan to travel somewhere during the autumn. The answer was “a bit” surprising: Boston (just got back), Zurich, Bern, Stockholm, Ljubljana, Heidelberg, Nuremberg, Rome, Miami, Ljubljana, Helsinki, and maybe Munich and/or another trip to Zurich… so I might not be able to blog as frequently as usual.
Most of those trips are public events (hyperlinked). If you’re anywhere close one of those cities, check them out and drop by.
Let’s assume we have a Branch with 1 Router and 2 WAN connections. We decide to use Intelligent Path Control with PfRv3 and design our policy such that the business critical traffic goes over one of the WAN clouds (MPLS, for example) and will use the other WAN cloud (Internet, for example) should a certain level of impairment (delay, loss, jitter) occur on the primary path.
But that business critical traffic is well….. critical to your business. So that probably isn’t really good enough. Let’s take this a couple steps further to make sure your business critical traffic is treated as such.
With Intelligent Path Control with PfRv3 what will actually happen is that while the business critical traffic is going over the primary channel, a backup channel will be created over the other WAN cloud. On top of that, PfRv3 will be checking the health of the path the backup channel is taking. Actually… let me be even more specific. PfRv3 will be checking the health of the exact path that business critical traffic would take if it were to be sent over the fallback WAN cloud.
“How is this accomplished?
Regardless of hashing algorithms Continue reading
NFV must move beyond that familiar, ubiquitous ETSI diagram.
The hosting firm's security tools start reaching into Azure, with other clouds to follow.
Software Defined Networking, and it’s latest incarnation SD-WAN seem to be all the rage at the moment. Having seen presentations from vendors large and small on the subject recently at Networking Field Day 10 I am still given to thinking there are a few things that get glossed-over by the vendors quite often. Foremost in my mind, is this (potentially heretical thought):
It is all very well creating virtual or ‘overlay’ networks which run over other networks to suit your purposes, but as someone famous once said, you can’t change the laws of physics. Packets must ultimately flow across a medium – wires, fibres or waves. The media doesn’t give a flying fart whether the packet is naked, or clothed in layers of MPLS or GRE headers – if that medium is congested and doesn’t support any form of packet prioritisation, your data is down the dunny.
There’s a trade-off here that perhaps not many people understand when they are shown smooth presentations by manufacturers. It seems to me that:
Software Defined Networking, and it’s latest incarnation SD-WAN seem to be all the rage at the moment. Having seen presentations from vendors large and small on the subject recently at Networking Field Day 10 I am still given to thinking there are a few things that get glossed-over by the vendors quite often. Foremost in my mind, is this (potentially heretical thought):
It is all very well creating virtual or ‘overlay’ networks which run over other networks to suit your purposes, but as someone famous once said, you can’t change the laws of physics. Packets must ultimately flow across a medium – wires, fibres or waves. The media doesn’t give a flying fart whether the packet is naked, or clothed in layers MPLS or GRE headers – if that medium is congested and doesn’t support any form of packet prioritisation, your data is down the dunny.
There’s a trade-off here that perhaps not many people understand when they are shown smooth presentations by manufacturers. It seems to me that:
Brad Smith will be a big voice in the future of cloud security policies, globally.
Come join Brocade for their DemoFriday on October 16th at 10:00am PT to discover a new and easy way to manage application growth that can significantly reduce your current cost structures.
Cisco ACI offers an elegant new approach to microsegmentation that makes it a powerful tool for security or network administrators.
Co-founder Umesh Mahajan takes the CSO role as the L4-7 startup braces for growth.
Join major industry thought leaders for an exciting conversation surrounding some of the hottest topics in SDN.
Reportedly Uber has grown an astonishing 38 times bigger in just four years. Now, for what I think is the first time, Matt Ranney, Chief Systems Architect at Uber, in a very interesting and detailed talk--Scaling Uber's Real-time Market Platform---tells us a lot about how Uber’s software works.
If you are interested in Surge pricing, that’s not covered in the talk. We do learn about Uber’s dispatch system, how they implement geospatial indexing, how they scale their system, how they implement high availability, and how they handle failure, including the surprising way they handle datacenter failures using driver phones as an external distributed storage system for recovery.
The overall impression of the talk is one of very rapid growth. Many of the architectural choices they’ve made are a consequence of growing so fast and trying to empower recently assembled teams to move as quickly as possible. A lot of technology has been used on the backend because their major goal has been for teams to get the engineering velocity as high as possible.
After a understandably chaotic (and very successful) start it seems Uber has learned a lot about their business and what they really need to Continue reading