About: Static application security testing

Facets (new session)
Description
Metadata
Settings
- Rule:
- Inverse Functional Properties:
- "Same As":

About: Static application security testing Goto Sponge NotDistinct Permalink

An Entity of Type : owl:Thing, within Data Space : dbpedia.demo.openlinksw.com associated with source document(s)
QRcode icon

http://dbpedia.demo.openlinksw.com/describe/?url=http%3A%2F%2Fdbpedia.org%2Fresource%2FStatic_application_security_testing

Static application security testing (SAST) is used to secure software by reviewing the source code of the software to identify sources of vulnerabilities. Although the process of statically analyzing the source code has existed as long as computers have existed, the technique spread to security in the late 90s and the first public discussion of SQL injection in 1998 when Web applications integrated new technologies like JavaScript and Flash. For the year of 2018, the Privacy Rights Clearinghouse database shows that more than 612 million records have been compromised by hacking.

Attributes	Values
rdfs:label	Static application security testing (en)
rdfs:comment	Static application security testing (SAST) is used to secure software by reviewing the source code of the software to identify sources of vulnerabilities. Although the process of statically analyzing the source code has existed as long as computers have existed, the technique spread to security in the late 90s and the first public discussion of SQL injection in 1998 when Web applications integrated new technologies like JavaScript and Flash. For the year of 2018, the Privacy Rights Clearinghouse database shows that more than 612 million records have been compromised by hacking. (en)
dcterms:subject	Static program analysis Security testing
Wikipage page ID	62778843 (xsd:integer)
Wikipage revision ID	1118130913 (xsd:integer)
Link from a Wikipage to another Wikipage	Static program analysis Application software Security testing Dynamic application security testing Instrumentation Interactive application security testing SQL injection Class (computer programming) Lint (software) Function (computer programming) Static program analysis Adobe Flash Player False positives and false negatives JavaScript Software development process Abstract syntax tree Black-box testing Code injection Code review Software audit review Security testing White-box testing
sameAs	Static application security testing Static application security testing Static application security testing
dbp:wikiPageUsesTemplate	dbt:Reflist
has abstract	Static application security testing (SAST) is used to secure software by reviewing the source code of the software to identify sources of vulnerabilities. Although the process of statically analyzing the source code has existed as long as computers have existed, the technique spread to security in the late 90s and the first public discussion of SQL injection in 1998 when Web applications integrated new technologies like JavaScript and Flash. Unlike dynamic application security testing (DAST) tools for black-box testing of application functionality, SAST tools focus on the code content of the application, white-box testing.A SAST tool scans the source code of applications and its components to identify potential security vulnerabilities in their software and architecture.Static analysis tools can detect an estimated 50% of existing security vulnerabilities. In SDLC, SAST is performed early in the development process and at code level, and also when all pieces of code and components are put together in a consistent testing environment. SAST is also used for software quality assurance. even if the many resulting false-positive impede its adoption by developers SAST tools are integrated into the development process to help development teams as they are primarily focusing on developing and delivering software respecting requested specifications. SAST tools, like other security tools, focus on reducing the risk of downtime of applications or that private information stored in applications will not be compromised. For the year of 2018, the Privacy Rights Clearinghouse database shows that more than 612 million records have been compromised by hacking. (en)
prov:wasDerivedFrom	wikipedia-en:Static_application_security_testing?oldid=1118130913&ns=0
page length (characters) of wiki page	13264 (xsd:nonNegativeInteger)
foaf:isPrimaryTopicOf	wikipedia-en:Static_application_security_testing
is Link from a Wikipage to another Wikipage of	Application security DevOps Dynamic application security testing Interactive application security testing GrammaTech Static program analysis John Jackson (hacker) Kiuwan Semgrep List of tools for static code analysis Security testing Visual Expert
is foaf:primaryTopic of	wikipedia-en:Static_application_security_testing

Faceted Search & Find service v1.17_git139 as of Feb 29 2024

Alternative Linked Data Documents: ODE Content Formats:

RDF

ODATA

Microdata

About

OpenLink Virtuoso version 08.03.3330 as of Mar 19 2024, on Linux (x86_64-generic-linux-glibc212), Single-Server Edition (378 GB total memory, 67 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software