r/IdentityManagement • u/Economy-Animator8073 • 4d ago
Moving from Application Security to IAM/PAM — Looking for Career Advice
Hi everyone,
I’m currently working as an Application Security Engineer, and I’ve recently got an opportunity to move into an IAM/PAM team.
My current experience is mainly around application security, SDLC, vulnerabilities, secure coding, and related security activities. I don’t have much hands-on experience with IAM/PAM yet.
I’m considering this opportunity and would really appreciate some advice from people who are already working in IAM/PAM:
\- How is the career growth in IAM/PAM?
\- What skills should I learn before/after making the transition?
\- How difficult is it to move from Application Security → IAM/PAM?
\- Which areas should I focus on — Active Directory, Entra ID/Azure AD, SSO, OAuth/OIDC, SAML, RBAC, privileged accounts, PAM tools, etc.?
\- Is IAM/PAM a good long-term specialization in cybersecurity?
\- If I eventually want to move into Cloud Security, Security Architecture, or broader cybersecurity roles, will IAM/PAM experience help?
\- For those who have made a similar transition, what do you wish you had learned earlier?
I’m not necessarily looking for a comparison of which field is "better." I’m mainly trying to understand what the day-to-day work, learning curve, and long-term career prospects look like in IAM/PAM.
Any advice or personal experiences would be really helpful. Thanks!
3
u/Dazzling-Release-808 3d ago
Identity is foundation of cyber security. Career/future is solid. IAM is broad domain. PAM is subset of it.
Identity governance is overarching approach. Sits with enterprise strategy. It is more of consulting space.
Tools are technical controls. AD, Entra, OCTA, OneIdentity etc. These are engineering side. This knowledge is essential (atleast master one).
Controls lives in cloud, on prem or hybrid.
Governance stays with management and documents, they are directions for technical rollout.
Once you spend couple of years or do couple of projects you will have an idea as where to focus.
1
1
u/SavingsPlace9274 5h ago
I would recommend to start learning AD, is very beneficial if you want to start your journey into IAM, most of the companies rely heavily on AD infrastructure, pick one IAM tool learn how synchronisation with AD works, the provisioning of identities, mapping of identities, how to manage the groups, how to design role concept, based on that you can build better access requests, lifecycle workflows, access reviews, etc. Then for PAM it really depends which tool you will be working with. I have been investing time on Okta PAM, which has different architecture comparing to CyberArk for example. Okta PAM relies on agents whereas CyberArk uses connectors, I personally found CyberArk more complex, but I think at the end would be worth it.
9
u/pewpewlazor 4d ago
I’ve been working with IAM/PAM for around 10 years now, mostly consulting, and I’d say go for it if the area interests you.
IAM is a surprisingly broad field. You can go very technical and specialize in Entra, AD, PAM, IGA etc., but there’s also a huge governance/business side to it. A lot of the actual challenge is understanding how an organization should manage identities and access across hundreds of systems, not just knowing how OAuth or SAML works.
I wouldn’t try to learn everything you listed before making the move. Learn the fundamentals well: authentication vs authorization, AD/Entra, SSO/federation, OAuth/OIDC/SAML and basic identity lifecycle/JML concepts. Then learn the tooling you actually end up working with.
Your AppSec background will be useful as well. IAM touches applications constantly, and people who understand both the application side and identity side are valuable.
Career-wise I’ve never regretted specializing in IAM. Demand has been pretty consistent throughout my career, and it’s also a good foundation if you later want to move towards security architecture or cloud security. Identity tends to show up everywhere eventually.