Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

Fix Tenable One findings where developers work: Tenable and OpenAI Daybreak Defense Factory

Fix Tenable One findings where developers work: Tenable and OpenAI Daybreak Defense Factory

Tenable One customers can now bring selected findings into OpenAI Daybreak Defense Factory through a local Codex Security CLI import with Tenable’s description and solution attached, so developers can fix them where they already work. OpenAI built the connector, one of the select supported integrations in the OpenAI Daybreak Defense Factory.

Key takeaways

  1. Code security findings often lose their context in the handoff. Security teams pass code findings to developers as exports and tickets, and developers end up reinvestigating before they can fix anything.
  2. Daybreak Defense Factory imports selected Tenable One findings. OpenAI built a Tenable One connector into Codex Security, which OpenAI publishes as open source. The connector reads findings through the Inventory Export API in Tenable One or from CSV exports. Each finding arrives in the local Codex Security workbench with its name, severity and state, plus Tenable’s description and solution.
  3. You can try it today with OpenAI’s setup guide. Select a code repository and its findings in Tenable One, export them, then preview and import them into Codex Security against your local checkout of the repository.

Why code findings stall between security and development

A vulnerability often takes an indirect path from the security team that finds it to the developer who fixes it, and important context gets lost along the way. The security team sends the finding over as an export or a ticket, where a development team triages it. When a developer finally picks it up, they still have to work out which code is affected and what a good fix looks like before they can write a line of code to fix it. Most of that context already existed on the security side. It just didn’t make the trip.

We think the fix should start where the developer already works. That’s the idea behind Tenable One’s integration with OpenAI Daybreak Defense Factory: the security team selects findings in Tenable One, and the developer imports them locally with the Codex Security CLI, with Tenable’s description and solution attached when available. Each finding keeps its Tenable finding ID, and its file path and line number when the export includes them.

What Daybreak Defense Factory imports from Tenable One

The findings come from code repository assets in the Tenable One Exposure Management Platform inventory. Each one carries its name, severity, and state, along with Tenable’s description of the issue and Tenable’s solution.

After the import, the Daybreak Defense Factory is designed to help the developer investigate the affected code, decide which findings to prioritize, and propose a fix in the code.

Import Tenable One findings into your Defense Factory in four steps

To try it today, OpenAI’s setup guide walks you through a local command-line import:

  • Select the repository and findings. In the Tenable One inventory, open the Code Repository asset and copy its asset ID and the IDs of the findings you want to import.
  • Export the selection. Export the asset and findings through the Inventory Export API (for tenants on cloud.tenable.com), or start from existing CSV exports. The guide’s export helper checks that each finding belongs to the selected asset. If your export includes file paths and line numbers, the guide shows how to keep them in the import.
  • Preview, then save. Run codex-security publish findings --provider tenable with --dry-run against your local checkout to preview the import. When the preview looks right, run it again without --dry-run and confirm to save the findings.
  • Read the import back. Run codex-security findings imported to list what Codex Security saved, with each Tenable finding ID and the “not assessed” status that Codex Security gives it at the start.

To refresh the findings later, import again with the same --source-key value, a tenant alias, plus the asset ID. According to the guide, Codex Security updates the evidence for findings that changed and keeps identical findings as they are.

Get started

OpenAI’s setup guide has the full commands, the helper scripts, and the CSV formats.

Learn more:

Author

Learn more