Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Application security
open-in-new
<h2 id="approaches">Approaches</h2> <p>Different approaches will find different subsets of the security <a href="/facts/Vulnerability/CJ1Mx1uG">vulnerabilities</a> lurking in an application and are most effective at different times in the software lifecycle. They each represent different tradeoffs of time, effort, cost and vulnerabilities found. </p> <ul><li><a href="/facts/Design_review/N6vjDtBs">Design review</a>. Before code is written the application's architecture and design can be reviewed for security problems. A common technique in this phase is the creation of a <a href="/facts/Threat_model/WhveDvPP">threat model</a>.</li> <li><a href="/facts/White-box_testing/mVc9WRoa">Whitebox</a> security review, or <a href="/facts/Code_review/1I93ffGF">code review</a>. This is a security engineer deeply understanding the application through manually reviewing the source code and noticing security flaws. Through comprehension of the application, vulnerabilities unique to the application can be found.</li> <li><a href="/facts/Blackbox/j2m9znVs">Blackbox</a> <a href="/facts/Information_security_audit/B261JIFY">security audit</a>. This is only through the use of an application testing it for security vulnerabilities, no source code is required.</li> <li>Automated Tooling. Many security tools can be automated through inclusion into the development or testing environment. Examples of those are automated DAST/SAST tools that are integrated into code editor or CI/CD platforms.</li> <li><a href="/facts/Bug_bounty_program/KfyUbdlL">Coordinated vulnerability platforms</a>. These are hacker-powered application security solutions offered by many websites and software developers by which individuals can receive recognition and compensation for reporting bugs.</li></ul> <h2 id="security-threats">Security threats</h2> <p>The Open Worldwide Application Security Project (<a href="/facts/OWASP/t30EKe8Q">OWASP</a>) provides free and open resources. It is led by a non-profit called The OWASP Foundation. The OWASP Top 10 - 2017 results from recent research based on comprehensive data compiled from over 40 partner organizations. This data revealed approximately 2.3 million vulnerabilities across over 50,000 applications.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> According to the OWASP Top 10 - 2021, the ten most critical web application security risks include:<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> </p> <ol><li>Broken <a href="/facts/Access_control/08zE5Pz8">access control</a></li> <li>Cryptographic failures</li> <li><a href="/facts/Code_injection/6gPRDpd1">Injection</a></li> <li>Insecure design</li> <li>Security misconfiguration</li> <li>Vulnerable and outdated components</li> <li>Identification and authentification failures</li> <li>Software and data integrity failures</li> <li>Security logging and monitoring failures*</li> <li>Server-side request forgery (SSRF)*</li></ol> <h2 id="security-controls">Security controls</h2> <p>The <a href="https://top10proactive.owasp.org/">OWASP Top 10 Proactive Controls 2024</a> is a list of security techniques every software architect and developer should know and heed. </p><p>The current list contains: </p> <ol><li>Implement access control</li> <li>Use cryptography the proper way</li> <li>Validate all input & handle exceptions</li> <li>Address security from the start</li> <li>Secure by default configurations</li> <li>Keep your components secure</li> <li>Implement digital identity</li> <li>Use browser security features</li> <li>Implement security logging and monitoring</li> <li>Stop server-side request forgery</li></ol> <h2 id="tooling-for-security-testing">Tooling for security testing</h2> <p>Security testing techniques scour for vulnerabilities or security holes in applications. These vulnerabilities leave applications open to <a href="/facts/Exploit_(computer_security)/EdlqsRJM">exploitation</a>. Ideally, security testing is implemented throughout the entire <a href="/facts/Software_development_life_cycle/cIDtuNPN">software development life cycle</a> (SDLC) so that vulnerabilities may be addressed in a timely and thorough manner. </p><p>There are many kinds of automated tools for identifying vulnerabilities in applications. Common tool categories used for identifying application vulnerabilities include: </p> <ul><li><a href="/facts/Static_application_security_testing/eN4lDLk2">Static application security testing</a> (SAST) analyzes source code for security vulnerabilities during an application's development. Compared to DAST, SAST can be utilized even before the application is in an executable state. As SAST has access to the full source code it is a white-box approach. This can yield more detailed results but can result in many false positives that need to be manually verified.</li> <li><a href="/facts/Dynamic_application_security_testing/V8vvzwdv">Dynamic application security testing</a> (DAST, often called <a href="/facts/Vulnerability_scanner/3HCta3LV">vulnerability scanners</a>) automatically detects vulnerabilities by crawling and analyzing websites. This method is highly scalable, easily integrated and quick. DAST tools are well suited for dealing with low-level attacks such as injection flaws but are not well suited to detect high-level flaws, e.g., logic or business logic flaws.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> <a href="/facts/Fuzzing/I1GK5kxr">Fuzzing</a> tools are commonly used for input testing.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a></li> <li>Interactive application security testing (IAST) assesses applications from within using software instrumentation. This combines the strengths of both SAST and DAST methods as well as providing access to code, HTTP traffic, library information, backend connections and configuration information.<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a><a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> Some IAST products require the application to be attacked, while others can be used during normal quality assurance testing.<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a>[<i>promotional source?</i>]<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a>[<i>promotional source?</i>]</li> <li><a href="/facts/Runtime_application_self-protection/1etB91nl">Runtime application self-protection</a> augments existing applications to provide intrusion detection and prevention from within an application runtime.</li> <li>Dependency scanners (also called <a href="/facts/Software_composition_analysis/0AnjobxB">software composition analysis</a>) try to detect the usage of software components with known vulnerabilities. These tools can either work on-demand, e.g., during the source code build process, or periodically.</li></ul> <h2 id="security-standards-and-regulations">Security standards and regulations</h2> <ul><li><a href="/facts/CERT_C_Coding_Standard/qwgEwoUJ">CERT Secure Coding standard</a></li> <li>ISO/IEC 27034-1:2011 <i>Information technology — Security techniques — Application security -- Part 1: Overview and concepts</i></li> <li>ISO/IEC TR 24772:2013 <i>Information technology — Programming languages — Guidance to avoiding vulnerabilities in programming languages through language selection and use</i></li> <li><a href="/facts/NIST_Special_Publication_800-53/Ggcp9vN8">NIST Special Publication 800-53</a></li> <li>OWASP ASVS: Web Application Security Verification Standard<a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a></li></ul> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Common_Weakness_Enumeration/LsL19Ff9">Common Weakness Enumeration</a></li> <li><a href="/facts/Data_security/VApktKQD">Data security</a></li> <li><a href="/facts/Mobile_security/6AhXW68J">Mobile security</a></li> <li><a href="/facts/OWASP/t30EKe8Q">OWASP</a></li> <li><a href="/facts/Microsoft_Security_Development_Lifecycle/NgEou5TJ">Microsoft Security Development Lifecycle</a></li> <li><a href="/facts/Usable_security/lYIuIcSa">Usable security</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Happe, Andreas (3 June 2021). "What is AppSec anyways?". snikt.net. <a href="https://snikt.net/blog/2021/06/03/what-is-appsec-anyways/" target="_blank">https://snikt.net/blog/2021/06/03/what-is-appsec-anyways/</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>"Web Application Security Overview". 2015-10-23. <a href="https://msdn.microsoft.com/en-us/library/ff648636.aspx" target="_blank">https://msdn.microsoft.com/en-us/library/ff648636.aspx</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Shuaibu, Bala Musa; Norwawi, Norita Md; Selamat, Mohd Hasan; Al-Alwani, Abdulkareem (2013-01-17). "Systematic review of web application security development model". Artificial Intelligence Review. 43 (2): 259–276. doi:10.1007/s10462-012-9375-6. ISSN 0269-2821. S2CID 15221613. <a href="/wiki/Doi_(identifier)" target="_blank">/wiki/Doi_(identifier)</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Korolov, Maria (Apr 27, 2017). "Latest OWASP Top 10 looks at APIs, web apps: The new OWASP Top 10 list is out, and while most of it remains the same, there are new additions focusing on web applications and APIs". CSO. ProQuest 1892694046. <a href="/wiki/ProQuest" target="_blank">/wiki/ProQuest</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>"OWASP Top 10 - 2021: The Ten Most Critical Web Application Security Risks". Open Web Application Security Project. 2021. Retrieved January 11, 2022. <a href="https://owasp.org/Top10/" target="_blank">https://owasp.org/Top10/</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>"Web Application Vulnerability Scanners". NIST. <a href="http://samate.nist.gov/index.php/Web_Application_Vulnerability_Scanners.html" target="_blank">http://samate.nist.gov/index.php/Web_Application_Vulnerability_Scanners.html</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>"Fuzzing". OWASP. <a href="https://owasp.org/www-community/Fuzzing" target="_blank">https://owasp.org/www-community/Fuzzing</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>Williams, Jeff (2 July 2015). "I Understand SAST and DAST But What is an IAST and Why Does it Matter?". Contrast Security. Retrieved 10 April 2018. <a href="https://www.contrastsecurity.com/security-influencers/question-i-understand-sast-and-dast-and-how-to-use-them-but-what-is-iast-and-why-does-it-matter" target="_blank">https://www.contrastsecurity.com/security-influencers/question-i-understand-sast-and-dast-and-how-to-use-them-but-what-is-iast-and-why-does-it-matter</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>Velasco, Roberto (7 May 2020). "What is IAST? All About Interactive Application Security Testing". Hdiv Security. Retrieved 7 May 2020. <a href="https://hdivsecurity.com/bornsecure/what-is-iast-interactive-application-security-testing/" target="_blank">https://hdivsecurity.com/bornsecure/what-is-iast-interactive-application-security-testing/</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>Abezgauz, Irene (February 17, 2014). "Introduction to Interactive Application Security Testing". Quotium. Archived from the original on April 3, 2018. Retrieved January 25, 2018. <a href="https://web.archive.org/web/20180403193750/http://www.quotium.com/resources/interactive-application-security-testing/" target="_blank">https://web.archive.org/web/20180403193750/http://www.quotium.com/resources/interactive-application-security-testing/</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>Rohr, Matthias (November 26, 2015). "IAST: A New Approach For Agile Security Testing". Secodis. <a href="https://blog.secodis.com/2015/11/26/the-emerge-of-iast/" target="_blank">https://blog.secodis.com/2015/11/26/the-emerge-of-iast/</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> <li id="fn:12"><p>"OWASP Application Security Verification Standard". <a href="https://owasp.org/www-project-application-security-verification-standard/" target="_blank">https://owasp.org/www-project-application-security-verification-standard/</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li> </ol>