Security testing for most cyber pros may seem like a no-brainer, almost like table stakes. However, nothing could be further from the truth. Despite the hundreds of exposed web applications and APIs in our attack surfaces, many assets remain dangerously untested and vulnerable to cyberattacks. With AI on the rise, this number will only get bigger.
This comes as no surprise. In a recent survey of over 100 cybersecurity professionals in the U.K., it was stated that threats to their web applications are of high concern. Yet, most security teams only manage to test these applications monthly, leaving a significant portion of applications vulnerable, highlighting a critical gap in our cybersecurity programs.
So why is it that we can’t manage to properly test?
Attack Surfaces are Becoming Unmanageable
Attack surfaces have always been a moving target. They fluctuate as organizations expand their tech stacks and integrate with other customer and partner systems. But in the long run, they only grow, making it difficult to keep up.
The same pool of UK cyber pros revealed that their organizations are struggling to keep up with the sheer volume and dynamic nature of web applications. In fact, 54.2% of respondents admitted that the number of web applications in their environment is too large for adequate testing.
Other significant barriers include the number of APIs to be tested and the time required to test each web application, cited by 59.8% and 55.1% of respondents, respectively.
The poll also revealed a shocking fact: These organizations experience significant security events quarterly related to their web application, which can take up to eight hours to fix.
So, Where is the Testing?
Organizations use a variety of methods including DAST, IAST and penetration testing to identify vulnerabilities, misconfigurations and other weaknesses in web applications.
Yet, more than a quarter of the respondents admitted to lacking a formal process for testing the security of their web application. Nearly half said they rarely use security testing tools or methods to uncover vulnerabilities in their web applications.
Reasons for infrequent testing and limited coverage:
- Too many apps and APIs: The sheer number of applications and APIs to be tested can be overwhelming
- Not enough time: Time constraints prevent thorough and frequent testing
- Frequent app updates and changes: Constant updates and changes to applications make it difficult to maintain a consistent testing schedule
- Insufficient staff: A lack of skilled personnel to conduct extensive testing
- Budget limitations: Financial constraints restrict the ability to invest in comprehensive testing tools and resources.
Tackling the Problem
Time and resource constraints aside, improving the testing frequency and effectiveness is non-negotiable. A few best practices include:
- Continuous monitoring: Ongoing visibility into the attack surface empowers organizations to be proactive and guide remediation activities effectively. Continuous monitoring helps in identifying vulnerabilities early, reducing the risk of successful attacks.
- Automation: Almost three-quarters of UK leaders surveyed stated plans to increase automation within their web application security testing workflows. Automation can save time, money and effort, provided it does not create additional problems such as generating false positives. It can streamline the testing process, allowing for more frequent and comprehensive assessments.
- Production testing: Testing in the production environment, rather than in sandboxes or offline, ensures that all elements affecting a web application — including databases, open-source libraries and authentication mechanisms — are considered. This approach provides a more accurate representation of potential vulnerabilities and their impacts.
- Investment in DevSecOps: To accelerate development cycles and improve time-to-market, organizations have invested in DevOps software to publish code more quickly. However, they have not invested in security software (DevSecOps). Integrating security into the DevOps pipeline is crucial for ensuring that rapid development does not come at the cost of compromised security.
Taking a Step Back
The big message here is that organizations are becoming increasingly exposed, and testing methods are inadequate to secure the environments.
Automated testing methods are not table takes. A quick shift can provide more comprehensive coverage, faster identification of vulnerabilities and a quicker remediation process.
It can streamline labor-intensive manual processes by performing continuous or frequent testing of all web apps and associated APIs in the environment, accurately identifying risks and filtering out low-priority issues or events.
Not only will it significantly improve an organization’s security posture, but it will also relieve some of the pressure on the security team.