Skip to content

Document upstream blocker for imported-engine threat detection - #75386

Closed
pelikhan with Copilot wants to merge 1 commit into
mainfrom
copilot/fix-threat-detection-import
Closed

pelikhan with Copilot wants to merge 1 commit into
mainfrom
copilot/fix-threat-detection-import

Conversation

Copilot AI commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Imported engines are normalized to built-in threat detectors, bypassing their harness and tracing. Opt-in detection requires generic harness support in gh-aw-threat-detection.

  • Changes: None; the issue remains unresolved.
  • Blocker: The latest detector release, v0.5.3, rejects custom engine IDs and exposes no harness-command interface.
  • Prerequisite: Release generic-engine support upstream before adding compiler opt-in, detection-job setup, command configuration, and updated release pins.

Copilot AI linked an issue Nov 6, 2026 that may be closed by this pull request
Copilot AI changed the title [WIP] Fix threat detection issue for imported engine definition Document upstream blocker for imported-engine threat detection Nov 6, 2026
Copilot AI requested a review from pelikhan November 6, 2026 09:04
@pelikhan pelikhan closed this Nov 6, 2026
@github-actions
github-actions Bot deleted the copilot/fix-threat-detection-import branch November 14, 2026 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Threat detection cannot run on an imported engine definition

2 participants