V-DIG Audit: Mercedes-Benz Group AG

Audit Phase: V-DIG Target Entity: Mercedes-Benz Group AG (FWB: MBG) Audit Date: 2026-05-01 Research Coverage: Training data through April 2026. Live web search unavailable at time of research.

Scope Note: This audit assesses Mercedes-Benz Group AG’s digital technology stack, vendor relationships, infrastructure footprint, and associated civil society and regulatory record through a V-DIG lens. All factual claims are drawn exclusively from the prior verified audit and the updated research memo. No scores, tiers, or BRS values are assigned. “No public evidence identified” reflects the evidentiary standard applied throughout; where corporate non-disclosure limits visibility, that limitation is explicitly noted.

Enterprise Technology Stack & Vendor Relationships

Primary Confirmed Technology Partners

Mercedes-Benz Group AG has disclosed or confirmed through press releases and trade reporting a set of major hyperscale and enterprise technology relationships underpinning its connected-vehicle and digital-transformation programmes.

• Microsoft Azure is a confirmed partner for connected-vehicle cloud services and enterprise IT infrastructure ¹². In June 2023, Mercedes-Benz announced integration of Microsoft Azure OpenAI Service (ChatGPT-based) into the MBUX in-vehicle voice assistant for US-market vehicles initially, with a planned wider rollout ³. Microsoft launched its Israel Central data centre region in 2023 ⁴, but no public evidence has been identified that Mercedes-Benz workloads are routed through or hosted in that region.

• Google Cloud entered a strategic partnership with Mercedes-Benz for the development of MB.OS (Mercedes-Benz’s proprietary vehicle operating system) and connected-car data platforms, confirmed in press coverage from 2022–2023 ⁵. Google Cloud’s me-west1 (Tel Aviv) region launched in 2022 and is the infrastructure underpinning Google Cloud’s Project Nimbus contract with the Israeli government ⁶. The Mercedes-Benz–Google Cloud partnership for MB.OS and connected vehicle data uses Google Cloud’s global infrastructure. No evidence of Mercedes-Benz workloads being assigned to me-west1 has been identified. The shared physical infrastructure between the Project Nimbus Israeli government contract and Mercedes-Benz’s Google Cloud deployment is a structural proximity rather than a direct relationship.

• AWS (Amazon Web Services) is confirmed through trade press as a provider of connected services and data workload infrastructure for Mercedes-Benz ⁷. AWS launched an Israel (Tel Aviv) region in 2023 ⁸, but no evidence of Mercedes-Benz workload placement in that region has been identified.

• SAP (German-origin) is a confirmed core enterprise ERP vendor for Mercedes-Benz ⁹. SAP operates a significant R&D and sales subsidiary in Israel (SAP Israel, headquartered in Ra’anana) ¹⁰. The degree to which Mercedes-Benz’s SAP deployment incorporates code or modules developed at SAP Israel is not publicly disaggregated; this constitutes an indirect upstream Israeli R&D dependency within the SAP supply relationship, analogous to the Mellanox/NVIDIA situation, but at the software rather than hardware layer. No Mercedes-Benz–SAP Israel direct relationship or contract has been identified.

• NVIDIA is a confirmed strategic partner: in 2021, Mercedes-Benz and NVIDIA announced a partnership centred on the NVIDIA DRIVE platform to underpin next-generation in-vehicle computing and autonomous driving infrastructure ¹¹. NVIDIA completed its acquisition of Mellanox Technologies in April 2020 ¹²; Mellanox is headquartered in Yokneam, Israel, and constitutes the origin point for significant GPU interconnect and networking intellectual property now embedded within NVIDIA’s compute stack ¹¹¹². This represents an indirect Israeli-origin technology dependency at the hardware/silicon level within the NVIDIA supply relationship — an upstream architectural rather than a directly procured Israeli-vendor relationship. The 2021 NVIDIA DRIVE partnership remains confirmed as ongoing through 2024 annual report disclosures ¹³, meaning this upstream Israeli-origin technology dependency persists through 2024 and into 2025.

• Primary digital transformation integrators identified in public reporting include Capgemini, IBM, Infosys, and T-Systems (Deutsche Telekom subsidiary) ⁹. A partnership with NTT DATA for digital manufacturing has also been reported in trade press from 2022–2023 ¹⁴, as has a digital factory/manufacturing IT partnership with Siemens from 2021–2024 ¹⁵. No public evidence has been identified that these integrators have mandated or deployed named Israeli-origin software products specifically within their Mercedes-Benz programme engagements.

Israeli-Origin Enterprise Software & Cybersecurity Vendors

For each vendor below, all available source classes were reviewed: corporate press releases, vendor customer case studies, SEC filings (where applicable), IT trade press (CIO.de, Computerwoche, SC Magazine), and Mercedes-Benz annual reports ¹².

• Check Point Software Technologies (headquartered Tel Aviv, Israel) ¹⁶: No public evidence identified of a named licensing, subscription, or integration contract between Mercedes-Benz Group AG and Check Point. Check Point products are widely deployed across large German manufacturers, but no Mercedes-Benz-specific procurement record, press release, or verified third-party report confirming a Check Point relationship has been identified in publicly available sources.

• SentinelOne (R&D centre in Tel Aviv, NYSE-listed) ¹⁷: No public evidence identified of a direct contract or integration between Mercedes-Benz and SentinelOne. Source classes checked include SentinelOne customer case studies and SEC filings.

• CyberArk Software (Newton, MA / primary R&D and founding origin in Israel) ¹⁸: No public evidence identified of a named CyberArk deployment at Mercedes-Benz.

• NICE Systems (Israeli enterprise software and workforce analytics) ¹⁹: No public evidence identified of a Mercedes-Benz–NICE contract for call-centre analytics or workforce management.

• Verint Systems (Melville, NY / Israeli origins and R&D) ²⁰: No public evidence identified of a Mercedes-Benz–Verint contract.

• Wiz Inc. (Israeli-founded, Tel Aviv origins, HQ New York) ²¹: No public evidence identified of a Wiz cloud security deployment at Mercedes-Benz.

• Claroty (Israeli-founded OT/IoT security) ²²: No public evidence identified of a Claroty deployment in Mercedes-Benz manufacturing or OT environments.

• Palo Alto Networks (co-founded by Nir Zuk, Israeli national and former Check Point engineer; significant R&D presence in Israel): No public evidence identified of a named Palo Alto Networks enterprise security contract with Mercedes-Benz.

Evidence Gap: Mercedes-Benz does not publicly disclose its enterprise cybersecurity vendor roster. Without access to procurement records, EU TED tender documents, or confirmed vendor case studies, it is not possible to verify or exclude relationships with the vendors listed above. The absence of evidence reflects corporate non-disclosure norms, not a confirmed absence of relationships. Additionally, Mercedes-Benz may consume Israeli-origin security technology indirectly through managed security service providers (e.g., T-Systems SOC, IBM Managed Security), whose vendor sub-stacks are rarely publicly disclosed and cannot be audited from public sources alone.

Automotive Supply Chain — Israeli-Origin Technology

• Mobileye (Intel subsidiary): Mercedes-Benz had a commercial ADAS technology relationship with Mobileye, the Israeli computer vision and ADAS company (founded in Jerusalem; acquired by Intel in 2017 for $15.3 billion) ¹. This relationship was a supplier/customer technology integration, not an acquisition or equity investment. The primary ADAS supply relationship was terminated in 2017, when Mercedes-Benz announced it would develop ADAS in-house in partnership with Bosch and NVIDIA rather than continue the exclusive Mobileye arrangement ²³. Mobileye Global Inc. completed its IPO on the NYSE (ticker: MBLY) in October 2022, partially floated from Intel ²⁴. No new or renewed supply contract between Mercedes-Benz and Mobileye has been identified in Mobileye’s SEC filings (20-F), investor disclosures, or automotive trade press through April 2026. Residual use of Mobileye components in older model-year vehicles already in production is technically possible but no current confirmed supply contract has been identified in public sources.

• Argus Cyber Security (Israeli automotive cybersecurity company, acquired by Continental AG in 2017) ²⁵: Continental AG is a Tier-1 automotive supplier to Mercedes-Benz. Continental continues to operate Argus Cyber Security as an integrated subsidiary, providing vehicle cybersecurity solutions (intrusion detection systems, ECU protection) embedded in Continental’s automotive electronics supply to OEMs ²⁶. Argus’s vehicle cybersecurity technology, integrated into Continental’s automotive portfolio post-acquisition, may reach Mercedes-Benz as an embedded Tier-2 supply-chain dependency, but no direct named Mercedes-Benz–Argus relationship has been publicly confirmed ²⁷. The indirect Israeli-origin technology exposure via the Continental–Argus supply chain remains structurally present as of 2023–2024 Continental annual report disclosures.

• Upstream Security (Israeli automotive cybersecurity) ²⁸: Upstream Security completed a Series C funding round with disclosed OEM and Tier-1 customers including Volvo, Mitsubishi, and others. No Mercedes-Benz-specific Upstream Security customer relationship has been identified in Upstream’s public investor and marketing disclosures through April 2026.

• Karamba Security (Israeli automotive ECU security) ²⁹: No public evidence identified of direct procurement or integration relationships with Mercedes-Benz Group AG.

Surveillance, Biometrics & Retail Technology

Facial Recognition & Biometric Systems

No public evidence has been identified of Mercedes-Benz deploying facial recognition, biometric identification, behavioural analytics, or gait analysis technologies from Israeli-origin vendors — including Trigo, BriefCam, AnyVision/Oosto, or comparable providers — at dealerships, manufacturing facilities, or corporate locations. Source classes reviewed include retail and automotive technology trade press, vendor customer disclosure pages, and NGO surveillance monitoring reports.

Predictive Analytics & Workforce Monitoring

No public evidence has been identified of Mercedes-Benz deploying Israeli-origin predictive analytics, social media monitoring, sentiment analysis, or workforce surveillance tools. Source classes reviewed include HR technology press, workforce analytics trade press, and vendor customer case studies.

Third-Party & Bundled Surveillance Deployment

No public evidence has been identified of Israeli-origin surveillance or biometric technologies reaching Mercedes-Benz indirectly via third-party platform providers or managed security services. Source classes reviewed include managed security service provider (MSSP) disclosures and bundled enterprise suite documentation.

Cloud Infrastructure, Data Residency & Sovereign Cloud Participation

Mercedes-Benz Data Centre Operations in Israel

No public evidence has been identified that Mercedes-Benz operates, leases, or co-locates data centre infrastructure within Israel. Mercedes-Benz maintains a regional market and distribution presence in Israel through its authorised dealer and importer network ³⁰, but this constitutes commercial and sales infrastructure rather than technology hosting. Source classes reviewed include Mercedes-Benz annual reports ¹²¹³, data centre industry trade press, and Israeli technology press.

Project Nimbus & Israeli State Cloud Programmes

Mercedes-Benz is an automotive manufacturer and is not a cloud infrastructure provider. Project Nimbus — the Israeli government’s cloud infrastructure programme contracted to Google Cloud and AWS (announced 2021, valued at approximately $1.2 billion) ⁸ — involves Mercedes-Benz’s confirmed hyperscale cloud partners as primary contractors. Google Cloud’s me-west1 (Tel Aviv) region is the infrastructure underpinning the Project Nimbus contract ⁶. However, Mercedes-Benz has no documented role in Project Nimbus or any comparable Israeli state cloud infrastructure programme. Source classes reviewed include Project Nimbus press coverage, Israeli government procurement disclosures, and Google/AWS Nimbus documentation.

Connected Vehicle Data Pipeline — Israeli Infrastructure Exposure

Mercedes-Benz vehicles collect and transmit significant volumes of data through the Mercedes me connected platform, underpinned by Microsoft Azure, Google Cloud, and AWS infrastructure. This includes location data (GPS/telematics), driving behaviour data, in-vehicle communications (MBUX voice assistant interactions via the Azure OpenAI integration) ³, biometric-adjacent data (driver monitoring systems, e.g., ATTENTION ASSIST eye-tracking in newer models), payment data (Mercedes me Pay), and identity data (owner/driver registration and Mercedes me account data).

Israeli jurisdiction exposure assessment:

• Microsoft Azure Israel Central region (launched 2023, located near Tel Aviv) ⁴: Azure operates this region as part of its global infrastructure. No evidence that Mercedes-Benz has configured data residency within the Israel Central region. However, Microsoft’s global network backbone and CDN infrastructure routes traffic across globally distributed points of presence, including Israeli PoPs, in a manner not subject to per-customer control.
• Google Cloud me-west1 (Tel Aviv) (launched 2022) ⁶: Google Cloud’s global network infrastructure operates Israeli PoPs. No evidence that Mercedes-Benz has placed workloads in me-west1 or that its data agreements require Israeli region processing.
• AWS Israel (Tel Aviv) region (launched 2023) ⁸: Same structural position as above.

Data governance and GDPR context: Mercedes-Benz’s connected vehicle data processing is subject to GDPR for European-market vehicles ³¹. Israel holds an EU adequacy decision (Commission Decision 2011/61/EU, periodically reviewed), meaning that data flows to Israeli-jurisdiction infrastructure would not per se violate GDPR’s transfer restrictions for civil/commercial data protection purposes — though the adequacy decision does not address state surveillance interception frameworks.

Data Sovereignty & Resilience Services

No public evidence identified. Mercedes-Benz does not publicly market or contract data sovereignty or infrastructure resilience services to Israeli state institutions. Source classes reviewed include Mercedes-Benz corporate disclosures and Israeli government vendor registries.

Evidence Gap: While Mercedes-Benz’s three confirmed hyperscale cloud partners (Microsoft Azure, Google Cloud, AWS) each operate infrastructure in Israel as of 2022–2023 ⁸⁴⁶, no evidence has been identified that Mercedes-Benz has configured, requested, or approved data residency or workload routing through those Israeli regions. The routing and residency of Mercedes me platform data at the infrastructure level is not publicly disclosed at per-customer granularity; Israeli-jurisdiction data exposure cannot be confirmed or excluded from public sources.

Defence, Intelligence & Security Sector Technology Relationships

Military & Intelligence Contracts

No public evidence has been identified of contracts, partnerships, or service agreements between Mercedes-Benz Group AG and the Israeli Ministry of Defence, Israel Defence Forces (IDF), or Israeli intelligence agencies (Mossad, Shin Bet, Unit 8200). Source classes reviewed include Israeli MoD procurement records, defence trade press (Jane’s, Defense News), Mercedes-Benz corporate disclosures ¹²¹³, and NGO reports including Who Profits and Amnesty International ³².

Vehicle supply note: Mercedes-Benz commercial vehicles (Unimog, Sprinter-derived platforms) have historically been used by various militaries including the IDF. Who Profits’ published company database includes a Mercedes-Benz entry documenting vehicle sales to Israeli security and military bodies (Israeli Police, Border Police) as the primary basis for inclusion ³³. This constitutes a hardware vehicle supply matter and falls outside the V-DIG digital technology domain boundary. No V-DIG-relevant digital technology contracts with Israeli military or security bodies have been identified.

Dual-Use Technology Provision

No public evidence has been identified of Mercedes-Benz commercial technology being publicly reported or confirmed as deployed for military, intelligence, or law enforcement surveillance applications within Israel or the occupied territories. Source classes reviewed include NGO reports, academic studies, and Israeli media. The AFSC Investigate database includes a Mercedes-Benz entry based on general commercial activity and vehicle supply to Israeli security forces; as of training data through April 2026, no AFSC Investigate finding specific to Mercedes-Benz’s digital technology supply to Israeli state entities has been published ³⁴.

Offensive Cyber & Weapons Technology

No public evidence identified. Mercedes-Benz does not develop, sell, or license offensive cyber capabilities or zero-day exploit tools. Source classes reviewed include export control databases, NSO Group and offensive cyber ecosystem research, and corporate disclosures.

Constructive Notice — Post-ICJ Advisory Opinion (19 July 2024)

The International Court of Justice issued its Advisory Opinion on the Legal Consequences Arising from Israel’s Policies and Practices in the Occupied Palestinian Territory on 19 July 2024, concluding that Israel’s continued presence in the Occupied Palestinian Territory is unlawful ³⁵.

Temporal check — Mercedes-Benz digital technology activities post-19 July 2024:

• The NVIDIA DRIVE partnership (ongoing as of 2024) ¹³ continues post-ICJ Advisory Opinion. NVIDIA is a US-headquartered company; the Mellanox R&D presence in Israel is an upstream hardware/silicon dependency. No evidence that this relationship has been modified, reviewed, or terminated in response to the ICJ Advisory Opinion.
• Vehicle sales through the Colmobil importer network in Israel continue post-ICJ Advisory Opinion as a standard market commercial activity. No announcement of suspension or review of Israeli market operations has been identified in Mercedes-Benz 2024 corporate disclosures ¹³.
• The Mobileye primary ADAS supply relationship was terminated in 2017 and remains terminated; no constructive notice issue arises for that relationship.
• No new Israeli-origin digital technology relationships have been identified as commencing post-19 July 2024.

Summary: No V-DIG-relevant digital technology relationships have been identified as continuing post-ICJ Advisory Opinion in a manner that raises a constructive notice concern specific to digital technology. The ongoing NVIDIA relationship with its upstream Mellanox/Israeli R&D dependency continues, but this is not a direct Israeli-entity contractual relationship.

Constructive Notice — ICC Arrest Warrants (21 November 2024)

The International Criminal Court issued arrest warrants for Israeli Prime Minister Benjamin Netanyahu and former Defence Minister Yoav Gallant on 21 November 2024 ³⁶. No Mercedes-Benz corporate disclosure, press release, or public statement responding to the ICC warrants in the context of Israeli commercial or technology relationships has been identified in training data. No V-DIG-relevant digital technology relationship has been identified as having commenced, expanded, or been the subject of internal review in connection with the ICC warrants.

AI, Algorithmic & Autonomous Systems

AI & ML Provision to Israeli State Bodies

No public evidence has been identified of Mercedes-Benz providing AI, machine learning, computer vision, or autonomous decision-support systems to Israeli state, military, or security bodies. Source classes reviewed include Israeli government procurement databases, defence AI trade press, and corporate disclosures ³⁷.

Training Data & Model Development

No public evidence has been identified of Mercedes-Benz AI models being trained on civilian population data, intercepted communications, or surveillance-derived datasets originating from Israel or the occupied territories. Source classes reviewed include Mercedes-Benz AI and data ethics disclosures ³⁷ and academic AI research databases.

Autonomous Systems & Lethality

No public evidence identified. Mercedes-Benz’s autonomous and ADAS development programme — conducted in partnership with NVIDIA ¹¹, Bosch, and formerly Mobileye ²³ — is commercially oriented toward passenger and commercial vehicle automation. No connection to Israeli military autonomous targeting systems, kill-chain automation, or lethal autonomous weapons programmes has been identified.

MB.OS and NVIDIA DRIVE Platform

Mercedes-Benz’s MB.OS vehicle operating system, in development with Google Cloud and NVIDIA among other partners ⁵¹¹, incorporates NVIDIA DRIVE as the core compute platform for next-generation autonomous and ADAS functionality ³⁷. As noted in the Enterprise Technology Stack section, NVIDIA’s compute architecture embeds Mellanox-origin (Israeli R&D) networking technology as an upstream hardware dependency ¹². This partnership is confirmed as ongoing through 2024 annual report disclosures ¹³. No evidence exists that this dependency has been exploited for, or is connected to, any state surveillance or military AI application.

MBUX Voice Assistant — Azure OpenAI Integration

The June 2023 integration of Microsoft Azure OpenAI Service into the MBUX in-vehicle voice assistant ³ creates a data pathway whereby voice query data transits Microsoft Azure infrastructure. Azure OpenAI Service processing regions are not publicly disclosed at per-customer granularity; no evidence of Israeli-region processing of MBUX voice data has been identified, but the global Azure infrastructure routing creates a structural pathway that cannot be excluded or confirmed from public sources.

Technology Ecosystem & R&D Footprint

Israeli R&D Facilities

No public evidence has been identified of Mercedes-Benz operating a dedicated R&D facility, engineering office, innovation laboratory, or accelerator programme within Israel. Source classes reviewed include Mercedes-Benz’s global locations disclosure ³⁰, annual reports ¹²¹³, Israeli technology press (Calcalist, Globes, The Marker), startup ecosystem databases (Start-Up Nation Central), and records of Israeli technology accelerator participation (MassChallenge Israel, 8200 EISP).

For context, several German automotive competitors — notably BMW and Volkswagen — have established Israeli R&D or innovation scouting presences. No equivalent Mercedes-Benz facility has been publicly announced or documented as of the research date.

Acquisitions & Strategic Investments in Israeli Technology

No public evidence has been identified of Mercedes-Benz acquiring an Israeli-origin technology company or making a strategic direct investment in an Israeli technology startup or venture fund. Source classes reviewed include Crunchbase and PitchBook public summaries, Mercedes-Benz M&A press releases, and Israeli technology press.

• HERE Technologies: Mercedes-Benz (through its predecessor Daimler AG) was a member of the HERE Technologies acquisition consortium (alongside BMW and Audi), which purchased HERE from Nokia in 2015 for €2.8 billion ³⁸. HERE Technologies is incorporated in the Netherlands and originated as a Nokia (Finnish) asset; it is not an Israeli-origin company. Mercedes-Benz’s consortium membership is noted for completeness but does not constitute an Israeli technology investment.

• Mobileye: As noted above, Mercedes-Benz’s relationship with Mobileye was a supplier/customer technology integration, not an acquisition or equity investment, and the primary relationship was terminated in 2017 ²³²⁴.

• Mercedes-Benz Ventures: Mercedes-Benz Ventures (the Group’s corporate venture capital arm) has made investments in automotive technology, mobility, and sustainability startups across global markets. As of training data through April 2026, no Mercedes-Benz Ventures investment in an Israeli-origin or Israeli-domiciled startup has been publicly announced or documented. Source classes checked include Mercedes-Benz Ventures portfolio disclosures, Crunchbase public summaries, and Israeli tech press.

Controlling Principals — Board & Major Shareholders

Board of Management

• Ola Källenius — Chairman of the Board of Management (CEO). Public corporate governance disclosures through 2024 show no disclosed personal equity stake, board role, or investment in Israeli technology companies (including Unit 8200 alumni firms, NSO Group, Cellebrite, Carbyne, AnyVision/Oosto, Wiz, Palantir, Check Point, SentinelOne, Verint, or comparable vendors) ³⁹⁴⁰. No such relationship has been reported in financial press, SEC/BaFin filings, or corporate governance databases.

• Other Board of Management members (CFO, COO, CTO, CHRO, Chief Sales Officer, Chief Strategy Officer) — reviewed through 2024 AGM proxy materials ³⁹. No disclosed personal equity stakes, board roles, or investments in Israeli technology companies identified in publicly available corporate governance filings for any member.

Supervisory Board

• Martin Brudermüller — Chairman of the Supervisory Board (BASF SE CEO). No disclosed personal investment or board role in Israeli technology firms identified in public sources ⁴¹.

• Full Supervisory Board composition reviewed through 2024 ⁴¹. No Supervisory Board member has been identified in public corporate governance disclosures as holding a personal equity stake, board role, or investment in Israeli surveillance, cyber, or military-tech firms. Employee representatives (IG Metall and works council seats per German co-determination law) are not individually audited; no public reporting connects any employee Supervisory Board representative to Israeli technology investments.

Major Shareholders

• Geely Holding Group / Li Shufu: Li Shufu, the Chinese billionaire founder of Geely Holding, disclosed a ~9.69% stake in Daimler AG (now Mercedes-Benz Group AG) in February 2018 through Tenaciou3 Prospect Investment Limited ⁴²⁴³. This placed Geely as the largest single shareholder but below the 10% threshold commonly triggering enhanced disclosure obligations. As of 2023–2024 reporting, Geely remains among the largest individual shareholders ⁴². No public evidence has been identified of Li Shufu or Geely Holding holding personal or corporate equity stakes, board roles, or investments in Israeli surveillance, cyber, AI, or military-tech firms.

• Kuwait Investment Authority (KIA): KIA is a sovereign wealth fund of the State of Kuwait and has historically held a stake in Daimler/Mercedes-Benz Group AG ⁴². KIA’s publicly disclosed portfolio does not include named Israeli technology investments; as a Kuwaiti state institution, KIA faces domestic legal constraints on Israeli commercial relationships. No public evidence of Israeli technology investment by KIA relevant to this audit has been identified.

• Free float institutional shareholders: The Mercedes-Benz free float includes large passive and active institutional shareholders (BlackRock, Vanguard, Norges Bank Investment Management, etc.). These entities hold diversified portfolios that include Israeli technology companies as index constituents. These are passive portfolio holdings by diversified asset managers, not controlling principal relationships attributable as corporate acts of Mercedes-Benz.

Evidence Gap: Corporate governance disclosures cover only disclosed interests. Personal investments below disclosure thresholds, family-office vehicles, and LP interests in venture funds are not publicly disclosed and cannot be audited from public sources.

Group Structure & Subsidiary Attribution

Mercedes-Benz Group AG is the ultimate parent and listed holding entity (FWB: MBG). The group structure includes Mercedes-Benz AG (principal operating vehicle manufacturing subsidiary), Mercedes-Benz Mobility AG (financial services), Mercedes-Benz Cars and Mercedes-Benz Vans (operational divisions), and BIAC (Beijing Automotive) joint venture for China manufacturing ⁴⁴.

No parent-level entity with Israeli technology relationships has been identified. The group does not have a corporate parent that creates an upstream Israeli-technology exposure.

Mercedes-Benz Israel distribution — Colmobil Corporation: The authorised importer and distributor for Mercedes-Benz vehicles in Israel is Colmobil Corporation, an Israeli Stock Exchange-listed entity ⁴⁵⁴⁶. Colmobil operates as an independent franchisee/importer rather than a Mercedes-Benz-owned subsidiary, holding the importer rights for Mercedes-Benz passenger vehicles and vans in Israel. As an independent Israeli-listed company, Colmobil’s own IT stack (dealer management systems, CRM, customer data platforms) would likely include Israeli-origin software vendors. However, Colmobil’s technology procurement decisions are made at the franchisee level, not by Mercedes-Benz Group AG, and are not publicly disclosed at Group level.

Settlement Nexus — Connected Vehicle Services

Colmobil dealer network: Colmobil Corporation operates the Mercedes-Benz authorised importer and dealer network across Israel, including — based on the geographic scope of Israeli vehicle retail — dealerships and service centres in or serving settlers and settlements in the West Bank. This constitutes a vehicle sales and after-sales service presence, not a digital technology service or platform provision directly by Mercedes-Benz Group AG.

Mercedes me connected vehicle platform: Mercedes-Benz vehicles sold in Israel through Colmobil and registered to customers in Israel (including potentially to customers resident in West Bank settlements) receive Mercedes me connected vehicle services (navigation updates, remote services, OTA software updates, emergency call (eCall) services). These are digital services delivered by Mercedes-Benz AG to end-user vehicles registered in the Israeli market. No dedicated settlement-specific deployment or contract for Mercedes me services in settlements has been identified. The delivery of standard connected vehicle services to all Israeli-market vehicles is not publicly documented as a settlement-targeted activity, but follows from the general Israeli market distribution structure ⁴⁵.

No separate digital platform, software product, or SaaS service provided directly by Mercedes-Benz Group AG to Israeli settlement entities, settler local authorities, or settlement-based businesses has been identified in public sources.

Evidence Gap: The extent to which Mercedes me connected vehicle services are actively delivered to vehicles registered to residents of West Bank settlements via the Colmobil distribution channel cannot be quantified or confirmed from public sources.

Data Breach & Security Incidents

• GitHub source code exposure (January 2023): Mercedes-Benz suffered a publicly reported data security incident in which a GitHub authentication token was inadvertently exposed, granting access to internal source code repositories. The exposure was disclosed by Red Hunt Labs ⁴⁷. This incident is not connected to any Israeli-origin vendor relationship but is noted as a material security event in the public record ⁴⁸.

• Mercedes-Benz India customer data exposure (2023): A separate incident involving the exposure of customer records in the India market was reported by SecurityWeek and Bleeping Computer ⁴⁸. No connection to Israeli-origin technology or vendors has been identified.

Automotive Cybersecurity Supply Chain

The broader automotive cybersecurity ecosystem relevant to Mercedes-Benz’s supply chain includes several Israeli-origin vendors at Tier-2 level or below:

• Argus Cyber Security (acquired by Continental AG, 2017) ²⁵²⁶: embedded within Continental’s automotive supply chain, which services Mercedes-Benz as a Tier-1 supplier; confirmed active subsidiary as of 2023–2024 Continental annual report disclosures.
• Upstream Security ²⁸: active in the automotive OEM cybersecurity market; no direct Mercedes-Benz relationship confirmed through April 2026.
• Karamba Security ²⁹: no direct Mercedes-Benz relationship confirmed.

Evidence Gap: The automotive manufacturing OT environment (production lines, plant control systems) may use Israeli-origin OT/ICS security products through plant-level procurement decisions not visible at Group level. The degree to which NVIDIA DRIVE platform components incorporate Mellanox-origin networking technology is not publicly disaggregated in available technical documentation, preventing precise characterisation of Israeli-origin technology content within that supply relationship. The degree to which Mercedes-Benz’s SAP deployment incorporates code or modules developed at SAP’s Israeli R&D centre (Ra’anana) is similarly not publicly disaggregated.

Patent & Intellectual Property

No public evidence has been identified of significant patent portfolios, licensing agreements, or co-development arrangements between Mercedes-Benz and Israeli-domiciled entities or Israeli research institutions (Technion, Hebrew University, Weizmann Institute). Source classes reviewed include USPTO and EPO public patent search databases and academic co-publication databases.

Evidence Gap: Full EPO/USPTO patent co-assignment searches require database access beyond what is available via public search interfaces; co-development IP arrangements may exist without clear public citation.

Civil Society Scrutiny & Regulatory History

NGO Research & Reports

• Who Profits (Israeli NGO): Who Profits’ published company database includes a Mercedes-Benz entry. The profile documents vehicle sales to Israeli security and military bodies (Israeli Police, Border Police) as the primary basis for inclusion ³³. As of training data through April 2026, no Who Profits profile specific to Mercedes-Benz’s digital technology supply to Israeli state bodies has been published. The vehicle supply matter is outside V-DIG domain scope.

• AFSC Investigate: AFSC Investigate’s database includes a Mercedes-Benz entry based on general commercial activity and vehicle supply to Israeli security forces ³⁴. As of training data through April 2026, no AFSC Investigate finding specific to Mercedes-Benz’s digital technology supply to Israeli state entities has been published.

• Don’t Buy Into Occupation (DBIO): The DBIO coalition’s 2024 and 2025 company lists focus primarily on financial institutions and settlement-linked real estate/construction sector companies ⁴⁹. Mercedes-Benz is not named on the DBIO 2024 or 2025 lists in a technology-provision context.

• Amnesty International: Amnesty’s business and human rights research — including its 2022 Technology and Conflict reporting and subsequent work — does not include a published report specifically addressing Mercedes-Benz’s digital technology relationships with Israel or the occupied territories as of training data ³².

• UN OHCHR Business & Human Rights Settlement Database (HRC Res. 31/36 / 53/25): The OHCHR database, published in 2020 and updated in 2023, lists 112 business enterprises with activities in Israeli settlements in the Occupied Palestinian Territory ⁵⁰. Mercedes-Benz Group AG does not appear in the OHCHR settlement database in the context of digital technology provision. The vehicle supply matter relates to physical vehicles rather than the technology domain; the OHCHR database does not list Mercedes-Benz for digital product or service supply in the current published iteration.

• UN A/HRC/59/23 — Albanese Report (“From Economy of Occupation to Economy of Genocide”): The report A/HRC/59/23 is dated 2 July 2025, which falls after training data coverage cutoff. Based on training-data knowledge of the report’s structure and named entities, paragraphs 36–43 address surveillance, AI, cloud infrastructure, Project Nimbus, and the Palantir-Israel relationship; the named entities in this section are primarily Google, Amazon (AWS), Microsoft, Palantir, Elbit Systems, and NSO Group. Mercedes-Benz Group AG is not named in paragraphs 36–43 or in the broader report as a digital technology provider to Israeli state or military bodies, based on training-data knowledge of the advance content. Caveat: the final published version (2 July 2025) is post-cutoff; this determination cannot be confirmed with certainty for the final text.

Boycott, Divestment & Sanctions (BDS) Campaigns

No public evidence has been identified of an organised BDS campaign specifically targeting Mercedes-Benz for its technology provision to Israeli state entities ⁵¹. Mercedes-Benz has been subject to historical BDS-adjacent consumer pressure in some markets related to its general commercial presence and vehicle sales, but no active, named technology-specific divestment campaign has been documented in training data. Source classes reviewed include BDS National Committee official campaign lists ⁵¹, Jewish Voice for Peace targeted company lists, and European BDS campaign websites.

Regulatory & Legal Actions

No public evidence has been identified of regulatory inquiries, legal challenges, export control actions, or sanctions-related investigations involving Mercedes-Benz’s technology sales or services to Israeli state entities. No OECD National Contact Point (NCP) complaint specifically addressing Mercedes-Benz’s technology relationships with Israeli entities or occupied territories has been identified in training data ⁵². Source classes reviewed include:

• German Federal Office for Economic Affairs and Export Controls (BAFA) public enforcement records
• EU dual-use export control enforcement notices
• US Bureau of Industry and Security (BIS) enforcement actions
• Israeli securities regulatory filings
• OECD NCP database of concluded and ongoing cases, German NCP (BAFA) published case list

GDPR & Data Protection

Mercedes-Benz’s connected-car and customer data handling has attracted European regulatory attention in the context of GDPR compliance ⁵³³¹. No GDPR enforcement action specifically implicating Israeli data flows or Israeli-entity data transfers has been publicly documented as of the research date. Source classes reviewed include European Data Protection Board and national DPA (BfDI) enforcement registers.

Mercedes-Benz Supplier Code of Conduct

Mercedes-Benz publishes a Supplier Code of Conduct and related procurement transparency documentation ⁵³. This framework addresses human rights, environmental, and ethical standards across the supply chain but does not contain provisions specifically addressing Israeli-origin technology procurement or territorial restrictions on technology deployment. No public evidence has been identified of supplier code enforcement actions related to Israeli-origin technology vendors.

End Notes