docs: list Watch Rule operators and clarify no regex support#236
Merged
Conversation
Customers were assuming `operator: matches` works as a regex; only `is` / `contains` / `starts with` / `ends with` are supported, the comparison is literal and case-insensitive, and unknown operators are silently dropped on the sensor. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
maximelb
added
the
to-code-review
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
operator: matcheswith a regexvalue. The Exfil docs describe the four Watch Rule fields (event/path/operator/value) but never list which operators actually exist or how the value is matched, so the misuse was easy to land in.sensor/modules/hbs/exfil_engine.c) and the cloud extension (ext-exfil/ext/defaults.goExfilWatchOperators) agree on exactly four operators:is,contains,starts with,ends with. All four do literal, case-insensitive string matching — values are lowercased on both sides before comparison and there is no regex/glob engine anywhere. An unknown operator string maps to 0 server-side, which the sensor'sexfilEngine_newswitch treats as invalid and drops the rule entirely.Watch Rule Operatorssubsection under## Using the Exfil Extensionwith the operator table and a short list of the surprising behaviors (no regex, case-insensitive, string-only fields, unknown operators silently dropped).Test plan
npx --yes markdownlint-cli2 "docs/5-integrations/extensions/limacharlie/exfil.md"— 0 errors🤖 Generated with Claude Code