How trellix-enterprise/expertrules works
1. This repository is a rule library, not an application runtime. Its primary function is to store and distribute Trellix Endpoint Security Expert Rules for the Exploit Prevention policy.
2. The top-level architecture is content-first and folder-based. The main domain split is between TRELLIX/ and COMMUNITY/, which represent two provenance boundaries: Trellix-authored/validated rules versus externally contributed community rules.
3. TRELLIX/ is the operational core. It contains curated rule sets organized by security intent and detection theme, including ACCESS_PROTECTION, DEFENSE_EVASION, MALWARE_BEHAVIOR, PAYLOAD_EXECUTION, PRIVILEGE_ESCALATION, MITRE, and GENERIC_RULES.
4. GENERIC_RULES/ acts as the reusable pattern layer. These files are examples and building blocks for common event types such as file, process, registry, section, TCL, and value-based behaviors. In architecture terms, this is the template/reference subsystem that other higher-level detections are based on.
5. The non-generic TRELLIX/* folders are the production rule layer. These files are concrete detections and mitigations for specific abuse cases, malware families, and CVEs, often mapped to ATT&CK techniques. They are meant to be validated and adapted for deployment.
6. TRELLIX/MITRE/ provides ATT&CK-aligned organization. It groups rules by technique and year, making this repository usable both as a rule catalog and as a detection engineering index tied to adversary behavior.
7. COMMUNITY/ is the contribution and research boundary. It contains community-authored detections and a MITRE/ subfolder, showing that community content is also organized around technique mappings and threat scenarios, but is separated from Trellix-owned rule sets.
8. Each Markdown file is a self-contained documentation artifact. The architecture is distributed across many files rather than centralized in a schema or executable package, so the unit of reuse is the individual rule document.
9. The main data flow is editorial rather than programmatic: rule authors create or refine a rule document, Trellix validates selected rules, and the consumer copies the rule content into the Trellix Endpoint Security ePO Console under Exploit Prevention → Signatures → Add Expert Rule.
10. The repository’s operational integration point is the Trellix ePO Console, which is the actual deployment target. The repository itself does not execute detections; it supplies rule definitions that are manually or operationally imported into policy.
11. The README establishes the governance boundary. It recommends testing rules in non-production environments, indicating that false positives and environment-specific tuning are expected parts of the deployment workflow.
12. Support and collaboration are externalized through GitHub issues and Trellix documentation/training links. That means the repo functions as a managed knowledge base with a contribution workflow, not as a compiled software system.
13. For diagramming, the most accurate model is: contributors/authors produce Markdown rule artifacts; those artifacts are organized by ownership and detection domain; consumers extract rule content into Trellix Endpoint Security policies; and deployed endpoint behavior is controlled by ePO-managed Exploit Prevention policy.
Main entry points: TRELLIX TRELLIX · COMMUNITY COMMUNITY · GENERIC_RULES Generic Rules · README.md README
Components 16
TRELLIX
Validated and curated rule content.
- TRELLIX · Primary curated rule corpus for production use.
TRELLIX - Generic Rules · Reusable event-pattern templates and examples.
TRELLIX/GENERIC_RULES - Access Protection · Curated mitigations and detections for abuse cases, CVEs, and malware.
TRELLIX/ACCESS_PROTECTION - Defense Evasion · Rules targeting evasive technique abuse and stealthy activity.
TRELLIX/DEFENSE_EVASION - Malware Behavior · Family- and behavior-specific malware detections.
TRELLIX/MALWARE_BEHAVIOR - Payload Execution · Rules for initial execution and payload-launch abuse.
TRELLIX/PAYLOAD_EXECUTION - Privilege Escalation · Rules covering elevation and privilege abuse paths.
TRELLIX/PRIVILEGE_ESCALATION - MITRE Map · ATT&CK-aligned organization for curated Trellix rules.
TRELLIX/MITRE
COMMUNITY
Externally contributed and research-driven rules.
- COMMUNITY · Community-authored detections and research content.
COMMUNITY - Community MITRE · ATT&CK-aligned community rule organization.
COMMUNITY/MITRE
Governance
Contribution and usage guidance.
- README · Repository overview, usage, and deployment guidance.
README.md - Contributing · Contribution workflow and expectations.
CONTRIBUTING.md - Code of Conduct · Community behavior and collaboration policy.
CODE_OF_CONDUCT.md - License · Repository licensing terms.
LICENSE - CODEOWNERS · Ownership and review boundary for repository content.
.github/CODEOWNERS.md - ePO Console · Operational import point for Expert Rules under Exploit Prevention.
Connections 21
- README → TRELLIX: describes · README introduces the curated rule corpus and its structure.
- README → COMMUNITY: describes · README differentiates community content from Trellix-owned content.
- README → ePO Console: deploys to · Rules are copied into Trellix Endpoint Security policies for use.
- Contributing → COMMUNITY: guides · Contribution workflow is centered on community submissions.
- Code of Conduct → COMMUNITY: governs · Sets collaboration expectations for contributors.
- CODEOWNERS → TRELLIX: reviews · Ownership boundary for curated repository content.
- TRELLIX → Access Protection: contains · Core curated detections organized by security intent.
- TRELLIX → Defense Evasion: contains · Curated detections for evasion-related behaviors.
- TRELLIX → Malware Behavior: contains · Curated malware family and behavior detections.
- TRELLIX → Payload Execution: contains · Curated execution and payload-launch detections.
- TRELLIX → Privilege Escalation: contains · Curated elevation-of-privilege detections.
- TRELLIX → Generic Rules: contains · Reusable template and example rule layer.
- TRELLIX → MITRE Map: contains · ATT&CK-aligned catalog for curated rules.
- COMMUNITY → Community MITRE: contains · Community rules are also organized by ATT&CK mapping.
- Generic Rules → Access Protection: patterns for · Generic event patterns underpin concrete production rules.
- Generic Rules → Defense Evasion: patterns for · Reusable patterns support higher-level detections.
- Generic Rules → Payload Execution: patterns for · Reusable patterns support payload execution detections.
- MITRE Map → ePO Console: translated into · Technique-mapped rules are imported for enforcement.
- Community MITRE → ePO Console: translated into · Community detections can be adapted for deployment.
- ePO Console → TRELLIX: consumes · Operational users extract rule content from documents.
- ePO Console → COMMUNITY: consumes · Community content can be reviewed and adapted before use.