ACM Home Page
Please provide us with feedback. Feedback
Security in the browser
Full text Digital EditionDigital Edition HtmlHtml (27 KB),  PdfPdf (9.49 MB)
Source
Communications of the ACM archive
Volume 52 ,  Issue 5  (May 2009) table of contents
Security in the Browser
SECTION: Practice table of contents
Pages 40-45  
Year of Publication: 2009
ISSN:0001-0782
Authors
Thomas Wadlow
Vlad Gorelik  AVG Technologies
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 244,   Downloads (12 Months): 2788,   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/1506409.1506422
What is a DOI?

ABSTRACT

What can be done to make Web browsers 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
Google. Browser Security Handbook; http://code.google.com/p/browsersec/wiki/Main.
 
2
ISecPartners. Attacking AJAX Applications; http://www.isecpartners.com/files/iSEC-Attacking_AJAX_Applications.BH2006.pdf.
 
3
Wikipedia. Comparison of Web Browsers; http://en.wikipedia.org/wiki/Comparison_of_web_browsers.
 
4
Wikipedia. HTTP cookie; http://en.wikipedia.org/wiki/HTTP_cookie.
 
5
Wikipedia. Phishing; http://en.wikipedia.org/wiki/Phishing.
 
6
Wikipedia. XMLHttpRequest; http://en.wikipedia.org/wiki/XMLHttpRequest.

Collaborative Colleagues:
Thomas Wadlow: colleagues
Vlad Gorelik: colleagues