Weave Identity

For the last 20 years, the digital identity market has been primarily focused on protocols and what's transiting the wires; it has not been standardizing interfaces to data at rest. We have not thought about data-at-rest and the schema thereof since our LDAP days and inetOrgPerson. Over the last year I have been writing about what I think modern IAM looks like and what are the architectures we need to support it. Although I do not fully understand this moment in the market, I feel strongly that the future of IAM includes a robust data tier and near-real time events. To that end, IAM’s drought of attention with respect to schema and data-at-rest must end. Regardless of what you call the latest iteration of the IAM market, the real battle is being fought to be the new identity data tier for the enterprise. Technology providers are pulling different kinds of IAM data together both admin- and run-time. Some are even infusing all of that with event-time data. And in this way, they are addressing one of the fundamental flaws in traditional IAM product approaches: they only know about the data they can push and pull through their own connections to applications and services. While that's great and needed, it is by no means enough. If an IAM solution’s data repository is closed to you, the buyer and consumer of their services, it does you less good, than an open one. Keep reading at Weave Identity... https://lnkd.in/gXsn2H2b And many thanks to the friends that helped make this idea better including: Lori Robinson Erik Gustavson Sean O'Dell Nishant Kaushik Firdaus Modak Andrew Cameron Mike Kiser Darran Rolls Paresh Bhaya

For the last 20 years, the digital identity market has been primarily focused on protocols and what's transiting the wires; it has not been standardizing interfaces to data at rest. We have not thought about data-at-rest and the schema thereof since our LDAP days and inetOrgPerson. Over the last year I have been writing about what I think modern IAM looks like and what are the architectures we need to support it. Although I do not fully understand this moment in the market, I feel strongly that the future of IAM includes a robust data tier and near-real time events. To that end, IAM’s drought of attention with respect to schema and data-at-rest must end. Regardless of what you call the latest iteration of the IAM market, the real battle is being fought to be the new identity data tier for the enterprise. Technology providers are pulling different kinds of IAM data together both admin- and run-time. Some are even infusing all of that with event-time data. And in this way, they are addressing one of the fundamental flaws in traditional IAM product approaches: they only know about the data they can push and pull through their own connections to applications and services. While that's great and needed, it is by no means enough. If an IAM solution’s data repository is closed to you, the buyer and consumer of their services, it does you less good, than an open one. Keep reading at Weave Identity... https://lnkd.in/gXsn2H2b And many thanks to the friends that helped make this idea better including: Lori Robinson Erik Gustavson Sean O'Dell Nishant Kaushik Firdaus Modak Andrew Cameron Mike Kiser Darran Rolls Paresh Bhaya

With Gartner IAM Summit fresh in my memory, thoughts... People: It was so good to see so many friends and colleagues under one roof. And it was even better to be able to share the stage with Andrew Nash and Hannah Hershey Sutor on behalf of IDPro? to talk about the things we wish we knew when we were starting our careers. As we said from the stage, relationships and mentoring had oversized impacts on our careers and something we all treasure. Trends: Machine Identity/Non-Human Identity and Shared Signals (CAEP) was on everyone's lips. It was amazing to see the packed interop room showing off multiple vendors demonstrating how they support OpenID Foundation's Shared Signals Framework. And I deeply appreciated Felix Gaehtgens talking about identity-first security as differentiated from identity security. Also, I'd be remiss if I didn't mention Erik Wahlstr?m's mantra of "be a seagull" #iykyk Customers: It was an absolute blast to be able to spend time with some many of my customers. It was even better to hear analysts give shout out to my/Weave Identity's customers including SGNL, Natoma, and TrustFour Technologies. As well as seeing the excitement around Beyond Identity and AKA Identity! 2025 is shaping up to be an extremely exciting year here in IAM-land!

This 4 part series on modern IAM architecture has been a blast! I have really treasured the feedback I have received and excited that it is triggering conversations throughout the market! Check out part 4!

Last week I provided a few techniques for thinking about the systems that you need to protect and optimizing controls for them. That included identifying which kind of policy (admin-, run-, or event-time) was most important for which kind of system as well as some thoughts on policy complexity per type of system to be protected. This week I want to present what I believe is a conceptual architecture for modern IAM. It feels very different from the kinds of IAM infrastructure architectures you might be familiar with. It is, in some sense, a higher level architecture into which you would place classical components such as IGA or an IDP. But instead of me presenting it here, read on and discover! https://lnkd.in/dnYiG4P5 #iam #weaveidentity

Welcome back to part 3 of my thoughts on enterprise patterns for modern IAM. Last week I provided a few techniques for thinking about the systems that you need to protect and optimizing controls for them. That included identifying which kind of policy (admin-, run-, or event-time) was most important for which kind of system as well as some thoughts on policy complexity per type of system to be protected. This week I want to present what I believe is a conceptual architecture for modern IAM. It feels very different from the kinds of IAM infrastructure architectures you might be familiar with. It is, in some sense, a higher level architecture into which you would place classical components such as IGA or an IDP. But instead of me presenting it here, read on and discover!

Last week I published?part one of my four part series on "Enterprise Patterns for Modern IAM"?in which I discussed the principles that should inform the design of a modern IAM architecture. This week, in part 2, I am offering up a way to think about the kinds of systems your IAM architecture is meant to protect and a means to align controls to that goal. https://lnkd.in/eDTribrw #zsp #weaveidentity

Last week I published?part one of my four part series on "Enterprise Patterns for Modern IAM"?in which I discussed the principles that should inform the design of a modern IAM architecture. This week, in part 2, I am offering up a way to think about the kinds of systems your IAM architecture is meant to protect and a means to align controls to that goal. https://lnkd.in/eDTribrw #zsp #weaveidentity

I am stoked to sit down and have a chat with Aviad Mizrachi of Frontegg! This is a topic I haven’t had an opportunity to really talk about in public for quite some time! Looking forward to it!

Over the last few months I have been working on ideas about modern IAM architecture, what it contains, and how to think about it. This is the first of four posts that expand on my previous thoughts. This post will examine the principles that should inform a modern IAM architecture. The second post will offer up a way to think about the systems a modern IAM architecture enables and protects along with the controls it provides. The third post will describe a notional architecture that embodies the principles discussed next and allows for the deployment of IAM controls. Lastly, I will talk about how to get started building a modern IAM architecture. And with that I present part of 1 “Enterprise Patterns for Modern IAM: https://lnkd.in/e-6dHYUv