Application Security (AppSec)

Tim

27th October 2021

5 min read

Implementing application security (AppSec) from the beginning

There is a movement in the IT security world that is gaining traction, and it is based around the implementation of security within applications from the beginning. You may have heard buzzwords like “AppSec”, “DevSecOps” and “Shift Left”, but what do they actually mean? What does it take to “Shift Left” when developing a secure application? You can read about dealing with dependencies in our blog post.

In this article, we will explore how implementing security testing and controls earlier on in an application’s Software Development Life Cycle (SDLC) can impact a business. We will also discuss the ways a traditional application assessment may bring to light bigger issues than just insecure code, as well as the differences between the remediation performance of any potential vulnerabilities.

Using SQL injection as an example, even though injection has slipped in the OWASP Top 10 this year, injection attacks are still prevalent and common during application tests. Consider that an application has been fully developed in the ‘traditional’ method; no security assessments were performed at the beginning (threat modelling) or during (secure code reviews). Then, before the application is put into production, a security assessment is required for assurance purposes.

 

The scenario

Consider a scenario where a software development company contacts us for an application assessment. The application consists of a bootstrap frontend. There is a search form for querying critical business information, such as customer order details from an online retailer. The frontend end is supported by an API, which queries the business-critical database.

During the application assessment, a consultant identifies a potential SQL injection vulnerability in the search functionality with an apostrophe (‘). A database syntax error is returned.

There are many actions we could perform at this point. However, we only need to validate the weakness, for which a sleep command will suffice. Once the vulnerability is confirmed, a call is made to the relevant security contact and we discuss in-depth the vulnerability that we have identified and our recommendations to remediate this.

 

What next?

The consultant continues the application assessment in the hunt for more vulnerabilities, but the client now has a situation on their hands. An application has been developed to the point of release and all of a sudden, a significant security issue is identified.

This causes a number of challenges. Do the developers action the finding, mitigate the issue by ensuring database queries are parameterised and user input is sanitised, and accept that there are no longer any bugs in the code? Or, should they perform a full code review to supplement the application assessment with a further level of assurance?

Consider that the application does not solely support searching for customer orders. It likely supports queries for searching for items, quantities, sizes and colours; which may all support additional filters such as ordering or grouping. All of which may provide an opportunity for a malicious actor to achieve SQL injection.

There may be thousands of lines of code to analyse and check for entry points and insecurely written database queries. This takes a significant amount of time and often results in development teams missing deadlines and overspending on this remediation activity.

 

Shift Left, DevSecOps?

This is why Shift Left and DevSecOps (or SecDevOps) have come into the spotlight. The industry wants to build secure applications from the ground up which eliminates the need for the above remediation activities.

This may consist of threat-modelling prior to any code being written. A detailed plan of the application structure, its processes, inputs and outputs, and authentication mechanisms is used to identify where weaknesses may be found in the development stage.

Developers may be trained to write secure code or given access to tooling that will help to identify and explain potential vulnerabilities. There are tools available that analyse code or can be implemented into DevOps pipelines that automatically check for vulnerabilities and provide detailed information, prior to being accepted and merged into the codebase.

 

Final thought

Shift Left and DevSecOps are not going to happen overnight and are not a responsibility that relies solely on the development team. The shift has to be adopted by the entire organisation and support should be given to the development team by offering expertise and tooling. Collaboration between security teams and development teams should be encouraged.

There should not be a compromise between rapid development cycles and best practice security. When an organisation adopts security early on, both can be achieved. This will improve security posture and reduce costs of security integration while maintaining fast delivery which ultimately leads to business success.

Resources

  • Insights
  • Labs

OWASP Top 10 2021 Released

The Open Web Application Security Project (OWASP) is a not-for-profit organisation that aims, through community-led open-source projects, to improve the security of web-based software. OWASP…

What is penetration testing and why is it important to use a CREST-approved provider?

Trusting the effectiveness of your IT security controls is crucial to mitigate risks and malicious access to your systems and the information they store. Penetration…

How secure use of the cloud can digitally transform your business

Companies that move towards digital transformation can innovate more quickly, scale efficiently and reduce risk by implementing cloud security best practices. Businesses must keep up…

How to prepare your business for secure cloud migration

The cloud holds a lot of potential for organisations. Moving your IT environment to a secure cloud provides flexibility and agility. It allows your team…

Celebrating Sentrium’s contribution to cyber security

2020 is the year that remote working exploded. Businesses and the general public had to quickly adapt to new ways of working caused by the…

What is CREST and what are the benefits of using a CREST accredited company?

We’re delighted to announce that Sentrium Security is now a CREST accredited company! This is an exciting achievement for us and it’s great to be…

Preventing exploitation of the Follina vulnerability in MSDT

The Follina Exploit A zero-click Remote Code Execution (RCE) vulnerability has started making the rounds which is leveraging functionality within applications such as Microsoft Word.…

Application Security 101 – HTTP headers

1. Strict-Transport-Security The HTTP Strict Transport Security (HSTS) header forces browsers and other agents to interact with web servers over the encrypted HTTPS protocol, which…

New Exchange RCE vulnerability actively exploited

Exchange admins now have another exploit to deal with despite still reeling from a number of high profile attacks this year including ProxyLogon and ProxyShell.…

How effective is secure code review for discovering vulnerabilities?

We’ve recently discussed application security and the trend we’re seeing in which companies are increasingly implementing security early on in the Software Development Life Cycle…

Enhancing Security in your Software Development LifeCycle – Dealing with Dependencies

The adoption of agile practices has resulted in the emergence of shift-lift testing, where testing is performed much earlier in the Software Development LifeCycle (SDLC).…

TOP