Podcast
Root Causes 305: The Fifth Pillar of Certificate Lifecycle Management
Hosted by
Jason Soroko
Fellow
Original broadcast date
May 24, 2023
In our episode 143 we introduced the Four Pillars of Certificate Lifecycle Management. Now, two years later, we introduce a fifth pillar of CLM.
Podcast transcript
Lightly edited for flow and brevity.
TCTim CallanWe’re going to start with a little trip back in time. In our Episode 143, we introduced a concept, which at the time we called “The Four Pillars of Certificate Automation.” And those were, just as a reminder for everybody: Discovery – finding certificates and bringing them into the system and knowing what they are; deployment or provisioning – getting the certificate; ordering it and deploying it out in the world; revoke and replace – sometimes called Lifecycle Management where you do the other things that you have to do with your certificates to keep them current and refreshed and secure; and then renewal – where you take your certificates that are expiring and getting them renewed. And those four pillars, we’ve had a little picture in our webinars which you may have joined us on where there are four pillars, and then on the top there is a cap, a penumbra. It kind of looks like a classical building, like a classical temple or something. And that cap on the top was visibility because those pillars supported visibility but visibility also enabled the pillars.
And so, that was a concept you and I built. We ran a bunch of webinars about it. We’ve talked about it with a lot of people. We’ve had these graphics that have floated around. They’re in assets. We’ve seen other people take this idea, even though I’m pretty sure you and I were the first people to advance it, and we’ve seen it show up in other discussions of the CLM space by other people who aren’t Sectigo. And that’s really sort of moved into the dialog in a pretty significant way. But it has been more than two years, right? And the world changes.
And so, that was a concept you and I built. We ran a bunch of webinars about it. We’ve talked about it with a lot of people. We’ve had these graphics that have floated around. They’re in assets. We’ve seen other people take this idea, even though I’m pretty sure you and I were the first people to advance it, and we’ve seen it show up in other discussions of the CLM space by other people who aren’t Sectigo. And that’s really sort of moved into the dialog in a pretty significant way. But it has been more than two years, right? And the world changes.
TCTim CallanYeah.
TCTim CallanOh yeah.
TCTim CallanRight.
And you know what, I think we’re getting another pillar - -
TCTim CallanAnother pillar!
TCTim CallanI agree. IT workflow automation is right.
TCTim CallanIt could be those platforms. It could be, your PagerDuty. It could be your SIM.
TCTim CallanIt could be your APM solution. It could be your ITSM solution.
TCTim CallanM-O-U-S-E.
And that’s why we used this really generic term of IT workflow automation, and that is because there’s so many forms of that that are out there. I think as the CLM industry is maturing and we are realizing we don’t exist in a vacuum; we don’t exist on an island; we exist in people’s real, real IT systems. And in fact, we are a fundamental part of it. We need to make sure that we are plugged into those kinds of central messaging units that are automating these kinds of steps, Tim, and I think it deserves its own pillar.
TCTim CallanI agree with you. And let me add, I think that it is a two-way flow. Which is to say you need your CLM to drive those other systems, right? You need to, for instance, you know, you and I did an episode not that long ago about how certificates are chock full of events, and those events need to get plugged into your SIEM, right? But then, you want to drive in the other direction as well. So, for instance, I want to be able to order cert and choose to get a cert in your, let’s say, ServiceNow, but then that actually needs to trigger the CLM and have the CLM do that work. Or I want to discover a cert. I might discover a cert using, let’s say, my APM product and then I want those discovered certs to get hooked into the CLM where they can then be part of what’s under management. And so both platforms strengthen the work that the other one does, and both platforms can take information from the other and can push information to the other that drives the behavior of the visibility or the reporting that you want to see in that other one. Do you agree?
But again, this goes right back to what I’m saying which is, this is not the CLM vendor industry inventing that. That really depends on what works inside of your IT system; what works in your IT workflow; what is automatable; and, what needs to have a human check-and-balance? Which is in itself a form of workflow.
TCTim CallanThat too can be part – when you look at the holistic workflow that you need there, you’re right, some of these things can happen on their own. You can have Program 1 triggers Program 2 and the program does what it’s supposed to do, or your workflow might be Program 1 triggers Program 2, and what’s it’s supposed to do is put this in front of the person and say, do you want me to proceed? Yes/no. Right? And that’s fine also. Likewise, the visibility thing. Tou got reporting in your CLM, you got reporting in your ITSM, you got your reporting in you APM, you got reporting in your SIEM. You may want to get different reports in different places for different reasons. And that’s okay. You might like the report better here, it’s more comprehensive over there, etc. or it’s focused in on what I want over here, it’s got all those particular items that I’m looking for, and there’s no reason why all of those dashboard/reporting/search/alerting engines can’t be adjacent and simultaneously operational and they can just populate each other with correct information that the other one uses that they have. And there’s no reason why we can’t have that as well, and that would just make every one of them stronger.
TCTim CallanPerfect example.
TCTim CallanAnd again, this could come from multiple directions. Like, there might be a reason why I prefer to have my Slack notifications coming out of my ITSM platform rather than my CLM. And that’s okay. Or vice versa. Maybe I prefer to have this category of notifications come out of my CLM, and that too is okay, right? But these are other things that administrators will be thinking about, and it would be nice if they had some control and some choice, and they could really look and say, well which of these is best and why, and make sure that they’re using it appropriately.
TCTim CallanAbsolutely. So we may work on the wording. This is kind of a new idea. Just like if you go all the way back to our 143, you’ll see that some of our terminology has changed, even though the fundamental concept didn’t change. Likewise, we may somewhere along the line go back to and reference this episode, roughly in the ballpark of 300 and say, well, this is what we used back then. But either way, I think this idea, IT workflow integration or IT workflow automation has definitely become a very important part of how we need to think about the CLM space.