For our first member spotlight of 2022, we’re featuring a person whose numerous and ongoing contributions to the cloudsec community are only part of what make him so delightful. Plus, he’s a Parisian and a hobbyist photographer so double points.

You may know Victor Grenu aka zoph from his 

 service on Twitter or his AWS Security Digest (

!) which we both highly recommend to stay in the know.

In our Q&A with Victor, you’ll learn more about the inspiration behind MAMIP, other projects Victor has up his sleeve, and of course, his thoughts on IAM including what he’d change about default behavior. We also included a list of the resources Victor shares in his Q&A answers.

If you check out Victor’s social media and blog profiles, you’ll notice he has a couple golden mantras: 

Try to be a rainbow in someone else’s cloud

Making things boring with simple automation

. While we agree with the former (joy is one of our IAM Pulse Community principles!), we’d say for the latter that what Victor’s done with MAMIP in particular may be boring to some but we can all agree we wouldn’t want to be without it!

All the kudos to Victor for kicking off this year’s IAM in the Spotlight and sharing more of his background and IAM insights.


What's the technology you're most excited to learn and work with?

K8s. No – just kidding. Generally speaking, AWS security related technologies and I also love to find vulnerabilities on websites / apps I’m using personally. I found a few last year that led to generating a few bug-bounty rewards.

What project are you working on now that most excites you?

I’m working in my free time (so not so much), on a micro-SaaS product around AWS FinOps and waste detection. I hope to open beta test in 2022 and see what is happening next. Small bet.

 who used to run CLI commands on his laptop periodically. I wanted to apply some automation and visibility where cloudsec folks are – on Twitter.

With this new regularity we could spoil services / feature releases from AWS as announcements / blog posts (almost) synchronized to the release / update of corresponding IAM Managed Policies. It also provides us the capability to keep history and see what is happening: release / error / rollback of IAM Managed Policies as everything is on git.

What’s the most surprising notification you received from your MAMIP service?

I think the most surprising notification was SupportServiceRolePolicy and internal AWS policies that have been pushed to public by error. I maintain a 

, to keep track of AWS failures on AWS Managed Policies.

) that provides potential threats over IAM Managed Policies (resource exposure, privilege escalation, etc...).

Describe the strangest AWS environment you’ve walked into on a client job.

A small startup where all resources were on public subnets, “isolated” from each other with subnetting, IAM roles with trust-policies on AWS: “*” and full of AccessKeys/SecretKeys without any rotation. 


We started again from scratch with new accounts setup and deleted this legacy one. Really big time here :)

What motivates you to share your work and expertise with the larger community?

I really like the usage of social media in my daily work, I love to be able to talk directly with the senior leadership team of AWS Security and developers on Twitter.
Asking questions, sharing thoughts with other customers, helping each other is our only option, right?

Where do you think IAM is going to go next?

I think they [cloud providers] will work on simplicity, a more comprehensive language, especially for new comers. They will integrate helpers and tooling that comes from OSS from the community. Policy validation, simulation, better error messages, etc...

I am already talking to AWS IAM teams using Twitter or CloudSecurity Forum (Slack). I am also (for the second year) part of the AWS Community Builders program that allows me to have a privileged communication channel to AWS Teams.

If you could change one thing about how IAM works, what would it be?

I will change default behavior for many things like: 

- Required MFA on root account
- Disable the ability of the root user to create AccessKey/SecretKey
- Better Default password policy
- Encryption by default on many services: SQS, S3, EBS Volumes etc..
- Default to IMDSv2 for EC2 Instances- etc..

What's the one thing companies should be doing that they're not?

Take IAM seriously, and ask help from external consulting firms to outsider feedback on their AWS security posture.

What's the most fun project you've ever worked on?

In my free time I like to participate in CTF especially on hacking conferences. I loved to participate with friends at “TheHack” a French hacking conf. I hope to participate in larger conferences after the pandemic. (CCC, Blackhat, DEFCON).

If computers magically no longer existed, what would you do for a career?

Renovate and open a guest room in one of beautiful regions of France.

, DIY, renovation of an old house (1958), and some woodworking.


MAMIP - Monitor AWS Managed IAM Policies Changes


Adopt a slow-tech approach by reading only essential, digest summary of what is going on in the AWS Security landscape.

What you will find:
- Highlight of the week
- Change since last week on AWS Managed IAM Policies
- Curated Cloud Security Newsletters
- AWS API changes
- IAM Permissions changes
- Most upvoted posts on r/AWS
- Top shared links on Twitter (by cloudsec folks)
- Most engaged Tweets from the community

https://github.com/z0ph/MAMIP/blob/dev/HALL_OF_FAILS.md


Cloud Security Forum on Slack (send a DM to 

IAM in the Spotlight - Victor Grenu

Since we first launched the IAM Pulse community a few months ago, our members have contributed a wealth of knowledge in article form – topics ranging from 

designing least privilege access controls

. We aim to give cloud professionals a platform to share their expertise and build their personal brand in a low effort, high impact way. I’m excited to introduce a new type of technical content that our members can publish, and the community as a whole can engage with – IAM Policy documents.

Policies are the backbone of each cloud provider’s IAM services. They specify 

. Every cloud provider has a unique (and complex) specification for IAM policies, however each can be represented as JSON documents. When designing for least privilege access, it’s best to avoid the defaults, and customize policies to the nature of your workloads and your teams. But have you ever opened up your code editor and stared blankly at where to start? Our IAM Policy Catalog is a place to browse usable and customizable examples to get you on your way.

 is a browsable and searchable index of member contributed IAM Policy documents, filterable by provider and service. Want to keep your team’s permissions fine-grained by tag? Spinning up a Lambda function and want to write a policy for the attached role? Find an example from the community here. Once you find a policy that matches your needs, you can tailor to your environment by substituting the inline variables to your values.

Community members can contribute their own examples to the Catalog through a simple form wizard. Policies are specified for a specific cloud provider, and optionally tagged for services impacted such as Amazon EC2 and S3. Paste your JSON code in the editor and add any documentation as markdown. To help the reader customize, follow the instructions to carve out variables individually. When you’re ready, publish your Policy to get added to the Catalog.

 today. To publish a Policy to the Catalog, membership to the IAM Pulse community is free – 

 to personalize your profile and start contributing your knowledge. Shared learning drives collective intelligence!

A community-led catalog of customizable IAM Policy document examples across AWS, GCP, and Azure.

Introducing the IAM Policy Catalog

Earlier today, Olympia (our Head of Community) and I were guests on 

 Twitter space, where we talked about our take on DevRel, how we're building a community, and what our goals are. Given the broad range of topics, and speaking about our goals, we decided to expand a bit and share a written version here. 

When IAM Pulse approached me to join the Community team, and I imagined myself helping the whole world learn cloud security, I immediately said yes. And then I thought about it, and asked them what that means. DevRel, a function that used to be found only at large companies, has taken off and is growing in popularity. However, if you ask each DevRel practitioner what their job is, you’re going to get a lot of different answers - similar to asking someone who practices DevOps exactly what their job is.

Developer relations and developer advocates come in all shapes and sizes, and focus on different things. As far as I can tell, the role describes:

 - Raise public awareness of a brand and build a network

 - Build things using the company’s tools or platform themselves. They find rough edges public developers would find and use their internal connections to get things fixed up

 - Work to bring users onto a platform in a concrete “users” and “dollars” sense

 - At the forefront of technology, they identify the boundaries of what products can do, and push those boundaries. They advise the product team to integrate any ideas they have

 - Write trainings and build up help docs. Documentation touches a lot of these areas!

 - Answer questions in online forums or respond to customer requests in a customer service-like role

And as with most long-winded explanations, the real answer is closer to “all of the above” (especially at smaller companies!). DevRel means connecting with users of a platform or product, often using social media. Then learning their trials and tribulations with using your platform or tooling, often by testing it out yourself, which can help you become an expert at it. And then potentially helping your dev teams focus on the competitive advantages you see your product having in the market, and telling folks about it. It’s a lifecycle of customer feedback to improve the product and developer experience.

In the same way that DevOps attracts engineers with multiple specialties, DevRel does too. DevOps is being a developer and also knowing how to run services, what we call “Operations.” And DevRel is being a developer and also fostering a relationship with the community at large. 

DevRel is interesting in this very technical field due to it attracting “authentic” people - those that can connect with others and build strong relationships. Often DevOps, or internal development attracts very technical, serious people. They’re folks you can rely on, and who will answer the phone on Saturday night when you very much need them to repair your services. With DevRel, you want engaging, empathetic teachers, folks who have the social skills and patience to take your questions and help you do an even better job in your own career. These folks have outsized personalities, and are often popular on blogging, social media, and speaking circuits, and are often at the top of their fields (or at least their social profile makes it seem that way). 

DevRel, just like DevOps, is rapidly evolving, and it’s fascinating to be a part of it. I hope I am of service to all of you in all the ways I said above, and if you have suggestions, corrections, or want to help push this industry forward, let me know. 

DevRel Without a Platform

What is a Cloud IAM Advocate?

I am so excited to be writing to you today. I just joined the IAM Pulse team as our first Cloud IAM Advocate! My role is an incredibly fun one:

Build secure cloud services and then release the instructions to you for free!

Listen to your ideas about how to use IAM and the creative ways you're solving cloud security in your industries

As many of you know, IAM, or Identity and Access Management, 

 cloud security - they're equivalent terms. Despite the central role of IAM in securing cloud services, it's often treated as a secondary consideration. A sort of, "Once this service is built, 

 you want to secure it properly, you should next think about IAM". The public cloud is amazing, but no service is immune to security problems, and thinking about security as something you do last is a sure-fire way to secure something poorly.

We know cloud security is critically important to every business in every vertical, so our goal at IAM Pulse is to elevate IAM to its own practice. Cloud security shouldn't be seen as a bolt-on, it should be a secure foundation that we build from.

My background is in operations and DevOps in almost every discipline. I've built large Windows domains, constructed call centers, secured enterprise manufacturing and healthcare, executed digital and physical penetration testing, spun up DevOps for applications and infrastructure, and even worked with the US Department of State to build secure solutions in the cloud.

Security is never an optional step. It is absolutely critical to the success and CIA (Confidentiality, Integrity, and Availability) of every network and application I've ever interacted with.

I hope you're nodding along with me! And if you are, you can help us push the state of cloud security forward. As you build secure solutions in the cloud, 

please share your best practices, clever hacks, and novel solutions with me at 

 We would be absolutely thrilled to publish your bright ideas, and elevate you and security to new heights.

You can find me in dozens of places on the web - I keep a directory at 

 or you can reach me at IAM Pulse at kyler.middleton@iampulse.com.

The IAM community is big and amazing, but fragmented because the industry thinks of IAM only within service or resource verticals. We want to help the industry realize IAM is a single discipline. Let's do this.

 to hear more from me - I'm diving into multi-cloud K8s, dynamic IAM based on Terraform reads at compile time, and building a library of IAM security best practices for all of AWS's resources and services. It's going to be awesome.

Kyler Middleton
Cloud IAM Advocate
IAM Pulse

Hello World - Joining the Team as a Cloud IAM Advocate

As a cloud professional, we know you have a lot of thoughts about IAM – good and bad, we get it! Take this brief survey to help guide our focus areas, and we’ll donate $5 to Hack the Hood for your effort.

Closing out the calendar year means wrapping up the last of your todos, while wrapping up the last of your gifts to the family. If you’re like me, you’re racing against time in both cases – let’s just hope the quality of your todos beats the quality of my gift wrapping (read as: poor).

The change of the calendar is also an opportunity to both reflect on the past year (with mostly disdain) and look ahead to the new year (with mostly hope). We’ve learned an immense amount as a team with just a few months of community and content building behind us, and we’re most certainly looking ahead to a helpful and fruitful year.

Our mission is to make IAM simple and accessible for everyone. We’re doing so by finally giving IAM the attention it deserves. If you carry any responsibility for cloud environments – whether AWS, GCP, or Azure – you’ve undoubtedly encountered IAM. And my bet is that you have… thoughts.

We'd love for you to share those thoughts by following this brief survey. It should only take 15-20 minutes, and for every complete submission, 

. That may not sound like a lot, but 1,000 surveys is $5,000 – so take part and then tell all your (fellow cloud) friends!

 is an award-winning non-profit whose mission is to empower low-income youth of color with the knowledge, skills, and relationships they need to pursue careers in tech. Hack the Hood’s core program, “Bootcamp,” teaches coding, design, and 21st century workplace skills to youth ages 16-24 while they build websites for real small business clients.

Take the 2022 Cloud IAM Survey

‘Tis the time of year to spread holiday cheer!

Please consider taking part in some charitable fun!


Share what you’ve learned or mastered in IAM

Whether a puzzling challenge, an ‘a ha!’ moment, or a policy gem.

Putting knowledge into practice is the key.


So capture your thoughts, reflections, and musings

If you need ideas, we’ve got great member content for perusing.

Then pick one of five stellar charities and $100 will be disbursed!


We’ll spotlight each of the five on social media this week

From expanding career pathways to empowering girls in STEM - take a peek.


We’ll also send you some swag, a special First 100 Authors box

Filled with clever, useful goodies (sorry, no Crocs).


We hope you’ll take part in this holiday campaign

Before you fully unwind and pop that champagne!



IAM Spotlighting Five Fantastic Charities

As a startup within Okta’s incubation program, OktaX, our IAM Pulse Team selected these fantastic organizations who are also 

 invests in entrepreneurs who are using technology to accelerate social impact. Fast Forward’s investments span beyond philanthropic funding, through products and programs that bridge the tech and nonprofit sectors to build capacity for tech nonprofits.

 re-engineers the way BIPOC girls from marginalized communities experience STEM by catalyzing out-of-school time (OST) STEM educators and STEM professionals into equity educators and advocates through training and curricula that promote access, belonging and persistence.

 trains and mentors Black male youth in technology creation, entrepreneurship, and leadership skills to transform their lives and communities.

 is increasing the number of low-income, first-generation, and historically under-represented students who graduate from college. In partnership with high schools and colleges, Beyond 12’s technology platform and coaches together provide students with the academic, social, and emotional support they need to succeed in higher education and in life.

 provides pathways to career success for high school students in underserved communities through skills training, meaningful work experiences, and impactful relationships.

Share your IAM knowledge and we'll donate $100 to a great cause 

IAM in the Holiday Spirit

We’re back with a new IAM in the Spotlight featuring one of our OG members, Kyler Middleton, who has been with us since the beginning. Kyler continues to play a key 

(get it?!) as a top contributor to our IAM Pulse Community.

IAM in particular is challenging – it's the cornerstone of all foundational security in AWS, yet it is complex, manual, and prone to errors. That makes it a ripe target for innovation and automation

, hear Kyler’s approach to writing and learning, tackling new puzzles and complexities in the IAM domain, and re-thinking the PR approval process. Kyler also reflects on syncing Azure DevOps to AWS and how growing up on a farm fixing the neighbors’ computers led to rewarding opportunities for professional growth - and payment in delicious brownies. 

After viewing this Spotlight, you’ll understand why Kyler is such a valued member of this community and be sure to check out Kyler’s very detailed and helpful articles too!

AWS IAM: Assuming an IAM role from an EC2 instance

AWS IAM: Share ECR Docker Image and Secrets between AWS Accounts

Terraform Dynamic IAM Policy Construction

How do you approach your writing process and topic selection?

I've been reading and writing my entire life – I noticed early on I could communicate much more clearly and precisely with written words than speaking. So it feels very natural to me to write! I write about the projects at work that interest me. If there's a challenging puzzle to solve, that piques my interest, and I dig into it until it's solved. Then I enjoy teaching others and sharing how I solved it. IAM in particular is challenging – it is the cornerstone of all foundational security in AWS, yet it is complex, manual, and prone to errors. That makes it a ripe target for innovation and automation. I hope I can help solve a tiny bit of this puzzle, and many, many smart people can help take their own bites out of it also! 

In one of your articles, you talk about the challenge of syncing Azure DevOps to AWS. Any tips/tricks for the IAM Pulse Community?

That has been such a fun problem! Microsoft, of course, provides lots more guidance and tooling to help you integrate to their cloud – after all, that's where they make their money. But I've always been more of a "write it myself" person, so I didn't spend even a minute sad that there wasn't a built-in AWS authentication tool, I went out and wrote it myself. We use bash and AWS CLI calls to IAM to authenticate and assume any role we need. 

It was a big project, and it helped me learn a ton about IAM. I'm a big proponent that the best way to learn anything, but particularly cloud, is to just. Go. Do it. That's why all my articles are focused on helping the reader "do" the work. I'm not trying to introduce abstract principles, or vague ideas about what you should build, rather, I'm helping you build whatever you want, using some of the tools and knowledge I've picked up along the way. 

What's currently puzzling you as you work in IAM? If you could get community input on a tough question, what would you ask? 

Why aren't there more tools and automation around IAM from cloud providers? This service is a huge part of cloud security. In the old days in a data center, we had layers of defense – firewalls used different authentication from routers, which were different from servers, which were different from databases. If you wanted to seriously cripple a company you had to compromise many systems. 

Compare that to a cloud environment today – if you can compromise a single administrative IAM user or profile, you can literally delete every resource and all data contained everywhere in a couple of minutes. That's incredibly scary, and I wish cloud providers would confront IAM in a much more serious way. If the tool isn't easy to use, people will make mistakes. And mistakes here have huge consequences. 

If you could wish a new IAM tool into existence, what would it do? 

A tool that provides templates for common usage patterns. If you could describe in plain language that you want to access a container registry in a different account, and it would provide template IAM files to start with, that would be an amazing time-saver, and I don't think would be a huge uplift to build. Maybe that's the future of IAM Pulse and they'll be a library of common use cases and IAM Pulse could host them all for us. We'll just have to see! 

Is there a commonly accepted best practice that you think adds more complexity than it is worth?

I think it's common to have an elite team of PR reviewers that control approvals and have memorized all the security, operational, and naming rules for an organization. Which works great, but there is always drift between team members, and what if those team members aren't available? I love to see new tooling coming out that permits automating this approval process. 

I'm working hard to identify tooling and processes that can safely automatically approve PRs for our infrastructure to avoid this concentration of control into the hands of a few senior staff. This helps to standardize and democratize changes, not to mention potentially making approving much quicker and easier for our developers. This job will never be done - not until computers are more creative and smarter than people, and I don't expect we'll see that for a long, long time. 

How did you get to the position you hold today? Were you always working in this space?

For people that have always known me as a DevOps engineer, it might surprise them to find out I grew up on a farm. Many people don't realize how technological farming has become - farmers are constantly challenged to adopt new technology and processes to improve the efficiencies of their farms. Most operate as independent businesses on the razor's edge of survival, so there's a ton of experimentation that happens. 

They were among the first folks I knew that adopted home PCs. And of course, early home PCs broke - a lot! And they could hardly afford to have someone drive an hour or more to get to their farmhouse to fix it, and bill them however many dollars a mile or hour. Certainly not when there was this quirky kid nearby who'd love to click all the buttons on all their computers, and sometimes even fix things when doing so, and also took payment in brownies. 

I was halfway through a library science degree in college when I found out that computers don't come naturally to everyone, which was shocking to me, which is funny in retrospect and that jobs in computer science pay really well and are a real adult job. I immediately switched my major to IT, but my small college in Nebraska cancelled the computer science program before I could finish. 

I finished with a library science degree, chased my partner to a larger town, took a job at Best Buy, and worked my way into Geek Squad, and read every technical book I could find to get certs and move up jobs. I bounced around to lots of roles - telecommunications, systems, hosting providers, InfoSec. I did my best to understand all I could, automate my entire job away, and then leave to find new challenges. 

I've been up-front with my current manager today - I'll leave when I automate my whole job and so far, I haven't managed to automate it away. But one day I will, or at least I'll try, and then I'll go find some more challenges.

Member interview series

IAM in the Spotlight - Kyler Middleton

The following is a guest blog post from the IAM Pulse Community.

Not so long ago, any business trying to get a competitive edge with technology could not do without dedicated help, whether it was contracted, or an on-staff IT Manager.  But, IT was often poorly understood, and often badly managed--and stereotypically derided as aloof, incomprehensible, and yes, incompetent. And for decades, as the cost of technology has fallen, IT Managers have been asked to do more with less. Now, DevOps and other trends in automation are really putting the squeeze on the IT Manager.

These days businesses can get by without dedicated IT Management. But advances in DevOps, the ubiquity of SaaS offerings and ever increasing advances in automation have not eliminated the need for IT Management. In the absence of dedicated resources, IT Management (including IAM) is a second job for someone in the company: the CFO, the HR Manager, a Principal Engineer, or that entrepreneur building their startup. They have insufficient time and resources to be an “expert” in IAM. Lacking the time and expertise, they struggle to build a safe and manageable IAM system for their business. They struggle to control who has access to their information--they struggle to keep their arms around their own intellectual property.

Identity Access Management (IAM) is such a part of our everyday lives, we seldom give it much thought. It is just a part of the wires, fiber optic cable, and software that are the backbone of the Internet. It is like the roads we drive--there all the time, but generally experienced unconsciously. And like those roads, even with safety measures like traffic lanes, street signs and signals, it can be dangerous.

We know not all drivers obey the rules of the road. Generally, drivers do, but sometimes when they are in a hurry, they run a red light. Sometimes drivers are on unfamiliar roads with unfamiliar rules. And sometimes drivers just make mistakes; they veer left, when they should have veered right. We all make mistakes. For all of these reasons we witness daily pile-ups on our roads.

Like roads without traffic lanes and street signs, the Internet without IAM would be chaos.

Even with IAM the Internet is dangerous! Shortcuts, lack of concern and mistakes lead to some nasty security breaches, not to mention the routine aggravation when users have difficulty getting access to their systems and data.

Learning and implementing IAM is doable, but hard. Tools for IAM are available for larger businesses. When those tools fall short, these businesses can compensate with dedicated technical resources to fill gaps. For your everyday IT Manager, IAM is chock full of technical jargon, complicated certificate management, careful copying and pasting incomprehensible access URLs, and faulty integrations that often fall short of the promise of SSO, and require some manual user provisioning on either the identity provider and service provider side or both

 that is reliable, easy to use and secure. The 

If you’re thinking this declaration is unnecessary because we have SAML or some other existing service or protocol, you’ve missed the point. If so, consider electronic payments for a comparison. You don’t need to understand how the Automated Clearing House (ACH) system works to make an electronic payment. You don’t even need to know there is an ACH system. All you need to do is tell your bank where you want your money to go. Your bank does the work of getting your payment there. In the same manner, we want a 

 will only be a “standard” when it is implemented widely. Wide adoption of the 

amongst the applications services we typically use or an ability to overlay the 

over existing IAM systems is necessary to achieve its benefits.

Adding applications, services and user assignments is as easy as select, commit and go.

When integrating identity and service providers systems will provide. comprehensible error messages when configurations do not work.

User management (provisioning and deprovisioning) will incorporate role, individual and group provisioning over all systems. Today’s integration gaps need to go away.

Please, no tech-speak. If you want an IT Manager to, “to access an API endpoint, to download a metafile and inspect a system’s SAML attributes,” you’ve fallen off the path. We want a 

that incorporates relatable metaphors, in the same way as our computers have “desktops” and “files.”

 by complicated certificate or encryption key management

Certificate management and encryption keys are complex and confusing even for seasoned IT people. Any system that explicitly requires the generation of certificates or encryption keys is fundamentally hard to use. The 

 we want obfuscates the heavy lifting of certificate management.

The goal of a small business is to become a big business. When business outgrows the 

, stepping up to an “advanced IAM model” should be an evolution, not a rip and replace nightmare.

Any system that is responsible for controlling access to our applications and data needs to be auditable. The 

we want will maintain an audit log of provisioning activities, configuration changes, and other important events, like failed logins. This audit log needs to be readily accessible (and read-only) to the IT Manager.

Let’s not forget why we are doing all of this. We want to keep our applications and data secure. Identity and access management is meant to improve security by making access to our applications and data easier to manage. Ease of use cannot come at the expense of security. We want a reliable, easy to use and secure

The IT Manager is being squeezed.

The IT Manager's Declaration for IAM

IAM full of ideas today. Full of puns, too.

You're probably reading this article because you're brainstorming topics for
publication here on IAM Pulse. Perfect. You're in the right place!

Do you have a unique IAM use case? If you work with IAM policy regularly, what
tools do you use? What does a normal day look like auditing or pen-testing
policies?

On this page you'll find a number of topics and questions about working with
IAM from a variety of industry roles. Take a minute and read through the list.
My hope is that one of these questions will inspire your take on the answer.

This list will be updated as content is posted and the discussion around IAM
evolves. Check back occasionally for fresh questions and topics.

How do you manage a large number of cloud accounts?

How would you improve departmental collaboration when it comes to IAM policy?

Which IAM workflows scale and why? What lessons have you learned?

Have you used IAM at scale in any unique ways?

What do you think the biggest challenges are for managing IAM at scale?

How do you build a least privilege CI/CD pipeline?

Can you recommend ways to test IAM policy changes for errors?

Any advice for troubleshooting IAM access denied errors?

Do you manage IAM across multiple clouds? How?

What makes IAM difficult for DevOps? How would you make it easier?

How do you secure a k8s clusters with least privilege IAM?

Any advice for people getting started with containers and IAM?

Have you combined IAM and container access in a unique way?

What lessons have you learned about combining IAM with containers?

Examples of managing container access with IAM policy.

What are your most common roadblocks to implementing IAM fixes?

Where do you find the most pain points in securing IAM policy?

Any advice for people getting into cloud security?

Can you suggest any quick wins for other InfoSec teams?

Examples of detecting privilege escalation in IAM policies.

Read the IAM Pulse Blog

Get the IAM Pulse Check Newsletter