Deploying Identity Solutions – ‘Field of Dreams’ Doesn’t Work

(Note: this topic is background for a panel that I’m participating on June 20th at the Cloud Identity Summit, in Chicago, Illinois. I wrote this in hopes of informing some of the context around the panel, though I’m sure it will be revisited in some respect during our session.)

Knock, Knock: Identity is here. Identity Who? Exactly.

Tuesday, June 20th, 4:20pm, Chicago Ballroom IX

The genesis for this panel took place during dinner following the Ping Identify conference in New York. Rob Davis from TIAA & I were talking about some of our challenges in deploying identity solutions, especially ones where customer, stakeholder, or developer engagement are required. In other words, pretty much everything except directory synchronization. Even governance solutions, like certification or privileged access management, that had the benefit of the ‘stick’ approach to service adoption; seemed to lag in engagement even when doing so wasn’t necessarily voluntary. You could lead the horse to water (you knew there would be a horse analogy, right?), but you couldn’t make them drink.

The simple reality was, this is no ‘Field of Dreams’. We built it, but they didn’t come to participate. Password recovery and management solutions are probably the easiest one to point to as an example of this failure. Nearly every enterprise worth their salt has deployed a password management and recovery product and yet password recovery is perpetually listed as the number one reason users call the help desk!

Rob & I both agreed that this would be an excellent subject for a talk at CIS. So I commenced finding the right people that could both explain their own challenges in this space and hopefully offer up solutions that might help others, including myself, succeed in the future. Between Rob & I, we had both financial services and healthcare/life sciences covered, but I wanted diversity of perspective. Through some networking, I think we put together a really great breadth of knowledge and experience across many industries. In addition to yours truly, we also have:

Bernard Diwakar – Security & IAM Architect at Intuit

Frank Villavicencio – CPO, Security Management Services at ADP

Steve Hutchinson – Principal Identity Architect at GE

And finally, no panel is successful without an awesome moderator, so naturally I asked Ian Glazer of Salesforce, Kantara, & IDESG if he’d do the honors in spite of his incredible schedule at the conference. Some promise of bourbon may have been part of the exchange, but in the end I think we’ve got a killer lineup of identity pros that will share their wit, wisdom, and experience on this important subject.

But wait! Part of what will make this a successful session is great questions and shared experiences from the audience. So bring your own stories and let’s make this a conversation!

Unfortunately, the scheduling gods put Rob’s talk against the panel, so we had to go to the bullpen. See you in Chicago! If you can’t make it, follow the action using #CloudIDSummit tag on Twitter.

RSA Thoughts, Part 1

(photo credit: Brian Campbell)

I think teaching eviscerated my time for blogging. Going to try and put more energy in it this year. Naturally, I’m going big on this revival with a two part post about my experience at the RSA Conference, to the best of my knowledge the largest security conference on the planet (especially if you count their global adjuncts).

This was my first RSA, both as an attendee and speaker. I thought Oracle OpenWorld was huge. Good gravy. I think estimates had it at about 45,000 attendees. In spite of the size, kudos to RSA and their management vendor who run an incredibly tight conference for that scale.

On one hand it’s awesome that we have so many people, vendors, and speakers focused in the information security space. On the other, its a touch overwhelming and nearly impossible to get to all the content you want. Overall I think that’s a good problem to have, because this is a tough problem to solve. It was refreshing that they featured an identity track (a first, I believe) at the conference.

The good news is they make much of the content available online, including some videos of the sessions. Mine has audio but no video, which isn’t a loss, heh. It isn’t very technical, but has a solid foundation on some of the key elements and challenges that go into a Privileged Access Management program. I’ve delivered this talk at the Cloud Identity Summit, BSides Charlotte, and IT Hot Topics, but this was definitely the most mature version of the talk because of the time that has passed and the lessons learned.

My talk was on Thursday, which originally I loved because I thought it would give me more time to prepare. I was mistaken. This talk is by far the most mature of the ones I’ve developed so very little additional time was needed to update it for the conference. I don’t know necessarily that I would have wanted to go on Tuesday, as there were some serious heavyweights in the industry to compete against. My biggest concern was making sure I kept my energy balanced throughout the sessions, networking, and vendor parties so that I could be sharp as possible when it came time to take the stage. It required missing a few tracks, but I eventually achieved that.

I discovered in the hours leading up to my talk that seat reservations had reached a level that they created an overflow room in case demand exceeded capacity. That was extremely flattering, but I did my best not to make it bigger than it was. The talk wasn’t changing, or the stage. I was thrilled that so many people were interested in this area, because I think sometimes it gets lost in between the traditional domains of identity & access management and information security. Clearly others felt the same way given the number that turned up.

Overall, I couldn’t be more pleased with how the talk went. Even though the hall was a little dark so they could broadcast it to the overflow room, I could feel the engagement and energy from the audience. It showed when I finished, as the questions that emerged were insightful and thought provoking. Once we wrapped up, I went outside and answered even more questions, happily, for another 40 minutes. Such great conversation with such intelligent and thoughtful people! I retired to the speaker’s lounge to decompress a little and make some mental notes from some of the questions that were asked. (photo credit: Scott Bollinger)

I know I’m kind of working this post backwards, but the next chapter will have some of my takeaways from the conference, both in hallway conversations and some of the tracks and keynotes I attended.

I’m writing this post at the airport with a feeling of extreme gratitude for the opportunity that was presented to me, and all of the support that I’ve received from countless people to help make this conference a personal and professional success.

PS. Thanks to Ian Glazer for the support.

How Do I Get Into InfoSec?

This is a question I hear often, in a variety of forms that I won’t belabor here. It’s always difficult to answer in a short conversation. To be honest, the point of this post is really self-serving; mainly, to give folks I speak with an easy place to look that I can remember when having this conversation.

I could make an effort to answer this question, but frankly I think anything I could offer would be redundant and not as expertly versed as some people I respect that have already attempted to do so. Some conversations I had at RSA is what encouraged me to finally get something written.

Two people have done a really nice job with this subject. The first, in a somewhat older post from 2014, is Daniel Miessler. That isn’t meant to short his contributions in this space, far from it. This post just provides a really nice overview of getting into this field. His blog is also excellent and quite prolific.

Next is Lesley Carhart, a Digital Forensics & Incident Response (DFIR) expert, a self-described “Full Spectrum Cyber-Warrior Princess”, and an all-around thoughtful person. She has a terrific blog (and posts way more frequently than I do, though I hope to change that).

Of particular importance is the fact that she posts frequently to an advice section of her blog that often includes career guidance. To whit, here’s a link to several terrific posts on building an infosec career. I would encourage someone to start with the Chapters 1-3 Megamix.

I will post some follow-up thoughts on this subject, particularly a more specific consideration for folks wanting to learn more about identity & access management, but I hope this helps some people. Oh, and if you’re not following these folks on twitter, you’re missing out.

Dropbox, 2FA, FIDO, and You

fbDusting the blog off for a PSA. Hopefully most of you are aware of the news surrounding Dropbox’s 2012 hack and some of the new details surrounding it.

Not going to say too much beyond this but simply request that my friends (or anyone who reads this) do the following:

  1. If you’re using dropbox, change your password, even if you’ve done it since 2012. Make the new password unique (avoid reuse especially for services like this), and strong.
  2. Please, please, please setup two factor authentication (2FA). This article walks you step by step thru the process. Do NOT opt for text messages as the form of verification. Easiest is using a mobile app. If you want a recommendation, go with Authy. Its a terrific mobile app and syncs across devices. It has the added benefit of working with a number of common services like Gmail, facebook, amazon, microsoft live, wordpress, evernote, tumblr, slack, and I’m sure a list of others.
  3. Consider, in addition to #2, buying a FIDO U2F compliant security token, like Yubikey to secure the account. It’s not as convenient for mobile, but is more secure in my opinion. Doing 1 & 2 gets you solid. #3 is even better.

Finally, seriously consider setting up 2FA for all your accounts that have it. If you aren’t sure if your service offers it, check  here. If they don’t, tell them to get it or consider a competitor. If they only have SMS/text for 2FA, consider a competitor.

Vague Signals & Behavioral Analytics

Gartner Analyst Anton Chuvakin shreds the myth that excelling in detection of threats means you should be at the same level or higher of preventing them. For some (including myself), this should be obvious. Preventing, detecting, and responding to security threats should be treated and evaluated as independent disciplines. Excellence in one doesn’t guarantee a level of maturity in either of the others. Unfortunately, given that some security vendors insist on perpetuating this myth, Chuvakin by necessity eviscerates this false premise with several good arguments. I’m only going to focus on one because of its impact in identity or user behavior analytics.

One of the points that Chuvakin makes regarding prevention is that signals in this area are often vague, making prevention with this level of data impossible, unless you want angry users storming your gates for being denied access. This is particularly true when evaluating the activity or behavior of a user. While some machines are capable of measuring the risk score of a given activity, do we really want a block on a connection when it barely crosses a threshold that may or may not be valid? The smarter approach would be escalate the user’s request to another level of authentication. Even if the challenge succeeds, it might make sense to flag the activity for human review.

If I login from a London based IP address 6 hours after my last known activity (from the US), it might be prudent to have the system in question challenge me for another factor of authentication to ensure the credentials have not been compromised. If no response is given or the session is terminated, flagging the account for review would be prudent. Even better, if the analytics engine has access to my travel & badging data (both viable points of integration), the signal to noise ratio on the event could be reduced (or escalated) quickly. Human intervention may still be useful here but automation becomes at least feasible based on our ability to raise or lower the risk score of the event based on the user’s response.

This level of sophistication for behavioral analytics as a  prevention protocol is fairly mature, but still pretty nascent for most enterprises. I see this as one of the early challenges in developing a behavioral analytics program. The use case I described is pretty straightforward, but establishing baselines for user behavior, especially in large enterprises, is far more daunting. Integrating that knowledge with your access management tools & policies is another level of challenge. That doesn’t mean we shouldn’t attempt to do so, however.

As a side note, this is an area where the concept of Shared Signals intrigues me. As our identity fabric becomes more and more decentralized/federated, adding external events to our behavioral analytics engine only seems to make sense. Further, we still hold control over how to interpret those events vs. relying on a machine interpretation of an external event that raises a higher level of vagueness on what took place.

It stands to reason that detection activities would mature at a faster rate than prevention. Arguably response activities can mature even faster, given appropriate resources. All three are worth investing in to protect company assets. But in the end reality has to intervene in our expectations with respect to achievements in one bearing any relationship to maturity in the other two.

 

MacID and Apple Watch Update

I know, its been awhile. Teaching in addition to my day job seems to have robbed me of blogging bandwidth.

First, I want to brag on a pretty nifty use case for the Apple Watch (and iPhone, obviously) MacID. This is an extension of TouchID for authenticating with OS X based systems.

There have been some other tools in this space, but by far this is the most elegant. You can unlock your OS X based system (Yosemite and higher, I believe) either from your iPhone or Apple Watch. Additionally, privilege elevation is handled nicely by the app. That alone is a nice addition vs. normal unlock apps.

My only real complaint about the app is consistent with other unlock apps: bluetooth flakiness. Sometimes the app just decides it isn’t connected to the Mac and requires that I reopen the app on my iphone to get them on speaking terms again. Otherwise, its a great product.

Second, an update on my Apple Watch experience. Overall, I still love it. Its a great extension of my iPhone and works very nicely as a fitness wearable. I have been using Apple Pay on the watch pretty regularly and that has been a really enjoyable experience.

One notable application that I want to call out is MyBivy (short for bivouac, you’ll get why in a moment). This clever kid at HackDC unveiled a wearable app that could potentially help people with PTSD and/or night terrors using haptic feedback in response to certain conditions that the watch could track, like elevated heart rate and sudden movements. To be clear, right now its only available on Pebble, but they are looking to port it to Apple Watch as well. I just think its a brilliant concept and hope it has the success that is so needed for people suffering from PTSD and night terrors. They have a kickstarter project if you’re interested in contributing.

The Watch OS2 release was mostly a success, with one glaring issue. After upgrading, my calendar events wouldn’t show up on the watch. I opened a ticket with Apple and it was resolved within a few days. I suspect it had something to do with the fact that my iPhone is managed by MobileIron, but I don’t know that for certain. I’ve communicated with a few people on twitter about it and some were resolved and some are still outstanding. The calendar is one of my favorite features because it keeps my phone in my pocket and keeps me on track during busier days.

Finally, a minor note on battery life. Most days, the watch performs like a champ, with me dropping it in the charger at 50-60% battery remaining. However, and this only started post OS2, I have had a fair number of days in the past month where the battery life just heads south quickly. Today I was at 1% before 4pm. My unconfirmed suspicion is there is likely a rogue process chewing it up, but I don’t use a ton of apps on the device, so its hard to pin down. Needless to say, I’m buying a charger to keep in my bag for the odd time that this happens. To be clear, in general the watch performs well on battery life. I think I may start tracking this, though, just to see if I can identify a pattern. Perhaps I should build a battery tracking app, hah.

I’ve been jotting a few thoughts down regarding the identity implications of the EU Safe Harbor decision, but not sure if I feel qualified to comment overall. We’ll see if research can help me out on that. Cheers.

Nymi Band – Loads of Potential

When this video first launched, the identity geek in me had a nerdgasm. The idea of continuous, contextual, biometric authentication in a low profile wearable has undeniable appeal. in a world in which users routinely have to navigate countless sets of credentials as part of their daily lives, could this really be ‘one band to rule them all’? Ok, after the eyeroll for the pun, the potential is extreme for this device to be a game changer.

Realizing the potential is always the struggle, and Nymi has experienced that like most startups. They’ve pivoted from consumer to enterprise use cases recently, and I think that will serve them well.

Anyway, the emphasis of this post is on my experience with the developer version of the band to date.  Thus far, it has been positive, but not without some bumps. Being that the band still isn’t RTM for public consumption, that’s almost expected.

Unboxing

I didn’t take photos or do a silly youtube of this, but Nymi clearly took notes from Apple on the unboxing experience and meticulous design. You can see the package near the end of the video above. The package was elegant and very well presented. I think that experience is a little underrated when we’re talking new technology. They did a very nice job here, even for a dev kit experience.

The Windows Experience

I hate to start with the bad, but this is how it was experienced when I first received the band late last year. Part of the dev kit comes with a usb bluetooth adapter. This is understandable, because not all devices support Bluetooth 4/BLE, windows especially. So now the band and related software is at the mercy of the Windows API’s.

The first test was on my corp laptop, a Lenovo T400 Thinkpad running Windows 7. The software installation required a separate install for the bluetooth hardware, but that’s expected. The companion software (required to enroll/identify you, bio-metrically) installed successfully and I was able to enroll my band pretty easily. The key here is to just ‘be still’ and let it read your ECG for about 90 seconds. I did get a few false rejections initially, but the software easily allows you to ‘condition’ your profile by doing more reads. Eventually, the FRR (false rejection rate) diminished considerably. This did raise a question: will consumers be this patient?

The 2nd piece is the unlock software. In effect, this is what you install to get the OS to recognize the device as a means of authentication. The windows implementation (compared to OS X, more on that in a moment) is a little clumsier, because the ‘login’ is presented as a secondary user from your primary login. I don’t really blame Nymi for this, because I believe some of this is a limitation of Windows Authentication API unless you implement this as part of the GINA (Graphical Identification and Authentication library). Especially for enterprise use cases, this might raise a CIO’s blood pressure (pardon the pun). If your PC stays persistently on, the unlock works pretty consistently (64-bit windows only, for now).

The challenge comes in for windows systems coming out of sleep. Sleep is always Windows nemesis, at least for my experience. And when you’re relying on a bluetooth service and adapter to authenticate you to come out of sleep mode well, it doesn’t always behave. The experience here thus far has been pretty inconsistent. My devices sleep unless they are in use, so this is a hurdle. In my conversations with Nymi support staff, they are aware of the issue and are actively working to tune that process. With Windows being the dominant desktop platform, I have little doubt they will smooth those issues out.

Still, waking up and unlocking my windows PC and Macbook without typing in a password is a pretty nice experience. Here’s my process:

  1. Fasten NymiBand
  2. Open iPhone 6 with TouchId
  3. Open Nymi Companion on iPhone
  4. Activate band (already enrolled) either via HeartID or TouchId (more on this in a moment)
  5. Login to MacBook by raising lid and pressing enter (<10 seconds)
  6. Login to Windows PC by bringing out of sleep (keyboard) and select Nymi user profile (30-60 secs)

Pretty cool, huh?

iOS Companion

Previously, I had to use a PC to activate my band. That won’t be the average user’s experience. So adding the iOS companion was a huge leap forward. The iOS companion works flawlessly and really was the first user experience that, in my opinion, showed Nymi starting to realize their vision for the ideal user experience. Registration & enrollment were flawless. I could either register my heart rhythm for the enrollment or allow the band to be a proxy for TouchId, yet another well executed biometric implementation. I’ve played with both, but currently use TouchId for activation in the morning.

OS X Experience

This started out rocky due to some installation issues, but eventually both the companion (pre iOS) and the unlock installed well. Now the experience goes up a level. Not only does unlock work seamlessly coming out of sleep, the re-lock feature (if enabled) can detect when your band is out of proximity of your MacBook and automatically lock your device. I found this to be a really nice feature at work. This was another case where the developers really began to show up how the vision could be realized.

Wearable Aesthetics

In this area, I struggle a bit. When I first received the band, I already wore a Fitbit Surge on my non-dominant wrist. Two bands on one wrist is a little too goth for my liking, so I went with my dominant wrist. That was ok, but definitely took some getting used to with respect to keyboards. Now I own an Apple Watch and the dynamic is the same.  I have to wonder, however, if this aspect of wearables will be a barrier to adoption for some. I honestly don’t know the answer to this.

Summary & Leftover Questions

Overall, I’d call the beta experience a success, especially once the iOS companion was released. its easy to see some of the promise in this technology helping reduce our reliance on something as insecure and unreliable as passwords.

Extending this beyond the desktop, and realizing some of the novel use cases in the video are where questions emerge. Could I pair my NymiBand with my 2015 Prius to unlock it? I have a feeling this will be easy given the advances Toyota has already implemented in keyless entry. My 2007 Tundra…not so much but I’m being unfair on that one.

The key challenge I see for the band will be enrollment on the target system, especially for those looking for configuration vs. security experiences. For me, given that I own the PC, MacBook, iPhone, and the Prius, enrollment is easy. What about public systems like the hotel, payment systems, retail chains, airport security, etc? Also, where does privacy play? The upside of the NymiBand is that you could theoretically ‘disappear’ by disconnecting the band. This is unlike Tom Cruise’s character when he walks into the next generation Gap with someone else’s eyes in Minority Report. These are open questions and not meant to infer an indictment of the technology or their approach. There is a ton of potential here, and I look forward to seeing how Nymi’s delivery and, perhaps more importantly, their partnerships help realize the vision of this platform as a next generation in digital identity.

30+ Days with the Apple Watch

Originally, I had planned a review (thus far) of an emerging authentication technology, and that is still on the horizon. But, it hasn’t gone gold yet so I feel like I have time. Instead, I thought I would post my mostly unedited thoughts on the Apple Watch.

At launch, I hadn’t planned to buy one. As intrigued as I was by the platform, I had intended to take a ‘wait and see’ approach. I used the same approach with the iPhone (my first wasn’t until the 3GS came out), and that worked well for me.

Another reason I was reluctant was that I already had a top notch fitness wearable in the Fitbit Charge HR and was pretty happy with it.

So why did I stray? The short answer is simply that I was reading some very exciting reviews and, more importantly, I came into a little unexpected money that would allow me to acquire the Sport version mostly guilt free.

I’ve been using the watch now for a little over a month. It arrived shortly after I left for San Diego to speak and attend a conference. I would have loved to have had the watch with me, but in many respects I was thankful that I didn’t have the distraction. That proved to be wise, as the first day with it was a bit of a loss in productivity as I explored this new platform.

Design

Out of the box you can see this is highly consistent with Apple’s unwavering design standards. This is a highly elegant watch. I was pleased that the weight wasn’t too cumbersome (have the 42mm sport model). Attaching the band takes a little getting used to, but I find it superior to my Fitbit in its security on my wrist.

Unpacking and Startup

Again, Apple shines here as people have come to expect a certain experience from even just opening the box and unpacking your new device. This one was no different for me. I immediately pluged the charger and set the watch to finish charging fully. A pleasant surprise is that this battery does not take long to charge at all. One to two hours is all I’ve needed on most days.

The startup is fairly easy, with some caveats. This is a new platform, much like unboxing your very first VCR or DVD player. Reading the manual helps and Apple does a very nice job of sending you an email in advance to let you watch a series of videos to pair, setup, configure, and use your new watch. You can even schedule an appointment to have someone walk you through some of this. I chose not to, as I wanted to explore this on my own time. The videos are a huge help to get used to to the interface and to get up to speed quickly. If someone flies into this blindly, I could see them getting frustrated. This isn’t just like operating an iPhone, though there are certainly parallels. Overall I got up to speed quickly and felt comfortable using it.

One complaint I have it that Apple loads EVERY app from your phone that has a watch companion app. I happen to have a ton of apps on my phone and this proved cumbersome. It isn’t terribly difficult to uninstall a phone app, it just takes time and I personally would have liked to be selective in what apps were installed on my watch.

(I just got notified by my watch that I need to stand for a few minutes, a feature that I truly enjoy)

Notifications

In my opinion, this is one of the early potential killer apps. Any application can be configured for notifications on your watch. This is an early example of where you have to figure out what is useful to you. Text messages, twitter notifications, and fitness feedback are my early key notifications, but I see potential for a lot more. The watch is simply less obtrusive than powering up your phone and allows me to keep my focus on my interactions with other people.

I can see this area being one of the early development frontiers. How do we get a user the key information they need in a context that is useful? Application and use of medication is one area where I could see this being highly useful. (disclosure: I work for a pharmaceutical company where compliance (or lack of) is a top reason where therapies can fail).

Phone Calls

This area is novel. I was a huge Get Smart fan growing up, so the ability to take a call on my watch is pretty cool to me. That said, I love knowing quickly on my watch who is calling and how I want to handle the caller. Like notifications, this makes for a less disruptive experience than reaching into my pocket to handle my phone. I have taken a few calls on the watch, and the audio is pretty solid. In private settings I could see me using it for brief chats (your car is ready, for example), but not as an extended conversation mode. Overall, I’d say this feature is delivered pretty well.

Apps

This is always the big question: what are the killer apps? Here’s a few I’ve found handy thus far:

CPI Security – Simply put, I can arm and disarm my home alarm system from the watch. It uses the phone interface, but I’ve found it pretty handy. CPI did a nice job of not trying to do too much here. This is another area where I think notifications could be handy.

Authy & 1Password – I lump these together because the use case is the same. The ability to easily pull up my code for two factor authentication on sites is highly useful to me. Because this is my field of focus, naturally I’m looking forward to seeing how the watch can be securely leveraged as a factor of authentication. I see a lot of potential in this area.

Map My Fitness – I’m conflicted on this app. I like the interface with my phone, but I’m also enjoyed the basic activity app as well. This is still a comparison in progress. The biggest different to date is I get the map data from MMF, and I do not with the activity app. How important is that? We’ll see. I do like being able to manage this from my watch instead of my phone when I’m at the gym, hiking, or riding my horse. This is another area I see developing rapidly from both Apple and other fitness manufacturers.

Calendar – during the work week, this is a really nice app. The form factor is so much more convenient over the phone or iPad for quick glances.

Note that I haven’t used the word ‘killer’ with any of these apps. I don’t view them that way, at least not yet. Tim Cook was pretty clear when the platform launched that the applications would drive the success of this platform, and I’m pretty much in that corner. I also think the ‘killer app’ metaphor gets overused. The app that delivers the biggest value will vary by user, in my opinion.

Battery

Of course, one of the early knocks on the Apple Watch, even pre-launch, was the battery life. Maybe it was due to the low expectations, but I haven’t had an issue at all. I get 1.5-2 days of life and haven’t had that be really an inconvenience. Generally, I just slap it on the charger when I go to bed and have yet to run out of juice. I did test a few days going to a 2nd day and didn’t have an issue.

Verdict

Overall, I love the new platform and am very excited for its potential as developers sink their teeth into the new SDK. That said, this device isn’t a ‘must have’ for everyone. By that, I mean its more of a luxury item that can enhance your life depending on how you choose to use it. That is partly why I don’t think this category will explode like smartphones have just yet. It will, eventually, and there’s little doubt in my mind that Apple is a pioneer in this category and will continue to do so in the future.

Welcome to Identity Bytes!

This is the next generation of my attempt at blogging more often (like, more than once a year) about digital identity and events in information security. This has been a pretty eventful year in this space so there is a lot to talk about! My first real post (coming soon, I promise) will be about my experience with next generation authentication technologies.

I even have a 2nd post in the hopper surrounding my experience at the, in my humble opinion, best digital identity conference of the year, the Cloud Identity Summit. That was my first segue into speaking at a national (global?) conference and to say the experience was memorable would be an understatement.

Thanks for reading!

Lance