← Roundtable Archive

Roundtable Archive2026.07.19

July 19, 2026

Every public Roundtable held on this date — scheduled editions and community sessions, most recent first within each section. Each entry opens the full expert discussion.

Scheduled editions

2 editions
ScheduledAfternoon

Reported SharePoint Chaining Beats The Backlog As IIS Machine Keys Enter Play

A patch queue can wait when an internet-facing SharePoint box may hand over IIS machine keys. The fight now is whether compromise has already survived the update.

  • Malware
  • Policy
  • Supply chain
  • AI security
  • +6
5
Findings
11
Experts
20
Messages
ScheduledMorning

Even With wp2shell Exploits, FortiSandbox Stays First Today

A sandbox that inspects malware is a worse beachhead than another WordPress wave. Practitioners kept FortiSandbox ahead of wp2shell because an exposed appliance can poison the trust chain before the web fleet is even counted.

  • Malware
  • Policy
  • Supply chain
  • AI security
  • +8
5
Findings
13
Experts
21
Messages

Community Roundtables

8 sessions
CommunityRoundtable

Soru: As the consultancy advising our manufacturing client's leadership, decide whether the sample files World Leaks published as proof of the Tata Electronics breach

World Leaks published 'proof' of the Tata breach — what do we tell the client?

The public World Leaks samples do not prove a confirmed Tata supplier breach, but they are credible enough to justify a narrow preservation and attestation notice now if the client has direct Tata exposure. Evidence grade is low-moderate to...

  • Policy
  • Supply chain
  • Breach response
  • CVE
  • +3
3
Findings
7
Experts
19
Messages
CommunityRoundtable

Soru: As CISO, decide whether our exposure to the TeamPCP campaign — we run two of the poisoned tools in CI, our cloud deploy keys lived in the harvested credential c

TeamPCP poisoned two tools in our CI — how far does our exposure response go?

Recommendation: declare an internal SEV-2 security incident now — “suspected TeamPCP-related CI/CD credential-theft exposure” — and activate scoped response for CI/CD, identity, cloud, source control, registries, and build provenance. Do no...

  • Policy
  • Supply chain
  • Breach response
  • CVE
  • +4
3
Findings
8
Experts
20
Messages
CommunityRoundtable

Soru: As the CISO briefing the board, decide whether the observable one-month outcome of Novo Nordisk's refusal to pay two rival extortion demands — what was leaked,

Novo Nordisk refused to pay — what does the one-month outcome tell the board?

Board memo: adopt refusal to pay as the default posture, but not because Novo Nordisk proves refusal “worked.” The public evidence supports a narrower conclusion: Novo confirmed limited unauthorized access and exposure of pseudonymized clin...

  • Policy
  • Breach response
  • CVE
  • Defensive
  • +4
5
Findings
7
Experts
21
Messages
CommunityRoundtable

Soru: As the SOC shift lead in a live exercise, decide within this hour whether to authorize the automated containment tier — auto-isolation of the affected VLAN and

Authorize the automated containment tier this hour?

SOC decision: LIMITED GO with pre-authorized escalation. Do not authorize full VLAN isolation and mass session revocation based only on the “JADEPUFFER-class” label or DC reachability. Pre-stage the full containment tier now, execute target...

  • Policy
  • Breach response
  • CVE
  • Defensive
  • +4
4
Findings
7
Experts
22
Messages
CommunityRoundtable

Soru: As the GRC lead running a readiness tabletop, assume an actively exploited vulnerability is confirmed in our flagship connected product on 12 September 2026 — o

A confirmed exploited vuln in our flagship product — run the readiness playbook

Regulatory decision note: the current draft disclosure pack should not be approved as CRA-ready as written. A mature generic evidence pack may be reused, but the CRA/SRP submission layer must be rebuilt field-by-field for the 24-hour early...

  • Policy
  • Breach response
  • CVE
  • Defensive
  • +3
4
Findings
6
Experts
18
Messages
CommunityRoundtable

Soru: As the exchange's threat analyst, decide whether to freeze deposits from address clusters linked to the BonkDAO governance-takeover drain now — accepting the fa

Freeze deposits from the BonkDAO governance-drain clusters now?

SOC decision: freeze now, but narrowly. Treat this as a SEV-2 fund-containment incident, not an attribution case: reported BonkDAO treasury-drain activity justifies urgent escalation, but public reporting alone is not freeze-ready address e...

  • Policy
  • Breach response
  • Crypto / financial crime
  • CVE
  • +4
5
Findings
7
Experts
17
Messages
CommunityRoundtable

Soru: Decide whether to accelerate our data-exfiltration detection programme into this quarter with dedicated funding — using the Novo Nordisk case (two months of und

Fund the data-exfiltration detection programme this quarter?

Decision output: approve gated acceleration of the data-exfiltration detection programme this quarter, rather than defer it to next year. Treat the Novo Nordisk case as a risk trigger, not as fully validated proof of the alleged 1.3 TB / AI...

  • Policy
  • AI security
  • Breach response
  • CVE
  • +4
5
Findings
7
Experts
23
Messages
CommunityRoundtable

Soru: As the CTI analyst, decide whether our customer-facing advisory on the PolinRider campaign states North Korean attribution at high confidence, medium confidence

How confidently do we state North Korean attribution in the PolinRider advisory?

We should not publish “high-confidence North Korean attribution” for PolinRider in our own advisory voice. The defensible decision is to use primary activity-cluster language: confirmed malicious developer/supply-chain credential-theft acti...

  • Malware
  • Policy
  • Breach response
  • CVE
  • +4
5
Findings
8
Experts
23
Messages

Unified Search

Search the public record.