Notifications
Clear all
Topic starter
25/06/2026 5:12 pm
TL;DR: Identity programmes mature faster when teams treat community learning as part of operating model development, not an afterthought, according to SailPoint. Its Community is now publicly accessible and points readers to five resources, including on-demand sessions, user groups, webinars, and a wiki, as a way to grow identity security knowledge and professional networks.
NHIMG editorial — based on content published by SailPoint: 5 Resources to Develop Your Identity Security Knowledge and Network
Questions worth separating out
Q: How should identity teams use professional communities to improve governance?
A: Identity teams should use professional communities to compare operational patterns, validate process assumptions, and collect examples they can turn into internal playbooks.
Q: Why does peer learning matter in identity security programmes?
A: Peer learning matters because identity controls often fail at implementation, not design.
Q: How do you know if identity training is actually helping?
A: Identity training is helping when teams make fewer repeat mistakes, resolve access issues faster, and document controls in a way that other practitioners can reuse.
Practitioner guidance
- Map community learning to your internal IAM roadmap Identify which identity topics your team repeatedly relearns, then assign those topics to a repeatable learning loop that includes training, peer discussion, and documented playbooks.
- Use external peer groups to pressure-test governance assumptions Bring unresolved questions about process design, exception handling, and operating model maturity to a practitioner group before you formalise them internally.
- Build a searchable internal knowledge base for identity operations Capture lessons from webinars, workshops, and incidents in a structured wiki so access governance, privilege handling, and onboarding or offboarding decisions are not dependent on tribal knowledge.
What's in the full article
SailPoint's full blog covers the community resources and participation details this post intentionally leaves for the source:
- How to register for public community access and what new members can see once inside
- Which on-demand Community Day sessions and educational webinars are available to watch
- How the User Group directory helps practitioners find peer groups by location or industry
- What the IdentityNow Wiki contains for APIs, rules, best practices, and quick-reference guidance
👉 Read SailPoint's blog on five resources for identity security knowledge and networking →
Identity security community access: what practitioners can gain?
Explore further
25/06/2026 5:45 pm
Identity community is a control amplifier, not a marketing layer: The value of a public practitioner community is that it reduces implementation entropy across identity programmes. Identity controls fail most often at the handoff between policy and execution, where teams interpret the same process differently. A shared community gives practitioners common examples, common language, and faster pattern recognition. The implication is that governance quality improves when knowledge is distributed beyond a single centre of excellence.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap.
A question worth separating out:
Q: What should security leaders look for in an identity learning resource?
A: Security leaders should look for resources that combine practical examples, peer discussion, and searchable guidance. A useful resource helps teams answer real questions about privilege, access governance, and lifecycle management, rather than only offering abstract theory or product-oriented messaging.
👉 Read our full editorial: Identity security knowledge gaps are best closed through community
