There's only going to be one episode 128 of IPv6 Buzz, and this is it. In this Cisco Country Digital Acceleration Program sponsored episode, co-hosts Ed Horley and Scott Hogg talk with Pradeep Kathail and Mark Townsley. Pradeep is the CTO of Enterprise Networking, and Mark Townsley is a Cisco Fellow in the Meraki Business Unit.
The post IPv6 Buzz 128: Cisco Enabling IPv6 In The Enterprise (Sponsored) appeared first on Packet Pushers.
One of the common concerns about migrating applications to Kubernetes is the control over the network traffic egressing your environment. Due to its highly dynamic architecture, Kubernetes will not tie a specific IP address to an application by default. Instead, it will lease a different IP address from an IP pool whenever the application restarts.
Suppose you use traditional network security appliances like firewalls to provide network perimeter protection. In this case, enforcing the least privilege principle by allowing only a specific application to egress traffic outside your network is impossible. In a firewall configuration, you must specify the application IP address when creating the egress rule. As it is impossible to determine the application IP address, you must allow access to the nodes’ IP addresses if you are using overlay, or to the entire IP range you use in the IP pool. By doing this, you will also allow access to any application running on that Kubernetes cluster.
Learn more: Kubernetes Network Policy: Code Example and Best Practices
A better option would be to use Kubernetes network policies, which enable you to create rules to allow ingress and egress traffic to a workload based on the labels applied to Continue reading
If you had to rank the level of hype around specific datacenter technologies, the top thing these days would be, without question, generative AI, probably followed by AI training and inference of all kinds and mixed precision computing in general. …
Rest In Pieces: Servers And CXL was written by Timothy Prickett Morgan at The Next Platform.
OpenStack, the venerable open source cloud controller born in 2010 out projects pulled together by Rackspace Hosting and NASA, continues to push on despite its death being predicted myriad times over the past several years. …
Reports Of OpenStack’s Death Greatly Exaggerated was written by Jeffrey Burt at The Next Platform.
Andrei Robachevsky asked me to spread the word about the new MANRS+ customer survey:
MANRS is conducting a survey for organizations that contract connectivity providers to learn more about if and how routing security fits into their broader supply chain security strategy. If this is your organization, or if it is your customers, we welcome you to take or share the survey at https://www.surveymonkey.com/r/BDCWKNS
I hope you immediately clicked on the link and completed the survey. If you’re still here wondering what’s going on, here’s some more information from Andrei:
Andrei Robachevsky asked me to spread the word about the new MANRS+ customer survey:
MANRS is conducting a survey for organizations that contract connectivity providers to learn more about if and how routing security fits into their broader supply chain security strategy. If this is your organization, or if it is your customers, we welcome you to take or share the survey at https://www.surveymonkey.com/r/BDCWKNS
I hope you immediately clicked on the link and completed the survey. If you’re still here wondering what’s going on, here’s some more information from Andrei:
Welcome to this episode of Day Two Cloud! Today, we'll be diving into the world of platform engineering and internal developer portals. Our special guest, Suzanne Daniels, Developer Relations Lead at Port, will be sharing her insights on how platform engineering can take your DevOps journey to the next level. With platform engineering, you can treat technology as a product and developers as customers, resulting in a more efficient and effective workflow.
The post Day Two Cloud 199: Platform Engineering With Suzanne Daniels appeared first on Packet Pushers.
Kubernetes documentation clearly defines what use cases you can achieve using Kubernetes network policies and what you can’t. You are probably familiar with the scope of network policies and how to use them to secure your workload from undesirable connections. Although it is possible to cover the basics with Kubernetes native network policies, there is a list of use cases that you cannot implement by just using these policies. You can refer to the Kubernetes documentation to review the list of “What you can’t do with network policies (at least, not yet)”.
Here are some of the use cases that you cannot implement using only the native Kubernetes network policy API (transcribed from the Kubernetes documentation):
While I was hanging out at Cisco Live last week, I had a fun conversation with someone about the use of AI in security. We’ve seen a lot of companies jump in to add AI-enabled services to their platforms and offerings. I’m not going to spend time debating the merits of it or trying to argue for AI versus machine learning (ML). What I do want to talk about is something that I feel might be a little overlooked when it comes to using AI in security research.
After a big breach notification or a report that something has been exposed there are two separate races that start. The most visible is the one to patch the exploit and contain the damage. Figure out what’s broken and fix it so there’s no more threat of attack. The other race involves figuring out who is responsible for causing the issue.
Attribution is something that security researchers value highly in the post-mortem of an attack. If the attack is the first of its kind the researchers want to know who caused it. They want to see if the attackers are someone new on the scene that have developed new tools and Continue reading
The best defense is a good offense, and as it turns out, the best offense is also a good offense. …
AMD Widens Server CPU Line To Take Bites Out Of Intel, Arm was written by Timothy Prickett Morgan at The Next Platform.