I'm going to be super excited.

Yep.

So, yeah, so with regards to certificate rotation, automation is going to be key, right? We are going to have to automate this.

No one's going to want to rotate certificates manually every 30 days.

Today, that's the case because we do it annually.

So administrators, they're trained to do that.

They have run books.

yeah that's actually maybe a good segue into more of the private pki side we spent a good amount of time on on public but earlier on you mentioned that this movement to 47 days and a lot of the kind of strict uh deadlines being put on for public certificates doesn't apply to the private side but i'm curious uh what when you go in and and help companies of any size with their private pki for issuing their internal certificates What are the validity periods and timelines you typically recommend? Is it one size fits all or kind of how do you break those down based on the use case?

Right.

Microsoft has given us a bunch of, um, uh, tools to do that.

If you go to, I think it's, um, aka.ms/um, securebootplaybook, I think is the client version, and securebootforserver is the server version of that.

There's a ton of information there.

I won't rehash that, that here, but ultimately, there's a ton of information for ways to kick off the process, monitor the process, and so forth.

And, and back to the story I was, I started at the top of the, of the hour here, I wrote a PowerShell script because I was frustrated with the fact that the default command, uh, Get-SecureBoot, um, U- Get-UEFISecureBoot, I think is the command, doesn't return anything that I can readily look at.

So I wrote a PowerShell script called Get-UEFI Certificate-

Mm-hmm