Podcast
Root Causes 520: How Prepared Are IT Teams for 47-day Certificates?


Hosted by
Tim Callan
Chief Compliance Officer
Jason Soroko
Fellow
Original broadcast date
August 20, 2025
Sectigo has released the results of its 2025 State of Crypto Agility report which surveyed IT professionals in charge of certificates to measure their readiness and preparation for 47-day SSL/TLS maximum certificate term. We go over the results.
Podcast Transcript
You and I talked about chunking this up, Jason, was it's a big survey. There's a lot to discuss. So what we're going to do in this episode is we are really going to focus on the results around the march to 47 days.
And that will be what we cover here. And then we'll ask our listeners to join us again in a future episode where we'll discuss the results for PQC. Does that sound good?
Question one. And I think what I want to do here, Jason, is read the question in its entirety, verbatim, and then give the results with the percentages just straight through. And then let's talk about it and the significance of it, and then let's move on to the next question. Does that work?
Next. We have a partial inventory, but some certificates may be unknown. That is 33%. Almost exactly a third.
Next. We are not sure how many certificates we have or where they're used. That is 13%.
And then lastly, we rely on manual tracking or informal methods - 26%.
So I got a few but react, Jason, react.
And that strikes me as probably the norm for most organizations, which is, look, we're partially implemented. We're not complete cavemen. We are doing what we can, but it's a hard and tractable problem, and no, it is certainly not universally solved.
Very confident - 17%.
Moderately confident - 37%.
Slightly confident - 33%.
And not at all confident - 0%.
So what do you think of that?
And I think maybe we got a little bit of that same I don't know what I don't know going on here as well. But even if we took these at face value, it would show that there's a lot of recognition out there that this is a potential problem area, and I'm encouraged by that. I'm glad there's a lot of that recognition. I'm less worried about a global enterprise IT community that knows that this is a problem that needs solving than about a global enterprise IT community that thinks this is a problem that's solved.
So these are people in the certificate world. This isn't a survey of just random IT professionals or random enterprise employees. So let's understand that. I want to give you that color, and with that, I'm going to invite both you and the listeners to take a second and guess at what you think. It's a simple yes/no question. No other options. Yes or no. Take a guess at what percentage you think said that yes, they were aware of the ballot to reduce, or the guidelines to reduce maximum validity down to 47 days.
That is extremely high. Again, I'm encouraged. I think part of what we've been worried about is the IT community being caught flat- footed on this, which is part of why we've been so vocal about this. And I've been traveling around to cities throughout North America. You have been to. Talking to enterprise, the people in charge of certificates of enterprises, just telling them hey, look, this is happening, and you have to have a plan. I'm very encouraged to see this number be this high, and it's good because it means it at least increases the likelihood that appropriate action is taken on time.
Very prepared. We already have automated systems in place to manage monthly renewals - 19%.
Somewhat prepared. We have plans or partial automation in progress to manage monthly renewals - 40%.
Not very prepared. We will rely mostly on manual processes to manage monthly renewals - 40%.
Not prepared. We have no current plan or process to manage monthly renewals - 1%.
So what do you think of that?
Let me. Let me. I'm going to double click and profile that answer. That's an influential, probably a higher ranked Linux administrator who's saying I'm going to keep doing my job and I'm not going to automate my job away. And we've tried to speak to that profile to say it's wrong. Don't do that. Don't do that.
I mean, I was really pleased by that. I think the 13% that say that they're good to go, hey, that's great. But that low number probably shows that most people just aren't there yet. And let's not forget the 30-day part of the question is on purpose, because a 47-day certificate probably should be renewed every 30 days with 17 days grace. So that's why the question was asked.
Because I will bet you there are gaps that have not been considered and that you might not be aware of, that are not good to go, and this is your opportunity to clear out those white spaces so that when that date arrives, you're actually truly good to go. But it's encouraging to see that more than half, 60%, nearly two thirds, 59%, seem to have put some effort into preparing for a fast cadence of regular renewal in an automated fashion.
And then I think overall number three, it is, there is, I think, because of the way things were screened, an overall bias towards a very high percentage of awareness and a very high awareness, therefore to say, now that you've mentioned it, I'm going to make a plan.
And so, there it is.
Question five. “How concerned are you about the impact of 47 day certificate lifespans on your organization?”
Extremely concerned - 21%.
Very concerned - 31%.
Moderately concerned - 26%.
Slightly concerned - 17%.
And not at all concerned - 4%.
So I literally remember a recent conversation I had with someone from a global 2000 company, and he said, you know what? We're not gonna go to a six-month cadence on these things. We're gonna go straight to monthly, because everything that's automated is just gonna go straight to monthly. Because why not? And I say, good on you.
I mean, this concern, I think, connects a lot with those parts of the organization where either that automation isn't in place, the manual management is still going on, or where they don't feel that it's proven reliable, universally applied.
And so that when that day does roll around, it actually isn't a problem. Now, the other thing I'll add on this, Jason, is the step down process, as it was originally designed by Apple, was designed to some degree to mitigate that problem, because you're going to go down to six months, and then you're going to go down to three months. So once we're on a three month cadence, a lot of these things are going to be blowing up anyway, and we'll be finding them and bringing them, corralling them, so that by the time we get to one month certs, hopefully, ideally, the majority of them have been discovered and dealt with.
All right. Next question, question six, which automation methods or platforms does your organization currently use for certificate management? This is a pick all. So pick many. Pick as many as you want. So we'll just see the relative popularity of these things.
So certificate lifecycle management - CLM platform - 67%.
ACME - automated certificate management environment - 58%.
Homegrown or custom built automation - 57%. That's a high number.
IT Service Management, IDSM platform - 45%. Which is actually a surprisingly high number to me.
SCEP - simple certificate enrollment protocol - 41%.
And EST - enrollment over secure transport - 33%.
Then there was another category. Nobody gave us anything in the other category, and then none of these 1%.
So 99% are using at least one of these solutions. And those are the percentage of the total who picked those things. So thoughts and observations?
Moving on. Question seven, what percentage of your organization's SSL/ TLS certificates are automated for each of the following tasks? Now this is a mean. So let me explain how this works. Each individual respondent gives a number between 0% and 100% of what percentage of their certificates are automated, and then we take those numbers and we do a mean average of them. So doesn't exactly necessarily affect the mean average of the total certificates, because someone with a lot of certificates gets calculated the same as someone's fewer certificate, but again, best you can do in an instrument like this. So with that, let's look at what are these mean averages. Okay, so again, what percentage of your organization's SSL/TLS certificates are automated for each of the following tasks.
The first one, renewing certificates - 52.5%. I'll drop off the 52%.
Deploying certificates - 33%.
Performing domain control validation. We might want to return to why that matters here - 32%.
Provisioning certificates for new applications or services - 31%.
And revoking and otherwise managing certificates - 27%.
So this answer, right here, the way that you were framing the question, I was starting to not like it until I heard the answers and I was like, oh, this is actually probably much closer to reality for that group of people.
And what would those numbers be? 48%, 77%. Or 67%. 48%, 67%, 68%, 69%.
Already fully automated - 5%.
No - 0%.
I'm not at all surprised.
So, I tell you what, though, here's the theme that's coming out, Tim, and we're not done doing this survey yet. My god, you guys have so much homework to do. So much homework to do.
Will you increase automation? One of the things, again, this is more anecdotal, but having talked to a lot of people for a long time, I talked to a lot of the certificate managers in organizations who say, listen, I want to increase my technology investment and what happens is, I'm competing for roadmap and budget with other things.
So normally, under these circumstances, we would either look at the top one critical or the top two critical and significant. And so why don't I just roll down the top two results, and we'll see a sense for what these are.
So security concerns. Top two is 56%.
Compliance or audit constraints. Top two is 63%.
Budget. Top two is 45%.
Uncertainty about vendor tools or solutions. Top two is 40%.
Integration concerns. Top two is 54%.
Competing roadmap items. Top two is 57%.
Job security - one you talked about - top two is 27%.
And awareness of alternatives. Top two is 21%.
So the biggest ones are in order. Compliance or audit constraints, followed by competing roadmap items, then integration concerns, then security concerns, and then there's kind of a gap, and then they've got a bunch that are much smaller - budget, uncertainty about vendor tools or solutions, job security and awareness of alternatives. So what do you think of that?
So it's like there's a batch and then everything else is down below it. And those are kind of what we hear.
So here's the question, to what degree do you see overlap in your organization's preparedness for 47 day public SSL/TLS certificates and post-quantum cryptography. Are you ready? Do you want to think of it in your mind and take a guess before I say?
Significant overlap - 38%.
Moderate overlap - 34%.
Slight overlap - 10%.
No overlap whatsoever - 8%.
Don't know - 2%.
So if you kind of batch the bottom three together, we got 20% who don't see a lot of overlap. The remaining 80% say it's moderate, significant or complete overlap. I don't agree. I don't agree on the complete overlap for what's worth?

