WEBVTT

00:00:00.540 --> 00:00:01.070
Finally,

00:00:01.070 --> 00:00:05.320
let's peer into how an organization could maintain their

00:00:05.320 --> 00:00:08.960
legal and regulatory privacy mandates.

00:00:09.540 --> 00:00:14.560
Fortunately, you do not have to create a framework from scratch.

00:00:14.560 --> 00:00:16.160
There are many out there.

00:00:16.170 --> 00:00:20.740
The first one we'll take a look at is the Generally Accepted Privacy Principles

00:00:20.740 --> 00:00:24.190
from the American Institute of Certified Public Accountants,

00:00:24.300 --> 00:00:25.860
otherwise known as AICPA.

00:00:26.140 --> 00:00:29.970
There are 10 privacy principles to pay attention to.

00:00:29.970 --> 00:00:34.100
Management has to do with the entity defining,

00:00:34.110 --> 00:00:34.900
documenting,

00:00:34.900 --> 00:00:39.470
communicating, and assigning accountability, there that term is again, legal

00:00:39.470 --> 00:00:43.380
liability, for its privacy policies and the procedures.

00:00:43.390 --> 00:00:47.650
Notice means that the organization would provide notice about its privacy

00:00:47.650 --> 00:00:52.160
policies and procedures and identify the purpose for which personal information

00:00:52.160 --> 00:00:56.050
is collected, used, and retained and also disclosed.

00:00:56.140 --> 00:01:00.700
There's a very strong position that organizations need to

00:01:00.700 --> 00:01:03.230
maintain related to choice and consent.

00:01:03.240 --> 00:01:08.220
These are the choices available to the individual and makes sure that the

00:01:08.220 --> 00:01:13.070
controller obtains implicit or explicit consent with respect to the

00:01:13.070 --> 00:01:15.990
collection, use, and disclosure of their personal information.

00:01:16.000 --> 00:01:19.640
The collection means that the personal information is only

00:01:19.640 --> 00:01:22.450
for the purposes intended in the notice.

00:01:22.480 --> 00:01:26.730
Use, retention, and disposal have to do with the limits that should be put

00:01:26.740 --> 00:01:32.470
upon the entity collecting the information so that it is only used for the

00:01:32.470 --> 00:01:35.860
stated purpose. And once that purpose is fulfilled,

00:01:36.040 --> 00:01:38.760
it is no longer utilized.

00:01:38.840 --> 00:01:42.580
When we think about the idea of access,

00:01:42.590 --> 00:01:47.160
making sure that there is adequate protection on that information,

00:01:47.160 --> 00:01:53.400
the idea of disclosure means that the personal information should not

00:01:53.400 --> 00:01:59.010
be put forward to a third party unless implicitly or explicitly given

00:01:59.010 --> 00:02:01.310
consent by the data subject.

00:02:01.320 --> 00:02:06.950
There is the idea of security for privacy that would be included in this, so

00:02:06.950 --> 00:02:12.030
the entity protects the information against unauthorized use, both physical and

00:02:12.030 --> 00:02:15.990
logical. Making sure that the information is accurate, up to date, and

00:02:15.990 --> 00:02:18.960
complete. And then you have ongoing monitoring.

00:02:19.840 --> 00:02:23.760
If you consider for a moment the DNA of the

00:02:23.760 --> 00:02:26.400
Generally Accepted Privacy Principles,

00:02:26.410 --> 00:02:33.520
you could see that the predecessor of the OECD way back in 1980 kind of

00:02:33.520 --> 00:02:36.850
sets the tone for even the principles that you see here.

00:02:37.340 --> 00:02:42.090
General data privacy concerns have to do with answering these questions.

00:02:42.100 --> 00:02:45.260
Where is the location of the data?

00:02:45.740 --> 00:02:51.340
What is the specific practice? An organization may not be part of an

00:02:51.350 --> 00:02:56.270
industry, but by their participating in a particular practice,

00:02:56.280 --> 00:03:02.070
they may come under the regulatory requirements and, obviously, the law.

00:03:02.070 --> 00:03:07.100
Also, who is involved in the maintenance of the data? Well,

00:03:07.110 --> 00:03:12.680
let's look at these roles for a few moments. When we think about data privacy,

00:03:12.690 --> 00:03:17.390
the center of the universe should be the data subject.

00:03:17.590 --> 00:03:24.150
The data subject is an identified or identifiable natural person.

00:03:24.540 --> 00:03:30.470
The data controller is the public authority or agency that alone or

00:03:30.470 --> 00:03:34.220
jointly determines the purpose and means of the processing of the personal

00:03:34.220 --> 00:03:38.660
data based upon the consent of the data subject.

00:03:38.940 --> 00:03:40.520
The processor,

00:03:40.530 --> 00:03:45.510
you could think of them as being the platform upon which the data

00:03:45.510 --> 00:03:48.860
controller does the work concerning the data subject.

00:03:49.240 --> 00:03:56.010
If I were to introduce Netflix, if you are a member, AWS, and you,

00:03:56.130 --> 00:04:01.750
which role would be which for these primary data privacy roles?

00:04:02.840 --> 00:04:03.380
Well,

00:04:03.400 --> 00:04:09.650
if you answer you are the subscriber as the data subject, Netflix is the

00:04:09.650 --> 00:04:13.850
controller because that's who you made your agreement with on how they use

00:04:13.850 --> 00:04:21.040
your personal information, Netflix operates its environment on top of AWS,

00:04:21.050 --> 00:04:23.220
which would be considered the processor.

00:04:23.230 --> 00:04:29.990
It is the controller that has the liability for the protection of your data.

00:04:30.000 --> 00:04:32.870
While there are responsibilities among all three,

00:04:32.880 --> 00:04:39.060
the ultimate liability for the disposition of the data is with the controller.

00:04:39.540 --> 00:04:43.650
Now there are some sub‑roles that would report to the

00:04:43.650 --> 00:04:46.790
controller and the processor known as a custodian.

00:04:46.800 --> 00:04:52.590
A way of defining custodian simply is some type of engineer,

00:04:52.600 --> 00:04:57.470
some type of administrator who is managing the actual system.

00:04:57.470 --> 00:05:00.500
So Netflix has some of the best custodians or

00:05:00.500 --> 00:05:03.530
engineers in the world, and so does AWS.

00:05:03.540 --> 00:05:07.630
Those are simply folks that are going to report into the

00:05:07.630 --> 00:05:10.260
controller, report into the processor.

00:05:10.270 --> 00:05:16.030
The data steward will define the rules under which the data can be used.

00:05:16.040 --> 00:05:19.830
So you can think of them as a non‑technical person that sort of

00:05:19.830 --> 00:05:24.890
describes the architectural use of the data with either in the

00:05:24.890 --> 00:05:27.710
processor or the controller's world.

00:05:27.720 --> 00:05:32.690
They are the advocate for the subject in how the subject's information

00:05:32.690 --> 00:05:35.460
should be used according to laws and regulations.

00:05:35.940 --> 00:05:39.460
Many of the modern‑day cloud service providers are

00:05:39.460 --> 00:05:44.240
actually getting certified under ISO 27018.

00:05:44.250 --> 00:05:49.110
We'll bring this up again in later clips, but right now we want to define

00:05:49.110 --> 00:05:52.860
the five principles that they are certifying under.

00:05:52.940 --> 00:05:56.840
So, no matter where the cloud service provider exists, as far as

00:05:56.840 --> 00:05:59.710
their incorporation, under the certification,

00:05:59.720 --> 00:06:02.890
they agree that the cloud service provider must not use the

00:06:02.890 --> 00:06:07.260
personal data they receive for advertising and marketing unless

00:06:07.270 --> 00:06:11.670
expressly instructed to do so by the customer.

00:06:11.680 --> 00:06:16.650
They must have explicit control granted to the data

00:06:16.650 --> 00:06:19.590
subject for how their data will be used.

00:06:19.600 --> 00:06:24.040
The cloud service provider must inform customers where their data resides,

00:06:24.040 --> 00:06:28.750
disclose the use of subcontractors to process PII and make clear

00:06:28.750 --> 00:06:32.090
commitments about how the data is handled. And when it comes to

00:06:32.090 --> 00:06:35.790
communication, in case of breach, the cloud service provider should

00:06:35.790 --> 00:06:40.080
notify customers and keep clear records about the incident and

00:06:40.080 --> 00:06:42.300
their response to it.

00:06:42.310 --> 00:06:47.620
Also, on an annual basis, they should do a successful third‑party audit

00:06:47.630 --> 00:06:51.340
of the cloud service provider's compliance documents, the conformance

00:06:51.350 --> 00:06:54.970
with the standard, and showing it can be relied upon by customers to

00:06:54.970 --> 00:06:57.850
support their own regulatory obligations.

00:06:57.940 --> 00:07:02.070
A suggested practice, also from the American Institute of Certified

00:07:02.070 --> 00:07:05.600
Public Accountants, would be the Privacy Maturity Model.

00:07:05.740 --> 00:07:10.540
So an organization could get a measurement of their success and how they're

00:07:10.540 --> 00:07:14.890
doing when they're applying the GAAP principles that we previously saw, along

00:07:14.890 --> 00:07:19.830
with the Capability Maturity Model. At the ad hoc level, this is where

00:07:19.830 --> 00:07:22.790
procedures and processes are generally informal,

00:07:22.800 --> 00:07:24.460
incomplete, and inconsistent.

00:07:24.640 --> 00:07:27.840
You could even say chaotic. At the repeatable level,

00:07:27.840 --> 00:07:30.720
procedures or processes exist; however,

00:07:30.730 --> 00:07:34.430
they are not fully documented and do not cover all relevant aspects.

00:07:34.440 --> 00:07:37.530
But if I carried out the same thing twice,

00:07:37.540 --> 00:07:41.370
I should expect to get the same results. At defined, this is where

00:07:41.370 --> 00:07:45.890
procedures and processes are fully documented and implemented and cover

00:07:45.900 --> 00:07:50.550
all relevant aspects. And at managed, reviews are conducted to assess

00:07:50.550 --> 00:07:54.910
the effectiveness of the controls that are in place. At optimize, this

00:07:54.910 --> 00:08:00.470
is where you have continuous improvement toward optimization of all the

00:08:00.470 --> 00:08:01.860
given processes.

00:08:02.340 --> 00:08:07.050
Come on over to the summary clip, and we will close out this module.
