This is not a surprising outcome given the dominance of web applications and the global transition to remote, online working. But web applications have been a constant source of vulnerability since the early days of the internet. The rise of rich internet applications, paving the way for intuitive, any time, anywhere engagements on any device has exacerbated the situation.

The reality is that web applications present too easy a vulnerability point because of what development teams do – and don’t do. There are too many basic security vulnerabilities because development teams and their security auditors leave themselves wide open. For example, by not covering up the tracks to common folder locations where sensitive information can be obtained, they allow an enterprising hacker to gain easy access.

Disconnects in the security posture between different teams present gaps that can be exploited. For too many organisations, there is still too little sharing of either the security policies or the checklist of common vulnerabilities on which teams are regularly caught out.

We know that the landscape of attack vectors is constantly changing. Barracuda’s survey highlighted bot attacks, API security and software supply chain attacks. But there is a list of golden oldies that continue to be stubbornly prevalent – cross-site scripting, cookie poisoning, session hijacking, credential stuffing and SQL injection, to name but a few.

It is hard not to be critical of the developers of web applications. There are, after all, numerous studies pointing to their culpability in building in or leaving vulnerabilities. Yet, they are aware of the importance of making web applications secure, given that these apps are such a common access point for cyber crimes.

For all those who care about meeting the expectations of clients, whether they are inside or outside the organization, one of your top priorities should be to reduce risk in the web applications you develop.

There are many suppliers that can provide tools and audit services that can take web application security and privacy to a higher order of operation and robustness. The numerous products built on open source support provide cost-effective access. A strong testing regime is essential. This needs to be underwritten by automated support to allow for more effective and faster test coverage.

Two important bodies, the SANS Institute and OWASP, have worldwide recognition in monitoring and providing the leading security checklists for web application design. OWASP has embarked on a secure headers project that delivers HTTP response header descriptions that, if used, will help increase the security of applications.

Behind the need for security education, training, tools and best practices lies a simple fact: continuous checking not only helps to plug the gaps, it also creates an environment for speedy detection and resolution.

Enlightenment comes from knowing that vulnerabilities will always exist because nothing is infallible. Ultimately, giving development and security teams the time and space to regularly check with the right best practices and tools in place will reinforce the security of web applications considerably.