For Service Providers, Universal Customer Premise Equipment (uCPE) is getting more interesting every day. IHS Market analyst, Michael Howard, said in a recent SDxCentral article that “the uCPE [universal customer premises equipment] phenomenon is an almost perfect storm of five trends, whether it is white box, grey box, or more proprietary. This new uCPE market is resulting from enterprise demand that virtualized security functions reside physically inside the walls of enterprise locations.” The trends that Howard cites are:
The world is changing; it always has but the world is changing faster now than it ever has before. This general change is translating into even bigger changes in the cyber world. Some of the key areas that are evolving aren’t new, like availability or security. Others like automation are maturing quickly, and then there is the ever-present need for “easy.” Easy is a nebulous term, but in this case it refers to ease of procurement, ease of set up, flexibility in platform and ease of ongoing management.
This accelerated change is being driven by different market and business drivers. Some of the key market drivers are compliance, time to market, cyber loss risk, and increased competition around the user experience. This change is acutely felt in the ADC space.
Recently I spoke on security in Austin at the Big Communications Event, where Verizon announced their uCPE (Universal Customer Premise Equipment) platform. Notably, they are choosing a white box platform from Adva running Openstack on a generic Linux server with a KVM hypervisor. Verizon’s new platform will enable them to deploy the device as a generic piece of NVFi to host any VNF in this generic Linux/KVM/Openstack environment. If successful, this gives Verizon huge flexibility to configure and deploy new services completely remotely via SW and remove one of the major cost drivers of Carriers: deployment and maintenance of CPE.
Imagine browsing your favorite websites on your computer or playing a browser-based game when things start slowing down. You click the window in frustration hoping that the site responds, to no avail. Finally, the browser alerts you that something is making it run too slow and you need to reset it.
In the year 1453, the Ottoman Empire under Sultan Mehmed II was able to accomplish what none before them had ever been able to achieve. For more than a millennium, Byzantium had remained a bastion of the Orthodox faith, the great kingdom of the East. The hordes and barbarians that had caused the downfall of so many other empires had been unable to conquer this unconquerable city. Until one day when it all changed.
I remember when I first learned about Web application firewall technology. It seemed like magic to me: A device that could compensate for bad coding or unexpected/unintended web application functionality. It could do this by learning expected application behavior and then enforcing said behavior, even if the application itself was capable of allowing the unwanted behavior. The business case for such a technology is easily recognizable even more so today than it was in the mid- to early 2000’s when it first came out: the ability to have a device compensate for human error.
In this blog post we will cover the basics of building a truly resilient network where throughput isn’t always important, but reliability and redundancy are. We will look at this from the operators’ stand point.
Public clouds are great for managing applications and data without the frustration and expense of supporting the underlying infrastructure. When I lease a car, I am able to use it for the standard tasks that I perform. Functionally, the car is able to do the same things as a vehicle that I could purchase. I can run errands, drive to work, or even take trips.
One of the main advantages of leasing the car is that when there is a problem or maintenance needs to be performed, I am not responsible. The automobile dealer where I leased the car from handles all of those tasks. Oil changes, filter replacements, and all significant work to keep the car running well is taken care of without my intervention beyond bringing the car in when requested.
Security is an ever-evolving concept in theory and application. It is important to deploy and leverage technologies that can adapt and change with our security models. In the technology world, when the networking and application protocols were initially developed, minimal thought was given to security. Protocols like Telnet, FTP, DNS, SMTP, and even HTTP were designed for function and user-experience, not integrity.
I recently met with a regional cloud service provider (CSP) that has adopted provisioning on demand as their IT model. They spin up applications on demand, having virtualized most of their infrastructure and have developed tools to automate the provisioning of applications and servers for customers/tenants through a self-service portal. Rather than build-out and manage more and more physical infrastructure, with associated time and expense, the CSP is adopting the concepts of software-defined data center (SDDC) that builds on virtualization (of software, networking and storage) to offer software and network services for many different clients. More importantly, the CSP is also catering to needs of DevOps and IT architects – both internally, and externally for its tenants/clients by enabling true self service through automation.