HID - Workforce Identity and Access Management

PIAM - Strategies to Manage Identities Access within various systems

HID Season 1 Episode 1

PIAM - Strategies to Manage Identities Access within various systems.

Matthew Lewis Director of Product Marketing at HID IAMS and Donald Campbell, Senior Director of Product Management at HID Global discuss strategies to manage identities within various systems to enhance and optimize security procedures for workforce.


Speaker 1:

Powering trusted identities of the world's people, places and things. Every day, millions of people in more than 100 countries use our products and services to securely access physical and digital places over 2 billion things that need to be identified, verified, and tracked are connected through HID Global's technology.

Speaker 2:

Hey Don, how are you?

Speaker 3:

Uh, doing alright? How are you today?

Speaker 2:

I'm good. I know it's been, it's been so long since we talked. I think what, like 20 minutes<laugh>,

Speaker 3:

Uh, 20 or 30. Yes.

Speaker 2:

Yeah. And we're gonna keep talking about PIAM physical identity and access management. I feel like that's all you and I talk about these days. I wanted to spend a little time on something I keep hearing about when I'm talking with either the sales team or customers or partners, which is customers having a kind of a key pain point around managing all these identities or attributes of identities that are spread all over the place. HR has some, some attributes. IT has some. And what seems like is missing is, is some set of tools or some solution that kind of brings these all together. Is that, am I on the right track in how we could maybe think about solving that set of problems that the customers are having?

Speaker 3:

Yeah. The IM and PIAM is identity management and it's, it is all about that. It's about connecting into the various identity systems to keep them synchronized. So we're trying to avoid data errors. So if you, you start to type in the same identity, um, in system a and type them in, in system B, you may spell it differently. Use a different form of the name is you always sort of get stuck with, if I have Don Campbell in this system and Donald Campbell, is that the same person or are there two people that are, that are Don Campbell? Um,

Speaker 2:

Hopefully it's the same person.

Speaker 3:

Yeah. One of me is, is already too many.

Speaker 2:

Absolutely.

Speaker 3:

But trying to solve that problem after it, you split the identity like that is expensive. It's you have to find the person who would know in a large organization. It may not be one person who can even answer that question. So part of it is that it makes things faster, but more than that is it keeps them consistent. It reduces this type of uncertainty and error within the systems. And so, yeah, if you can't put an identity system in between to keep them synchronized, you, you really have to think, how do you solve this type of problem?

Speaker 2:

Yeah. That it reminds me a little bit of some of the, the master data management challenges I saw in a previous place where if you're thinking about, just call it a singular asset, but as it's moving throughout its life cycle, there's systems of record in that moment in time for a certain set of attributes, you know, I know at one point I, I saw it statistically like each wrong set of data or kind of data point costs$10. I imagine for an identity, it is substantially more expensive than that as a cost factor. So, you know, one of the things that that required was some set of engine at the core to help with addressing those problems. Is, is that in existence here? Is that kind of what we're talking about at

Speaker 3:

The heart? Exactly. Right. It's exactly what we're talking about. So we think about the policy engine here is it's really a set of rules. It's it's what are the sources who owns which data, which direction do we sync to make sure that we don't get into system a is updating something system B is trying to change it back so that we can keep all of that synced correctly, get the right data into the right places for you. On top of that, the PIAM system can be the owner of that identity and that information in the first place. For instance, contractors, HR is good with employees. There's, they're often good with certain classes of contractors like full-time contractors, but generally they're not good with all of the people that are coming and going. And then it is really only wanting to do with people when they're giving them IT access. But we have lots of people with access in the building coming in at night, coming in for process changes and things like that.

Speaker 2:

Yeah. So allowing maybe you, you know, from a development standpoint, you've got one pool of contractors on the marketing side. I may have a different pool of contractors, which definitely may have different needs and all of that.

Speaker 3:

Yeah, exactly. The ops team may have their own and what's, what's great within the identity system is you can delegate that. So each owner, each pool owner can do their own updates, can add their own identities. Yet I keep control at the center and we'll talk about issuing access and cards later, but I can keep control of that. And it's one of the, the key systems. In fact, we have some customers that look at this and say, well, the person who knows who, who the members of this team are actually the supplier, the contractor themselves, let's let them do the data entry or the data update of this. They can keep it up to date better than we can. So even pieces that get pushed out to the third parties that you work with.

Speaker 2:

Interesting. Okay. Yeah. And I imagine, you know, world ground to a halt, we're sort of opening up well different week different day depends on what we're doing and where we are, but opening

Speaker 3:

Up the closing down. Sure.

Speaker 2:

Yes. Significantly exacerbated this whole thing of understanding who is in the building at any moment in time, and then being able to control from week to week, maybe, you know, you're going to some sort of teaming version of a return to office where week one it's group, a week, two it's group B. So that, that accuracy in knowing who the flexibility and knowing when, or, or adjusting when is really gonna be playing into effect here.

Speaker 3:

Exactly. And, and I don't know about where you are, but we keep changing the information we want to gather, uh, week to week as well. So one week is questions to the next week. It's a, it's a vaccine card. So being able to rapidly change those rules to make it easy to apply the right policy for this week is really important.

Speaker 2:

Yeah. Yeah. And so, and we've kind of danced around it and you even mentioned it, um, all this is meant to help you get into a building. So I think we'll leave it at getting into the building as our next topic. And we'll thank everyone for joining. We're gonna do this again next time, Don. I appreciate the chat.

Speaker 3:

All right. Thanks.