Use this skill when the user needs help deploying, managing, or understanding Sigma rules, Soteria rules, SOC Prime rules, Community rules, or any other managed rulesets in LimaCharlie.
This skill helps you deploy and manage Sigma rules and other managed rulesets in LimaCharlie. Use this when users need help with:
Managed rulesets are professionally maintained, pre-built detection rules that can be deployed with one click to a LimaCharlie organization. They provide:
LimaCharlie supports multiple managed ruleset sources:
What: Open-source detection rules automatically converted to LimaCharlie format
Best for: Free, customizable coverage with community-maintained rules
Quick Deploy:
# Convert a single Sigma rule
curl -X POST https://sigma.limacharlie.io/convert/rule \
-H 'content-type: application/x-www-form-urlencoded' \
--data-urlencode "rule@my-sigma-rule.yaml"
# Convert multiple rules from GitHub directory
curl -X POST https://sigma.limacharlie.io/convert/repo \
-d "repo=https://github.com/SigmaHQ/sigma/blob/master/rules/windows/process_creation"
Common targets: edr (default for endpoint detection), artifact (for log analysis)
See REFERENCE.md for complete API documentation. See EXAMPLES.md for deployment examples.
What: Professional managed EDR detection ruleset with auto-updates
Best for: Comprehensive EDR coverage across Windows, Linux, macOS
Quick Deploy:
soteria-rules-edrRequired events: NEW_PROCESS, DNS_REQUEST, NETWORK_CONNECTIONS, FILE_CREATE, REGISTRY_WRITE, and more
MITRE Coverage: https://mitre-attack.github.io/attack-navigator/#layerURL=https%3A%2F%2Fstorage.googleapis.com%2Fsoteria-detector-mapping%2F%2Fall.json
See REFERENCE.md for complete event list and configuration. See EXAMPLES.md for deployment scenarios.
What: Managed AWS threat detection using CloudTrail and GuardDuty
Best for: AWS cloud security monitoring
Quick Deploy:
tor lookup (free)soteria-rules-awsPrerequisites: Active AWS CloudTrail and GuardDuty integrations
See REFERENCE.md for adapter configuration. See EXAMPLES.md for AWS deployment scenarios.
What: Managed Microsoft 365 threat detection
Best for: M365/Office 365 security monitoring
Quick Deploy:
tor lookup (free)soteria-rules-o365Coverage: Teams, Word, Excel, PowerPoint, Outlook, OneDrive
See REFERENCE.md for adapter configuration. See EXAMPLES.md for M365 scenarios.
What: Enterprise content platform with continuous updates
Best for: Organizations with SOC Prime subscriptions wanting automated content management
Quick Deploy:
socprime add-on in LimaCharlieSync: Rules sync automatically every 3 hours
Attribution: All detections show socprime as author
See REFERENCE.md for detailed setup. See EXAMPLES.md for integration scenarios.
What: AI-powered conversion of third-party rules (Anvilogic, Sigma, Panther, Okta)
Best for: Quick deployment of specific detections from various sources
Quick Deploy:
Sources: Anvilogic, Sigma, Panther, Okta rules
See REFERENCE.md for source details. See EXAMPLES.md for conversion examples.
| Ruleset | Cost | Updates | Visibility | Best For |
|---|---|---|---|---|
| Sigma | Free | Manual | Full | Custom rules, open-source coverage |
| Soteria EDR | Paid | Auto | None | Comprehensive EDR coverage |
| Soteria AWS | Paid | Auto | None | AWS security monitoring |
| Soteria M365 | Paid | Auto | None | M365/O365 security |
| SOC Prime | Paid* | Auto (3h) | Full | Enterprise content management |
| Community | Free | Manual | Full | Specific detections, quick starts |
*Requires SOC Prime subscription (separate from LimaCharlie)
For detailed comparison and selection guidance, see REFERENCE.md.
False Positive (FP) rules filter detections globally to reduce alert fatigue.
From a detection (fastest method):
From scratch:
# Ignore detection by name
op: is
path: cat
value: my-detection-name
# Ignore specific file
op: ends with
path: detect/event/FILE_PATH
value: legitimate-tool.exe
case sensitive: false
# Ignore specific host
op: is
path: routing/hostname
value: build-server-01
For complete FP rule syntax and advanced examples, see REFERENCE.md. For FP troubleshooting by ruleset, see TROUBLESHOOTING.md.
Always test rules before production deployment.
# Validate rule syntax
limacharlie replay --validate --rule-content rule.yaml
# Test against recent data (last 7 days)
limacharlie replay --rule-content rule.yaml \
--entire-org --last-seconds 604800
# Test with trace mode for debugging
limacharlie replay --rule-content rule.yaml \
--events event.json --trace
For complete testing workflows, see EXAMPLES.md. For test troubleshooting, see TROUBLESHOOTING.md.
# List all rules
limacharlie dr list
# Get specific rule
limacharlie dr get --rule-name my-rule
# Add a rule
limacharlie dr add --rule-name my-rule --rule-file rule.yaml
# Remove a rule
limacharlie dr remove --rule-name my-rule
# Export all rules (backup)
limacharlie dr list --format json > rules-backup.json
Use prefixes to organize rules by source:
sigma-windows-process-creation-suspicious-cmdsoteria-edr-windows-lateral-movementcustom-ransomware-indicatorsFor version control and IaC approaches, see REFERENCE.md.
Start with high-fidelity rulesets
Add broad coverage
Customize and tune
Continuous improvement
For complete best practices, see REFERENCE.md.
soteria-rules-edr - EDR detection rulesetsoteria-rules-aws - AWS detection rulesetsoteria-rules-o365 - M365 detection rulesetsocprime - SOC Prime integrationtor-ips - TOR lookup (free)This skill provides guidance for deploying and managing four types of managed rulesets:
When helping users:
The best approach combines managed rulesets for baseline coverage with custom rules for organization-specific needs.