#44 – Security Automation /w Benn Alp

Welcome to episode 44 of, your home of Ranting, Engineers, and Devops, where I’m joined by F5 Networks Global Security Solution Architect, Benn Alp.

Benn brings perspective based on many years of security experience across a range of roles and verticals. Learned in this episode:

  1. DevSecOps is finally getting some traction.
  2. Security vendors have started making more programmable security tooling.
  3. Culture is the most important thing to change in security. Removing the ‘no team’ label often attributed to security practitioners starts within the security team and how they serve the business.
  4. Benn’s arm movements are faster than the YouTube live-streaming frames per second transmission out of ‘Straya.

Enough words, watch now!


Thanks for listening! #40 – 2018 in Review

In episode #40 we take a look at the activity throughout the year.

NOTE: We’re almost at 20,000 views on the youtube channel. Help us get there by clicking play on this video below:

2018’s Posts:

In addition to the creation of two dedicated landing pages for:

Its been an honor creating content for you and I really appreciate the comments/feedback. Keep them coming! And if you have any ideas for episodes, please do get in touch here.

Thanks for listening! #27 – Distributed tracing with Istio on AWS

Ever wondered how you troubleshoot among ephemeral microservices in a container environment? Well, by tracing service interaction, that’s how! And I’m not just referring to outages here, this is also the secret to tracking down performance issues and inefficiencies among microservices.

In this episode I’m joined by Neeraj Poddar from F5 Innovation, Aspen Mesh! If you haven’t caught our previous episodes from the Aspen Mesh, Shawn Worke (their fearless leader) explains what its all about in #23 – Aspen Mesh w/ Shawn Wormke

But if you’re pressed for time and ou just want to know how to trace microservice interactions with Istio on AWS, then waste not another minute and watch this episode:

Thanks for joining us, Neeraj! Youy can find his great blog titled Distributed tracing with Istio in AWS <= there.

Thomas A. McGonagle – Author


My name is Thomas (Tom) A. McGonagle, and I am a new author. You might recognize me from previous REDtalks #16 and #14. I am a new Senior Product Management Engineer working on F5’s Programmability and DevOps. I am a former Field Systems Engineer based out of Boston, MA. Where I have lived my whole life, and over the last 10 years been devoted to the DevOps movement.

I have been a customer facing engineer my whole career. I was a DevOps strategy consultant at Booz Allen Hamilton and CloudBees the makers of Jenkins. I was a customer facing Site Reliability Engineer at RedHat, and I owned my own Puppet consulting business for three years. At Cloudbees, I had a blog called Field Notes from a DevOps Cultural Anthropologist. One of my favorite blogs, was a blog on Buddhism and DevOps

In addition to my work, I also spend a lot of time working with the DevOps community. I am the organizer of the Boston Jenkins Area Meetup group, which is the largest Jenkins meetup in the world as well as HackerNest the tech social meetup group. I am also active and help with the Boston DevOps meetup group and the F5 user’s meetup group. DevOps community organizing is a passion of mine.

Its an honor and a privilege to be an author on, I am both impressed and passionate about the message and content that Nathan has been able to create. My greatest professional goal is to get NetOps engineers practicing Agile and DevOps. I have been calling this Agile Networking, but we at F5 are coalescing around calling it Super NetOps.

My version of CAMS (Culture, Automation, Monitoring and Sharing) is ACAMS+ (Agile, Culture, Automation, Monitoring, Sharing, PLUS whatever is important to the customer, i.e., Network and Security). I find CAMS and ACAMS+ to be great frameworks for discussing DevOps. They are the core values of DevOps, but not its DNA. Cracking the DNA of DevOps requires a singular focus on teamwork and team mission.

The DNA of DevOps is as follows:

  • Team of coordinated specialists
  • Oriented to a common goal
  • Servant leader providing coordination and communication
  • Empathetic in dealings with others
  • Trust in the rest of the team
  • Dedication to the common goal
  • Selflessness, adherence to the greater good
  • Determination and resiliency in the face of difficulty
  • Honesty with the leader and the rest of the team
  • Commitment to the mission