Well that was quite the week at SecTor 2023! My voice was 100% gone at this point and I could barely whisper. Luckily, these two colleagues picked up the slack! I figured Rebecca's perspective would be very interesting as she jumped into this week with a learning attitude. In this video, she recaps things she learned like: ✅ APIs are like entrances to your house and shadow APIs are undiscovered opening which can allow in things you might not want in your house ✅ Managing security products used to be very different! From the consoles you used to the way some of them were deployed ✅ And you can tell someone's age by how they react when you mention Sun Solaris ☀️😂 Thanks @therealcipherk1 for jumping in! Thank you to everyone who stopped by our booth! And thank YOU if you've been watching along with the content! @F5 @DevCentral #AForceFor #GettingMyVoiceBack

🚴‍♂️ How do you know someone's a Peloton rider? They'll tell you 😂 And I've known @therealcipherk1 long enough to know he rides a Peloton many times over 😆 🧐 But did you know what you can find out about a Peloton rider through their API? Peter went over the details in his talk at #EdmontonBSides 🔐 There's an API for everything these days, which means that security for those APIs has certainly kept up, right?? 🫠 😀 Really fun stories shared by Peter. If you get the opportunity to watch him give this talk at an upcoming event, I suggest you do. For now, if you didn't watch it in Edmonton, he shares some of the key takeaways in this video. @F5 @DevCentral @NGINX #AForceFor #KnowingWhoRidesPelotons

We caught up with @therealcipherk1 to hear what he's been seeing so far at @RSAConference 2023 and some security automation that he's tackled recently.

Do you have an #app or client stuck in the previous decade? Check out @therealcipherk1 's article and why JWT is becoming the preferred modern authentication method: go.f5.net/gjhl9u

You got 30 minutes to grab coffee and a snack for What is @threatstack? @therealcipherk1 joins @jasonrahm and @buulam to share what Threat Stack does and why it matters. Today 9:30AM PT here: go.f5.net/947rd4

Article is just the facts - other than linking to his own whistleblower article, he makes zero mention of the possible side effects of publishing information from someone he believed to be an inside source at the time. Is it because he still doesn't want to expose his source?

RT F5Labs "A look at multi-cloud security strategies, including the emerging practices of omni-cloud, functions as a service, containers as a service, cloud security posture management, and data sovereignty. @dunsany with @therealcipherk1 and @lmacvi… x.com/F5Labs/status/14552523…"