# trellix-enterprise/expertrules architecture

> Architecture diagram of the GitHub repository trellix-enterprise/expertrules, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-05-21). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/trellix-enterprise/expertrules
- Repository: https://github.com/trellix-enterprise/expertrules

## Overview

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`](https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX) (TRELLIX), [`COMMUNITY`](https://github.com/trellix-enterprise/expertrules/tree/main/COMMUNITY) (COMMUNITY), [`TRELLIX/GENERIC_RULES`](https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/GENERIC_RULES) (Generic Rules), [`README.md`](https://github.com/trellix-enterprise/expertrules/blob/main/README.md) (README)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_root["Repository"]
end

subgraph group_trellix["TRELLIX"]
  node_trellix_root["TRELLIX<br/>validated rules"]
  node_generic_rules["Generic Rules<br/>pattern library"]
  node_access_protection["Access Protection<br/>production detections"]
  node_defense_evasion["Defense Evasion<br/>production detections"]
  node_malware_behavior["Malware Behavior<br/>production detections"]
  node_payload_execution["Payload Execution<br/>production detections"]
  node_privilege_escalation["Privilege Escalation<br/>production detections"]
  node_mitre_trellix["MITRE Map<br/>attack catalog"]
end

subgraph group_community["COMMUNITY"]
  node_community_root["COMMUNITY"]
  node_community_mitre["Community MITRE<br/>attack catalog"]
end

subgraph group_governance["Governance"]
  node_readme["README<br/>entry docs<br/>[README.md]"]
  node_contributing["Contributing<br/>process docs<br/>[CONTRIBUTING.md]"]
  node_code_of_conduct["Code of Conduct<br/>policy docs<br/>[CODE_OF_CONDUCT.md]"]
  node_license["License"]
  node_codeowners["CODEOWNERS<br/>ownership policy<br/>[CODEOWNERS.md]"]
  node_epo_console[("ePO Console<br/>deployment target")]
end

node_readme -->|"describes"| node_trellix_root
node_readme -->|"describes"| node_community_root
node_readme -->|"deploys to"| node_epo_console
node_contributing -->|"guides"| node_community_root
node_code_of_conduct -->|"governs"| node_community_root
node_codeowners -->|"reviews"| node_trellix_root
node_trellix_root -->|"contains"| node_access_protection
node_trellix_root -->|"contains"| node_defense_evasion
node_trellix_root -->|"contains"| node_malware_behavior
node_trellix_root -->|"contains"| node_payload_execution
node_trellix_root -->|"contains"| node_privilege_escalation
node_trellix_root -->|"contains"| node_generic_rules
node_trellix_root -->|"contains"| node_mitre_trellix
node_community_root -->|"contains"| node_community_mitre
node_generic_rules -.->|"patterns for"| node_access_protection
node_generic_rules -.->|"patterns for"| node_defense_evasion
node_generic_rules -.->|"patterns for"| node_payload_execution
node_mitre_trellix -->|"translated into"| node_epo_console
node_community_mitre -->|"translated into"| node_epo_console
node_epo_console -->|"consumes"| node_trellix_root
node_epo_console -->|"consumes"| node_community_root

click node_readme "https://github.com/trellix-enterprise/expertrules/blob/main/README.md"
click node_contributing "https://github.com/trellix-enterprise/expertrules/blob/main/CONTRIBUTING.md"
click node_code_of_conduct "https://github.com/trellix-enterprise/expertrules/blob/main/CODE_OF_CONDUCT.md"
click node_license "https://github.com/trellix-enterprise/expertrules/tree/main/LICENSE"
click node_codeowners "https://github.com/trellix-enterprise/expertrules/blob/main/.github/CODEOWNERS.md"
click node_trellix_root "https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX"
click node_community_root "https://github.com/trellix-enterprise/expertrules/tree/main/COMMUNITY"
click node_generic_rules "https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/GENERIC_RULES"
click node_access_protection "https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/ACCESS_PROTECTION"
click node_defense_evasion "https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/DEFENSE_EVASION"
click node_malware_behavior "https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/MALWARE_BEHAVIOR"
click node_payload_execution "https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/PAYLOAD_EXECUTION"
click node_privilege_escalation "https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/PRIVILEGE_ESCALATION"
click node_mitre_trellix "https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/MITRE"
click node_community_mitre "https://github.com/trellix-enterprise/expertrules/tree/main/COMMUNITY/MITRE"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_trellix_root,node_generic_rules,node_access_protection,node_defense_evasion,node_malware_behavior,node_payload_execution,node_privilege_escalation,node_mitre_trellix toneAmber
class node_community_root,node_community_mitre toneMint
class node_readme,node_contributing,node_code_of_conduct,node_license,node_codeowners,node_epo_console toneRose
```

## Components

### TRELLIX

Validated and curated rule content.

- [TRELLIX](https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX): validated rules · Primary curated rule corpus for production use. · `TRELLIX`
- [Generic Rules](https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/GENERIC_RULES): pattern library · Reusable event-pattern templates and examples. · `TRELLIX/GENERIC_RULES`
- [Access Protection](https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/ACCESS_PROTECTION): production detections · Curated mitigations and detections for abuse cases, CVEs, and malware. · `TRELLIX/ACCESS_PROTECTION`
- [Defense Evasion](https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/DEFENSE_EVASION): production detections · Rules targeting evasive technique abuse and stealthy activity. · `TRELLIX/DEFENSE_EVASION`
- [Malware Behavior](https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/MALWARE_BEHAVIOR): production detections · Family- and behavior-specific malware detections. · `TRELLIX/MALWARE_BEHAVIOR`
- [Payload Execution](https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/PAYLOAD_EXECUTION): production detections · Rules for initial execution and payload-launch abuse. · `TRELLIX/PAYLOAD_EXECUTION`
- [Privilege Escalation](https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/PRIVILEGE_ESCALATION): production detections · Rules covering elevation and privilege abuse paths. · `TRELLIX/PRIVILEGE_ESCALATION`
- [MITRE Map](https://github.com/trellix-enterprise/expertrules/tree/main/TRELLIX/MITRE): attack catalog · ATT&CK-aligned organization for curated Trellix rules. · `TRELLIX/MITRE`

### COMMUNITY

Externally contributed and research-driven rules.

- [COMMUNITY](https://github.com/trellix-enterprise/expertrules/tree/main/COMMUNITY): community rules · Community-authored detections and research content. · `COMMUNITY`
- [Community MITRE](https://github.com/trellix-enterprise/expertrules/tree/main/COMMUNITY/MITRE): attack catalog · ATT&CK-aligned community rule organization. · `COMMUNITY/MITRE`

### Governance

Contribution and usage guidance.

- [README](https://github.com/trellix-enterprise/expertrules/blob/main/README.md): entry docs · Repository overview, usage, and deployment guidance. · `README.md`
- [Contributing](https://github.com/trellix-enterprise/expertrules/blob/main/CONTRIBUTING.md): process docs · Contribution workflow and expectations. · `CONTRIBUTING.md`
- [Code of Conduct](https://github.com/trellix-enterprise/expertrules/blob/main/CODE_OF_CONDUCT.md): policy docs · Community behavior and collaboration policy. · `CODE_OF_CONDUCT.md`
- [License](https://github.com/trellix-enterprise/expertrules/tree/main/LICENSE): license · Repository licensing terms. · `LICENSE`
- [CODEOWNERS](https://github.com/trellix-enterprise/expertrules/blob/main/.github/CODEOWNERS.md): ownership policy · Ownership and review boundary for repository content. · `.github/CODEOWNERS.md`
- **ePO Console**: deployment target · Operational import point for Expert Rules under Exploit Prevention.

## Connections

- 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.
