Browser Security: Lessons from Google Chrome

The Web has become one of the primary ways people interact with their computers, connecting people with a diverse landscape of content, services, and applications. Users can find new and interesting content on the Web easily, but this presents a security challenge: malicious Web-site operators can a...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:ACM queue 2009-06, Vol.7 (5), p.1
Hauptverfasser: Reis, Charles, Barth, Adam, Pizano, Carlos
Format: Artikel
Sprache:eng
Schlagworte:
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
container_end_page
container_issue 5
container_start_page 1
container_title ACM queue
container_volume 7
creator Reis, Charles
Barth, Adam
Pizano, Carlos
description The Web has become one of the primary ways people interact with their computers, connecting people with a diverse landscape of content, services, and applications. Users can find new and interesting content on the Web easily, but this presents a security challenge: malicious Web-site operators can attack users through their Web browsers. Browsers face the challenge of keeping their users safe while providing a rich platform for Web applications. Generally speaking, the danger posed to users comes from three factors, and browser vendors can help keep their users safe by addressing each of these factors: 1. severity of vulnerabilities, 2. window of vulnerability, and 3. frequency of exposure. To make Google Chrome even more secure, experts are investigating further improvements to the browser's security architecture, such as mitigating the damage that plug-in exploits can cause and more thoroughly isolating different Web sites using separate sandboxed processes. Ultimately, their goal is to raise the bar high enough to deter attackers from targeting the browser.
doi_str_mv 10.1145/1551644.1556050
format Article
fullrecord <record><control><sourceid>proquest</sourceid><recordid>TN_cdi_proquest_journals_1784135241</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>4034838221</sourcerecordid><originalsourceid>FETCH-LOGICAL-c1850-5fdf8276945a2a4c832b7fa10c0398594dc8136c2a0788536a72efc42663f6e3</originalsourceid><addsrcrecordid>eNotjUFPAyEUhInRxFo9eyXxKpUH7wHrTTe1mmziwd4bpKA2tSh0Y_z3YvQy3zeXGcbOQc4AkK6ACAzirNFIkgds0swKqxEOfx2VsFbLY3ZS60ZKhR3hhF3elvxVY-FPMYzlbf99zYdYa95Vnkp-54ucX7aR96-txFN2lPy2xrN_Ttnybr7s78XwuHjobwYRwJEUlNbJKWs6JK88BqfVs00eZJC6c9ThOjjQJigvrXOkjbcqpoDKGJ1M1FN28Tf7UfLnGOt-tclj2bXHFViHoEm1-AFHbkHv</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>1784135241</pqid></control><display><type>article</type><title>Browser Security: Lessons from Google Chrome</title><source>Alma/SFX Local Collection</source><creator>Reis, Charles ; Barth, Adam ; Pizano, Carlos</creator><creatorcontrib>Reis, Charles ; Barth, Adam ; Pizano, Carlos</creatorcontrib><description>The Web has become one of the primary ways people interact with their computers, connecting people with a diverse landscape of content, services, and applications. Users can find new and interesting content on the Web easily, but this presents a security challenge: malicious Web-site operators can attack users through their Web browsers. Browsers face the challenge of keeping their users safe while providing a rich platform for Web applications. Generally speaking, the danger posed to users comes from three factors, and browser vendors can help keep their users safe by addressing each of these factors: 1. severity of vulnerabilities, 2. window of vulnerability, and 3. frequency of exposure. To make Google Chrome even more secure, experts are investigating further improvements to the browser's security architecture, such as mitigating the damage that plug-in exploits can cause and more thoroughly isolating different Web sites using separate sandboxed processes. Ultimately, their goal is to raise the bar high enough to deter attackers from targeting the browser.</description><identifier>ISSN: 1542-7730</identifier><identifier>EISSN: 1557-7341</identifier><identifier>DOI: 10.1145/1551644.1556050</identifier><language>eng</language><publisher>New York: Association for Computing Machinery</publisher><subject>Computer architecture ; Computer viruses ; Network security ; Software ; Web browsers</subject><ispartof>ACM queue, 2009-06, Vol.7 (5), p.1</ispartof><rights>Copyright Association for Computing Machinery Jun 2009</rights><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c1850-5fdf8276945a2a4c832b7fa10c0398594dc8136c2a0788536a72efc42663f6e3</citedby></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><link.rule.ids>314,780,784,27924,27925</link.rule.ids></links><search><creatorcontrib>Reis, Charles</creatorcontrib><creatorcontrib>Barth, Adam</creatorcontrib><creatorcontrib>Pizano, Carlos</creatorcontrib><title>Browser Security: Lessons from Google Chrome</title><title>ACM queue</title><description>The Web has become one of the primary ways people interact with their computers, connecting people with a diverse landscape of content, services, and applications. Users can find new and interesting content on the Web easily, but this presents a security challenge: malicious Web-site operators can attack users through their Web browsers. Browsers face the challenge of keeping their users safe while providing a rich platform for Web applications. Generally speaking, the danger posed to users comes from three factors, and browser vendors can help keep their users safe by addressing each of these factors: 1. severity of vulnerabilities, 2. window of vulnerability, and 3. frequency of exposure. To make Google Chrome even more secure, experts are investigating further improvements to the browser's security architecture, such as mitigating the damage that plug-in exploits can cause and more thoroughly isolating different Web sites using separate sandboxed processes. Ultimately, their goal is to raise the bar high enough to deter attackers from targeting the browser.</description><subject>Computer architecture</subject><subject>Computer viruses</subject><subject>Network security</subject><subject>Software</subject><subject>Web browsers</subject><issn>1542-7730</issn><issn>1557-7341</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2009</creationdate><recordtype>article</recordtype><recordid>eNotjUFPAyEUhInRxFo9eyXxKpUH7wHrTTe1mmziwd4bpKA2tSh0Y_z3YvQy3zeXGcbOQc4AkK6ACAzirNFIkgds0swKqxEOfx2VsFbLY3ZS60ZKhR3hhF3elvxVY-FPMYzlbf99zYdYa95Vnkp-54ucX7aR96-txFN2lPy2xrN_Ttnybr7s78XwuHjobwYRwJEUlNbJKWs6JK88BqfVs00eZJC6c9ThOjjQJigvrXOkjbcqpoDKGJ1M1FN28Tf7UfLnGOt-tclj2bXHFViHoEm1-AFHbkHv</recordid><startdate>20090601</startdate><enddate>20090601</enddate><creator>Reis, Charles</creator><creator>Barth, Adam</creator><creator>Pizano, Carlos</creator><general>Association for Computing Machinery</general><scope>JQ2</scope></search><sort><creationdate>20090601</creationdate><title>Browser Security: Lessons from Google Chrome</title><author>Reis, Charles ; Barth, Adam ; Pizano, Carlos</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c1850-5fdf8276945a2a4c832b7fa10c0398594dc8136c2a0788536a72efc42663f6e3</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2009</creationdate><topic>Computer architecture</topic><topic>Computer viruses</topic><topic>Network security</topic><topic>Software</topic><topic>Web browsers</topic><toplevel>online_resources</toplevel><creatorcontrib>Reis, Charles</creatorcontrib><creatorcontrib>Barth, Adam</creatorcontrib><creatorcontrib>Pizano, Carlos</creatorcontrib><collection>ProQuest Computer Science Collection</collection><jtitle>ACM queue</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Reis, Charles</au><au>Barth, Adam</au><au>Pizano, Carlos</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Browser Security: Lessons from Google Chrome</atitle><jtitle>ACM queue</jtitle><date>2009-06-01</date><risdate>2009</risdate><volume>7</volume><issue>5</issue><spage>1</spage><pages>1-</pages><issn>1542-7730</issn><eissn>1557-7341</eissn><abstract>The Web has become one of the primary ways people interact with their computers, connecting people with a diverse landscape of content, services, and applications. Users can find new and interesting content on the Web easily, but this presents a security challenge: malicious Web-site operators can attack users through their Web browsers. Browsers face the challenge of keeping their users safe while providing a rich platform for Web applications. Generally speaking, the danger posed to users comes from three factors, and browser vendors can help keep their users safe by addressing each of these factors: 1. severity of vulnerabilities, 2. window of vulnerability, and 3. frequency of exposure. To make Google Chrome even more secure, experts are investigating further improvements to the browser's security architecture, such as mitigating the damage that plug-in exploits can cause and more thoroughly isolating different Web sites using separate sandboxed processes. Ultimately, their goal is to raise the bar high enough to deter attackers from targeting the browser.</abstract><cop>New York</cop><pub>Association for Computing Machinery</pub><doi>10.1145/1551644.1556050</doi><oa>free_for_read</oa></addata></record>
fulltext fulltext
identifier ISSN: 1542-7730
ispartof ACM queue, 2009-06, Vol.7 (5), p.1
issn 1542-7730
1557-7341
language eng
recordid cdi_proquest_journals_1784135241
source Alma/SFX Local Collection
subjects Computer architecture
Computer viruses
Network security
Software
Web browsers
title Browser Security: Lessons from Google Chrome
url https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-21T02%3A02%3A50IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Browser%20Security:%20Lessons%20from%20Google%20Chrome&rft.jtitle=ACM%20queue&rft.au=Reis,%20Charles&rft.date=2009-06-01&rft.volume=7&rft.issue=5&rft.spage=1&rft.pages=1-&rft.issn=1542-7730&rft.eissn=1557-7341&rft_id=info:doi/10.1145/1551644.1556050&rft_dat=%3Cproquest%3E4034838221%3C/proquest%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=1784135241&rft_id=info:pmid/&rfr_iscdi=true