Weekly Wrap for Aug. 30, 2019: AT&T CEO John Donovan gives his notice; VMware bets the farm on...
The CDN's Edge Computing Platform Service is built on Kubernetes and Docker using a container...
Broadcom claims its PEX88000 family of switches are "ideal for high-throughput and low-latency...
Cisco issued a patch for a critical bug in its IOS XE operating system that could allow a remote...
Who owns the network policy for your organization? How about the security policy?Identity policy? Sound like easy questions, don’t they? The first two are pretty standard. The last generally comes down to one or two different teams depending upon how much Active Directory you have deployed. But have you ever really thought about why?
During Future:NET this week, those poll questions were asked to an audience of advanced networking community members. The answers pretty much fell in line with what I was expecting to see. But then I started to wonder about the reasons behind those decisions. And I realized that in a world full of cloud and DevOps/SecOps/OpsOps people, we need to get away from teams owning policy and have policy owned by a separate team.
Where does the networking policy live? Most people will jump right in with a list of networking gear. Port profiles live on switches. Routing tables live on routers. Networking policy is executed in hardware. Even if the policy is programmed somewhere else.
What about security policy? Firewalls are probably the first thing that come to mind. More advanced organizations have a ton of software that scans for security Continue reading
To many North Americans, Hawai’i is a place of beaches, resorts, surfing, rainforests, and volcanoes — it’s a vacation destination.
But despite its tourism infrastructure and economy, Native Hawaiian communities in the far-flung chain of more than 130 islands face many of the same Internet connectivity challenges as Indigenous communities in Canada and the continental United States. And for a variety of economic, policy and geographic reasons, it is often excluded from efforts to improve access for Indigenous, rural and remote communities.
The Internet Society believes the Internet is for everyone and works with underserved communities to find and create local access solutions in some of the hardest-to-reach places on earth. What’s exciting is that despite the different geographic landscapes, the same community-led solution underway to improve Internet access in the high Arctic could also help Native Hawaiians carve their own path to better connectivity.
That’s why, in 2019, the Internet Society is holding its third annual Indigenous Connectivity Summit (ICS) in Hawai’i.
Including Indigenous voices in the planning and solutions that shape the Internet is a vital part of closing the digital divide. Previous summits in Santa Fe, New Mexico, in 2017, and Inuvik, Northwest Territories, Canada, Continue reading
There’s always something to learn from other people’s stories so we’re making it a point to spend time talking about past experiences and lessons learned. In this first foray into this format, Nick Russo joins us to talk about a formative leadership experience that happened early in his career and changed his perspective on what leadership and failure looked like.
The post Lessons Learned – Nick Russo – Leadership appeared first on Network Collective.
Today we are announcing the general availability of API Tokens - a scalable and more secure way to interact with the Cloudflare API. As part of making a better internet, Cloudflare strives to simplify manageability of a customer’s presence at the edge. Part of the way we do this is by ensuring that all of our products and services are configurable by API. Customers ranging from partners to enterprises to developers want to automate management of Cloudflare. Sometimes that is done via our API directly, and other times it is done via open source software we help maintain like our Terraform provider or Cloudflare-Go library. It is critical that customers who are automating management of Cloudflare can keep their Cloudflare services as secure as possible.
Securing software systems is hard. Limiting what a piece of software can do is a good defense to prevent mistakes or malicious actions from having greater impact than they could. The principle of least privilege helps guide how much access a given system should have to perform actions. Originally formulated by Jerome Saltzer, “Every program and every privileged user of the system should operate using Continue reading
The post One Way Delay Measurements and NetFlow appeared first on Noction.
After discussing the challenges one encounters even in the simplest networking scenario connecting two computers with a cable we took a short diversion into an interesting complication: what if the two computers are far apart and we can’t pull a cable between them?
Trying to answer that question we entered the wondrous world of transmission technologies. It’s a topic one can spent a whole life exploring and mastering, so we were not able to do more than cover the fundamentals of modulations and multiplexing technologies.
You need free ipSpace.net subscription to watch the video, or a paid ipSpace.net subscriptions to watch the rest of the webinar.
IBM and Orange Business Services top the list of U.K. SDN vendors, according to an ISG report that...
Quest Software unveiled Foglight Evolve, which features three new product lines: Foglight Evolve...