1 00:00:05,280 --> 00:00:10,440 This is identity at the center. If it has anything to do with 2 00:00:10,560 --> 00:00:17,960 IAM, this is the go to podcast now your hosts Jim McDonald and 3 00:00:17,960 --> 00:00:22,920 Jeff Stedman. Welcome to the Identity at the 4 00:00:22,920 --> 00:00:24,840 Center podcast. I'm Jeff and that's Jim. 5 00:00:24,840 --> 00:00:26,520 Hey, Jim. Hey, Jeff, how are you? 6 00:00:27,160 --> 00:00:30,720 Oh, not so bad yourself. I'm doing great and we're here 7 00:00:30,720 --> 00:00:33,760 recording a sponsor spotlight episode. 8 00:00:34,120 --> 00:00:38,640 I'm ready to get my learn on. Yeah, we've got another sponsor. 9 00:00:38,640 --> 00:00:40,600 Spotlights is great. People are really enjoying these 10 00:00:40,600 --> 00:00:41,800 each other. These are that's pretty cool 11 00:00:41,800 --> 00:00:42,880 when people embrace it like that. 12 00:00:42,880 --> 00:00:46,000 These are special off cycle episodes that we put together 13 00:00:46,000 --> 00:00:48,680 and we create these in collaboration with our sponsors. 14 00:00:49,120 --> 00:00:51,560 That's what helps us get into like more deeply into like 15 00:00:51,560 --> 00:00:55,320 questions around products, viewpoints, services, things 16 00:00:55,320 --> 00:00:58,560 like that. You know more of a more of a 17 00:00:58,600 --> 00:01:01,000 more of a deeper dive into those products than we would normally 18 00:01:01,000 --> 00:01:02,200 do. I would say, Jim, is that 19 00:01:02,200 --> 00:01:04,319 accurate? I think we, yeah, I think we've 20 00:01:04,319 --> 00:01:11,800 been very adamant about keeping advertising and marketing out of 21 00:01:11,800 --> 00:01:15,200 the podcast for years and it does create a limitation in 22 00:01:15,200 --> 00:01:18,360 terms of some of the questions that they would otherwise ask. 23 00:01:18,360 --> 00:01:22,520 So I think the sponsor spotlight is kind of taking some of those 24 00:01:22,520 --> 00:01:26,080 constraints off and lets us, you know, learn. 25 00:01:26,120 --> 00:01:31,000 And I think what's really cool about this episode is it's, you 26 00:01:31,000 --> 00:01:35,840 know, it's not maybe our typical episode where it's like, you 27 00:01:35,840 --> 00:01:39,960 know, core, everyday technologies that people might 28 00:01:39,960 --> 00:01:43,680 understand. It's going to open people's eyes 29 00:01:43,680 --> 00:01:47,720 to maybe another area. And that's why I think is great. 30 00:01:47,840 --> 00:01:50,120 I mean, I'm. I love bringing that kind of 31 00:01:50,520 --> 00:01:53,080 perspective to the podcast. Yeah, for sure. 32 00:01:53,080 --> 00:01:54,280 I think this is an area that I'm excited. 33 00:01:54,280 --> 00:01:56,280 This is something I have a little bit of experience in the 34 00:01:56,280 --> 00:01:58,760 past with when it comes to like physical security and sort of 35 00:01:58,760 --> 00:02:01,320 the blending of logical and physical access, things like 36 00:02:01,320 --> 00:02:03,040 that. But it's always better when you 37 00:02:03,120 --> 00:02:04,880 have smarter people than me talking about that. 38 00:02:04,880 --> 00:02:07,600 So why don't we go ahead and get to our sponsor? 39 00:02:07,600 --> 00:02:11,240 RF Ideas is today's sponsor and just to make it very clear, 40 00:02:11,240 --> 00:02:14,480 right, this is a special, you know, one off, It's a fully 41 00:02:14,480 --> 00:02:16,680 sponsored episode. That's what gives us access to 42 00:02:16,680 --> 00:02:18,720 great experts that we're going to have here on the show today. 43 00:02:18,720 --> 00:02:20,080 So let's go ahead and get started. 44 00:02:20,320 --> 00:02:22,320 If you're not familiar with RF Ideas, I would encourage you to 45 00:02:22,320 --> 00:02:23,960 go out and woke them up. But they're on a mission 46 00:02:23,960 --> 00:02:27,680 basically to bring and bridge physical and logical security 47 00:02:27,680 --> 00:02:29,320 together. And they have some pretty 48 00:02:29,320 --> 00:02:32,280 innovative credential readers. And it really provides a pretty 49 00:02:32,280 --> 00:02:34,960 what can be a a seamless authentication experience. 50 00:02:34,960 --> 00:02:38,120 It's like, OK, you sound like a marketing person, It it looks 51 00:02:38,120 --> 00:02:39,520 pretty cool. We're going to learn more about 52 00:02:39,520 --> 00:02:42,520 it, and I want to welcome to the show Raul Cepeda. 53 00:02:42,560 --> 00:02:44,680 He's the vice president of product management and 54 00:02:44,680 --> 00:02:46,280 marketing. Welcome to the show, Raul. 55 00:02:46,440 --> 00:02:48,080 Thank you. And we've also got Sarah King. 56 00:02:48,080 --> 00:02:49,720 She's a pre sale engineer with RF ideas. 57 00:02:49,720 --> 00:02:51,760 Welcome to the show, Sarah. Thanks, Jeff. 58 00:02:51,760 --> 00:02:55,000 Thanks, Jim. So one of the things we like to 59 00:02:55,000 --> 00:02:57,160 do before we get started is learn more about the backgrounds 60 00:02:57,160 --> 00:02:58,960 of people in this identity space. 61 00:02:59,000 --> 00:03:02,160 And I guess I'm going to ask you a question around this is rule 62 00:03:02,160 --> 00:03:04,360 we'll start with you. Can you kind of start off with, 63 00:03:04,480 --> 00:03:07,040 you know what is your background in the identity space? 64 00:03:07,040 --> 00:03:10,120 Obviously you're in kind of the, I guess I I I equate, you know, 65 00:03:10,120 --> 00:03:12,720 physical security with sort of badges and readers and things 66 00:03:12,720 --> 00:03:13,760 like that. And I know we'll talk about it 67 00:03:13,760 --> 00:03:16,720 in a little bit, but how do you, how did you get into the space 68 00:03:16,720 --> 00:03:19,800 of identity? Yeah, so I I've been part of the 69 00:03:19,800 --> 00:03:24,120 tech world for the better part of the last 1314 years, mostly 70 00:03:24,120 --> 00:03:28,000 in automation in general, but specifically on the security 71 00:03:28,000 --> 00:03:33,000 side, the 1st 12 plus years of my professional experience, I've 72 00:03:33,000 --> 00:03:35,120 been working as a systems integrator. 73 00:03:35,200 --> 00:03:37,840 So we worked, I worked for a systems integrator, we went out 74 00:03:37,920 --> 00:03:42,920 did implementations with end user customers and about two a 75 00:03:42,920 --> 00:03:46,920 little bit 2 plus years ago I joined RFID as to lead their 76 00:03:46,920 --> 00:03:50,080 their product and marketing and now we're out on a mission to 77 00:03:50,240 --> 00:03:53,120 develop innovative products out there for friend users and 78 00:03:53,200 --> 00:03:55,240 partners like. So you can say to yourself an 79 00:03:55,240 --> 00:03:58,320 identity person, a physical security person, an information 80 00:03:58,320 --> 00:04:01,400 security person, or some some weird hydra of all three. 81 00:04:01,600 --> 00:04:03,360 I think I'm a little bit of a Hydra. 82 00:04:03,360 --> 00:04:06,080 I mean, I think if I look at the background that I spent the 1st 83 00:04:06,080 --> 00:04:10,160 12 years, we implemented everything from bar coding 84 00:04:10,160 --> 00:04:14,640 solutions to physical security to identity solutions. 85 00:04:14,880 --> 00:04:18,279 Obviously the last couple years have been specifically tied to 86 00:04:18,279 --> 00:04:21,640 identity. So learning much more about this 87 00:04:21,640 --> 00:04:24,880 space in the last couple years. And so I guess now I consider 88 00:04:24,880 --> 00:04:26,760 myself mostly on the identity side. 89 00:04:26,800 --> 00:04:28,280 Well, welcome. The water's just fine. 90 00:04:28,280 --> 00:04:30,800 It's very pleasant. People are very accommodating. 91 00:04:31,160 --> 00:04:33,320 Sarah, from your journey, tell us a little bit about how you 92 00:04:33,320 --> 00:04:35,920 got into the identity space as we're as we're welcoming you 93 00:04:35,920 --> 00:04:37,480 into this. Yeah. 94 00:04:37,480 --> 00:04:42,680 So my background for about the last 15 years has been anything 95 00:04:42,680 --> 00:04:44,840 technology. I enjoy learning about new 96 00:04:44,840 --> 00:04:49,120 technology, how to help customers and and better their 97 00:04:49,120 --> 00:04:52,360 processes using technology. Started with RF Ideas almost a 98 00:04:52,360 --> 00:04:56,000 decade ago. Started just in a support role, 99 00:04:56,120 --> 00:04:59,200 tech support role. Ended up managing that tech 100 00:04:59,200 --> 00:05:01,480 support department. Customer service, and now I'm on 101 00:05:01,480 --> 00:05:04,760 the sales side. Yeah, I looked at your LinkedIn 102 00:05:04,760 --> 00:05:07,560 profile Sarah, and I saw that you were there for over 8 years 103 00:05:07,600 --> 00:05:10,240 and was like, wow, must be a pretty cool company to work for. 104 00:05:11,120 --> 00:05:14,200 It's a it's a really great company to work for and a fun 105 00:05:14,200 --> 00:05:17,320 company to work for and my my everyday changes. 106 00:05:17,440 --> 00:05:20,840 That's awesome to hear. Raul, tell us about this awesome 107 00:05:20,840 --> 00:05:22,720 company that Sarah just mentioned. 108 00:05:23,040 --> 00:05:25,520 What do you guys do? What do you do over Darf ideas? 109 00:05:26,680 --> 00:05:28,480 Yeah. So we've been around for about 110 00:05:28,480 --> 00:05:31,640 30 years manufacturing credential readers. 111 00:05:31,720 --> 00:05:34,920 And So what we're doing out there is, you know, what makes 112 00:05:34,920 --> 00:05:38,000 us a little bit unique from other, you know, card credential 113 00:05:38,000 --> 00:05:41,200 providers out there is that we're pretty agnostic when it 114 00:05:41,200 --> 00:05:43,360 comes to the credentials that we support. 115 00:05:43,480 --> 00:05:47,560 You know, so everything from proximity to contactless to 116 00:05:47,560 --> 00:05:51,360 mobile credentials, we're working with a lot of the global 117 00:05:51,360 --> 00:05:53,880 leading credential providers out in the marketplace. 118 00:05:54,360 --> 00:05:58,400 So that stands out out there. Most smart card reader 119 00:05:58,400 --> 00:06:00,920 manufacturers are typically focused on one or two 120 00:06:00,920 --> 00:06:03,480 credentials. We support you know over 100 121 00:06:03,480 --> 00:06:05,280 different credentials out there in the space. 122 00:06:05,640 --> 00:06:07,680 So we've been doing it for, for 30 years. 123 00:06:07,680 --> 00:06:11,160 You know, we're trusted across a lot of different verticals out 124 00:06:11,160 --> 00:06:14,280 there and so we're the go to for things in particular like 125 00:06:14,280 --> 00:06:15,880 healthcare. Just 30 years. 126 00:06:16,040 --> 00:06:19,040 I'm, you know, it's it. You guys have been on this 127 00:06:19,040 --> 00:06:21,280 passwordless journey for 30 years, right? 128 00:06:21,280 --> 00:06:24,240 It's always been about possession based authentication. 129 00:06:24,720 --> 00:06:27,840 Talk to us in that 30 years. Talk to us a little bit about 130 00:06:28,160 --> 00:06:32,000 the journey and some of the milestones that you can tie back 131 00:06:32,000 --> 00:06:35,840 to that 30 years. Yeah, I think you know if if we 132 00:06:35,840 --> 00:06:38,240 look at kind of where we were, where we started, where we 133 00:06:38,240 --> 00:06:40,960 really got our started, it's it's really in healthcare. 134 00:06:41,000 --> 00:06:44,480 You know we we partnered with a company called Imprevada who 135 00:06:44,480 --> 00:06:49,480 does a single sign on and we found an opportunity to help 136 00:06:49,480 --> 00:06:53,520 clinicians and staff improve their day-to-day productivity. 137 00:06:53,600 --> 00:06:56,800 The most common use case that you'll see out there is staff 138 00:06:56,800 --> 00:07:00,000 and clinician are going from patient room to patient room 139 00:07:00,240 --> 00:07:03,200 typing in a username and password, you know every time 140 00:07:03,200 --> 00:07:05,600 they go to a new room. And so we identified an 141 00:07:05,600 --> 00:07:09,680 opportunity to kind of help cut the time and and put more of the 142 00:07:09,680 --> 00:07:13,920 focus on the patient by allowing clinicians to take their ID 143 00:07:13,920 --> 00:07:18,520 badge and tap it on one of our credentials which enable them to 144 00:07:18,520 --> 00:07:22,960 single sign on you know onto their workstation or or PC. 145 00:07:23,000 --> 00:07:26,720 So you know it what we found is that it it started to cut a lot 146 00:07:26,720 --> 00:07:30,080 of the time you know for for those those patients so that 147 00:07:30,080 --> 00:07:31,920 they could be more focused on by the clinicians. 148 00:07:32,640 --> 00:07:35,960 Yeah, I mean, cutting the time's important, but it darnwell 149 00:07:35,960 --> 00:07:38,720 better work, right? I mean, you have a patient who's 150 00:07:38,720 --> 00:07:41,800 maybe in like a critical position, right, that you go up 151 00:07:41,800 --> 00:07:46,040 there, you do the the procs card, that person needs to get 152 00:07:46,040 --> 00:07:49,000 into the system and they've got to be the right person. 153 00:07:49,000 --> 00:07:52,960 So absolutely, you know, mission critical stuff, right? 154 00:07:53,400 --> 00:07:55,240 Absolutely. Yeah, I mean I I think secure 155 00:07:55,240 --> 00:07:57,120 authentication is part of it, right. 156 00:07:57,160 --> 00:07:59,840 Compliance is another factor that plays into it. 157 00:07:59,840 --> 00:08:02,440 I mean if you look at the big market drivers for our 158 00:08:02,440 --> 00:08:05,600 technology, you know it typically comes down to to three 159 00:08:05,600 --> 00:08:07,680 things. It's it's all about security 160 00:08:07,840 --> 00:08:11,880 mostly with data and endpoints, it comes down to compliance. 161 00:08:11,880 --> 00:08:15,040 So in in the healthcare example there you have things like HIPAA 162 00:08:15,480 --> 00:08:17,600 and then you have workforce productivity. 163 00:08:17,600 --> 00:08:21,640 So it just happens that in that one use case you see all three 164 00:08:21,720 --> 00:08:23,880 that that organizations are benefiting from. 165 00:08:24,000 --> 00:08:28,720 So rule one more question. So this name RF ideas and it's 166 00:08:28,920 --> 00:08:33,679 lowercase RF ALL CAPS ideas. I'm wondering how did that name 167 00:08:33,679 --> 00:08:35,400 come about because it's pretty unique. 168 00:08:35,520 --> 00:08:37,600 Yeah, it's, it's actually interesting, Jim. 169 00:08:37,600 --> 00:08:41,520 So we actually went through a rebranding a couple of years ago 170 00:08:41,520 --> 00:08:44,560 where if you looked at the spelling of our name, it was 171 00:08:44,560 --> 00:08:49,800 actually RFID was all caps and then the rest of it, EEZ was 172 00:08:49,800 --> 00:08:53,080 basically lowercase and that really stemmed from the 173 00:08:53,080 --> 00:08:56,760 technology that we supported which was RFID technology. 174 00:08:56,840 --> 00:09:01,400 So now Fast forward to a few years ago when we started saying 175 00:09:01,400 --> 00:09:04,440 hey, you know we're we're not really we're we're kind of 176 00:09:04,440 --> 00:09:08,080 pigeon pigeonholing ourselves into you know RFID. 177 00:09:08,080 --> 00:09:12,320 But we're much more, we're evolving into much more support 178 00:09:12,360 --> 00:09:16,840 credential support nowadays. And so we made a decision to 179 00:09:16,840 --> 00:09:21,720 kind of change the name branding to go lowercase RF and ideas. 180 00:09:22,000 --> 00:09:25,520 And part of that decision was that there's RF technology that 181 00:09:25,520 --> 00:09:29,040 we're supporting nowadays that's much more than just your 182 00:09:29,320 --> 00:09:31,920 traditional proximity cards or smart cards. 183 00:09:31,920 --> 00:09:35,360 We've evolved into mobile credentials, we've evolved into 184 00:09:35,360 --> 00:09:39,320 things like biometrics and so you know with it, it's kind of 185 00:09:39,320 --> 00:09:43,200 the RF which is kind of the base of the technology into more 186 00:09:43,200 --> 00:09:44,760 ideas that we're we're supporting. 187 00:09:45,120 --> 00:09:47,440 I love the origin story of company names. 188 00:09:47,560 --> 00:09:49,720 If I ain't fascinating, There's so many, so many interesting 189 00:09:49,720 --> 00:09:52,240 ones there and I love the play on words a little bit that 190 00:09:52,240 --> 00:09:55,240 you're doing the right kind of like RF ideas, like, OK, cool. 191 00:09:55,640 --> 00:09:57,200 Kind of the same thing we do with right identity at the 192 00:09:57,200 --> 00:09:59,320 Center for the podcast. You guys are in a very crowded 193 00:09:59,320 --> 00:10:02,720 space and you know, there's lots of vendors that play in physical 194 00:10:02,720 --> 00:10:05,000 security and have different form factors and so forth. 195 00:10:05,280 --> 00:10:07,680 Let me ask you a hard question. Maybe it's not so hard. 196 00:10:07,680 --> 00:10:09,320 I don't know. Why are you guys different? 197 00:10:09,320 --> 00:10:11,480 What sets you apart from your competitors in this space? 198 00:10:11,760 --> 00:10:14,120 Yeah, I think there's two things, right. 199 00:10:14,120 --> 00:10:16,880 One of them I I kind of touched on a little bit earlier in that 200 00:10:17,080 --> 00:10:20,240 our credential providers are agnostic when it comes to the 201 00:10:20,240 --> 00:10:21,800 credentials that we support, right. 202 00:10:22,120 --> 00:10:24,440 If you look at a lot of our competitors, they tend to kind 203 00:10:24,440 --> 00:10:27,680 of focus in on one or two credentials that kind of 204 00:10:27,680 --> 00:10:32,200 dominate a a particular region or a particular vertical. 205 00:10:32,240 --> 00:10:34,640 We tend to be a little bit more horizontal than vertically 206 00:10:34,640 --> 00:10:37,920 focused even though you look at some of the major markets that 207 00:10:37,920 --> 00:10:41,320 we are being implemented in. You'll see things like 208 00:10:41,320 --> 00:10:43,280 healthcare and and manufacturing. 209 00:10:43,640 --> 00:10:48,160 But I think the agnostic aspect helps us get into more 210 00:10:48,160 --> 00:10:50,720 environments out there. When you start to see 211 00:10:51,040 --> 00:10:54,160 deployments where there's multiple credentials being 212 00:10:54,160 --> 00:10:57,880 deployed, some for you know manufacturing settings, some for 213 00:10:57,880 --> 00:11:01,080 the front office, it's IT. It kind of gives us a little bit 214 00:11:01,080 --> 00:11:04,400 of a competitive advantage in those cases because they can 215 00:11:04,400 --> 00:11:08,520 leverage the same base platform or the same reader for a variety 216 00:11:08,520 --> 00:11:12,200 of different use cases. So you know, I'll give a great 217 00:11:12,200 --> 00:11:15,360 example here where you know we we've been deployed in a couple 218 00:11:15,360 --> 00:11:19,320 of Fortune 500 companies where they started using our 219 00:11:19,320 --> 00:11:22,280 credential readers for time and attendance, where they affixed 220 00:11:22,280 --> 00:11:26,760 our our readers to a time clock to automate and keep track of 221 00:11:26,760 --> 00:11:28,800 who was you know clocking in and out. 222 00:11:29,200 --> 00:11:33,040 And once they saw the advantages of our technology, they started 223 00:11:33,040 --> 00:11:36,000 evolving the use of our credential readers to things 224 00:11:36,000 --> 00:11:39,880 like single sign on and secure printing and and a variety of 225 00:11:39,880 --> 00:11:42,680 other use cases. So it's it's kind of the one 226 00:11:42,680 --> 00:11:46,200 benefit that if you have a multi credential support or there's a 227 00:11:46,200 --> 00:11:48,840 need for a multi credential support in your environment, our 228 00:11:48,840 --> 00:11:50,360 readers can can support them all. 229 00:11:50,800 --> 00:11:53,760 I feel like there's a lot of different form factors and 230 00:11:53,760 --> 00:11:55,160 standards when it comes to identity. 231 00:11:55,160 --> 00:11:57,400 And I know that, you know, there's things like Fido out 232 00:11:57,400 --> 00:12:01,040 there for credentials and authentication, you know, maybe 233 00:12:01,040 --> 00:12:04,320 more historically on the logical access side, but now creeping 234 00:12:04,320 --> 00:12:08,200 into the physical side as well. I guess one of the things that 235 00:12:08,200 --> 00:12:10,080 concerns me sometimes in this space is like, OK, well, I 236 00:12:10,080 --> 00:12:12,120 bought this product and now I only have things that work with 237 00:12:12,120 --> 00:12:14,000 that product. Is there some sort of 238 00:12:14,000 --> 00:12:16,960 interoperability or things like that that from a support 239 00:12:16,960 --> 00:12:20,280 perspective where you know there are some common worldwide 240 00:12:20,280 --> 00:12:23,520 credentials that you know the organization is supporting or 241 00:12:23,520 --> 00:12:25,760 helping to contribute? To what's really cool is that 242 00:12:25,760 --> 00:12:28,600 you could see our our readers amongst so many different 243 00:12:28,800 --> 00:12:32,080 variety of of places. You know, you could could walk 244 00:12:32,080 --> 00:12:35,440 in, you could see them on a production line on a on APLC. 245 00:12:35,960 --> 00:12:41,680 You can also see them on on HM is helping secure you know those 246 00:12:41,680 --> 00:12:44,480 typical use cases for a a shared workstation. 247 00:12:44,760 --> 00:12:48,320 And again, as Raul mentioned, you know, supporting so many 248 00:12:48,320 --> 00:12:53,080 different varieties of of badges, this could be used just 249 00:12:53,080 --> 00:12:57,320 about anywhere. So, Raul, a couple of acronyms 250 00:12:57,320 --> 00:13:01,400 got dropped there. HMI, I think it was PLC. 251 00:13:01,400 --> 00:13:03,600 Can you kind of tell us what those are? 252 00:13:03,840 --> 00:13:07,160 A human machine interface is, it's a user interface that 253 00:13:07,160 --> 00:13:10,120 connects a person to a machine or system. 254 00:13:10,120 --> 00:13:13,200 So quite often you're going to see these and in manufacturing 255 00:13:13,200 --> 00:13:15,120 facilities, that's where really where you're going to see them 256 00:13:15,120 --> 00:13:18,920 in manufacturing facilities. And so with frontline workers 257 00:13:18,920 --> 00:13:22,560 there, it's it's a shared workstation where you'll want to 258 00:13:22,560 --> 00:13:26,480 see, you know, users that want to authenticate onto these 259 00:13:26,480 --> 00:13:28,640 systems. Because it's a shared 260 00:13:28,640 --> 00:13:31,760 workstation, you're typically running, you know, 3 shifts 261 00:13:31,760 --> 00:13:35,080 throughout the day. And rather than having a shared 262 00:13:35,360 --> 00:13:39,320 PIN or a password, they're going to tap their reader or they're 263 00:13:39,320 --> 00:13:41,880 going to tap their badge onto a credential reader to 264 00:13:41,880 --> 00:13:44,360 authenticate. And I think the primary purpose 265 00:13:44,360 --> 00:13:46,640 there is for accountability. You know if something were to go 266 00:13:46,640 --> 00:13:50,360 off, you know they they know who was on that shift, they know who 267 00:13:50,360 --> 00:13:53,040 was on that machine. They make sure that that person 268 00:13:53,040 --> 00:13:56,480 is certified to to use that that those machine systems. 269 00:13:56,720 --> 00:14:00,800 Yeah, and similar to APLC. So PLC is a programmable logic 270 00:14:00,800 --> 00:14:05,440 controller similar to what Raoul said it it comes down to 271 00:14:05,440 --> 00:14:09,400 accountability on those manufacturing lines, making sure 272 00:14:09,400 --> 00:14:12,680 those who are supposed to be, you know, working those lines. 273 00:14:12,680 --> 00:14:15,480 Are, are. Actually permitted to do so, 274 00:14:15,480 --> 00:14:17,440 yes. All comes down to accountability 275 00:14:17,440 --> 00:14:20,640 as well as making sure that you know you're not taking the time 276 00:14:20,640 --> 00:14:25,640 to log in and out, you know of something that could bring the 277 00:14:25,640 --> 00:14:27,760 lines down. So also productivity. 278 00:14:27,920 --> 00:14:30,280 Yeah, you know, I'm, I'm picking up on the common thread. 279 00:14:30,280 --> 00:14:33,400 So there's these shared workstations, especially in 280 00:14:33,400 --> 00:14:37,440 healthcare, you have different patient rooms regardless of 281 00:14:37,440 --> 00:14:39,280 who's logging in. It's not like they bring their 282 00:14:39,280 --> 00:14:43,520 PCs from room to room, right? There's a a PC sitting there in 283 00:14:43,520 --> 00:14:46,760 a lot of cases and they just they can tap in and out 284 00:14:47,320 --> 00:14:50,480 manufacturing floor. You've got manufacturing 285 00:14:50,480 --> 00:14:55,480 stations where people share the workstation maybe throughout the 286 00:14:55,480 --> 00:14:58,080 day. What other industries are 287 00:14:58,240 --> 00:15:01,000 because it seems to me like there's just so many industries 288 00:15:01,000 --> 00:15:04,600 where you could run into the shared workstation scenario. 289 00:15:04,960 --> 00:15:08,640 And you know, I'm wondering, are there others that you see 290 00:15:08,640 --> 00:15:12,760 traction in or some of the most interesting use cases outside of 291 00:15:12,840 --> 00:15:14,880 those two? Yeah. 292 00:15:14,880 --> 00:15:18,240 So outside of those two, you know I'll give a couple of other 293 00:15:18,240 --> 00:15:22,720 shared workstation examples. The first one is you know going 294 00:15:22,720 --> 00:15:26,040 to your earlier question Jim about kind of the remote work, 295 00:15:26,120 --> 00:15:28,080 you know you're you're starting to see these we work 296 00:15:28,080 --> 00:15:31,520 environments, right, where it's shared offices and they have 297 00:15:31,520 --> 00:15:34,200 shared workstations in an office environment. 298 00:15:34,200 --> 00:15:38,120 So really enterprise organizations that that have a 299 00:15:38,120 --> 00:15:41,880 hybrid environment, employees come in, they have their little 300 00:15:41,880 --> 00:15:43,960 cubicle set up with their workstation. 301 00:15:44,240 --> 00:15:47,000 That's a great example there where you got another shared 302 00:15:47,000 --> 00:15:50,040 workstation environment, it might even be down to the shared 303 00:15:50,040 --> 00:15:53,760 laptop, right. And so a user taps their badge 304 00:15:53,760 --> 00:15:58,200 on their credential there and it's their user you know that 305 00:15:58,200 --> 00:16:02,000 that pops up or populates on the workstation And then the other 306 00:16:02,000 --> 00:16:04,320 common one you'll see is retail, right. 307 00:16:04,320 --> 00:16:07,800 So retail associates at the point of sale, very commonplace 308 00:16:07,800 --> 00:16:10,960 where you'll start to see some shared workstations where again 309 00:16:11,040 --> 00:16:15,000 typically you'll see a lot of Max stripe readers or even 310 00:16:15,280 --> 00:16:17,480 shared pins that they're that they're leveraging there. 311 00:16:17,480 --> 00:16:19,800 And again, there it's about accountability. 312 00:16:20,000 --> 00:16:23,240 You know, big retail stores want to make sure what associates 313 00:16:23,240 --> 00:16:26,440 were on those POS lanes and making sure that there's no 314 00:16:26,440 --> 00:16:28,200 theft occurring there at the same time. 315 00:16:28,880 --> 00:16:32,120 Now that you see one, the scenario where you have one of 316 00:16:32,120 --> 00:16:35,560 these shared workstation use cases and it's a large 317 00:16:35,960 --> 00:16:38,760 percentage of the user population, but you also have 318 00:16:38,760 --> 00:16:41,640 the corporate environment where then it's like, hey, let's 319 00:16:41,640 --> 00:16:44,960 bridge it back and have this kind of level of productivity 320 00:16:44,960 --> 00:16:47,600 for everyone. Because not only do you have 321 00:16:47,600 --> 00:16:52,400 that great share, you shared PC use case, but there's also just 322 00:16:52,400 --> 00:16:55,800 a convenience factor of not having to remember a password 323 00:16:55,800 --> 00:16:59,720 and rotate a password. If I can use the same badge to, 324 00:17:00,320 --> 00:17:05,480 you know, enter the door, get into my computer, you know, stop 325 00:17:05,480 --> 00:17:08,800 and start my time card, you know, I think you referenced the 326 00:17:08,800 --> 00:17:12,240 use case like that earlier, or a situation like that earlier, but 327 00:17:12,440 --> 00:17:15,240 I bet that happens more than you suspect. 328 00:17:15,960 --> 00:17:17,720 Absolutely. I mean work workforce 329 00:17:17,720 --> 00:17:20,680 productivity is is absolutely important with a lot of 330 00:17:20,680 --> 00:17:22,680 organizations. They want to make sure their 331 00:17:23,000 --> 00:17:26,400 their employees are efficient. So I I completely agree with you 332 00:17:26,400 --> 00:17:28,160 there, Jim. Yeah. 333 00:17:28,359 --> 00:17:31,840 So you talked about imprevada and that that healthcare 334 00:17:31,840 --> 00:17:34,560 scenario, I'd like to hear more about that. 335 00:17:34,560 --> 00:17:39,440 I mean you know is it make you I would imagine is making a lot of 336 00:17:39,440 --> 00:17:43,280 productivity impact on top of just the security. 337 00:17:43,280 --> 00:17:46,480 And like what I was, you know what impacted me First off was 338 00:17:47,080 --> 00:17:50,120 you know the ability to get in there quickly and and have it be 339 00:17:50,120 --> 00:17:51,960 reliable. But I would think from a 340 00:17:51,960 --> 00:17:55,640 productivity standpoint it's also like a huge impact. 341 00:17:55,640 --> 00:17:57,440 But what do you what do you really see out of this 342 00:17:57,440 --> 00:17:59,840 improvised use case? Yeah. 343 00:17:59,840 --> 00:18:03,920 So they, you know, jointly, we conducted a study a while back 344 00:18:03,920 --> 00:18:06,120 where improvised. I went out there to some of 345 00:18:06,120 --> 00:18:09,200 their end users and started to understand like what is the real 346 00:18:09,560 --> 00:18:12,200 return on investment that a healthcare organization's 347 00:18:12,200 --> 00:18:15,120 getting out of this, this joint solution, right. 348 00:18:15,120 --> 00:18:19,680 And So what they found was a lot of these nurses were typing in a 349 00:18:19,680 --> 00:18:24,480 password up to 70 times a day, you know, so and and they 350 00:18:24,480 --> 00:18:27,040 started do a little bit of a time study around it and they 351 00:18:27,040 --> 00:18:31,720 found that each clinician, so a nurse as an example was saving 352 00:18:31,720 --> 00:18:35,840 upwards of 45 minutes per shift just by not having to type in 353 00:18:35,840 --> 00:18:38,480 their password or do a password reset. 354 00:18:38,600 --> 00:18:42,160 So there was, there was time savings there of 45 minutes per 355 00:18:42,160 --> 00:18:46,680 person but then when you factor in the actual password resets 356 00:18:46,680 --> 00:18:51,360 that caused their IT team time and money that was an additional 357 00:18:51,360 --> 00:18:55,520 $770 per password reset that they had to do as well. 358 00:18:55,520 --> 00:18:59,120 So I think at the end it, it looked like with some of the 359 00:18:59,120 --> 00:19:02,960 major hospitals they were saving upwards of $1,000,000 a year 360 00:19:03,000 --> 00:19:05,680 just on on cutting out password resets. 361 00:19:06,600 --> 00:19:08,760 Yeah, there's no doubt that they're saving money. 362 00:19:08,760 --> 00:19:13,000 But I also think, like from a security standpoint, if you just 363 00:19:13,000 --> 00:19:15,760 type your password 70 times a day, guess what you're doing, 364 00:19:15,960 --> 00:19:17,920 you're picking the easiest password. 365 00:19:17,920 --> 00:19:20,760 And then when it comes time to change your password, you're 366 00:19:20,760 --> 00:19:24,160 just adding an extra exclamation point or a dollar sign or 367 00:19:24,440 --> 00:19:27,440 whatever you do to kind of increment it. 368 00:19:27,800 --> 00:19:30,760 But you know, bro, just to kind of key off of one thing that you 369 00:19:30,760 --> 00:19:34,240 mentioned and I don't, you know, you just mentioned it once, but 370 00:19:34,240 --> 00:19:37,240 you mentioned something about secure printers. 371 00:19:37,440 --> 00:19:39,760 So can you expand on that use case a little bit? 372 00:19:39,960 --> 00:19:44,400 So secure printing, the use case there is when you look at highly 373 00:19:44,400 --> 00:19:49,240 regulated environments like finance, like healthcare where 374 00:19:49,520 --> 00:19:53,400 information that is printed on a multi functional printer can be, 375 00:19:53,680 --> 00:19:56,280 you know it's it's somebody's privacy, right, it's somebody's 376 00:19:56,280 --> 00:20:00,320 confidential information, you have regulations like HIPAA. 377 00:20:00,760 --> 00:20:05,200 And the Sarbanes-Oxley act where you can't be leaving 378 00:20:05,200 --> 00:20:07,280 confidential information just laying around. 379 00:20:07,640 --> 00:20:10,320 And so with secure printing, what that enables an 380 00:20:10,320 --> 00:20:15,200 organization to do is, you know, a typical scenario is, you know, 381 00:20:15,200 --> 00:20:18,960 I go to my workstation, I go to hit the print button and then 382 00:20:18,960 --> 00:20:22,160 when I walk over to the multi functional printer, the paper's 383 00:20:22,160 --> 00:20:24,920 already already there, right? So I just pick it up and I walk 384 00:20:24,920 --> 00:20:27,160 away. But in these, in these 385 00:20:27,160 --> 00:20:30,440 environments where it's highly regulated, this information just 386 00:20:30,440 --> 00:20:31,920 can't be laying on the printer, right? 387 00:20:31,960 --> 00:20:34,560 Somebody forgets about it, somebody else comes over, they 388 00:20:34,560 --> 00:20:37,280 grab the paperwork and all of a sudden somebody's Social 389 00:20:37,280 --> 00:20:39,720 Security number is is stolen, right? 390 00:20:39,720 --> 00:20:42,320 Somebody's patient information is is taken. 391 00:20:42,680 --> 00:20:46,080 And so the way it works with our technology is our readers are 392 00:20:46,080 --> 00:20:49,800 embedded into these printers. And so I go to my workstation, I 393 00:20:49,800 --> 00:20:52,160 print it. Nothing actually prints onto the 394 00:20:52,160 --> 00:20:54,360 printer until I actually walk up to the printer. 395 00:20:54,560 --> 00:20:57,160 I tap my badge on the reader that's embedded within the 396 00:20:57,160 --> 00:21:00,200 printer and then it actually releases the job, the print job. 397 00:21:00,560 --> 00:21:02,480 Yeah. I mean I've always said like as 398 00:21:02,480 --> 00:21:06,480 IT professionals one of the things that we need to do is 399 00:21:07,200 --> 00:21:10,200 make things more automated make people more efficient. 400 00:21:10,200 --> 00:21:14,840 This sounds it's like it's right up that that alley where and 401 00:21:14,840 --> 00:21:18,640 besides the environmental factor right instead of like getting 402 00:21:18,640 --> 00:21:21,280 printed and someone just tossing in the trash can never gets 403 00:21:21,280 --> 00:21:24,800 printed until actually the receiver is there to cap it and 404 00:21:24,800 --> 00:21:27,720 get it. So I love all those factors kind 405 00:21:27,720 --> 00:21:31,160 of getting the sense that you're talking about like there's just 406 00:21:31,200 --> 00:21:37,000 OEM embedding use cases and I'm wondering how does, how do you 407 00:21:37,000 --> 00:21:42,040 go about integrating your technology into other products? 408 00:21:42,600 --> 00:21:45,560 Yeah. So we actually have a portfolio 409 00:21:45,800 --> 00:21:49,760 Wave ID is really the the base of our portfolio and within 410 00:21:49,760 --> 00:21:52,360 there we have several different form factors. 411 00:21:52,360 --> 00:21:55,720 You know, there's desktop readers, we have these what we 412 00:21:55,720 --> 00:21:58,920 call nano readers that are you know the the the world's 413 00:21:58,920 --> 00:22:02,280 basically smallest credential reader on the market today. 414 00:22:02,840 --> 00:22:06,400 But part part of that portfolio is also our OEM embedded modules 415 00:22:06,760 --> 00:22:12,000 that we work with different, you know, print laptop, you know 416 00:22:12,000 --> 00:22:15,880 medical device manufacturers out there where they want to have 417 00:22:15,880 --> 00:22:20,200 secure authentication as part of their overall hardware. 418 00:22:20,360 --> 00:22:23,320 And so we'll work with them to make sure that you know we 419 00:22:23,320 --> 00:22:27,440 conduct A sizing study and embed our technology with them and 420 00:22:27,440 --> 00:22:30,880 then along the ways get get the certification that's required 421 00:22:30,880 --> 00:22:34,120 like FDA and everything else. So, So yeah, we work with a lot 422 00:22:34,120 --> 00:22:36,960 of a lot of hardware manufacturers that want to 423 00:22:36,960 --> 00:22:39,960 implement secure authentication as part of their end product. 424 00:22:40,240 --> 00:22:42,560 Now imagine that you're probably working with lots of partners in 425 00:22:42,560 --> 00:22:46,120 that space and I guess sort of that you know go to market 426 00:22:46,120 --> 00:22:48,120 strategy of how do you, how do you get your product in the 427 00:22:48,120 --> 00:22:49,960 hands of as many people as possible, right. 428 00:22:49,960 --> 00:22:51,560 That's that's sort of the goal here. 429 00:22:51,560 --> 00:22:55,160 So I guess is that, you know, that sounds like that's one of 430 00:22:55,160 --> 00:22:57,400 the methods. Are there other methods of how, 431 00:22:57,840 --> 00:22:59,480 you know, how do you get this thing to become like, Oh yeah, 432 00:22:59,480 --> 00:23:01,760 This is why aren't we using this everywhere else? 433 00:23:01,760 --> 00:23:04,400 Is it are you talking to customers, Are you talking to 434 00:23:04,400 --> 00:23:07,240 like partners? Are you talking to, you know, 435 00:23:07,240 --> 00:23:09,720 the Octas, the pings, the Microsofts of the world say, 436 00:23:09,720 --> 00:23:12,160 hey, you know, we've got this fantastic product, how can we 437 00:23:12,160 --> 00:23:13,840 work together? What are What are some of the 438 00:23:13,840 --> 00:23:15,800 ideas that you've got there? No pun intended. 439 00:23:17,800 --> 00:23:19,080 Yeah, Jeff, it's a great question. 440 00:23:19,080 --> 00:23:22,360 I I think when you look at kind of you know we call it the 441 00:23:22,360 --> 00:23:25,520 routes, the market, there's three different avenues that 442 00:23:25,520 --> 00:23:28,440 that we kind of go to market. The the first one is kind of 443 00:23:28,440 --> 00:23:32,560 your traditional systems integrators or or value added 444 00:23:32,560 --> 00:23:36,880 resellers that you know they own the relationship with the 445 00:23:36,880 --> 00:23:39,360 customer out there. They're kind of presenting 446 00:23:39,360 --> 00:23:41,320 different solutions, understanding what the pain 447 00:23:41,320 --> 00:23:44,920 points and then they come to us and say hey this is what my 448 00:23:44,920 --> 00:23:48,000 customers pain points are, help us find a solution for that 449 00:23:48,000 --> 00:23:51,160 customer. And so we you know we sell the 450 00:23:51,160 --> 00:23:53,520 products through our distribution channel down to our 451 00:23:53,520 --> 00:23:56,320 channel partners and then ultimately they're the ones 452 00:23:56,320 --> 00:24:00,120 selling the product to the end user that's that's kind of the 453 00:24:00,120 --> 00:24:03,880 first throughout the market. The second one is through Isvs 454 00:24:03,880 --> 00:24:07,920 or independent software vendors. So we work with you know variety 455 00:24:07,920 --> 00:24:11,040 of different application software providers. 456 00:24:11,040 --> 00:24:14,720 So we mentioned a few like print management software. 457 00:24:14,840 --> 00:24:17,240 You know, there's time and attendance software. 458 00:24:17,240 --> 00:24:20,840 There's things like single sign on like like Improvata use case 459 00:24:20,840 --> 00:24:23,560 that we talked about. And what we'll do is we'll work 460 00:24:23,560 --> 00:24:27,400 with a lot of these Isvs, work on an integration between their 461 00:24:27,400 --> 00:24:30,520 software and our hardware. And then ultimately they're 462 00:24:30,520 --> 00:24:33,160 going to market with the full solution, the full software and 463 00:24:33,160 --> 00:24:35,680 hardware solution. And then the third one is the 464 00:24:35,680 --> 00:24:38,480 one that we just touched on a couple minutes ago, which is the 465 00:24:38,480 --> 00:24:41,680 OEM route, right. So we work with some of the OEM 466 00:24:41,680 --> 00:24:46,200 manufacturers again in the in the print space, laptops, 467 00:24:46,720 --> 00:24:50,440 medical devices where they'll take our OEM modules embedded 468 00:24:50,440 --> 00:24:53,160 into their hardware technology and then they sell it as a 469 00:24:53,440 --> 00:24:56,800 full-fledged system or solution to to the customer. 470 00:24:56,800 --> 00:25:00,840 So we are our primary go to market strategy is to go through 471 00:25:00,840 --> 00:25:03,800 the channel. We don't really sell direct at 472 00:25:03,800 --> 00:25:06,200 all. So we we tend to go through the 473 00:25:06,200 --> 00:25:09,400 channel. You know what I, I see the 474 00:25:10,240 --> 00:25:15,720 trending so much in the digital identity space is just this move 475 00:25:15,720 --> 00:25:19,720 from password, you know, knowledge based authentication 476 00:25:19,720 --> 00:25:22,640 to possession based authentication. 477 00:25:22,960 --> 00:25:26,640 Sorry, I was actually wondering, you know, I saw a brochure that 478 00:25:26,640 --> 00:25:30,480 you guys have around your digital wallet technology. 479 00:25:30,480 --> 00:25:33,360 It's just like I was drawn to it. 480 00:25:33,360 --> 00:25:36,320 It's like a a mobile app. Maybe you can tell us a little 481 00:25:36,320 --> 00:25:38,680 bit about it. Yeah. 482 00:25:38,680 --> 00:25:42,360 So it's been highly, highly requested years ago. 483 00:25:42,360 --> 00:25:46,400 We, we started in the the Bluetooth space recently. 484 00:25:46,400 --> 00:25:50,240 Now folks want to kind of go more of the the NFC route. 485 00:25:50,240 --> 00:25:53,280 So kind of like an Apple wall integration. 486 00:25:53,440 --> 00:25:55,160 So with the Apple Wall integration, you know you're 487 00:25:55,160 --> 00:25:59,120 offering customers still a tap and go experience. 488 00:25:59,120 --> 00:26:02,800 So you have your your credential on your phone embedded inside 489 00:26:02,800 --> 00:26:08,080 your Apple Wallet, still a tap and go experience somewhere to a 490 00:26:08,080 --> 00:26:12,000 way that you would present a card and also giving the 491 00:26:12,000 --> 00:26:15,160 customer an even more secure credential. 492 00:26:15,240 --> 00:26:18,080 Yeah, I think what's what's really cool about it is 493 00:26:18,360 --> 00:26:21,720 obviously as an app there's no hardware cost, right you're 494 00:26:21,960 --> 00:26:26,040 you're pushing it down to somebody's pre-existing, you 495 00:26:26,040 --> 00:26:29,560 know that a device that they probably own themselves. 496 00:26:29,560 --> 00:26:35,080 So it it kind of manages that hurdle, but at the same time you 497 00:26:35,320 --> 00:26:39,880 potentially still have the option for the hardware based 498 00:26:39,880 --> 00:26:42,120 solution. I'm just wondering like that 499 00:26:42,120 --> 00:26:46,240 seems like an industry trend. What are some of the other 500 00:26:46,240 --> 00:26:49,120 trends that you're seeing, Raul? Yeah. 501 00:26:49,120 --> 00:26:51,640 So I mean just to add on a little bit more on the mobile 502 00:26:51,640 --> 00:26:55,760 credentials, we look at you know 2023 for our organization, you 503 00:26:55,760 --> 00:26:59,600 know, three of the four largest deployments that we had in 23 504 00:26:59,600 --> 00:27:01,520 were all mobile credentials, right. 505 00:27:01,520 --> 00:27:05,200 I I think we're starting to see a lot more organizations that 506 00:27:05,200 --> 00:27:09,160 want a future proof their environment and kind of start to 507 00:27:09,160 --> 00:27:12,800 stray a little bit away from ID, from physical ID batches, which 508 00:27:12,800 --> 00:27:14,520 you know what we continue to support. 509 00:27:14,520 --> 00:27:17,480 We see a lot of environments where they still want to have a 510 00:27:17,480 --> 00:27:21,840 combination of physical batches for one part of their office and 511 00:27:21,840 --> 00:27:24,880 mobile for another part of their for for their office. 512 00:27:24,880 --> 00:27:29,200 So but we are starting to see a big shift away from physical to 513 00:27:29,200 --> 00:27:32,800 mobile and in particular as Sarah mentioned kind of the 514 00:27:33,640 --> 00:27:37,160 shift to NFC in particular or the OR the digital wallets. 515 00:27:37,200 --> 00:27:40,720 And and we really simply launched a press release about a 516 00:27:40,720 --> 00:27:44,960 month ago where we just became Apple certified for for the 517 00:27:44,960 --> 00:27:47,360 Apple Wallet. But in terms of other you know 518 00:27:47,360 --> 00:27:51,360 trends that we're seeing out there is for those organizations 519 00:27:51,360 --> 00:27:54,800 that still want to stay with their physical badge this big 520 00:27:54,800 --> 00:27:56,880 move to secure credentials, right. 521 00:27:56,880 --> 00:28:01,360 So proximity is kind of, you know, was the first flavor of ID 522 00:28:01,360 --> 00:28:03,600 badges that ever existed out there. 523 00:28:03,960 --> 00:28:06,480 What we've come to find obviously now you know that 524 00:28:06,480 --> 00:28:09,240 we've been in this space for a while is that proximity 525 00:28:09,240 --> 00:28:12,000 credentials are not the most secure, right. 526 00:28:12,000 --> 00:28:15,720 You know, somebody can take it, replicate it and and can you 527 00:28:15,720 --> 00:28:18,280 know hack into your your facility, right, from a physical 528 00:28:18,560 --> 00:28:21,760 access control perspective. But and the same thing for 529 00:28:21,760 --> 00:28:25,640 logical right, somebody steals your badge but now with physical 530 00:28:25,960 --> 00:28:30,000 what we're starting to see is you know is more a move to 531 00:28:30,000 --> 00:28:32,920 secure credentials within their environment. 532 00:28:32,920 --> 00:28:35,280 So they want some level of encryption. 533 00:28:35,600 --> 00:28:39,920 And then to add another piece to it is you start to see this move 534 00:28:39,920 --> 00:28:43,400 to multi factor authentication where you know they're assigning 535 00:28:43,440 --> 00:28:48,920 either pass keys or a personal PIN or even biometrics to kind 536 00:28:48,920 --> 00:28:52,080 of have that second and third layer of security for for their 537 00:28:52,080 --> 00:28:55,720 employees. Yeah, you know, it's got me 538 00:28:55,720 --> 00:28:58,440 thinking. So we got the shared workstation 539 00:28:58,440 --> 00:29:00,840 scenario, let's say the hospital room. 540 00:29:01,280 --> 00:29:05,080 Then you've also got folks who are, you know, maybe using 541 00:29:05,080 --> 00:29:08,920 laptops, but they're more stationary, but still have this 542 00:29:08,920 --> 00:29:12,880 use case that we're talking about from a hardware 543 00:29:12,880 --> 00:29:16,200 perspective, I mean, do are we looking at the same thing? 544 00:29:16,720 --> 00:29:19,840 Are the those proximity readers basically the same device 545 00:29:19,840 --> 00:29:23,600 whether you're talking about like a corporate workstation or 546 00:29:24,000 --> 00:29:25,600 something in the clinical setting? 547 00:29:26,320 --> 00:29:30,040 Yeah, I mean we we have several different form factors of how 548 00:29:30,160 --> 00:29:33,080 you know organizations want to deploy our readers. 549 00:29:33,080 --> 00:29:37,160 We do have some that are mounted on walls, some of them that are 550 00:29:37,160 --> 00:29:39,680 sitting on a desk. But at the end of the day the 551 00:29:39,680 --> 00:29:43,120 beauty of our technology is we do have you know readers that 552 00:29:43,120 --> 00:29:45,600 support all different technologies in one, right. 553 00:29:45,600 --> 00:29:50,240 So as an example or Wave ID Mobile Mini is is one of the 554 00:29:50,240 --> 00:29:54,440 products in our offering where you know in that same device, if 555 00:29:54,440 --> 00:29:58,360 they want to support Apple Wallet credentials, if they want 556 00:29:58,360 --> 00:30:02,520 to support BLE credentials, if they want to support physical 557 00:30:02,520 --> 00:30:06,480 credentials, they can do that by standardizing on one product 558 00:30:06,480 --> 00:30:08,760 within their whole environment. Yeah. 559 00:30:08,760 --> 00:30:13,120 So it seems like you guys are are really like on this edge of 560 00:30:13,680 --> 00:30:18,960 using the the mobile device. What about biometrics? 561 00:30:19,080 --> 00:30:23,720 Because I think biometrics is kind of like the the trend 562 00:30:23,720 --> 00:30:27,800 that's really picking up steam with the Face ID technology and 563 00:30:27,800 --> 00:30:30,360 things like that. Where does that fit into? 564 00:30:31,320 --> 00:30:33,120 You know, your stack of solutions? 565 00:30:34,160 --> 00:30:38,640 Yeah, So we have a a product called the, the Wave ID bio. 566 00:30:39,160 --> 00:30:42,760 The wave ID bio basically incorporates all these great RF 567 00:30:42,760 --> 00:30:46,000 technologies that we've been discussing along with a 568 00:30:46,000 --> 00:30:49,480 fingerprint scanner. So when we're talking in a world 569 00:30:49,480 --> 00:30:53,320 of even multi factor authentication, you can scan 570 00:30:53,320 --> 00:30:58,280 your ID badge and then also scan your your fingerprint for one 571 00:30:58,280 --> 00:31:01,560 way to have a multi factor authentication. 572 00:31:01,920 --> 00:31:04,960 Some of our partners also I mean they've they've embedded this 573 00:31:04,960 --> 00:31:09,440 product into their product. So making it very, very easy, 574 00:31:09,440 --> 00:31:12,800 especially let's say in a healthcare scenario to have 575 00:31:13,040 --> 00:31:16,520 literally right at their fingertips a way of doing multi 576 00:31:16,520 --> 00:31:19,360 factor authentication, biometric and RFI. 577 00:31:19,720 --> 00:31:21,720 Think this is a really important concept. 578 00:31:21,720 --> 00:31:27,560 So can these kind of traditional proximity cards and like a wave 579 00:31:27,560 --> 00:31:33,320 ID bio live side by side you know all and because to me 580 00:31:33,320 --> 00:31:38,440 that's always the challenge in IT is marrying legacy 581 00:31:38,440 --> 00:31:42,480 technologies and I'm not calling the it's still much better than 582 00:31:42,480 --> 00:31:45,560 the password right. But like now there's more 583 00:31:45,560 --> 00:31:48,800 cutting edge stuff and having them live side by side. 584 00:31:49,640 --> 00:31:51,600 I think that's the the real ticket. 585 00:31:52,400 --> 00:31:55,320 Yeah, absolutely. Yeah, it's a all in one product. 586 00:31:55,320 --> 00:31:58,800 So still leveraging you know whether you have an HID Prox 587 00:31:58,800 --> 00:32:02,920 badge or you know any any of the 100 badges that we that we 588 00:32:02,920 --> 00:32:06,280 support you can you can still use those along with the the 589 00:32:06,280 --> 00:32:10,280 biometric reader. Back in my day, I used to manage 590 00:32:10,280 --> 00:32:13,600 physical security, which meant ID badges and readers and things 591 00:32:13,600 --> 00:32:15,160 like that. And I think one of the things 592 00:32:15,160 --> 00:32:17,800 that I was when I was reading up on your company, one of the 593 00:32:17,800 --> 00:32:20,240 features out there is Reader Remote Management, which sounds 594 00:32:20,240 --> 00:32:23,040 very interesting to me because that is not something that I had 595 00:32:23,040 --> 00:32:25,680 before. So that meant I had to go out to 596 00:32:25,680 --> 00:32:27,960 specific readers, make sure they were, you know, connected to the 597 00:32:27,960 --> 00:32:30,160 networks, download card holder data, right? 598 00:32:30,160 --> 00:32:32,760 All that stuff. For those who aren't familiar 599 00:32:32,760 --> 00:32:37,320 with Reader remote management, tell us about what that is and 600 00:32:37,320 --> 00:32:40,920 why that is so important for people who haven't experienced 601 00:32:40,920 --> 00:32:44,760 that joy yet. Yeah, so one of the overwhelming 602 00:32:44,760 --> 00:32:48,200 demands we've started to get from not only our partners but 603 00:32:48,200 --> 00:32:51,640 end users is these readers are great, right? 604 00:32:51,640 --> 00:32:55,800 They work seamlessly with the different credentials types that 605 00:32:55,800 --> 00:32:58,400 are out there and what they have deployed in their environment. 606 00:32:58,800 --> 00:33:01,840 But what they wanted to, you know, what they've Billy been 607 00:33:01,840 --> 00:33:05,320 asking RF ideas for is a way to manage their devices in the 608 00:33:05,320 --> 00:33:08,600 field. So anytime there's a requirement 609 00:33:08,600 --> 00:33:12,640 for a firmware update, whether that's to, you know, fix bugs, 610 00:33:12,640 --> 00:33:17,360 whether that's to update feature enhancements on our devices, you 611 00:33:17,360 --> 00:33:20,880 know, historically it was a little bit of a pain to update 612 00:33:20,960 --> 00:33:22,440 our readers with that firmware, right? 613 00:33:22,440 --> 00:33:26,440 They had to go to every individual reader and tap a 614 00:33:26,440 --> 00:33:30,360 configuration card or connect it to their PC and use some of our 615 00:33:30,440 --> 00:33:32,240 software tools to be able to do that. 616 00:33:32,680 --> 00:33:37,280 Well, this concept of, you know, device management has been, you 617 00:33:37,280 --> 00:33:40,160 know, out there for a long time, especially in mobile devices. 618 00:33:40,520 --> 00:33:43,960 And so we kind of replicated that same concept to say, hey, 619 00:33:44,480 --> 00:33:47,240 we're going to build this tool that enables organizations that 620 00:33:47,240 --> 00:33:52,040 can you know update all their fleet of readers on their 621 00:33:52,040 --> 00:33:55,560 network all at once, right. And just like with mobile 622 00:33:55,560 --> 00:34:00,000 devices, they, they do it probably after hours and IT team 623 00:34:00,000 --> 00:34:03,240 will just push out an update and let all their readers get 624 00:34:03,240 --> 00:34:05,720 updated overnight, right. To to be able to do that 625 00:34:05,720 --> 00:34:09,320 seamlessly versus having to go one by one and waste IT 626 00:34:09,320 --> 00:34:12,440 resources, time and money. So it's just a much, much more 627 00:34:12,440 --> 00:34:15,719 efficient way for organizations to update their readers or 628 00:34:15,719 --> 00:34:18,159 reconfigure their readers. You know, very often we're 629 00:34:18,159 --> 00:34:21,639 seeing organizations that are shifting from 1 credential to 630 00:34:21,639 --> 00:34:22,880 another. You know, that could be a 631 00:34:22,880 --> 00:34:25,000 physical credential to a mobile credential. 632 00:34:25,320 --> 00:34:28,480 And this is a way to reconfigure those devices to now say, hey, 633 00:34:28,880 --> 00:34:31,520 we're now reading this new mobile credential and let's 634 00:34:31,520 --> 00:34:34,159 update all the readers to be able to read that new updated 635 00:34:34,159 --> 00:34:36,159 mobile credential. I would imagine that helps too, 636 00:34:36,159 --> 00:34:38,520 with making sure that things stay current for threats and 637 00:34:38,520 --> 00:34:40,159 attacks, right? There's always something that's 638 00:34:40,679 --> 00:34:43,760 needs to be patched or updated. I guess from a security 639 00:34:43,760 --> 00:34:46,600 perspective it helps with that as well, right? 640 00:34:46,600 --> 00:34:49,920 Being able to deploy a patch or firmware updated, whatever it 641 00:34:49,920 --> 00:34:51,360 may be right to stay on top of things. 642 00:34:52,440 --> 00:34:53,440 Absolutely. Yeah. 643 00:34:53,440 --> 00:34:57,280 I mean any any bugs we found any security you know risk that we 644 00:34:57,280 --> 00:35:01,200 found it's the great thing is we have a great customer and 645 00:35:01,200 --> 00:35:03,560 partner base out there that that brings us things to our 646 00:35:03,560 --> 00:35:06,080 attention. And you know where we run as a 647 00:35:06,080 --> 00:35:09,640 very nimble organization our engineering team is jumps right 648 00:35:09,640 --> 00:35:13,560 on these these bugs and and whatever we we find a a patch 649 00:35:13,560 --> 00:35:15,960 for it. We we redeploy the the new 650 00:35:15,960 --> 00:35:18,480 firmware and then we get it out to our partners and customers 651 00:35:18,480 --> 00:35:21,840 and you know more times than not we can fix these things in in 652 00:35:21,840 --> 00:35:24,000 less than 24 hours. So we've been talking about 653 00:35:24,000 --> 00:35:26,920 password less kind of throughout here as kind of a common thread. 654 00:35:26,920 --> 00:35:29,160 It seems like it's weaving its way around, which is great. 655 00:35:29,160 --> 00:35:30,960 I don't know anybody who likes passwords. 656 00:35:31,560 --> 00:35:35,560 I was browsing the site and it came across this Converge ID 657 00:35:35,560 --> 00:35:39,760 Password Plat Password less platform and it talks about 658 00:35:39,760 --> 00:35:43,280 basically converting over to Fido 2 security credentials, 659 00:35:43,280 --> 00:35:46,120 which is fantastic. And we certainly have, you know, 660 00:35:46,200 --> 00:35:48,320 talked with Fido people in the past. 661 00:35:48,720 --> 00:35:51,480 This is one of those first steps to removing passwords. 662 00:35:51,840 --> 00:35:55,520 But can you talk a little bit about the Converge ID platform, 663 00:35:55,520 --> 00:35:58,560 the password list platform and how that differs maybe from 664 00:35:58,560 --> 00:36:00,120 something like Wave ID, which you've mentioned as well? 665 00:36:00,120 --> 00:36:01,720 Because I know we're going to talk about that here in a second 666 00:36:01,720 --> 00:36:02,760 too. I want to ask you about that. 667 00:36:03,000 --> 00:36:05,320 Sure. So the Converge ID is our 668 00:36:05,320 --> 00:36:09,800 solution for users to have a password list experience. 669 00:36:10,240 --> 00:36:13,440 What's really cool about the solution and what sets us apart 670 00:36:13,440 --> 00:36:17,520 from other Fido 2 software solutions is that we can take 671 00:36:17,600 --> 00:36:21,960 the users current badge that they use to get into the door or 672 00:36:22,320 --> 00:36:25,440 whatever they're using it for. So it can be a a standard prox 673 00:36:25,440 --> 00:36:27,360 badge. Basically what the solution does 674 00:36:27,360 --> 00:36:34,040 is it turns it into a a Fido badge, so no added cost to the 675 00:36:34,040 --> 00:36:37,160 customer consumer and then offering that the extra layer of 676 00:36:37,160 --> 00:36:39,040 security. That's pretty amazing, I think. 677 00:36:39,040 --> 00:36:40,840 You take you so you take your existing badge. 678 00:36:40,840 --> 00:36:43,960 You don't have to rebadge your population, which is a pain in 679 00:36:43,960 --> 00:36:45,960 the butt. Yes, and expensive. 680 00:36:46,200 --> 00:36:47,080 And expensive. Yeah. 681 00:36:47,240 --> 00:36:49,560 And logistically a nightmare. And yeah, I've. 682 00:36:49,920 --> 00:36:51,520 I've been through that. I don't wish that anybody. 683 00:36:51,520 --> 00:36:53,720 Sometimes you have to do it for no, you know, for for reasons. 684 00:36:53,720 --> 00:36:57,680 But so I can take my existing ID badge, convert it into a 685 00:36:57,680 --> 00:37:02,040 password list credential, and then combine that with a wave ID 686 00:37:02,040 --> 00:37:04,040 reader. Is that how that would work to 687 00:37:04,080 --> 00:37:06,360 do? That that's exactly how it would 688 00:37:06,360 --> 00:37:08,160 work. So it's basically taking you 689 00:37:08,160 --> 00:37:11,320 know the option to to log in using the security key but 690 00:37:11,320 --> 00:37:14,320 instead of actually having to have that that Fido key using 691 00:37:14,320 --> 00:37:17,960 your your prox badges the Fido key and then in turn you can 692 00:37:17,960 --> 00:37:21,160 turn that into multi factor by adding a pen on the other side 693 00:37:21,160 --> 00:37:23,800 of that so. So tell me about the Wave ID 694 00:37:23,800 --> 00:37:27,240 platform then how is that different from the Converge ID 695 00:37:27,400 --> 00:37:31,720 password WAS platform? We've got Wave ID platform to 696 00:37:31,720 --> 00:37:34,440 help me understand sort of the positioning of of Wave ID and 697 00:37:34,440 --> 00:37:36,600 how that interacts. Yeah. 698 00:37:36,600 --> 00:37:39,960 So, so Converge ID, if you look at it that way, converge ID is 699 00:37:39,960 --> 00:37:42,120 the software side of our portfolio. 700 00:37:42,440 --> 00:37:45,800 Wave ID is the name that we give to our hardware platform. 701 00:37:45,880 --> 00:37:49,240 So you know we have several products out there like the Wave 702 00:37:49,240 --> 00:37:53,120 ID plus mini. We have the Wave ID Mobile Mini, 703 00:37:53,120 --> 00:37:57,640 the Wave ID Nano, the Wave IDSP Plus and the OEM embedded 704 00:37:57,720 --> 00:38:00,280 products. These are all part of our Wave 705 00:38:00,280 --> 00:38:03,720 ID hardware platform. So these are the actual physical 706 00:38:03,720 --> 00:38:07,120 credential readers that get deployed out there in different 707 00:38:07,120 --> 00:38:09,080 environments. So if you look at the two, 708 00:38:09,080 --> 00:38:11,560 Converge ID is our software, Wave ID is our hardware 709 00:38:11,560 --> 00:38:13,240 platform. Gotcha. 710 00:38:13,240 --> 00:38:15,800 So the combination of the both is really is really the 711 00:38:15,800 --> 00:38:17,880 differentiator saying we've got both the hardware and the 712 00:38:17,880 --> 00:38:21,200 software side, we're able to do this conversion, we've got 713 00:38:21,200 --> 00:38:25,280 password lists, everybody's happy and everybody you know 714 00:38:25,280 --> 00:38:26,960 that that the solution kind of works together. 715 00:38:26,960 --> 00:38:29,200 And then you've got the OEM side of things where you're 716 00:38:29,200 --> 00:38:32,240 integrating directly with other hardware vendors, right, that 717 00:38:32,240 --> 00:38:35,200 might be out there as well to integrate that same technology. 718 00:38:35,200 --> 00:38:37,400 So now you've got this cross-platform compatibility 719 00:38:37,400 --> 00:38:39,960 which sounds pretty sounds almost too good to be true. 720 00:38:39,960 --> 00:38:42,280 I'll be honest with you Rob. There's got to be a catch here 721 00:38:42,280 --> 00:38:43,680 somewhere. Yeah. 722 00:38:43,680 --> 00:38:46,440 Well, I I think the catch there Jeff is that we still need 723 00:38:46,440 --> 00:38:48,360 partners to deploy this stuff, right. 724 00:38:48,360 --> 00:38:50,640 I mean we don't, we don't do it, all right. 725 00:38:50,640 --> 00:38:54,520 We we're still very, very, very reliant on our channel partners 726 00:38:54,520 --> 00:38:57,400 out there whether that's the application software through our 727 00:38:57,400 --> 00:39:00,920 Isvs, whether that's through the systems integrators who provide 728 00:39:00,920 --> 00:39:03,880 their service and implementation and deployment services. 729 00:39:04,160 --> 00:39:07,520 So. So while it sounds too good to 730 00:39:07,520 --> 00:39:09,840 be true there with with the hardware and the software that 731 00:39:09,840 --> 00:39:12,680 that we're kind of bringing to market, you know I I do want to 732 00:39:12,680 --> 00:39:15,880 kind of re emphasize that you know we don't go to RAC, we we 733 00:39:15,880 --> 00:39:19,160 are very reliant and we value our channel partners out there. 734 00:39:19,480 --> 00:39:25,400 My initial impression when I looked at the RFI DS website was 735 00:39:25,400 --> 00:39:28,760 man, you could really make a business out of this. 736 00:39:29,040 --> 00:39:33,680 I think what I've I've come to listening to more about the 737 00:39:33,680 --> 00:39:38,240 solutions today is like, well I see a huge value add here, but I 738 00:39:38,240 --> 00:39:42,240 also see this is like a great model for your partners. 739 00:39:42,600 --> 00:39:46,400 Yeah, no, it it's a great, you know if we look at our our 740 00:39:46,400 --> 00:39:49,760 channel model, it's it's very, very traditional to what you see 741 00:39:49,760 --> 00:39:53,320 with with other hardware manufacturers that sell through 742 00:39:53,320 --> 00:39:56,120 a channel, right. And so the beauty and and the 743 00:39:56,120 --> 00:39:59,760 advantage or the benefit for our partners is that you know they 744 00:39:59,760 --> 00:40:03,520 can wrap around their services. They're the ones that own the 745 00:40:03,520 --> 00:40:05,920 relationship with the end user customers. 746 00:40:06,280 --> 00:40:10,120 And so you know, we just partner together behind the scenes to 747 00:40:10,120 --> 00:40:12,680 make sure that we're providing the best solution for our 748 00:40:12,680 --> 00:40:15,080 partners. But at the end of the day, they 749 00:40:15,080 --> 00:40:17,280 own the relationship with the customers they're. 750 00:40:17,640 --> 00:40:19,760 They're making their, their profitability, they're putting 751 00:40:19,760 --> 00:40:23,800 their margin mark up on it and they can still be very highly 752 00:40:23,800 --> 00:40:25,400 profitable. You know a lot of our, our 753 00:40:25,400 --> 00:40:28,080 partners feel like you know the margins they make with our 754 00:40:28,080 --> 00:40:31,440 products are are you know superior to to others out there 755 00:40:31,440 --> 00:40:34,320 in the marketplace. And so it's it's kind of a win 756 00:40:34,320 --> 00:40:38,560 win for all of us. Yeah, I mean the software by 757 00:40:38,560 --> 00:40:41,240 itself isn't going to do anything without the hardware. 758 00:40:41,240 --> 00:40:44,000 So you need the hardware. What does it? 759 00:40:44,080 --> 00:40:47,520 I mean if is there a typical implementation, what does the, 760 00:40:47,960 --> 00:40:51,960 you know, what does an implementation of your product 761 00:40:51,960 --> 00:40:54,360 look like? Is it really that you're rolling 762 00:40:54,360 --> 00:40:56,800 out the software and the hardware just is alongside of 763 00:40:56,800 --> 00:41:00,920 that? How or do folks say already have 764 00:41:00,920 --> 00:41:03,840 like a software like an Improvata environment and then 765 00:41:03,840 --> 00:41:08,680 they're upgrading to a better hardware solution being RFI DS? 766 00:41:10,200 --> 00:41:12,040 Yeah. So it really depends on on who 767 00:41:12,040 --> 00:41:15,400 the software partner is that you are working with a partner like 768 00:41:15,400 --> 00:41:18,280 Impervata, they've already leveraged our software 769 00:41:18,280 --> 00:41:20,920 developers kit, all of our AP is within their software. 770 00:41:20,920 --> 00:41:24,040 So a lot of times our our hardware is plug and play in 771 00:41:24,040 --> 00:41:29,280 those situations with with other software solutions, you know it 772 00:41:29,280 --> 00:41:33,200 would depend on you know the size of the location, what the 773 00:41:33,200 --> 00:41:36,120 focus is for that vertical, the architecture that you're 774 00:41:36,120 --> 00:41:38,800 deploying the reader into. So there are some variables 775 00:41:38,800 --> 00:41:41,760 involved, but we are lucky enough to have really, really 776 00:41:41,760 --> 00:41:44,720 great partners that we work with that have a really great 777 00:41:44,720 --> 00:41:46,800 understanding of our product as well. 778 00:41:48,000 --> 00:41:50,760 Yeah, that's really cool. Now if somebody already has 779 00:41:52,200 --> 00:41:55,840 badging system that they use, can they take those existing 780 00:41:55,840 --> 00:41:59,720 badges and leverage your hardware or do they need to 781 00:41:59,720 --> 00:42:04,120 reinvest in new badges? No, see the the the batches that 782 00:42:04,120 --> 00:42:08,280 they have because RF ideas we we read you know at least 100 783 00:42:08,280 --> 00:42:10,880 different card types at this point and all of the the 784 00:42:10,880 --> 00:42:14,600 industry leading card types out there we can basically read all 785 00:42:15,040 --> 00:42:17,760 card types on the market that are low or high frequency. 786 00:42:17,880 --> 00:42:19,560 Yeah, that's that's the beauty of it. 787 00:42:19,560 --> 00:42:22,600 I mean I think as we kind of you know, I think Jeff started the 788 00:42:22,600 --> 00:42:26,400 podcast here today is that you know we're we're merging these 789 00:42:26,400 --> 00:42:30,080 two you know markets together, right, the physical and the 790 00:42:30,080 --> 00:42:32,840 logical together. And and the beauty of our 791 00:42:32,840 --> 00:42:37,360 technology is that organizations you know can leverage the 792 00:42:37,360 --> 00:42:40,520 existing badge or the existing mobile credential that they're 793 00:42:40,520 --> 00:42:44,040 already using for physical access, for logical access. 794 00:42:44,040 --> 00:42:47,600 Now that user might need to have a different software, right, 795 00:42:47,600 --> 00:42:51,280 whether that's single sign on or time and attendance for those 796 00:42:51,280 --> 00:42:54,600 logical access solutions. But but again, it's it's the 797 00:42:54,600 --> 00:42:57,440 beauty of our technology that our readers can already leverage 798 00:42:57,440 --> 00:43:00,760 the existing credentials and and implement it for for anything 799 00:43:00,760 --> 00:43:03,080 beyond the door. I love the idea of this because 800 00:43:03,080 --> 00:43:06,200 I think it's an area that is under explored and under 801 00:43:06,200 --> 00:43:10,000 leveraged in a lot of identity programs today is a lot of folks 802 00:43:10,000 --> 00:43:13,560 draw the line at Oh well we handle logical access well, why 803 00:43:13,560 --> 00:43:15,120 not parts of the physical as well. 804 00:43:15,280 --> 00:43:18,160 What if you could use some of those things that were already 805 00:43:18,160 --> 00:43:21,840 carrying around to do MFA? You know, hear a lot of times 806 00:43:21,840 --> 00:43:24,880 like OK, well you know, can't use a phone or can't use these 807 00:43:24,880 --> 00:43:27,880 other sort of form factors, but they have an ID badge. 808 00:43:28,280 --> 00:43:32,000 Guess what, Now you've got you know potential for MFA between 809 00:43:32,000 --> 00:43:35,160 that and you know other components of the of the EMFA 810 00:43:35,160 --> 00:43:37,840 factors. So I love the idea of this and I 811 00:43:37,840 --> 00:43:40,080 love especially with the fact that I don't have to rebadge all 812 00:43:40,080 --> 00:43:41,280 of my employees, which is awesome. 813 00:43:41,920 --> 00:43:45,280 So thank you for that. I want to end the conversation 814 00:43:45,280 --> 00:43:49,040 on a lighter note and you know, we've had kind of a neck deep 815 00:43:49,040 --> 00:43:51,360 conversation. I feel like getting really kind 816 00:43:51,360 --> 00:44:01,080 of deep into RF ideas again, no pun intended readers, NFCHMIA, 817 00:44:01,080 --> 00:44:04,400 whole bunch of other stuff. I want to talk sports and 818 00:44:04,440 --> 00:44:07,160 Olympics specifically. So we're going to wrap up 819 00:44:07,160 --> 00:44:11,960 today's show by talking about if you could compete in any Olympic 820 00:44:11,960 --> 00:44:15,480 sport, summer or winter, doesn't matter, just Olympics. 821 00:44:15,920 --> 00:44:19,480 Which one would it be and why? Sarah, I'm going to start with 822 00:44:19,480 --> 00:44:21,400 you because I know you're itching to answer this question. 823 00:44:22,200 --> 00:44:24,120 I am. Oh, OK. 824 00:44:24,400 --> 00:44:27,360 I'm a huge sports fan. I'm not typically a fan of 825 00:44:27,360 --> 00:44:29,440 winter. It's funny because I live near 826 00:44:29,440 --> 00:44:34,760 Chicago, but I think I would have to go with bobsledding. 827 00:44:34,920 --> 00:44:38,400 I don't know if it's from the Cool Runnings movie or say, the 828 00:44:38,400 --> 00:44:43,520 Jamaican bobsledding or I I think it's would just be the 829 00:44:43,520 --> 00:44:46,320 biggest adrenaline rush and I'm all for that. 830 00:44:46,320 --> 00:44:49,320 So I would have to go with bobsledding and I've never done 831 00:44:49,320 --> 00:44:51,960 anything like that before. OK, so that was my next question 832 00:44:51,960 --> 00:44:54,680 is like, OK, so this is not based on any experience other 833 00:44:54,680 --> 00:44:57,960 than just watching a movie and seeing like, oh, that looks cool 834 00:44:58,680 --> 00:45:02,400 now would it be like solo or would it be like a bobsled team? 835 00:45:02,760 --> 00:45:05,800 No, I feel like I would have to be with a team so that people 836 00:45:05,800 --> 00:45:08,360 could calm my nerves while it's all happening instead. 837 00:45:09,080 --> 00:45:11,240 Of just yelling your your entire face out the whole way down. 838 00:45:11,400 --> 00:45:12,920 Yeah, I'd probably be that person. 839 00:45:13,440 --> 00:45:15,560 Pretty much. Raul, how about yourself? 840 00:45:15,640 --> 00:45:18,840 If you could compete in any Olympic sport, which one would 841 00:45:18,840 --> 00:45:21,400 it be and why? Yeah, so I mean, maybe I'll 842 00:45:21,400 --> 00:45:24,440 start Jeff with a little interesting fact about me. 843 00:45:24,680 --> 00:45:29,080 I was, I was actually pretty close when I was 17 to 844 00:45:29,080 --> 00:45:33,520 participating in the Olympics. So I was invited to try out for 845 00:45:34,000 --> 00:45:37,000 the Team USA Junior Olympics for hockey. 846 00:45:37,640 --> 00:45:41,000 Unfortunately, I got cut on the last cut and so I wasn't able to 847 00:45:41,000 --> 00:45:43,320 participate. So I wasn't quite quite up to 848 00:45:43,320 --> 00:45:46,320 par to to make the team. But, but I think it's a no 849 00:45:46,320 --> 00:45:48,560 brainer for me. I mean, I've been playing hockey 850 00:45:48,560 --> 00:45:53,720 since at the age of 6. I I now still am very, very 851 00:45:53,800 --> 00:45:57,520 involved in youth hockey here. My daughter Alexandra plays 852 00:45:57,520 --> 00:46:00,760 hockey. And so for me, I I would have 853 00:46:00,760 --> 00:46:04,520 loved to have had a chance to participate at A at a Winter 854 00:46:04,520 --> 00:46:08,120 Olympic hockey game in my time. Another Miracle on Ice per 855 00:46:08,120 --> 00:46:09,320 chance. Exactly. 856 00:46:11,160 --> 00:46:13,440 Jim, if you could compete in the Olympics, which sport? 857 00:46:13,440 --> 00:46:16,560 I guess the obvious answer for me would be baseball, because 858 00:46:16,560 --> 00:46:20,440 Lake Rowell said that was my sport growing up, but I can tell 859 00:46:20,440 --> 00:46:24,600 you definitely not good enough to represent this country in 860 00:46:24,760 --> 00:46:27,520 baseball. But a sport that I've always 861 00:46:27,520 --> 00:46:30,960 thought that I would be good at was curling because I know how 862 00:46:30,960 --> 00:46:35,120 to use a broom. I think I can get on one knee 863 00:46:35,120 --> 00:46:38,400 and slide on the ice and I think it's kind of sport, like the 864 00:46:38,400 --> 00:46:43,320 practices would be fun, bring your own 6 pack and you would 865 00:46:43,320 --> 00:46:47,920 just practice for a few hours. Yeah, or just or just drink and 866 00:46:47,920 --> 00:46:52,200 have the six pack at. At least right be on like the 867 00:46:52,200 --> 00:46:54,520 backup to the backup. What about you Jeff? 868 00:46:54,520 --> 00:46:56,560 You. Know this is a tough one because 869 00:46:56,560 --> 00:46:59,160 it's a few different sports. I kind of ripped to my Rolodex 870 00:46:59,160 --> 00:47:01,160 in my head here. I don't know if Taekwondo is 871 00:47:01,160 --> 00:47:05,080 officially a sport yet or not, but that was something I did 872 00:47:05,080 --> 00:47:07,480 when I was younger. But I'm actually most excited 873 00:47:07,480 --> 00:47:10,680 for the flag football coming to the Olympics in the near future. 874 00:47:11,120 --> 00:47:15,960 I love the NFL, That's my jam. And I think having played that 875 00:47:16,320 --> 00:47:20,320 very long time ago, a much faster, slimmer, younger Jeff 876 00:47:20,640 --> 00:47:22,760 was pretty decent at at football. 877 00:47:22,760 --> 00:47:26,880 So I would be on the flag football team, sort of a 878 00:47:26,880 --> 00:47:31,840 Christian McCaffrey type, kind of a scat back slot receiver and 879 00:47:31,840 --> 00:47:33,200 also the kicker. Because. 880 00:47:33,240 --> 00:47:36,920 This is what I did. So that you might pick 881 00:47:37,040 --> 00:47:39,400 basketball, even though you're not really the hype for 882 00:47:39,400 --> 00:47:41,640 basketball that was your. No, but I was good at basketball 883 00:47:41,640 --> 00:47:44,840 too, when I was younger. So I was, I was, I was actually 884 00:47:44,840 --> 00:47:46,440 probably much better at basketball when I was at 885 00:47:46,440 --> 00:47:47,520 football. When I think about it, that was 886 00:47:47,520 --> 00:47:49,800 probably a better pick. But I just like football, so 887 00:47:50,280 --> 00:47:51,640 I'll stick with that final answer. 888 00:47:54,360 --> 00:47:55,720 This has been a great conversation. 889 00:47:55,760 --> 00:47:57,960 I really appreciate you guys taking the time to kind of 890 00:47:57,960 --> 00:48:00,120 demystify this a little bit. This is an area that we really 891 00:48:00,120 --> 00:48:03,280 haven't talked too much about in the past on this podcast, is 892 00:48:03,280 --> 00:48:05,640 that blending in the physical and the logical worlds. 893 00:48:06,000 --> 00:48:09,160 I think there should be more of this and I really hope people 894 00:48:09,160 --> 00:48:10,960 take a look at some of the solutions you guys have out 895 00:48:10,960 --> 00:48:12,360 there. You know, go out, visit the 896 00:48:12,360 --> 00:48:14,960 website rfideas.com. We'll have some links in our 897 00:48:14,960 --> 00:48:16,640 show notes for people to check out things. 898 00:48:16,640 --> 00:48:21,240 But I love this idea of taking things that we're that people 899 00:48:21,240 --> 00:48:23,120 are already familiar about. You do not have to train people 900 00:48:23,120 --> 00:48:24,840 how to use an ID badge they already know. 901 00:48:25,320 --> 00:48:28,600 So why not leverage a solution like that for multi factor 902 00:48:28,600 --> 00:48:30,840 authentication or or heck even go into password lists. 903 00:48:30,840 --> 00:48:33,440 Write things like that and chances are you property already 904 00:48:33,440 --> 00:48:35,000 have a mix of the technologies you might already need. 905 00:48:35,000 --> 00:48:38,080 But I would certainly encourage people go out, check out the 906 00:48:38,080 --> 00:48:41,520 website connect with Raul or Sarah on LinkedIn. 907 00:48:41,520 --> 00:48:43,280 We'll have their LinkedIn profiles and our show notes 908 00:48:43,720 --> 00:48:45,080 roll. I want to turn over to you for 909 00:48:45,080 --> 00:48:47,680 kind of final thoughts. For people who listen to this 910 00:48:47,680 --> 00:48:50,960 episode, what's the one thing that they should take away from 911 00:48:50,960 --> 00:48:54,320 this conversation? Yeah, I I think the one take 912 00:48:54,320 --> 00:48:58,440 away here is and and Jeff kind of already touched on it is if 913 00:48:58,440 --> 00:49:01,320 you're, if you're an organization that is looking to 914 00:49:01,320 --> 00:49:05,800 kind of leverage the physical access credentials for logical 915 00:49:05,800 --> 00:49:07,280 access. So you want to secure your 916 00:49:07,280 --> 00:49:10,120 endpoints, you want to secure your networks, you want to 917 00:49:10,120 --> 00:49:13,160 secure your data. You know we're the solution for 918 00:49:13,160 --> 00:49:16,560 that, right? If you have a need for better 919 00:49:16,560 --> 00:49:19,600 productivity, for better security, for regulatory 920 00:49:19,600 --> 00:49:21,880 compliance, we're the good fit for that. 921 00:49:22,000 --> 00:49:25,480 So you know, come visit us, you know, talk to Sarah and I and 922 00:49:25,520 --> 00:49:27,600 and we're happy to help provide a consultation. 923 00:49:27,600 --> 00:49:31,200 There, Yeah, so visit the website rfideas.com again, links 924 00:49:31,200 --> 00:49:32,720 that we in our shows for people to check out. 925 00:49:32,920 --> 00:49:36,480 We're on the web idacpodcast.com at Twitter IDAC podcast. 926 00:49:36,480 --> 00:49:39,840 If you got questions that you wish you that we had asked, send 927 00:49:39,840 --> 00:49:42,080 them our way and we'll if you don't reach out to Raul and 928 00:49:42,080 --> 00:49:44,920 Sarah directly, we're happy to do it and maybe follow up in a 929 00:49:44,920 --> 00:49:47,520 in the future episode. So with that, we'll go ahead and 930 00:49:47,520 --> 00:49:50,440 leave it there for this episode. Appreciate everyone for 931 00:49:50,440 --> 00:49:52,680 listening and we'll talk with everyone in the next one. 932 00:49:54,840 --> 00:49:57,760 You've been listening to Identity at the Center. 933 00:49:58,080 --> 00:50:02,160 We hope you've enjoyed the show. Make sure to like, rate and 934 00:50:02,160 --> 00:50:05,800 review and we'll be back soon. But in the meantime, hit the 935 00:50:05,800 --> 00:50:09,960 website at identity@thecenter.com and find 936 00:50:09,960 --> 00:50:17,360 us on Twitter at IDAC Podcast. See you next time on Identity at 937 00:50:17,360 --> 00:50:18,320 the Center.