ACM Home Page
Please provide us with feedback. Feedback
Security in the Browser
Full text HtmlHtml (23 KB),  PdfPdf (129 KB)
Source
Queue archive
Volume 7 ,  Issue 2  (February 2009) table of contents
Web Security
FEATURE: Features table of contents
Pages 40-41  
Year of Publication: 2009
ISSN:1542-7730
Authors
Thomas Wadlow  Consultant
Vlad Gorelik  AVG Technologies
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 367,   Downloads (12 Months): 1370,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1515964.1516164
What is a DOI?

ABSTRACT

Web browsers leave users vulnerable to an ever-growing number of attacks. Can we make them secure while preserving their usability?


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Stamos, A., Lackey, Z. 2006. Attacking AJAX web applications. iSEC Partners; http://www.isecpartners.com/ files/iSEC-Attacking_AJAX_Applications.BH2006.pdf.
 
2
Wikipedia. Comparison of Web browsers; http:// en.wikipedia.org/wiki/Comparison_of_web_browsers.
 
3
Wikipedia, HTTP cookie; http://en.wikipedia.org/wiki/ HTTP_cookie.
 
4
Wikipedia. Phishing; http://en.wikipedia.org/wiki/ Phishing.
 
5
Wikipedia. XMLHttpRequest; http://en.wikipedia. org/wiki/XMLHttpRequest.
 
6
Zalewski, M. 2008. Browser Security Handbook. Google; http://code.google.com/p/browsersec/wiki/Main.

Collaborative Colleagues:
Thomas Wadlow: colleagues
Vlad Gorelik: colleagues