Panther AI boosts visibility and detection. See how in our Founder-Led Demo →

close

Panther AI boosts visibility and detection. See how in our Founder-Led Demo →

close

Panther AI boosts visibility and detection. See how in our Founder-Led Demo →

close

LATEST RELEASE

v1.117

Dec 5, 2025

Panther enables you to enrich incoming logs with data already in your data lake by creating custom enrichment sources with the output of a Scheduled Search.

New and Noteworthy
Now Generally Available
Enhancements
Schema Changes
Panther Developer Workflows
Bug Fixes
  • Trying to upload data to a deleted enrichment will now return an error.

  • The Enrichments page no longer shows an error if the “Manual Sync” import method is selected as a filter.

  • Creating Enrichment log types and selectors auto-mapping is now only based on the indicators present in the primary key.

  • Resolved an issue that would result in detections not having access to enrichment data.

  • Enrichment schema updates now take effect immediately without requiring switching to a different schema and back.

  • Parquet files from Teleport sources can now be ingested.

  • Resolved an issue where queries would run on a schedule even after they had been deleted.

Deprecations
  • Support for historical tables in the panther_lookups.public database stopped in this release. 

    • Tables like <lookupname>_XXX, <lookupname>_history_XXX, and <lookupname>_history stopped being populated and only the table containing the most up-to-date lookup data in <lookupname> will now be populated. 

    • If you were referencing these historical tables to know how a log event was enriched while being processed by detections, note that signals contain enrichment data.

  • Panther removed UDM (or Core Field) functionality in this release.

LATEST RELEASE

v1.117

Dec 5, 2025

Panther enables you to enrich incoming logs with data already in your data lake by creating custom enrichment sources with the output of a Scheduled Search.

New and Noteworthy
Now Generally Available
Enhancements
Schema Changes
Panther Developer Workflows
Bug Fixes
  • Trying to upload data to a deleted enrichment will now return an error.

  • The Enrichments page no longer shows an error if the “Manual Sync” import method is selected as a filter.

  • Creating Enrichment log types and selectors auto-mapping is now only based on the indicators present in the primary key.

  • Resolved an issue that would result in detections not having access to enrichment data.

  • Enrichment schema updates now take effect immediately without requiring switching to a different schema and back.

  • Parquet files from Teleport sources can now be ingested.

  • Resolved an issue where queries would run on a schedule even after they had been deleted.

Deprecations
  • Support for historical tables in the panther_lookups.public database stopped in this release. 

    • Tables like <lookupname>_XXX, <lookupname>_history_XXX, and <lookupname>_history stopped being populated and only the table containing the most up-to-date lookup data in <lookupname> will now be populated. 

    • If you were referencing these historical tables to know how a log event was enriched while being processed by detections, note that signals contain enrichment data.

  • Panther removed UDM (or Core Field) functionality in this release.

Ready for less noise
and more control?

See Panther in action. Book a demo today.

Get product updates, webinars, and news

By submitting this form, you acknowledge and agree that Panther will process your personal information in accordance with the Privacy Policy.

Product
Resources
Support
Company