Proceedings of the 2007 ACM/IFIP/USENIX International Conference on Middleware Companion 2007
DOI: 10.1145/1377943.1377956
|View full text |Cite
|
Sign up to set email alerts
|

Dynamic multi-process information flow tracking for web application security

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
17
0

Year Published

2008
2008
2015
2015

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 23 publications
(17 citation statements)
references
References 3 publications
0
17
0
Order By: Relevance
“…Secure Coding Practices [27,37,50] Lexical Analysis [9,10,49,54] Data-Flow Analysis [17,30] Context Free Grammars [52,53] New APIs [13,36] Learning [15,32,48] Query Modification [4,7,46] Runtime Tainting [22,29,42,56] Data-Flow Analysis [51] Hybrid [24,25,35] Syntax Embeddings [5] Intrusion Set Randomization [3,28,31] The most straightforward and sensible approach is the adoption of secure coding practices [27,50,37], like the ones we mentioned above to prevent sql code injection. However, this does not always happen, as programmers may not be aware of them, or time schedules may be tight, encouraging sloppy practices instead.…”
Section: Static Methods Dynamic Methodsmentioning
confidence: 99%
See 1 more Smart Citation
“…Secure Coding Practices [27,37,50] Lexical Analysis [9,10,49,54] Data-Flow Analysis [17,30] Context Free Grammars [52,53] New APIs [13,36] Learning [15,32,48] Query Modification [4,7,46] Runtime Tainting [22,29,42,56] Data-Flow Analysis [51] Hybrid [24,25,35] Syntax Embeddings [5] Intrusion Set Randomization [3,28,31] The most straightforward and sensible approach is the adoption of secure coding practices [27,50,37], like the ones we mentioned above to prevent sql code injection. However, this does not always happen, as programmers may not be aware of them, or time schedules may be tight, encouraging sloppy practices instead.…”
Section: Static Methods Dynamic Methodsmentioning
confidence: 99%
“…For instance, the system by Haldar et al [56] covers applications whose source code is written in Java, while the work by Xu et al [22] covers applications whose source code is written in C. A dynamic checking compiler called wasc includes runtime tainting to prevent sql and script injection [42]. To counter similar attacks, smask identifies tainted code by automatically separating user input from legitimate code [29].…”
Section: Dynamic Methodsmentioning
confidence: 99%
“…Newsome at al., have proposed dynamic tainting analysis for detecting exploits on commodity systems. Tainting has been also used solely in securing web applications [27,19,20], and, partially, for detecting and preventing code-injection attacks [18,21]. However, all of these frameworks target very precise problems, such as cross-site scripting [27] and SQL injection, or apply selectively to an isolated layer of the complete system.…”
Section: Related Workmentioning
confidence: 99%
“…WASC [40] is a compiler that adds taint checking in web applications to project against SQL and script injection attacks. An alternate approach is to use static taint propagation to detect vulnerabilities statically [51].…”
Section: Related Workmentioning
confidence: 99%
“…First, it combines application replay with offline taint analysis. Tainting has generally been used online for securing applications [40,42,51], but we are not aware of its use for data recovery. Second, we explore the benefits of finer-grained field-level dependencies at the database-tier than existing approaches that use row-level tainting [24,29,37].…”
Section: Introductionmentioning
confidence: 99%