Keith Dale

Big thanks to Brian Jimerson for sharing his perspective on Agentic Workloads in the Cloud Native Landscape at the Cincinnati Cloud Native Meetup last night! My big takeaway is that there are still problems to be solved in this space, especially in relation to security, but that we've solved these types of problems before. Brian did a great job drawing a parallel between the transition to microservice architectures and the transition to Agentic Workloads. We had to solve for distributed authentication and authorization with microservices, and that same problem exists, with even more risk, for autonomous agents. The Cincinnati Cloud Native Meetup will take a break for the holidays and return next year with a new series!

8

2 Comments

Is your IT strategy actually driving business growth, or just keeping the lights on? Many SMBs in Columbus spend thousands each year on tech but still face slow systems, security gaps, and wasted budgets. The issue isn’t the tools, it’s the lack of the right consulting partner. In our latest blog, we break down how the right IT consulting in Columbus can align your technology with business goals, strengthen cybersecurity, and future-proof your operations. Learn how to choose a partner who’s more than a vendor, one who helps your business scale confidently. 👉 https://lnkd.in/ghpw9UVM

2

Developer experience significantly impacts delivery speed, particularly at scale. {unscripted} is rolling into Chicago with an all-star panel featuring Travis Gosselin (SPS Commerce), Murray Butler (Thrivent), and Sreenath Gotur (Amazon Web Services (AWS)) to discuss how they’re rethinking internal tooling with platform engineering and AI at the center. From developer portals to API-first automation, they’ll share how treating developers like customers helps reduce friction, drive adoption, and unlock smarter workflows. Can't join us in Chicago? View the full list of cities and our virtual event. 👉 https://lnkd.in/gfp4SMfd

2

“There’s an RFC for that.” That’s something my colleague and resident networking genius, [Redacted], says right before my brain prepares for impact. We were in the middle of a migration from static routing to dynamic (BGP) when [Redacted] casually dropped, “You should probably be aware of the evil bit.” Now, I didn’t say it out loud (because I didn’t want to sound stupid), but my first thought was: “What the heck is the evil bit?” As usual, Jefferson had an RFC ready — RFC 3514: “The Security Flag in the IPv4 Header” — also known as the evil bit. For context, this is a 2003 IETF April Fool’s RFC that defines a “security flag” in IPv4 packets. Here’s the gist: If the evil bit = 0, the packet has no evil intent. If the evil bit = 1, the packet has evil intent, and secure systems should defend themselves accordingly. Problem solved, right? If only malware authors were this honest. [Redacted] went on to explain (somewhere between BGP sessions and Palo Alto configs) how “firewalls and IDS would love if that bit were real.” I nodded thoughtfully… and maybe zoned out somewhere between “autonomous systems” and “Border Gateway Protocol.” Later, I replayed the session and caught the gem: “Firewalls, or in our case the Palo Alto Networks PANs, need a way to distinguish between good and bad actors. So, they created the ‘evil bit,’ which gets stripped out of the IPv4 header in AS, but would remain in a malicious payload from an attacker.” Of course, it’s a joke RFC — but it’s also a clever reminder: Security would be easy if bad actors self-identified. Until then, we’ll keep doing it the hard way. Live long and route prosper. 🖖 #Networking #BGP #IPv4 #Cybersecurity #PaloAltoNetworks #RFC3514 #TechHumor

1

Claude hits No. 1 on the app store. ChatGPT uninstalls increase by 295%. In the words of Sam Altman, "the optics don't look good".

19

4 Comments