The traditional security model has put significant emphasis on what’s typically called the ‘external edge’. That is, the connection between your network and any third party network. This is also where we create a delineation between ‘trusted’ and ‘untrusted’ networks. Regardless of how you define this boundary, it becomes the focal point for any security related tooling. This creates some interesting challenges…
Scale – Applying security tooling at the external edge introduces some possible scale concerns. You now have a single point in the network has to scale to provide connectivity and security services to all of the users and applications. While this might make sense in smaller networks, aggregating everything in one place on larger networks can be challenging. Considering that many security tools can handle significantly lower amounts of traffic than routers and switches, you may find that doing this all in one place introduces a bottleneck in the network. Scaling security appliances is often a much larger task than scaling network links.
Network magic – I often joke that network engineers have to perform network magic to get all of the security tools all of the traffic they Continue reading
It's also integrated some of its VNFs with Oracle.
Placing an NFV bet on the virtual CPE.
Hi All, I left Amazon in late 2015 to become an independent contractor. I took a contract working for a small managed service provider, which was closer to my home and offered a more family friendly schedule. It wasn’t an easy … Continue reading
The post Thoughts on leaving Amazon appeared first on The Network Sherpa.
Read about the programmatic & policy-based future of security. Right here, right now.
Brain Gracely, chair of Interop's Cloud Connect track, discusses how enterprises can make the most of public and private cloud, while containing costs, supporting business growth, and ensuring application quality.
Learn more about the Cloud Connect program and register for Interop, May 2-6 in Las Vegas.
Since Parse's big announcement it looks like the release of migration guides from various alternative services has died down.
The biggest surprise is the rise of Parse's own open source Parse Server. Check out its commit velocity on GitHub. It seems to be on its way to becoming a vibrant and viable platform.
The immediate release of Parse Server with the announcement of the closing of Parse was surprising. How could it be out so soon? That's a lot of work. Some options came to mind. Maybe it's a version of an on-premise system they already had in the works? Maybe it's a version of the simulation software they use for internal testing? Or maybe they had enough advanced notice they could make an open source version of Parse?
The winner is...
Charity Majors, formerly of Parse/Facebook, says in How to Survive an Acquisition, tells all:
Massive props to Kevin Lacker and those who saw the writing on the wall and did an amazing job preparing to open up the ecosystem.
That's impressive. It seems clear the folks at Parse weren't on board with Facebook's decision, but they certainly did everything possible to make the best Continue reading
The post Worth Reading: How to Defend Your Backlog appeared first on 'net work.