There are only two things a SOC should be called:
Yes. Do you have specific questions or do you need something like an ELI5? Do you know how public key cryptography works?
That's not at all what I'm talking about. I don't mean "how do certs work?" I mean "actually dealing with certs in the real world."
They typically do a background check themselves unless it's from a recruiter. In that case the recruiter is expected to vet the candidate. Only time I've seen someone rejected for a criminal record was when they didn't say it up front and we found out about it. They got dropped from the interview process at that point.
Here again foler is a lying dinger sucker. Every fucking job on planet earth in tech asks if you have a record you pista driving antique lamp collecting shitbag.
I ran PKI operations for a large financial institution for 18 months. Even the experts are retards. Look at the recent let's encrypt outage leading to auth 0 outages.
I never have been explicitly asked if I have a record.
So you are looking for best practices? Do you want a list on things to do?
Voice and IVR traffic that contains credit card numbers must be PCI compliant. That means encrypted SIP trunks out to the provider and any other 3rd party apps in the talk path, more certs between the IVR applications and the core voice stack, identity certs between all the servers within the core voice stack, and also TLS certs for the call recorders and all the other adjunct call center application servers like wallboards, screen pop apps, CRM plugins, etc. It's a lot of certs.
