Harshil Agrawal

Hey IAM folks, if someone polled your co-workers today, how would they rate the authentication experience they have today on a scale of 1-10? Here's what kills the ratings for most enterprises: 1. Inconsistency - Having to use multiple and inconsistent MFA tools to access company apps. 2. MFA Fatigue - Requiring users to re-authenticate or do MFA again when unnecessary 3. Lockouts - When providing the wrong credential or expired passwords lead to account lockouts that stop people from working Only by unifying the authentication experience and streamlining can we ever expect to win over everyone in the company. Here is a diagram of our Authentication Speedway, a map to getting to the most frictionless and highly secure authentication experience for your workers! https://lnkd.in/g92bnSgS

22

Slightly tardy update, but worth the wait. Two weeks ago the New York Kubernetes meetup held a fantastic event at the F5/NGINX offices focused on Earth Day 🌎⚡️🌳 with an all-star cast: ⭐️ Anne Currie, Co-chair of the Green Software Foundation, and author of the new book from O'Reilly, "Building Green Software" ⭐️ Ravi Sarkar, Enterprise CTO - Technology Strategy, Microsoft, and ⭐️ Sergio Méndez, CNCF Ambassador 🗣️ I led a discussion with Anne and the in-person attendees about topics like green maps, dynamic tariffs, and building data centers near renewable power optimized for energy use for certain times and places. 📊 Ravi presented on environmental sustainability as a Green Software Foundation Champion from his position at Microsoft. Focusing on making software's development and use more energy efficient. 🌱 Sergio Méndez presented updates from the CNCF Environmental Sustainability Technical Advisory Group (TAG ENV), including a focus on software that can help detect and perhaps help solve energy-related issues, and many other going on of the TAG. It's a little more encouraging to me than it is distressing, but hey in this critical problem space there's no room for greenwashing. So what can you do to get involved? 1. Continue to follow and if you can attend these New York Kubernetes and Cloud native community meetups, as we'll keep a thread running throughout upcoming events at least in announcement form https://lnkd.in/e4RZKNbN 2. Join and participate in CNCF TAG ENV https://lnkd.in/eCXecdi9 3. Let us know if you have any questions and we'll help point you in the right direction 💖🌳👀

27

2 Kommentare

I cannot recommend this episode of Cloud Security Podcast with Jimmy Mesta 🤙 and Ashish Rajan 🤴🏾🧔🏾‍♂️ enough - but I'll take it further than Ashish does when he points out the Kubernetes sized gap in CSPM. Saying you do cloud security posture management without meaningful Kubernetes support is like saying you provide supply chain security but you don't support code. Yes you run other stuff in your cloud, but Kubernetes is the mission control center of modern applications. If you don't think your organization uses Kubernetes, it's time to talk to your developers as soon as possible, because I guarantee you're using it or a similar container orchestration tool. This is why I'm all in on the future of CDR - all the ignored posture management alerts in the world don't stop a single attack on your most critical infrastructure, only innovators like RAD Security (and the few companies that have dedicated the proper focus to K8s https://lnkd.in/esMY-Kgp) provide meaningful security against modern threats. https://lnkd.in/eHcpVVJi

46

9 Kommentare

Were you impacted by the #crowdstrike issue yesterday? I was looking at my feed this morning and I saw a post from a VP at Microsoft. His post reminded me about the importance of having a good DevOps practice in your organization. Here's an excerpt: "Yes, some human wrote a bad line. Someone can “git blame” and point to a human and it’s awful. But it’s the testing, the Cl/CD, the A/B testing, the metered rollouts, an oh shit button to roll it back, the code coverage, the static analysis tools, the code reviews, the organizational health, and on and on. It’s always one line of code but it’s NEVER one person." This reminded me so much of the reason why I chose to write a book on DevOps. We don't just talk about pipelines, but we talk about everything Microsoft's VP mentioned up above. Mistakes like the CrowdStrike issue shouldn't happen. Now, more than ever, having a good DevOps/SDLC strategy is super important. The CrowdStrike issue should have never made it to production. Luckily for you, I just published a book on DevOps with the Atlassian tools! If you write software and you don't have a good DevOps strategy in place, make sure you pick up my latest book! Don't be like CrowdStrike!

39

10 Kommentare