Many companies wonder about whether SAST or DAST is better for application security testing. What are the relative benefits of each methodology? Is it possible to make use of both?
SAST and DAST are not mutually exclusive and should be used in conjunction with each other. One should be used by the developers to ensure security is being addressed as they are writing the code. The other is used for evaluating existing applications already in production to ensure they are not susceptible to any new vulnerabilities that have been discovered.
The real question is which should have a higher priority when it comes to introducing the concepts into your application security model. Unfortunately, there is no single answer to which comes first. It all depends on your organizations culture, business model, and your relationships with the various impacted groups.
Both. They are not in competition with each other.SAST is used for analyzing your written code for practices and patterns that are risky or vulnerable.DAST is used @ runtime for analyzing the app for vulnerabilities as shown in other ways on the runtime memory stack, etc.Both provide different value.Look into RASP vs DAST vs IAST as well.
For application security you ideally need SAST, SCA and DAST. You need all three as they essentially measure different things:
SAST identifies bad coding practices that potentially could be exploited
SCA identifies known vulnerabilities in the libraries and components you are using and this is the main attack vector on applications.
DAST identifies some of the weaknesses that SAST and SCA identified, but also identifies weaknesses in the configuration. You might have the perfect application code with zero vulnerabilities, but if it is misconfigured, for instance using a default password, it still can be breached.
If you have to choose, look at SCA and then DATS first as that gives you the best bang for your buck from a risk reduction perspective