WEBVTT
Kind: captions
Language: en

00:00:00.810 --> 00:00:05.279
Building the most secure browser that we can
is a top priority for the Google Chrome team.

00:00:05.279 --> 00:00:09.000
A secure browser helps guard against threats
such as phishing and malware, which could

00:00:09.000 --> 00:00:11.460
steal your passwords - or worse.

00:00:11.460 --> 00:00:15.590
Sandboxing is a feature that we’ve built
into Google Chrome to enhance the browser’s

00:00:15.590 --> 00:00:16.590
security.

00:00:16.590 --> 00:00:18.789
Here’s how sandboxing works:

00:00:18.789 --> 00:00:23.070
In Chrome, every every website or web application
you open in the browser is a separate and

00:00:23.070 --> 00:00:24.839
independent process.

00:00:24.839 --> 00:00:29.410
For example, if you open three different websites
in three different browser tabs, each tab

00:00:29.410 --> 00:00:32.360
you open corresponds to a separate process.

00:00:32.360 --> 00:00:37.120
So if one tab crashes, the browser and other
tabs you have open shouldn’t be affected.

00:00:37.120 --> 00:00:42.010
Sandboxing provides a layer of protection
around each of these processes. Just like

00:00:42.010 --> 00:00:48.200
an actual sandbox, it is designed to build
a restricted environment around each process.

00:00:48.200 --> 00:00:52.200
If you inadvertently open a malicious web
page designed to harm your computer or even

00:00:52.200 --> 00:00:56.160
a familiar website that has been hacked, the
browser’s sandbox is designed to prevent

00:00:56.160 --> 00:01:00.990
malicious code on the exploited website from
causing further damage to your computer. The

00:01:00.990 --> 00:01:06.049
malicious code is contained within the sandbox
so that it does not affect other tabs in your

00:01:06.049 --> 00:01:07.719
browser or your machine.

00:01:07.719 --> 00:01:12.320
So something bad can be running in one tab,
but as soon as you close the tab, it’s gone

00:01:12.320 --> 00:01:15.020
 - without any harm to your computer.

00:01:15.020 --> 00:01:19.619
In Chrome, all web pages that you view in
the browser are sandboxed. However, there

00:01:19.619 --> 00:01:23.950
are other parts of the browser that benefit
from sandboxing too.

00:01:23.950 --> 00:01:27.689
Plug-ins are additional pieces of software
that plug into the browser to enable useful

00:01:27.689 --> 00:01:33.069
functionality. For example, Adobe Flash Player
is a widely used plug-in that enables web

00:01:33.069 --> 00:01:39.740
content such as online videos and games. Plug-ins
also allow you to view PDF documents online.

00:01:39.740 --> 00:01:44.159
Plug-ins are widely used and enable powerful
functionality, but that widespread usage and

00:01:44.159 --> 00:01:48.630
power can make them prime targets for security
attacks across all browsers.

00:01:48.630 --> 00:01:52.520
Users are even more vulnerable to attacks
if they are running plugins that aren't up

00:01:52.520 --> 00:01:57.649
to date. Out-of-date plugins frequently contain
known vulnerabilities.

00:01:57.649 --> 00:02:01.719
In our efforts to better protect Chrome users
from security exploits, we’ve built and

00:02:01.719 --> 00:02:06.960
sandboxed Flash and PDF functionality directly
into Chrome. These integrations take advantage

00:02:06.960 --> 00:02:11.590
of Chrome’s auto-update mechanism to help
ensure that they are never out-of-date. This

00:02:11.590 --> 00:02:16.069
means that as a Chrome user, you’ll always
receive the latest security fixes and patches

00:02:16.069 --> 00:02:18.730
for these integrations.

00:02:18.730 --> 00:02:23.799
To learn more about Chrome and security, visit:
google.com/chrome/security.