Imperva: Half of On-Prem Databases Contain Vulnerabilities

One out of every two on-premises databases globally has at least one vulnerability, finds a new study from Imperva Research Labs spanning 27,000 on-prem databases, based on insights from a proprietary database scanning service introduced by Imperva Innovation five years ago.

Imperva released the results of the study this week, which found, in total, 46% of on-premises databases worldwide, accounted for in the scan, contained known vulnerabilities.


Cyber experts weighed-in on this latest report from Imperva.


Joseph Carson, chief security scientist and Advisory CISO at ThycoticCentrify:

It comes as no surprise that many organizations still struggle to patch systems and reduce critical vulnerabilities, especially on databases. The balance between productivity and security is always a fine line. When databases are offline, it typically means the business productivity is impacted. Databases can contain sensitive information such as employee data, personal identifiable information, health data, financial details, intellectual property and much more so it is vital that organizations protect and secure databases with the highest priority. While the report does include some concerning numbers, it does not tell the complete picture as while the number of vulnerabilities is high it does not detail other security controls used to protect those databases. Patching systems is critical but it is also important to have strong access controls using privileged access security along with detailed auditing and MFA.

Tim Wade, Technical Director, CTO Team at Vectra:

In some respects, for those of us who’ve managed the chaos that exists inside an enterprise, these numbers aren’t surprising. Certainly the presence of neglect and a lack of IT hygiene are an important part of this finding, but it’s equally important to contextualize these findings against the reality that databases are disproportionately a part of essential business systems relative to other infrastructure. This reality creates tension between the risks of disruption via exploitation from failing to patch and the inevitable cases where patches aren’t fully baked, and themselves cause disruption. This tension exposes how the notion that enterprises will simply dig their way out of security holes with vulnerability management is a work of speculative fiction – known and unknown vulnerabilities will always exist in some noteworthy quantity, exploitation will occur as a byproduct of this, and it is incumbent on security professionals to invest in the capabilities necessary to detect and respond to such inevitabilities before material damage is done.

Yaniv Bar-Dayan, CEO and co-founder at Vulcan Cyber:

The world’s data has exploded to almost incomprehensible levels of scale. To store all of this data, and make it usable, we’ve had to create database technologies that are both functional and secure, attributes that are often at odds with each other and are difficult to attain considering the complexities of scale.

Security teams have three options to address data security:

  1. Do nothing and play the odds. This option isn’t acceptable to most organizations, but as we can see from Imperva’s research is the path almost half of all on-prem database administrators have chosen.

  2. Outsource to a data service like AWS or Snowflake. This doesn’t completely absolve the data owners from security responsibilities, but it goes a long way to reduce the burden. Cloud and data lake services can still be hacked through user configuration error or faulty user access control vulnerabilities. But the DBaaS service providers operate their cyber risk management and vulnerability remediation programs at the highest levels of program maturity which provides much needed relief for many organizations who don’t want to own these responsibilities.

  3. Be like the data service providers and attain a “transformative” level of risk mitigation and vulnerability remediation maturity. There are four levels of risk and vulnerability remediation program maturity, with “reactive” being the least mature and “transformative” being the most mature at level 4. Our own research finds that 55% of vulnerability management programs are at maturity level 1 or level 2 which draws a direct parallel to the prevalence of known, but unresolved, on-premises database vulnerabilities.

Keep in mind that even though a database might contain a vulnerability, it doesn’t necessarily mean that the vulnerability poses a meaningful risk to the business. There is a chance the database security team is doing their job right and has identified the vulnerability, assessed the threat against the database assets, and prioritized it at a non-critical level of risk to the business.

The Imperva data doesn’t tell us if the vulnerabilities are acceptable based on the owner’s assessment of risk, and vulnerability severity according to NIST guidelines is simply one input into what should be a custom risk score that is meaningful to the end user. Risk-based vulnerability prioritization is essential for effective data security.

Hank Schless, Senior Manager, Security Solutions at Lookout:

Even as the cloud has taken over the way we store and access data, there will always be a certain amount of on-prem infrastructure and applications that need to be monitored and secured. For many industries and organizations, this is because of compliance reasons or simply because it would be too much of an undertaking to move a massive amount of critical infrastructure and data to the cloud.

There are a number of risks involved in keeping things on-prem, especially from the security perspective. This report points out one of the most glaring challenges of on-prem, which is implementing security patches for vulnerable databases and other infrastructure. Organizations need to rely on their admins to download and install these patches as they’re made available. While admins may be diligent in doing so, it’s almost inevitable that they’ll miss a couple of resources. In that case, one vulnerable database is just as bad as one hundred. In addition, on-prem services may reach an age where they’re no longer supported. With few exceptions, this means that they will not receive a patch if additional vulnerabilities are discovered after they’re no longer supported.

Even if an organization’s infrastructure, apps, and data have to remain on-prem to some extent, the IT and security teams can still take a modern approach to securing them. Typically, access to these resources has been done through VPN, but nowadays even VPN solutions are being found to have vulnerabilities in them.

The modern approach to securing access to on-prem and private apps or infrastructure is by leveraging a zero trust network access (ZTNA) solution. In doing so, organizations can extend the security benefits of the cloud to on-prem services. Most importantly, it enables teams to build dynamic access policies that take into account contextual signals such as the user, location, device OS and profile, user and device risk score, and more to determine whether the on-prem resources are safe to be accessed. Users can access on-prem resources from any location and any device, whether it’s managed or unmanaged, without needing to hairpin traffic. ZTNA also enables teams to cloak their internet-facing private apps to prevent them from being discovered by attackers crawling the internet for vulnerable assets.

Implementing ZTNA enables teams to include on-prem resources in their zero trust architecture and move towards a modern approach to securing the interactions between users, devices, networks, and data.


###