OpenNashPodcasts

Topic

Datadog

17 facts from 2 episodes, in date order. These are what speakers said on the shows, each linked to the moment it was said. They aren't independently verified.

Undated

Daniel Whitenack cites Datadog and Splunk as products that monitor many microservice endpoints and support root cause analysis.

“a product like a Data Dog or a Splunk or something like that, right? That actually ties into all those endpoints, helps you monitor, do root cause analysis”

Daniel Whitenack · The Myth of Model Wars: Open vs Closed AI in 2026, 0:32:39

Undated

Datadog gave ChatGPT licenses to every non-developer employee who wanted one, according to Emilio Escobar.

“we just got Chatgpt licenses for everyone, and it was like, whoever wants it, gets it.”

Emilio Escobar · The CISO Playbook for AI Agents | Datadog, 0:03:00

Undated

An internal Datadog business-intelligence tool showed data from a warehouse that was thought to be protected by table and row permissions.

“it's data that is in a data warehouse, and we thought we had the right table and row permissioning and all of that.”

Emilio Escobar · The CISO Playbook for AI Agents | Datadog, 0:05:04

Undated

Datadog runs role-based MCP servers, such as one for sales development representatives, to govern the data AI tools can reach.

“we have role-based MCP servers as well, so we have an MCP server for SDRs and things like that”

Emilio Escobar · The CISO Playbook for AI Agents | Datadog, 0:05:40

Undated

In Datadog's sandbox approach, coding agents cannot read credential files such as AWS or NPM publish secrets in a developer's home directory.

“So even if you have a file in your home directory that has your AWS secret, your NPM publish secret or what have you, the agent on the sandbox can't touch it.”

Emilio Escobar · The CISO Playbook for AI Agents | Datadog, 0:06:29

Undated

Datadog already had a command-line tool that issues short-lived access tokens, which it uses to supply credentials to agents.

“we already have a CLI tool that will give you these ephemeral tokens to these things.”

Emilio Escobar · The CISO Playbook for AI Agents | Datadog, 0:06:29

Undated

Datadog's security team built an LLM-based judge that evaluates the intent behind a piece of code.

“my team built out of a necessity. A judge that evaluates using AI LLMs, that evaluates the intent behind a piece of code.”

Emilio Escobar · The CISO Playbook for AI Agents | Datadog, 0:07:44

Undated

Datadog accepts third-party code contributions, such as integrations, to its open source Datadog Agent.

“We take 3rd party code contributions to it, things like integrations and what have you, so code written by other people.”

Emilio Escobar · The CISO Playbook for AI Agents | Datadog, 0:08:13

Undated

Datadog's judge identified malicious code that was injected into packages during software supply-chain hijacks.

“we threw this thing at those packages. And it was able, actually able to identify the malicious piece of code that was injected or introduced during the hijack.”

Emilio Escobar · The CISO Playbook for AI Agents | Datadog, 0:08:40

Undated

Datadog says it finds a notable number of malicious agent skills in public skill marketplaces.

“We actually find quite a bit of malicious skills in all these marketplaces.”

Emilio Escobar · The CISO Playbook for AI Agents | Datadog, 0:00:27

Undated

Datadog runs its judge on every agent skill before the skill is introduced into the company.

“So what we do is now we put this judge in front of every skill that wants to get introduced.”

Emilio Escobar · The CISO Playbook for AI Agents | Datadog, 0:09:19

Undated

Emilio Escobar says Datadog was asked to put its name on a list and wait to get access to restricted frontier AI capabilities.

“we have to put our company name on the list and then we're supposed to wait”

Emilio Escobar · The CISO Playbook for AI Agents | Datadog, 0:18:40

Episodes