Privacy risk register and vendor management
Most privacy risk is held by someone else: the vendors that store, analyze, support and send the data. The register is where those risks stop being a feeling and become a list with names on it.
The short version
A privacy risk register lists each privacy risk with an owner, a current treatment, a level the organization has agreed to accept and a review date, so that privacy decisions are recorded rather than remembered. The vendor review feeds it, because a processor is the most common source of a privacy risk an organization cannot fix directly.
Privacy vendor review asks what the vendor does with personal data and on what terms; security vendor review asks how well it protects it, and a sound programme runs the two together. The security side is covered in the vendor risk management programme and the broader register practice in the cyber risk register.
Which vendors get which attention
Vendors are tiered so that review effort follows exposure: the more personal data a vendor touches and the more access it has to your systems, the deeper the review. A vendor touching little data with little access gets a light check; one touching a lot of data with little access gets a contract review; one touching little data with a lot of access gets a security review; and one high on both gets the full review.
The grid is a starting rule, adjusted where a vendor’s role or location changes the picture.
What you get
The register
Each risk with an owner, a treatment, an accepted level and a review date. Accepted risks are recorded as accepted, by name, with an expiry.
Processor review
A data processing agreement is the contract that governs a vendor’s handling of personal data on your behalf, and Article 28 of the GDPR requires processing by a processor to be governed by a contract or other legal act. For each in-scope vendor we read the agreement against what the vendor actually does. The text of the GDPR is on EUR-Lex; whether your agreement meets the law that applies to you is for your counsel.
Sub-processors
A sub-processor review asks which other companies the vendor passes your data to, where they are, and whether you are told before the list changes.
Transfers
Vendor locations feed the transfer register.
How the work runs
We start from the vendor list in the data map, tier it, review the highest tiers first and build the register as the findings come in. The handover includes a routine for new vendors, so the register does not go stale. For the questionnaires vendors send back, see vendor risk questionnaires that work.
Who it is for
Organizations whose customers or regulators ask who processes their data, those about to sign a significant new vendor, and groups taking over a vendor estate after an acquisition, where third-party and M&A due diligence is the earlier step.
Under US law
US rules put terms in the vendor contract: California’s regulations list what a service provider contract must say, the FTC Safeguards Rule asks financial institutions to require safeguards by contract, and HIPAA asks for written assurances from business associates. The terms and their sources are tabulated on security and privacy terms in technology contracts.
How the work is bounded
The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.
SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.
Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.
Questions we are asked
What is a privacy risk register?
A privacy risk register lists each privacy risk with an owner, a current treatment, a level the organization has agreed to accept and a review date, so that privacy decisions are recorded rather than remembered.
What is a data processing agreement?
A data processing agreement is the contract that governs a vendor’s handling of personal data on your behalf, and Article 28 of the GDPR requires processing by a processor to be governed by a contract or other legal act.
What is a sub-processor review?
A sub-processor review asks which other companies the vendor passes your data to, where they are, and whether you are told before the list changes.
How does this differ from security vendor review?
Privacy vendor review asks what the vendor does with personal data and on what terms; security vendor review asks how well it protects it, and a sound programme runs the two together.
Send the vendor list
Background reading: vendor privacy reviews that scale. Send the vendors that hold personal data, or the ones you worry about most. The reply says what a review and register would cover. See also all privacy services.