2020 · Israel · J - Information and communication · Data theft and leak publication
Analysed 2026-11-06 by Hermes
Open this case in the tool →Data theft and leak publication
Strategy to Leadership
Evidence coverage: 3/6 stages, weight 17/60
Decisive stage: response (clearest evidence) · Alternative: Expertise to Execution
(1) Strategic expectation at the victim: Portnox is an Israeli network access control and segmentation vendor whose doctrine and customer commitments are built on detecting intrusions and protecting the customer data its products and services touch; customers such as Bezeq, Elbit, El Al and Clalit had documents and credential data held in its environment. (2) What happened in practice: in late December 2020 the Iran-linked Pay2Key operation published customer documents and a customer list with passwords from Portnox's internal servers, claiming about 1 TB taken; Portnox learned of it from the publication itself and said only that it was 'conducting an intensive investigation in order to understand the scope of the event'; months later its own blog still framed the case as 'the attempted Portnox breach', and no substantive follow-up disclosure is on record. The entry vector for this victim is undisclosed and is not load-bearing; recovery was not in play. (3) The gap sits in the doctrinal column at the leadership break (response stage, clearest evidence): the expectation and the relevant knowledge were at strategic level - the company's own public statements, its vendor posture and its duties toward customer data - yet what leadership communicated diverged from the documented reality (published customer credentials and legacy customer security assessments), and the disclosure obligation triggered by the attacker's leak was never closed out publicly; customers whose credential data was published were left to learn from the leak. That is a knowing-doing gap in strategy-to-communication, not merely weak security. A secondary Expertise to Execution pattern (stored credentials and legacy customer data exfiltrated without egress prevention) is visible but only inferable, never documented by a source. RM39 (Strategy to Leadership lens): leadership disclosure behaviour diverged from expectations - disclosure was triggered by the attacker's leak, the company's public account (an open-ended 'intensive investigation', later 'the attempted Portnox breach') underplayed published customer documents and credentials, and no follow-up disclosure is documented (causal role: Constraining). RM16 (Strategy to Leadership lens): commitments on custodial data responsibility were not reflected in decisions - the leaked set included a 2018 customer security assessment that reporting noted as likely outdated and credential lists for customers and employees, data-governance obligations not operationalised (causal role: Amplifying). RM35 (Strategy to Leadership lens): exfiltration and data-loss risk received no effective strategic attention - bulk data left undetected and surfaced only on the attacker's leak site, in a company whose product line is network visibility and control (causal role: Amplifying).
RM16 — Data governance / minimisation gapRM35 — Egress / exfiltration monitoring gapRM39 — Breach notification / disclosure failureThe 1 TB theft volume is the attacker's unverified claim; the published 3 GB (customer documents, customer and employee password lists) is what press reported. Portnox never issued a detailed public confirmation: the classification of the response stage rests on the victim's own minimal statements and the absence of any documented follow-up disclosure, not on a regulator or forensic report. The initial access vector for this victim is undisclosed; the Fox Kitten/Pay2Key group-wide pattern of exploiting known VPN/edge flaws (ClearSky, Check Point, CISA 2024 advisory reporting) was treated as context only and not used for the DV-Type. The alaraby source_url in the case file now serves at newarab.com; the redirect target is cited. Israel's National Cyber Directorate declined to comment (Ynet). EuRepoC date fields (start_date 01.12.2020, attribution_date 01.01.2020) are first-of-month placeholders; media dating is 24-25 December 2020. Description matches the stated victim; no data-quality mismatch. Link check: newarab.com blocks automated access (HTTP 403); the page was opened and read during research. Link check: timesofisrael.com blocks automated access (HTTP 403); the page was opened and read during research.