Transcript
A (0:01)
You're listening to the N2K space network.
B (0:10)
At Thales. They know cybersecurity can be tough and you can't protect everything. But with Thales, you can secure what matters most. With Thales industry leading platforms, you can protect critical applications, data and identities anywhere and at scale with the highest roi. That's why the most trusted brands and largest banks, retailers and healthcare companies in the world rely on Thales to protect what matters most. Applications, data and identity. That's Talas. T H A L E S learn more@thalesgroup.com cyber.
A (0:55)
If you work with the US Department of Defense, and likely many of you listening do, then you already know that there are some requirements in place to implement best practices in cybersecurity. Are those requirements going far enough though? The federal government is starting to see that no they don't. And that is why they are implementing the Cybersecurity Maturity Model Certification Program, otherwise known as the cmmc. Okay, so what is the cmmc? Well, you're about to find out with me.
B (1:50)
Maria.
A (1:50)
I'm Maria Ramazas and this is T Deep Space. A new policy is about to come into effect here in the United States. So if you are a space company that works with the US Federal government, specifically the Department of Defense, then you're going to need to become acquainted with cmmc, if you aren't already. And our guest and expert, Jacob Horne is here to help.
B (2:16)
I am Jacob Horne. I am the chief CyberSecurity evangelist at Summit 7. We are a managed service provider, so essentially the outsourced IT and security department, specifically for defense contractors who need to comply with their contractually mandated cybersecurity requirements. And Chief Evangelist is a purely made up title. It basically says I don't have a sales quota. And I'm just here to try to translate all of the regulatory gobbledygook around all of the cybersecurity requirements into human speak the best that I can because there's a lot of people affected by the requirements and regulations and they all sort of speak a different language from the people writing the requirements. And that's, that's my job. I've been working in security now for almost 20 years. I started out active duty in the Navy as a cryptologic technician doing some cool Secret Squirrel high speed stuff attached to the National Security Agency, which was super, super interesting. I was able to do a deployment which is pretty rare for somebody with my job in the Navy and I hated it. So I got out of the Navy and then I worked as a sort of standard SOC operations, 24 by 7 watch floor out in Hawaii, living the dream. Then I decided that I wanted to get back to Southern California, where I was from, and they needed a ton of people doing compliance work. And I was like, sure, it's fine with me. I don't mind, you know. And there I was minding my business, running ATO packages, risk management framework, NIST control stuff. People who have worked with the prime contractors and with the government directly will know what I'm talking about. And one day the supply chain people came into my office absolutely freaking out because all of the suppliers needed to comply with this new set of requirements. In a document called NIST Special Publication 800 171, they said, you're the NIST control guy. What is this? And that was a consulting opportunity because there were a bunch of people out in the muggle world, you know, manufacturing parts to go on space systems and weapon systems and things like that that had never needed to interact with NIST controls directly because they weren't on the federal side. So I started doing some consulting and sort of just explaining how these requirements work, talking to folks at the NIST Manufacturing Extension Partnership Program, things like that. One thing led to another and the Summit seven folks came to me and said, do you want to do marketing? And I was like, you just want me to keep explaining things to folks? And they said, yeah. So here we are.
