OpenAI ChatGPT Enterprise Codex Security Scan Configuration Changed
Detects ChatGPT Enterprise Codex security-log events that create or update a repository scan configuration. Changing scan scope, lookback, or notification rules can weaken secrets scanning coverage or redirect findings.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteWindows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
Known benign triggers
- Security engineering teams legitimately onboard repositories and tune scan lookback windows.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| platform.openai.com/docs/compliance | 33 |
| www.elastic.co/docs/reference/integrations/openai_chatgpt_enterprise | 33 |
From the source
- At source
- Open at source
- Upstream identifier
- 6c634405-3880-4354-8fea-925ec7eadd9b
- Tagged by the source as
- Mitre Atlas: AML.T0081Data Source: OpenAI ChatGPT EnterpriseDomain: GenAIPlatform: OpenAIResources: Investigation GuideRule Type: ES|QLService: OpenAI ChatGPT EnterpriseTactic: Defense EvasionUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Oct 17, 2026
- Version
- 1