Ir al contenido principal

Fourth-Party Risk Management

Fourth-Party Risk Management: The blind spot in Third-Party Risk Management.

As organizations, we’ve made real progress in managing third-party risk, assessing vendors, signing NDAs & DPAs, and running due diligence checks. But there’s a quieter, deeper layer we may overlook: fourth-party risks.

Fourth-Party Risks is the exposure we inherit from our vendors’ vendors; their cloud providers, subcontractors, and invisible dependencies woven into our digital supply chains.

Why fourth-party risk should be a source of concern for us:

  • We have limited visibility into who our vendors rely on.
  • Their security posture impacts us; even when we have no contract with them.
  • We’re accountable for compliance failures tied to someone two degrees removed.
  • An outage or breach downstream can take us down, too.

Some notable examples? The 2021 Kaseya ransomware attack. Thousands of companies downstream were impacted; many of whom didn’t even know they were connected (Kaseya VSA ransomware attack). Also, the 2025 Workday's breach that exposed business contact detail which could be used further to conduct social engineering scams (Workday Hit by Social Engineering Attack, Third-Party Data Exposed).

What are we doing, and what should we be doing, as information security leaders?

  • Asking vendors to share who they rely on (think: SBOMs and transparency).
  • Including fourth-party controls in contracts and SLAs.
  • Using tools to monitor not just vendors, but their ecosystems.
  • Practicing zero trust and preparing for breakdowns beyond our direct control.

Supply chain trust is no longer linear; it's layered, and it’s inherited. If we don't go beyond third-party risk, we will not be able to see the full map.


If Third-Party Risk Management is of interest to you, you may also read: Understanding Third-Party Risk Management (TPRM) in Cybersecurity and SBOM: Software Bill of Materials.

Comentarios

Entradas populares de este blog

Reporte SOC 2 Type 2 en la seguridad de la información

La importancia del reporte SOC 2 Type 2 en la seguridad de la información En un entorno digital donde la confianza y la seguridad son fundamentales, las organizaciones deben demostrar que sus prácticas de protección de datos cumplen con estándares rigurosos. Uno de estos estándares es el SOC 2 (Service Organization Control 2) Type 2 , un informe que evalúa cómo una empresa maneja la seguridad, disponibilidad, integridad del procesamiento, confidencialidad y privacidad de los datos. Este reporte es esencial para empresas que manejan información sensible, ya que proporciona evidencia objetiva sobre su capacidad para proteger la información de sus clientes y socios comerciales. ¿Qué es un reporte SOC 2 Type 2? El SOC 2 Type 2  es un informe de auditoría que evalúa los controles internos de una organización  relacionados con la seguridad de la información. Desarrollado por la AICPA (American Institute of Certified Public Accountants), este informe sigue los Criterios de Servicios...

Managing Cyber Risks: Third-Party and End-User Challenges

🔐 Managing Cyber Risks: Third-Party and End-User Challenges Our organizations face a multitude of cyber threats that can compromise data integrity, disrupt operations, and damage reputations. Among the most challenging risks are those posed by third parties and end users. These risks often operate outside the direct control of the organization, yet their actions or inactions can have profound security implications. Understanding these risks and implementing effective controls is essential for building a resilient cybersecurity posture. 🔗  Third-Party Risks arises when organizations rely on external vendors, suppliers, or service providers who have access to our sensitive systems or data. These partners may not adhere to the same security standards, creating vulnerabilities that can be exploited by malicious actors. High-profile breaches, such as those involving supply chain attacks, have underscored the dangers of insufficient oversight in third-party relationships. The challeng...

Compendio de terminología computacional / Compendium of Computational Terminology

1a versión: 22/julio/2023 Actualizado: 28/mayo/2026 2FA: Two-Factor Authentication 3DEA: Triple Data Encryption Algorithm 3DES: Triple DES 3PS: Third Person Shooter AAM: Agentic Access Management AC: Access Control ACL: Access Control Lists AES: Advanced Encryption Standard AI: Artificial Intelligence AIoT: Artificial Intelligence of Things AitM:  Adversary-in-the-Middle AML: Anti-Money Laundering AOC: Attestation Of Compliance API: Application Programming Interface APT: Advanced Persistent Threat ASCII: American Standard Code for Information Interchange ASM: Attack Surface Management ASPM: Application Security Posture Management ASV: Approved Scanning Vendor for PCI ATM: Automated Teller Machine ATT$CK: Adversarial Tactics, Techniques, and Common Knowledge AV: Antivirus AWS: Amazon Web Service B2B: Business to Business B2C: Business to Consumer BAS: Breach and Attack Simulation BAU: Business As Usual BBP: Bug Bounty Program BCM: Business Continuity Management ...