Third party

Third-party risk and the LGPD: how to protect your data

· 12 min read ·

When a vendor leaks personal data you handed over, the bill usually arrives in your name. Under the LGPD (Lei Geral de Proteção de Dados, Brazil's General Data Protection Law), the controller makes the decisions about processing, and the processor handles the data on the controller's behalf, following its instructions. Notifying an incident to the ANPD (Agência Nacional de Proteção de Dados, Brazil's data protection authority) and to data subjects is also the controller's duty. That is why the vendor's contract, assessment and monitoring have to work together. This article shows how the law splits that responsibility and what to do to reduce the exposure in practice.

Reliance on vendors has grown, and the attack surface with it. In the 2026 edition of its Data Breach Investigations Report, Verizon found that breaches involving a third party reached 48% of the total, up 60% (Verizon, 2026 Data Breach Investigations Report). In the 2025 edition, that share had already doubled to 30% (Verizon, 2025 Data Breach Investigations Report). For whoever is accountable for data protection, that means nearly half of the breaches analysed had a third party somewhere in the story.

The full lifecycle of a vendor risk programme, from inventory to offboarding, is covered in the guide to vendor risk management. The focus here is narrower: what the LGPD and the ANPD say about the relationship between the organisation that hires and the one that processes the data, and how that shapes the contract and the monitoring.

Why LGPD third-party risk starts with your vendors

Every vendor that receives personal data is an extension of your risk environment. The problem is visibility: you know where your own data lives, but you rarely know where the copy the vendor kept has ended up.

Sub-processors make that opacity worse. The LGPD does not define the role, but the ANPD's guidance on processing agents describes a sub-processor as the company hired by the processor to help it process data on the controller's behalf, and says that, depending on the case, it may also answer to the ANPD (ANPD, Guidance on the Definitions of Processing Agents and the Data Protection Officer, version 2.0, in Portuguese). In practice, a payroll provider uses a cloud provider, which uses a backup service, and your employee's data travels along a chain you have never seen. When one link fails, the incident lands back on your governance.

Three factors make a vendor a sensitive point for privacy:

  • Access to databases holding personal or sensitive data, often with broad privileges.
  • Security controls you neither manage nor inspect directly.
  • Contracts that describe the service but say little about how data is processed.

Network of digital connections representing the vendor chain and the flow of personal data

What the LGPD says about controllers and processors

The LGPD (Law No. 13,709/2018) defines the controller as the party that makes decisions about processing and the processor as the party that processes data on the controller's behalf (art. 5, VI and VII). From there, the law allocates the duties:

  • Instructions and verification. The processor handles data according to the controller's instructions, and the controller checks compliance with its own instructions and with the applicable rules (art. 39). Overseeing the vendor is part of the controller's role.
  • Records. Both controller and processor must keep a record of the processing operations they carry out (art. 37).
  • Security. Both must adopt technical and administrative security measures (art. 46), and anyone involved in any phase of processing remains bound to guarantee security even after it ends (art. 47).
  • Data subject rights. When a data subject asks for correction, deletion, anonymisation or blocking, the controller must immediately inform the agents it shared the data with, so they do the same (art. 18, § 6).
  • Incidents. Notifying the ANPD and the data subject of an incident that may cause relevant risk or harm is the controller's obligation (art. 48).

Liability for damage follows the same logic. A controller or processor that causes damage in breach of the law must compensate for it (art. 42). The processor is jointly and severally liable when it breaches the legislation or fails to follow the controller's lawful instructions, in which case it is treated as a controller (art. 42, § 1, I). To escape liability, an agent has to prove one of the grounds in art. 43, for example that there was no breach of the law or that the damage was caused exclusively by the data subject or a third party. The ANPD's guidance sums it up: as a rule, liability sits with the controller, and the processor's joint liability is the exception.

What weighs most day to day is the incident clock. Under Resolution CD/ANPD No. 15/2024, the controller must notify the ANPD and the data subjects within three business days, counted from when the controller learns that the incident affected personal data (arts. 6 and 9). The resolution does not create a separate duty for the processor; the notification form only asks for the processor's identity, where there is one (art. 6, § 2, X). If the vendor is slow to report, little time is left to assess the risk and notify. The details of the notification are in the map of ANPD regulations.

Contract clauses and privacy assessments

The contract is the first third-party risk control you can require before any data changes hands. The ANPD's guidance acknowledges that the LGPD does not expressly require a contract between controller and processor, but treats one as good practice, because the clauses limit what the processor can do, set parameters for allocating responsibility and reduce uncertainty. Among the points that can be defined, the guidance lists the subject matter, duration, nature and purpose of processing, the types of personal data, and the rights, obligations and responsibilities related to the LGPD.

Clauses a data processing agreement usually contains:

  1. The purpose, data types and explicit limits of the authorised processing, with the obligation to follow the controller's instructions.
  2. Minimum security measures, such as access control and encryption, and upkeep of the record of processing operations.
  3. Rules on subcontracting. The ANPD's guidance recommends that the processor obtain formal authorisation, general or specific, from the controller before hiring a sub-processor, and says it can be included in the contract itself.
  4. Notice of incidents to the controller within a short, defined period, compatible with the three business days the controller has to notify the ANPD, along with the information needed for that notification.
  5. Support in handling data subject requests, retention, return or deletion of data when the contract ends, and a security duty that continues after termination.
  6. The right to audit and to request evidence of compliance.

Two cases need extra attention. If the vendor processes data outside Brazil, as many cloud and SaaS services do, the international transfer needs one of the mechanisms in art. 33 of the LGPD; organisations relying on contractual clauses must adopt the ANPD's standard clauses without changes, as the map of ANPD regulations explains. And in institutions authorised by the BACEN (Banco Central do Brasil, Brazil's central bank), contracts for data processing, storage and cloud services must also follow CMN (Conselho Monetário Nacional, Brazil's National Monetary Council) Resolution No. 4,893/2021, the subject of the guide to third-party risk and CMN Resolution 4,893.

A privacy assessment complements the contract. Before hiring, map which data the vendor will access, in what volume and with what sensitivity, and what a leak would mean in that context. Vendors that touch sensitive data or large volumes deserve deeper analysis and concrete evidence of controls, not just a self-assessment questionnaire. That analysis also feeds the data protection impact report (RIPD), which the ANPD may require from the controller (art. 38). The LGPD compliance checklist shows where the vendor inventory fits into the rest of the programme.

Professional reviewing compliance documents and data protection contracts

How do you monitor vendor compliance continuously?

Continuous monitoring means treating a vendor's compliance as a state that changes, not as an annual stamp. A questionnaire answered at onboarding tells you how the vendor looked on that day. It says nothing about a change in security leadership, a new cloud integration or the incident nobody reported six months later.

In practice, continuous monitoring combines four elements:

  • Reassessments at a frequency proportionate to the vendor's risk, not a single calendar for everyone. A common practice is to formally reassess critical vendors at least once a year.
  • Triggers that prompt a new review whenever something relevant changes: a merger, a new sub-processor, a change in the country where the data is held, a public incident.
  • Objective indicators tracked over time, not one-off form answers.
  • Evidence collected on a recurring basis, with a record of who reviewed it and when.

Good warning signals are what separate monitoring from bureaucracy. It pays to design key risk indicators that anticipate problems, such as contracts without a data protection clause, overdue assessments or unauthorised sub-processors, so that a vendor's decline shows up on the dashboard before it shows up in the headlines.

How do you bring third-party risk and privacy into GRC?

Bringing third-party risk into GRC connects contracts, controls and evidence for every vendor in a single view, instead of spreadsheets kept separately by each department. Legal holds the contract, security holds the technical assessment, procurement holds the vendor record, and nobody sees the vendor as a whole. That fragmentation is what makes an audit drag on and an incident catch the company off guard.

An integrated approach starts from a single inventory of vendors and controls, reused across the requirements of the LGPD, ISO/IEC 27001 and other frameworks. That way, the same evidence that proves a vendor's access control can serve several obligations. The Third-Party Risk module in Eagle, by Futture, was designed for this cycle: vendor records, assessments and criticality classification, risks, contracts and periodic reviews, risk signals, monitoring and action plans, linking supply chain risk to enterprise risk. AI helps classify and prioritise, and the user reviews, approves or adjusts each relevant result.

The practical goal is to have the answer ready when the ANPD, an auditor or the board asks how the company oversees a vendor: the contract, the latest assessment, the attached evidence and the review date. Data protection stops being a collection of scattered documents and becomes a process you can demonstrate.

Conclusion

Start where the exposure is greatest: list today the vendors that access sensitive personal data or large volumes of it and check, for each one, whether there is a contract with data protection clauses, an incident notice period compatible with the ANPD's three business days and a recent privacy assessment. Those that fail on these points are your review priority. From that list, set reassessment triggers and bring the oversight into your GRC process, so that third-party risk and privacy share the same control inventory and the same evidence.

Sources consulted on 15/11/2026: the LGPD (Law No. 13,709/2018); Resolution CD/ANPD No. 15/2024; the ANPD's Guidance on the Definitions of Processing Agents and the Data Protection Officer (version 2.0, April 2022); Verizon news releases on the 2025 and 2026 DBIR. This article is for information only and does not constitute legal advice.

Further reading: Vendor Risk Management: Best Practices; ANPD regulations: a map of what your company must comply with; LGPD Compliance: A Practical Checklist for Companies.

Frequently asked questions

What is third-party risk in the context of the LGPD?

It is the exposure to leaks, sanctions and reputational damage that comes from sharing personal data with vendors and processors. As a rule, responsibility for the processing lies with the controller, and it is the controller that must notify the ANPD and data subjects of an incident that may cause relevant risk or harm, even when the failure happened at the vendor.

Does the controller stop being responsible when it hires a processor?

No. The processor handles data according to the controller's instructions, and the controller checks that those instructions and the rules are being followed (art. 39 of the LGPD). The processor is jointly and severally liable when it breaches the law or the controller's lawful instructions (art. 42, § 1, I), but that does not remove the controller's liability, which it escapes only on the grounds listed in art. 43. The contract and monitoring are how that oversight is recorded.

Which data protection clauses should a vendor contract include?

The LGPD does not prescribe a template, but the ANPD treats a contract as good practice. It usually defines the purpose, data types and limits of processing, security measures, authorisation for sub-processors, a short deadline for reporting incidents to the controller, support for data subject requests, retention and deletion at the end of the contract, and the right to audit.

How often should vendor compliance be assessed?

The initial assessment happens before hiring, and oversight should be continuous. A common practice is to formally reassess critical vendors, such as those processing sensitive data or large volumes, at least once a year, and also whenever something relevant changes, such as a new sub-processor or an incident.

Official references

About the author

Founder, Futture.ai | CISSP

Cybersecurity, governance and risk management specialist with over 25 years of industry experience. CISSP-certified, founder of Network Secure and Futture.ai.

Read next

← Back to the blog