Risk Sources
are Business Activities
Business activities that involve the collection, use, retention
or disclosure of personal information are the sources of privacy
risk. Based on Nymity’s research, some of the top risk
laden business activities are:
Sales
& Marketing |
Records
Management |
Transfers
of Personal Information |
Workplace
Management |
- Secondary Marketing
- E-Mail Marketing
- Telemarketing
- Customer Service
|
- Safeguarding Data
- Records Retention
- Records Destruction
|
- Cross-border Transfers
- Use of 3rd-Parties
- Lawful Disclosures
- Handling Access Requests
|
- Surveillance and Monitoring
- Recruiting Process
- Background Checks
- Conducting Investigations
|
What is Privacy Risk
Management?
Privacy risk management is organizational actions that control
privacy risk.
Based on Nymity’s research, privacy risk management
is most often a pragmatic approach to reducing privacy threats.
For privacy risk management, most organizations do not use
standard risk management methodologies such as: Enterprise
Risk Management (ERM), or Operational Risk Management (ORM),
or Asset-based Risk Management methodologies, or a Risk Controls
Self-Assessment (RCSA) or any of the other structured approaches
to risk management.
Nymity has found that the three most common approaches to
privacy risk management are:
'Static’ Privacy Risk Management
Organizations rely on past investments in privacy programs
and the privacy officer providing best efforts to stay informed
of developments in privacy, striving to keep business units
up-to-date on new privacy risks.
For more information, visit 'Static'
Privacy Risk Management using PrivaWorks.
'Reactive' Privacy Risk Management
Advice provided by a privacy officer to business units upon
request, typically in the form of phone conversation, email
or a quick meeting. The privacy office quickly researches
the question, possibly obtains outside legal advice and provides
an opinion to the business unit.
For more information, visit 'Reactive'
Privacy Risk Management using PrivaWorks.
'Intuitive’ Privacy Risk
Management
In some organizations, privacy risk management is an intuitive
process in which the privacy officer takes a consultative
role and works with a business unit representative, usually
in support of a project or during an audit process.
The process typically involves a meeting or two to identify
the privacy risks, assesses current risk management measures
and develops new strategies to mitigate the identified risks.
Privacy Officers have some time to prepare for these meetings.
For more information, visit 'Intuitive'
Privacy Risk Management using PrivaWorks.
Nymity’s Risk
Terminology
- Threats are known and measurable results
of an event that would have a negative impact to the company.
For privacy, a threat typically results in loss of revenue
or increased costs.
- Vulnerabilities are business attributes
that increase the likelihood of the threat. For privacy,
vulnerability results from business activities involving
the collection, use, retention and disclosure of personal
information.
- Likelihood is the probability that
a vulnerability will be exploited to the extent that it
has a measurable impact on the organization.
- Impact is the measurement of the results
a threat. Impact can be measured using a numerical scale,
dollar value, or relative comparison (low, medium and
high). For privacy, impact is influenced by corporate
brand, number of customers, potential for loss of business,
etc.
- Controls are actions organizations
take to reduce the likelihood and/or the impact of a threat.
PrivaWorks
Web-based Support that Works
PrivaWorks is a web-based support solution for privacy that
works. The power of PrivaWorks is its unique design for controlling
privacy risks and that it is quick, complete, and easy to
use.
Designed for controlling privacy risks, PrivaWorks features:
- privacy risk reviews for business activities
- a monthly privacy risk advisory report
- a structured library of privacy resource materials
- web-based access that is quick and easy to use and
- excellent customer service that includes free support
and free training.
The PrivaWorks value proposition is its:
1. Proprietary Research Methodology:
Based on two proven premises:
a. Privacy risk and risk management data are
available and with structured research can be identified
and effectively presented; and
b. Risk analysis by business activities is
the most effective structure for the delivery of known
privacy risks, compliance requirements and risk management
considerations.
2. Research Team
Led by a Privacy Lawyer and a former Chief Privacy
Officer, the research team are experts at utilizing
the proprietary PrivaWorks research methodology.
3. Web-Based Delivery Model
Web-based delivery allow subscribers to easily access
risk management materials.
PrivaWorks consists of three major components:
A. Risk Reviews;
B. a monthly Risk
Advisory Report; and
C. Resource Materials.
A. Risk Reviews
Based on Nymity’s research, the most effective structure
for supporting privacy risk is reviews by business activity,
as:
- it is business activities that result in the collection,
use, retention and disclosure of personal information
and which is the source of privacy risk;
- new projects or concerns are typically related to business
activities; and
- misunderstanding the application of privacy laws to
business activities can result in unnecessary restrictions.
To effectively present privacy risk and risk management,
each Risk Review has six sections:
- Business Activity
Definition
- Privacy Risks
- Legislative Requirements
- Privacy Risk Controls
- GAPP Criteria
- Precedent
and Supplementary Resources
A.1
Business Activity Definition
Based on the PrivaWorks proprietary research methodology,
the definition section ensures a clear understanding
of the business activity and establishes the scope of
the Risk Review. This section provides:
- common definitions;
- examples;
- key terminology;
- an understanding of why the business activity
is a source of privacy risk.
Learn more about PrivaWorks. |
|
Example: Secondary Marketing
The Canadian Marketing Association, in its Code of
Ethics, defines marketing as "a set of business practices
designed to plan for and present an organization's products
or services in ways that build effective customer relationships".
Secondary is defined in Webster's Online Dictionary
as "that which is incidental to what is original or
primary".
Marketers commonly define secondary marketing as the
marketing of products and services to current customers
or those with whom they have an existing business relationship
or alternately, as using personal information obtained
from an individual in a goods or services transaction
(or inquiry) to market to that individual goods or services
unrelated to the original transaction.
In PIPEDA
Case Summary #316, the Assistant Federal Commissioner
stated as follows: "It was indicated that while the
marketing itself may not be secondary in a marketer's
technical sense, to the individual customer, there was
no doubt that the organization's marketing purposes
were secondary to those for which he or she initially
provided personal information."
A few examples of secondary marketing are:
- A customer provides personal information to
a bank for the purposes of obtaining a credit
card. After a credit card has been issued, the
bank uses the personal information to solicit
the customer to switch their mortgage to the
bank.
- A customer purchases an appliance and provides
their name and address for delivery purposes.
The customer later receives marketing offers
for other products carried by the retailer.
- A customer subscribes to a magazine. The magazine
shares personal information with an unrelated
third party publisher who sends the customer
marketing offers for books and videos.
|
A.2 Privacy
Risks
Based on the PrivaWorks proprietary research methodology,
an up-to-date list of known vulnerabilities for each
business activity is maintained, providing subscribers:
- a quick and complete understanding of the known
risks; and
- the ability to determine applicability to their
organization.
Learn more about PrivaWorks. |
|
Partial Example: Cross-border Transfers
of Personal Information
Privacy risks associated with transferring data for
commercial purposes across provincial or international
borders include:
- customers unwilling to share data due to fears that
it may be transferred outside of Canada and available
to a foreign government e.g. under the USA Patriot
Act;
- customers concerned that the impact of national
security and national and international anti-terrorism
initiatives erode an individual's right to control
who has access to personal information;
- organizations at a competitive disadvantage by transferring
(or if customers perceive they are transferring) the
data to a foreign jurisdiction;
- complaints that result from notices explaining that
personal information is available to foreign governments;
- failing to provide notice, or adequate notice, of
cross-border transfers of data and advising that data
may be available to foreign governments leading to
complaints;
- customers or employees who want not only notice
of the transfer but to opt-out before their data is
transferred cross-border;
- an employee relying on the "whistle blower" provisions
of private-sector privacy laws to notify a privacy
commissioner that an organization intends to transfer
information abroad and claiming that this is a violation
of privacy law;
- organizations placing unnecessary restrictions on
cross-border data transfers resulting in unnecessary
cost and complicated business processes;
- organizations applying PIPEDA provisions to cross-border
data transfers not related to commercial activity;
- transferring data outside of Canada to an affiliate
or parent company with lower levels of safeguards;
- organizations failing to restrict access by foreign
subsidiaries to data held in Canada;
- data transferred to Canada from a foreign location
is subject to PIPEDA and thus individuals can make
access requests and file complaints;
- the occurrence of data breaches in jurisdictions
where data is transferred and stored;
- organizations possibly facing a commissioner's audit
because of cross-border transfers and the negative
perceptions and reactions to it by customers;
- customers more attentive to what may be happening
to their data when it crosses borders possibly leading
to an increase in access requests relating to data
disclosures.
|
A.3
Legislative Requirements
PrivaWorks provides a structured list and link to
the legislative requirements for the business activities
from the:
- federal private-sector privacy law, the Personal
Information Protection and Electronic Documents
Act (PIPEDA);
- British Columbia’s private-sector privacy
law, the Personal Information Protection Act
(BC PIPA);
- Alberta’s private-sector privacy law, the
Personal Information Protection Act (AB
PIPA);
- Quebec’s private-sector privacy law, the
Act Respecting the Protection of Personal Information
in the Private Sector (QC PPIPS).
For each legislative requirement:
- changes in privacy law are documented in red;
and
- regulations are presented in blue.
Learn more about PrivaWorks. |
|
Example: Use of GPS
PIPEDA
- An organization may collect, use or disclose personal
information only for purposes that a reasonable
person would consider are appropriate in the circumstances
- Section
5(3)
- Organizations must identify the purposes for which
personal information will be collected - Principle
4.2.2
- When personal information collected for one purpose
is to be used for a new purpose, organizations must
identify the new purpose and obtain consent - Principle
4.2.4
- Consent is required for the collection and subsequent
use or disclosure of personal information. In obtaining
consent:
- organizations must make a reasonable effort
to advise the individual of how the personal
information will be used - Principle
4.3.2
- the reasonable expectations of the individual
are relevant - Principle
4.3.5
- organizations may seek implied or express
consent depending on the sensitivity of the
personal information - Principle
4.3.6
- Organizations shall limit the amount and type
of personal information collected to what is necessary
to fulfill the purposes - Principle
4.4.1
- Personal information shall not be used or disclosed
for purposes other than for which it was collected,
unless consent is obtained or as required by law
- Principle
4.5
- Organizations shall be open about their policies
and practices with respect to the management of
personal information - Principle
4.8.1
PIPA BC
- An organization may collect, use or disclose employee
personal information without consent if:
PIPA AB
- An organization may collect, use or disclose personal
employee information without consent if:
PPIPS Quebec
- "Any person collecting personal information to
establish a file on another person or to record
personal information in such a file may collect
only the information necessary for the object of
the file" Section
5 .
- A person who collects personal information about
another person must inform that person:
- of the object of the file;
- of the uses of the information;
- the categories of person who will have access
to the information Section
8.
- Consent to the collection, communication or use
of personal information must be manifest, free and
enlightened and must be give for specific purposes
Section
14.
|
A.4 Privacy
Risk Controls
Based on the PrivaWorks proprietary research methodology,
an up-to-date list of known controls for each business
activity is maintained, providing subscribers a:
- complete understanding of actions an organization
can consider to mitigate privacy risk; and
- structured approach to creating privacy programs.
This section, in conjunction with the Privacy Risks
section, allows subscribers to present the threats and
solutions to business units for specific business problems.
Learn more about PrivaWorks. |
|
Partial Example: Records Destruction
Note: The following are the first thirteen (13)
of a total of sixty three (63).
- Establish a records destruction/disposal policy
and easily administered procedures, approved by management,
for retained personal information taking into account
business needs, legal requirements, access requests,
statutory, regulatory and recommended retention periods.
Note that only useful documents should be retained:
(section revised 12/14/2006)
- the rational for retention will dictate the
proper time period for destruction; and
- the location where operations are carried out
is relevant to determine the laws governing the
retention program.
- Create comprehensive destruction/disposal schedules
for stored records and adhere to a program of routine
destruction: (added 12/14/2006)
- the comprehensive destruction schedule will
take into account records that are obsolete, have
been superseded, are not to be archived, are no
longer required for the purpose for which it was
collected, are determined to be prohibited, or
other specific trigger point, and purge data not
needed for long term business or other relevant
purposes (see Records
Retention -Risk Review); (revised 01/02/2007)
- level of security afforded to the records during
destruction/disposal procedures must be consistent
with the level maintained throughout the records
life which must be consistent with the requirements
of private-sector privacy laws- See Safeguarding
Data -Risk Review. (revised 12/14/2006)
- Establish an annual maintenance of the destruction
schedule and update as appropriate; (added 01/02/2007)
- Adopt trade Association's records destruction standards
and guidelines if any; (added 01/02/2007)
- Assess whether de-identification vs. destruction/disposal
would be appropriate in specific circumstances;
- Implement destruction/disposal authorization procedures
with consideration given to two levels of a certified
internal approval process prior to any destruction/disposal
to ensure that records are no longer required even
though their retention periods have been met;
- Ensure records related to an investigation, audit,
legal process, claim, complaint or dispute are not
destroyed/disposed of: (section revised 12/14/2006)
- flag these records with a symbol, or other distinguishing
mark, which indicates that destruction/disposal
is on hold;
- responsible employees to be made aware of the
significance of any selected markings and of any
internal escalation process in the event clarification
is required.
|
A.5 GAPP Criteria
The Canadian Institute of Chartered Accountants (CICA)
and the American Institute of Certified Public Accountants,
Inc (AICPA) created the Generally Accepted Privacy Principle
(GAPP), which is a listing of criteria used for auditing
and creating privacy management frameworks.
The PrivaWorks Risk Review presents the criteria, as
defined by GAPP, for each business activity. Subscribers
are provided the details of what auditors will be looking
for if this business activity were subject to a GAPP
privacy audit.
Learn more about PrivaWorks. |
|
Example: Training Employees on Privacy
1.0 Management
1.1.1 Communication
to Internal Personnel
Privacy policies and the consequences of noncompliance
with such policies are communicated at least annually
to the entity's internal personnel responsible for collecting,
using, retaining and disclosing personal information.
Changes in privacy policies are communicated to such
personnel shortly after the changes are approved.
1.1.2 Responsibility
and Accountability for Policies
Responsibility and accountability are assigned to a
person or group for documenting, implementing, enforcing,
monitoring and updating the entity's privacy policies.
The names of such persons or group and their responsibilities
are communicated to internal personnel.
1.2.5 Supporting
Resources
Resources are provided by the entity to implement and
support its privacy policies.
1.2.6 Qualifications
of Internal Personnel
The entity establishes qualifications for personnel
responsible for protecting the privacy and security
of personal information and assigns such responsibilities
only to those personnel who meet these qualifications
and have received needed training.
|
A.6
Precedents and Supplementary Resources
Based on the PrivaWorks proprietary research methodology,
an up-to-date list of known precedents and supplementary
resources for the business activity are analyzed and
presented in a structured format. Each analysis includes
an overview of the resource, identifies the relevance
with links to the source document(s).
Precedents and Supplementary Resources include:
- Case law;
- Commissioners’ findings, orders and investigations;
- Legislative amendments;
- Guidelines and standards;
- Best practices identified in corporate initiatives;
- Papers, legal opinion, fact sheets from Nymity
and other qualified sources.
Learn more about PrivaWorks. |
|
Partial Example: Records Destruction
Note: This represents one(1) of a fourteen(14)
Precedents and Supplementary Resources
Vanderbeke v. Royal Bank of Canada
Overview
Further to the "not well founded" finding of the Assistant
Federal Privacy Commissioner that Mr. Vanderbeke's (the
"Applicant") complaint that the Royal Bank ("RBC') did
not properly retain mortgage renewal acknowledgement
letters issued in respect of its mortgages, he filed
a Notice of Application with the Federal Court pursuant
to PIPEDA. The Applicant sought an order that RBC retain
copies of all mortgage renewal acknowledgement letters
("letters"), provide access to the letters by persons
liable to pay RBC's mortgages and disclose to the Applicant
the total content of the letters issued in respect of
a 1996 mortgage. The judge dismissed the Application
and awarded RBC costs of $5,000. (06/02/2006)
Relevance
Judgment highlights:
Records Retention
- the terms of the mortgage, the mortgage number
and the address of the mortgage included in
both the Annual Statements and the letters constitutes
personal information under PIPEDA;
- RBC, however, is not obliged to retain the
letters in light of the fact that all the relevant
information contained in them is retained by
RBC in other forms or data banks and can be
recalled when requested subject to retention
periods;
- RBC confirmed by affidavit that the information
in the letters exists in several databases maintained
by RBC, the entire loan history can be accessed
through an online mortgage system and the Enterprise
Data Warehouse, all Renewal Agreements are scanned
and stored in a software program and the bulk
of information contained in the letters are
repeated in the Renewal Agreements and the online
mortgage system can produce the remainder;
- the Office of the Privacy Commissioner confirmed
the same information to the Applicant in response
to his complaint and found that the PIPEDA retention
requirements had been met by RBC.
www.canlii.org/ca/cas/fct/2006/2006fc651.html
www.privcom.gc.ca/cf-dc/2003/cf-dc_031215_e.asp
Commissioner's Finding- Case Summary #252 |
Risk Review Features
In addition, Risk Reviews support privacy officers with:
- structured lists that can be easily copied and
modified for a specific purpose;
- items in the list are presented as factual considerations
without opinions about the relative importance
allowing subscribers to copy and apply their own
opinions;
- monthly updates of new developments as reported
in the PrivaWorks Risk Advisory Report;
- dated updates so that subscribers can visit
a Risk Review and quickly identify additions and
amendments; and
- a magnifying glass icon
that links specific considerations to relevant
case law or commissioners’ findings, orders
and investigations.
B. Risk Advisory
Report
Based on the PrivaWorks proprietary research
methodology, a monthly report is produced that contains
new developments in privacy presented in a structure
that allows subscribers to quickly understand the impact
each development could have on their organization.
|
|
Example:
|
Developments include the following areas:
- Case law;
- Commissioners’ findings, orders and investigations;
- Guidelines and standards;
- Best practices identified in corporate initiatives;
- Papers, legal opinion, fact sheets from Nymity and other
qualified sources;
- Interviews, presentations, news articles.
The structure allows for the analysis of specific developments
to be copied and delivered to relevant business units in a
timely and simple form.
Nymity uses the following structured methodology to provide
analysis on each resource published in the PrivaWorks Risk
Advisory.
Title |
Title of the Development |
Business Activity |
Business Activity
that involves or is affected by the collection, use,
retention or disclosure of personal information. |
Source |
Source of the privacy
development. |
Overview |
Resource Overview
is the key facts describing the development. |
Relevance |
Relevance focuses
on privacy risk exposure for the Business
Activities identified and answers the following
questions:
- "How has my risk exposure changed?"
- "How can I change my risk exposure?"
|
CURD |
Collection, Use,
Retention and/or Disclosure
|
Category |
Resource Category
|
Industry |
The Industry impacted
by this development. |
Control |
Corporate Control
= Resources specific to Corporate Privacy Risk Management |
PI |
Relevant to Customer Personal
Information, Employee Personal
Information or both (Cus/Emp). |
Date |
Date the development
was published. |
CSA |
The CSA privacy principles
to which this resource pertains. |
GAPP |
The Generally Accepted Privacy Principles
(GAPP) to which this resource pertains.
|
Precedent |
Coming Soon. For Precedent
setting Developments a listing of the specific section
within the law referenced. |
Location |
The URL Location
of the resource. |
| Source
(Partial list)
- PrivaWorks
- Commissioners' offices
- Conferences
- Legislation
- Associations
- Magazines
|
Category
- Breach Reports
- Corporate Initiatives
- Findings/Orders/Investigations
- Guidelines
- Interviews
- Legislation
- Opinions
- Papers
- Presentations
- Studies
- Videos
|
Industry
(Partial list)
- All
- Financial services
- Telcos
- Retail
- Utilities
- Service providers
- Consumer services
- Manufacturing
- Distribution
- Healthcare
- Education
- Insurance
- Media
|
Control
- No
- Policy/Procedure
- Notice (includes contracts)
- Training
- Audits
- Metrics
- Incident Management
- Attestations
|
Learn more about PrivaWorks.
C.
Resource Materials
PrivaWorks Resource Materials provide second-level
support to privacy officers for:
- self-training;
- searches for specific topics, for example ‘SIN
numbers’ or ‘work product’;
- creating presentations; and
- research.
The Resource materials include:
- Papers and Guidelines
- Privacy Studies
- Breach Reports
- Corporate Initiatives
- Privacy Interviews
- Quick Reference Guides to privacy laws and GAPP
- Analysis of Commissioners’ findings, orders
and investigations;
- Litigation Reviews
PrivaWorks Resource Materials feature business activity
analysis.
|
|
Partial Example: Analysis of
Commissioners' findings, orders and investigations
PIPEDA Act Case Summary #96 - Bank Improperly Disclosed
Personal Information; Exception Under Section 7(3)(c)
Rejected
Business Activity
Overview
An individual complained that a bank disclosed his
personal information to the lawyer of the individual's
ex-spouse without his knowledge or consent. The bank
disclosed the personal information when the lawyer of
the complainant's ex-spouse subpoenaed the complainant's
bank for monthly statements of credit cards that the
complainant had personal or joint interest in over a
period of three years. The Commissioner concluded that
the complaint was "well-founded". (04/01/2004)
Relevance
Finding highlights:
- according to civil procedure in Quebec, a lawyer
may issue a subpoena;
- the subpoena presented indicated that the bank
could provide the documents to the lawyer or present
them to the court;
- the bank's policy is to prohibit disclosure of
personal information unless the relevant consent
is obtained or disclosure is made pursuant to a
subpoena or is otherwise permitted by law;
- the bank maintained that it had disclosed the
personal information as permitted by PIPEDA.
The complainant submits:
- the Quebec rules of civil procedure allow lawyers
to issue subpoenas without going to court but they
do not have the authority to compel the production
of records;
- the bank disclosed his personal information without
informing either the court or him;
- the bank was required to inform him of the subpoena
and to seek his consent, if the complainant refused
the bank would have been compelled to appear before
the court so that a judge could rule on the disclosure
request;
- contrary to the banks assertion that in a divorce
proceeding both parties are required to give a complete
account of financial information, the complainant
asserted that this was not required when the ability
to pay and the amount are not at issue.
The bank agreed that for any future subpoenas it
would provide the requested documents to the court,
unless it obtained the individual's consent.
Commissioner's position:
- by responding to the subpoena issued by a lawyer
as provided for in the rules of civil procedure
in Quebec, the bank relied on section 7(3)(c)
to disclose personal information without the
complainant's knowledge or consent;
- the lawyer did not have jurisdiction to compel
the production of records, only a court could have
done so;
- the records in question were not required to comply
with the rules of production as in the circumstances
of the divorce action the information was not relevant;
- the exception to knowledge or consent the bank
relied on for the disclosure of personal information
was inapplicable and the bank had contravened PIPEDA.
www.privcom.gc.ca/cf-dc/2002/cf-dc_021203_2_e.asp
|
'Static' Privacy
Risk Management using PrivaWorks
Based on Nymity’s research, many organizations have
had few or no complaints, access requests or breaches for
either customer or employee privacy. These organizations
often find themselves relying on previously implemented corporate-wide
privacy initiatives, such as privacy policies and privacy
notices for privacy risk management. Privacy officers
provide their best effort to stay informed of developments
in privacy and try to keep business units up-to-date on new
privacy risks.
PrivaWorks Customers
These organizations benefit using PrivaWorks in three ways:
- They receive the monthly PrivaWorks Risk Advisory Report,
which keeps privacy officers informed of privacy risk developments
potentially affecting the organization. The report,
structured by business activity, allows privacy officers
to quickly identify developments and understand the impact.
- The PrivaWorks Risk Advisory Report provides privacy officers
with content to distribute to business units, keeping them
informed of new developments.
- PrivaWorks provide resources to help maintain the effectiveness
of corporate-wide privacy initiatives such as:
- a privacy policy;
- privacy notices;
- training employees on privacy;
- privacy audits; and
- privacy impact assessments.
Nymity's research reveals that corporate-wide privacy initiatives
also carry risks, for example, there are many risks inherent
in implementing a training program. To control these
risk PrivaWorks provides Risk Reviews for corporate-wide privacy
initiatives.
Corporate-Wide
Privacy Initiatives |
Personal Information Handling Policies
(Including Privacy Policy)
|
Internal document(s) that define management's
intent regarding the organization's handling of personal
information. Policies are supported by specific
procedures that define employees involvement in handling
personal information, for example, access requests,
customer complaints, data breaches, new marketing programs,
incident reporting, etc.
|
| Privacy Notice |
Information made available to a customer that outlines
organization's information handling policies.
This may be a privacy statement on the organizations
website, a brochure, a call script, an entry form and
provisions in customer contracts. Privacy notice
is the mechanism for obtaining informed consent.
|
Training Employees on Privacy
|
Educating employees about the organization's policies
and procedures related to handling of personal information.
Effective employee training reduces the likelihood of
privacy breaches and complaints.
|
| Privacy Audit |
Structured assessments of organization's privacy
practices to ensure adherence to the organization's
policies and procedures. Privacy audits have multiple
benefits including training and establishing accountability.
|
Other corporate privacy initiatives include:
- Attestations;
- Incident Management Programs;
- Privacy Metrics Tracking and Reporting;
- Employee Codes of Conduct; and
- Corporate Communications.
PrivaWorks provides Web-based support for 'Static'
Privacy Risk Management that is quick, complete and easy to
use.
'Reactive’
Privacy Risk Management using PrivaWorks
Based on Nymity’s research, ‘Reactive’
advice to business units from the privacy officer is a common
form of privacy risk management. In this role, the privacy
officer provides advice to the business units on a reactive
basis.
The questions from business units to privacy officers may
take the form of:
- “Can we do …..?”; or
- “What are the privacy requirements for this …..?”;
or
- “How do we accomplish ……?”
;
- “We can’t do ……. because of
privacy, right?”
When a privacy officer is faced with these questions, he/she
must provide advice that would ensure compliance, reduce the
likelihood of a breach or complaint, while not putting unnecessary
restrictions on the business activity and do so in a short
period of time. In some cases, privacy officers will
seek an outside legal opinion.
PrivaWorks Customers
PrivaWorks customers benefit from PrivaWorks Risk Reviews
and Resource Materials that provide on-demand support, arming
them with the specific information in a structured format,
that facilitates a quick and complete response.
PrivaWorks provides Web-based support for 'Reactive'
Privacy Risk Management that is quick, complete and easy to
use.
'Intuitive’
Privacy Risk Management using PrivaWorks
Based on Nymity’s research, few organizations empirically
calculate privacy risk, but typically use an ‘Intuitive’
process to understand the likelihood of a privacy threat,
the vulnerabilities within the business activities and to
assess current controls.
The ‘Intuitive’ process allows for discussions
and decisions about what new controls would be appropriate
to further reduce the likelihood of a threat. This ‘Intuitive’
privacy risk management process is typically used in support
of a project or during an audit.
‘Intuitive’ privacy risk management is quick
when compared to a more empirical or academic approach to
risk management and is often accomplished in a single meeting
between the business unit and the privacy officer.
PrivaWorks Customers
Intuitive privacy risk management includes the following
steps:
‘Intuitive’
Privacy Risk Management |
Using
PrivaWorks Risk Reviews |
- Identify the vulnerabilities within the business
activity.
|
For each
business activity, Risk Reviews list known vulnerabilities
in the Privacy Risks section. |
- Identify requirements from privacy laws.
|
For each
business activity, Risk Reviews identify requirements
from privacy laws in the Legislative Requirements
section. |
- Identify/review current controls for effectiveness
|
For each
business activity, Risk Reviews identify known controls
in the Privacy Risk Controls and GAPP Criteria sections.
|
- Search existing precedents to identify any ‘red-flags’
or specific relevant risks.
|
For each
business activity, Risk Reviews identify known Precedents
and Supplementary Resources. |
- Assess the likelihood and impact of a threat
for each vulnerability.
|
For each
business activity, Risk Reviews Precedents and Relevant
Resources section identifies all known events of this
nature. |
- Calculate privacy risk and priorities to identify
areas for new controls.
Identify and implement new controls.
|
For each
business activity, PrivaWorks identifies known controls
in the Privacy Risk Controls and GAPP Criteria sections.
PrivaWorks Precedents and Supplementary
Resources identify best-practices to ensure unnecessary
restrictions are not placed on the business. |
PrivaWorks provides Web-based support for 'Intuitive'
Privacy Risk Management that is quick, complete and easy to
use.
|