welcome everyone to lessen 8.2 as we will review how to develop and deploy an internal privacy program.
This is the meat and potatoes of privacy compliance efforts.
I'm sure you've heard about this and work and via emails, and we will discuss all of that. In this lesson.
Cyber Re does have other content that relates to developing an internal privacy program.
This lesson will review some of that content,
but it will tailor it and put it through the lens of CCP, a compliance
this by no means over rules anything you have seen elsewhere.
But we're going to try to tailor some of the internal privacy program aspects to the obligations that the CCP a. Established
then item number two. The way I always learn.
By focusing on riel world examples,
we will go through some common use cases of how to develop an internal privacy program.
Let's jump right into it.
There are several key components that make up an internal privacy program.
If you are responsible for privacy at your organization, or maybe you are one day hoping to be,
I highly recommend pausing this video and making a list of the four items you see on your screen. Now
you need to have all four of these deployed and regularly updated at your organization in order to even have a shot at maintaining privacy compliance,
particularly the substantive obligations that the CCP requires of your business.
We already reviewed the notice and transparency obligations.
privacy impact assessments.
We'll get to that in a moment, but that's basically when you review the internal data handling processes and how that impacts the privacy of the individuals whose information you collect.
We've talked about that as well,
where information sits within your organization,
then an incident response plan.
How to address potential security incidents
and which stakeholders within your organization need to be included as you respond. And, of course,
your window of responding to the actual incident before actually notifying regulators and potential victims.
This is by no means an exhaustive list,
but please keep an eye out on these four requirements.
do not forget. Privacy policies are your public way of representing two individuals. How your organization collects, uses stores and shares personal information.
Think of it in many ways, as an advertisement or part of your corporate marketing or corporate information sharing activities.
It is fundamental to how the business operates.
I strongly recommend as a consequence of that
The laws in the space are always changing.
Just because the CCP is on the books now
does not mean there won't be further amendments and further changes to the way that the law is enforced.
Please be aware of the language You include.
Privacy impact assessment.
This is something we haven't really discussed yet,
Pius. I'll just use the acronym are actually required by the GDP are and other privacy laws,
in fact, and we'll get to this module nine.
If you're collecting sensitive personal information relating to religious or ethnic backgrounds, sexual orientation, trade union membership, Stuff like that,
the GDP are actually requires you to perform a more robust privacy impact assessment called the D. P I. A.
In any event, privacy impact assessments for now under the CCP A are still the best practice. But they are fundamental to actually deploying an internal privacy program that's going to help you secure the way information is being collected.
in order for the left hand to be talking to the right hand
in order for your marketing team to understand what the service lines are doing and vice versa,
you do need to have these privacy impact assessments drafted.
There's nothing mawr as you look at item number two than an internal document that captures the scope of personal information that will be collected
with whom it will be shared and any other potential privacy compliance risks that stem from that.
If there's ever a group of individuals at your company, or if there's a service line that wants to perform some type of function, some type of new activity, we strongly recommend you complete a P I A. Before that happens.
you are memorializing what type of information is going to be completed and collected and shared and stored, and for how long that activity should actually occur.
I'll speak for myself at Reliant.
I spend at least once a week performing and supporting a P a from one of my clients,
the point being there. This is something that needs to be done regularly.
If you don't complete thes,
you will likely have data processing activities that your company that you are unaware of.
If anything, it just makes people honest. And consider the privacy implications of what happens at your place of work.
I strongly recommend that this also be driven by the Privacy Office as well as I previously used the term privacy ambassador.
Make sure that there is someone at the service lines or the other internal offices that support the company, writ large
for how these P A s need to be completed.
This should not be exclusively driven by the privacy office.
If you do that on Lee, it will be a one man show
your likelihood of genuine success
that more or less covers FIA's.
I strongly recommend you research more on them
we will get to more of that in module eight as we progress.
Previously, I mentioned the importance of data mapping
item number two here.
Remember, it is critical to ensuring the successful completion of consumer requests.
That's the next lesson coming up here.
Because you can never allow individuals to either access or delete their information or opt out of the sale of their information if you don't know where the information is to begin with,
This is an internal exercise that you need to absolutely do.
Companies like mine help others perform these data mapping exercises
before we always arrive at a company. They typically have done some of these efforts on their own.
I strongly recommend you take a pen and paper and start identifying which key systems store information
the crown jewels. Item number three here.
That's the sensitive information, the stuff that if it were to be breached or leaked,
it would result in a mission critical failure for your organization.
Try to figure out where that information sits. If you do not know that answer now, I challenge you to find out that answer by the end of the week,
that is really something that you should be aware of.
information does not sit exclusively, either internally or externally.
On the right side of your screen. You'll see some of the SAS vendors and other cloud offerings in the market that are very popular.
Some of them may, for example, zoo want on bottom, right?
That is a software that's frequently used at conferences. They tend to keep information into perpetuity.
You might very well be responsible for the information that's being collected there.
Keep an eye on your external recipients and the external vendors you're using to store information
on the left side of your screen.
I have found that companies are traditionally more aware of information. Sits if it's on the hard drives or anything that's being saved on Prem. But keep an eye on your external vendors.
Incident Response plan.
This serves as an internal playbook for the organization.
How it should identify how you go through the security potential security incidents.
I strongly recommend you get your information security team and privacy team to coordinate ahead of time.
Please keep in mind the general rule in the United States is that you need to notify the state regulators within 30 days of a breach Butt heads up under the GDP are it's 72 hours
in summary item number one,
the documents you need to have developed in order to deploy a robust privacy program.
We talked about the Incidents Response plan.
You need to make sure that your data mapping is established. Your pia's
Please make sure you identify where personal information sits within your business.
I'll see you in the next video less than 8.3.
As we discussed the Consumer Request Channel,