Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Kubernetes is an extremely powerful tool for scaling, automating, and managing applications and systems. There’s a reason it has become industry standard, with over 80% of container-using enterprises running K8s, encompassing over 60% of enterprises in general. It makes sense that, sooner or later, Kubernetes users will need to contend with the FedRAMP framework and the security requirements necessary to maintain operations. Fortunately, this is generally a good thing.

Here on the Ignyte blog, we talk a lot about general information security frameworks like ISO 27001 and government frameworks like CMMC and FedRAMP. But that doesn’t mean that’s all we understand. One of the most broadly used security standards in the world is PCI DSS. The Payment Card Industry Data Security Standard is the standard that must be upheld by any and all entities that handle, process, or store cardholder data and authentication data for payments.

A key part of any security framework, from FedRAMP to ISO 27001, is enforcement. Putting out a set of standards is only as effective as the ability to penalize failure to comply. Within the ISO ecosystem, compliance is validated through the use of external audits. The auditors will evaluate your organization based on both ISO standards and other external factors, like regulatory requirements within your industry.

Now that CMMC is a mandatory part of participating in the defense supply chain, a lot of businesses are starting to grapple with the requirements and what they mean for operations. One of the biggest roadblocks is the use of an MSP, or Managed Services Provider. MSPs are the backbone of many businesses that don’t have the resources to spin up entire architectures on their own. It’s a huge benefit and allows companies to exist when otherwise the investment to get started would be way too high.

What happens when there’s an unexpected interruption to your business? Certainly, it depends on the kind of interruption. The way your business handles something like a power outage can be quite different from how you handle a wildfire, which will be different from how you handle a cyberattack. The core principles are the same. You want to have ways to defend your business, to restore services, and to ensure continuity as much as possible.

With any security framework, be it ISO 27001, FedRAMP, or CMMC, the goal is not to secure “your business.” It’s to secure sensitive and controlled information that your business handles. This is a fundamentally important way of looking at your security. Why does this matter? It’s all about borders. Where do you draw the line between what you keep secure and what you don’t care about?

When a cloud services provider wants to work with the federal government, they have to pass a rigorous audit to make sure they’re capable of properly securing the controlled information they would handle in the process. Achieving that Authority to Operate is done through the Federal Risk and Authorization Management Program and is the biggest barrier to federal contracts, and the bar is high. As many as 60% of CSPs attempting to pass their ATO audit will fail.

When you think about an IRS publication, you’re probably thinking about the complex forms you need to fill out, usually relating to taxes. That’s not all the IRS publishes, though, and one of the more important documents they maintain is called Publication 1075. When it comes to sensitive information for everyday Americans and private sector businesses, there’s very little more important and more sensitive than tax information.

Information security frameworks like CMMC are not just about enforcing security. They’re about enforcing accountability. That’s why a whole section of controls and rules that make up CMMC centers around incident response and reporting. You can’t just have security in place, but throw your hands up and do nothing if there’s an incident or breach. Nor can you sweep it under the rug and hope no one notices.

Across the ecosystem of federal contractors, a majority of deployments tend to be relatively standard. 80% of them will be FedRAMP impact level Moderate, for example, and most will have a standard set of considerations and concerns, such that a lot of security controls can be automated. It’s those outliers that make FedRAMP challenging.