Have You Connected the Dots Between Compliance and Your Security Framework?

March 9th, 2021


Businesses and enterprises often fall into the bad habit of turning compliance into an annual task of checking boxes. Going through audits or filling out self-assessments is necessary to avoid paying fines and, in some cases, to continue to operate. However, a check-box view of compliance does nothing to strengthen your security framework.

The Purpose of Compliance

Standards and regulations, such as the Health Insurance Portability and Accountability Act (HIPAA), Payment Card Industry (PCI), Service Organization Control (SOC) 2 Type II, or Federal Financial Institutions Examinations Council (FFIEC), are based on security best practices for businesses or organizations like yours. Each compliance requirement is meant to make your IT environment more secure – and in a world where cyberattacks are becoming more frequent, more expansive, and more complex (e.g., the SolarWinds hack), stronger security should be a priority for everyone.

Compliance’s Link to a Security Framework

When you dig deeper into compliance requirements, you can see the correlation between compliance and security. For example, the FFIEC Cybersecurity Assessment Tool breaks down security into five domains:

vs_alldomains_

  1. Cyber Risk Management and Oversight
  2. Threat Intelligence and Collaboration
  3. Cybersecurity Controls
  4. External Dependency Management
  5. Cyber Incident Management and Resilience

Then, FFIEC breaks down each of those domains into subdomains. For instance, Domain 3, Cybersecurity Controls, is divided into nine subdomains.

Cybersecurity Controls

  1. Infrastructure Management
  2. Access & Data Management
  3. Device/End-Point Security
  4. Secure Coding
  5. Threat & Vulnerability Detection
  6. Anomalous Activity Detection
  7. Event Detection
  8. Patch Management
  9. Remediation

The first subdomain, Infrastructure Management, has 10 specific requirements for compliance – and stronger security. For example, the first is “Network perimeter defense tools (e.g., border router and firewall) are used.” Businesses using the FFIEC security framework have two choices at this point. If you have a firewall, you check the box. Option two is to implement a firewall and make sure it’s optimized to keep malicious traffic out while letting necessary traffic through (so your employees won’t disable it to do their jobs). Furthermore, you base the choices you make about firewall configuration, as well as how it works on other perimeter defense tools, such as routers, intrusion prevention/intrusion detection system, gateways, virtual private network (VPN), log monitoring, data loss prevention and access control solutions, on periodic risk assessments and threat intelligence.

The FFIEC security framework does more than give an organization a “pass” or “fail” within each subdomain. It ranks your performance in each area:

  1. “Baseline”
  2. “Evolving”
  3. “Intermediate”
  4. “Advanced”
  5. “Innovative”

It’s also possible to get a zero for a subdomain if you miss one or more of the requirements in a subdomain. Infrastructure Management’s 10 requirements are:

  1. Have a firewall and other perimeter controls
  2. Systems that are connected to the internet are protected
  3. Ports are monitored
  4. Antivirus and antimalware are up to date
  5. You follow industry standards to configure systems
  6. Ports that aren’t used are disabled
  7. Access to make changes to configurations are monitored
  8. Programs that can override security systems are restricted
  9. Sessions are locked or terminated after a predefined timeframe
  10. Wireless networking has security settings and encryption

So, if you’re missing the mark on numbers 6 and 9, you’d get a rank of 0 for the subdomain. Worse, you’re leaving unused ports open for hackers to use as a way into your systems and, without time limits, you’re giving hackers unlimited time to break in and make changes. Basically, in this subdomain – or any other part of the framework — not paying attention to compliance requirements is not paying attention to security.

Visualizing Security Framework Maturity

FFIEC also recognizes that building a strong security framework is a continuing process. Visualizations can help you and your team see your business or organization’s current maturity, how it compares to minimum maturity – and how much progress you need to make.

 

Threat intelligence and collaboration

In this framework, many businesses and organizations find themselves in the 1-2 range but all will find areas where they can improve and make changes that will make their organizations more secure.

Break the Cycle of Compliance for Compliance’s Sake

When you first look at a compliance assessment tool or an audit report, it’s easy to be overwhelmed, but just quickly running through the list of requirements and checking boxes isn’t providing your business or organization with the greatest degree of security.

Compliance is meant to provide your business with a security framework that will protect your data, customers, systems, and, ultimately, your business from the devastating impacts of a data breach.

Many business leaders know their organizations are vulnerable to cyberattacks but don’t know how to address the problem. Compliance audits and assessment tools are an excellent place to start.

Leave a Reply

Let's Talk

+
VIRTUAL SYSTEMS HAS ACHIEVED VEEAM PLATINUM
for Veeam Cloud and Service Providers