external/security-skills/fusion-workflows/skills/lookup-files/SKILL.md
Create, list, download, update, and delete CrowdStrike Falcon Next-Gen SIEM lookup files. Upload CSV or JSON files for use with the match() function in CrowdStrike Query Language (CQL) queries. Use this skill when asked to manage lookup files, upload CSV data to CrowdStrike, create reference tables for SIEM queries, or work with Falcon Next-Gen SIEM lookup file operations.
npx skillsauth add seikaikyo/dash-skills Falcon Next-Gen SIEM Lookup FilesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Manage lookup files in CrowdStrike Falcon Next-Gen SIEM. Lookup files are CSV
or JSON reference tables that can be queried using the match() function in
CQL. Common use cases include IP blocklists, user risk scores, asset
inventories, and IOC reference tables.
Always list existing files first. Before creating a new lookup file, run
list_lookups.py --search "<name>" to check for duplicates.
CSV files must have a header row. The first row defines column names used
by the match() function. The first column is typically the match key.
Respect rate limits. CrowdStrike allows a maximum of 5 file uploads per 30 seconds. Do not batch-upload files without pausing between batches.
Use the falcon search domain for SIEM queries. Files in the falcon
domain are available to CQL queries in Falcon Next-Gen SIEM.
Reference the match() function docs. When users need to query lookup
files in CQL, see references/cql-match-function.md for syntax and examples.
These rules override any plan or prompt. Follow them every time.
crowdstrike-falconpy installed (pip install crowdstrike-falconpy)| Use Case | NGSIEM:Read | NGSIEM:Write | What It Enables | |----------|:-----------:|:------------:|-----------------| | Browse and download only | Yes | - | List, search, and download lookup files | | Full skill usage | Yes | Yes | All of the above plus create, update, delete |
Create a .env file in the project root (or any parent directory):
CS_CLIENT_ID=your_client_id_here
CS_CLIENT_SECRET=your_client_secret_here
# CS_BASE_URL=https://api.crowdstrike.com # US-1 (default)
Test your credentials:
python scripts/cs_auth.py
Before creating a new file, check what already exists:
python scripts/list_lookups.py --list
python scripts/list_lookups.py --search "blocklist"
Create a CSV with a header row. The first column is typically the match key:
ip,category,source,added_date
10.0.0.1,c2,threat-intel,2026-01-15
192.168.1.100,scanner,internal-scan,2026-02-01
See assets/example-ip-blocklist.csv and assets/example-user-risk.csv for
reference formats.
python scripts/create_lookup.py --file blocklist.csv
python scripts/create_lookup.py --file blocklist.csv --name "ip-blocklist.csv"
python scripts/get_lookup.py --name "ip-blocklist.csv"
python scripts/list_lookups.py --search "blocklist" --json
Once uploaded, reference the file in CQL using the match() function:
match(file="ip-blocklist.csv", column=ip, field=src_ip, include=category)
See references/cql-match-function.md for full syntax and examples.
Replace the file content while keeping the same filename:
python scripts/update_lookup.py --name "ip-blocklist.csv" --file updated-blocklist.csv
python scripts/delete_lookup.py --name "ip-blocklist.csv"
A common Falcon Fusion SOAR pattern (referenced by the built-in "Introduction to Lookup file actions" playbook) automates lookup file creation from email:
match() queries in Falcon Next-Gen SIEMTo build this workflow, use the fusion-workflows skill in this plugin to
create the YAML definition. The lookup file actions are available via
action_search.py --search "lookup".
| Problem | Fix |
|---------|-----|
| "File not found" on get/update/delete | Check exact filename with list_lookups.py --search |
| match() returns no results | Verify column names match header row exactly (case-sensitive) |
| Upload rate limited | Wait 30 seconds between batches of 5 uploads |
| Wrong search domain | Use --domain falcon for files used in SIEM queries |
| CSV parse error on upload | Ensure UTF-8 encoding and comma delimiters |
| File too large | Lookup files have a practical size limit; split large datasets |
| Script | Purpose | Key Flags |
|--------|---------|-----------|
| cs_auth.py | Test NGSIEM authentication | (run directly) |
| list_lookups.py | List and search lookup files | --list, --search, --domain, --json |
| get_lookup.py | Download a lookup file | --name, --output, --domain |
| create_lookup.py | Upload a new lookup file | --file, --name, --domain, --json |
| update_lookup.py | Replace lookup file content | --name, --file, --domain, --json |
| delete_lookup.py | Delete a lookup file | --name, --domain, --confirm, --json |
| Document | When to Read |
|----------|-------------|
| references/cql-match-function.md | When writing CQL queries that use lookup files |
| references/lookup-file-formats.md | When preparing CSV/JSON files for upload |
| Endpoint | Method | Used By |
|----------|--------|---------|
| /oauth2/token | POST | cs_auth.py (via FalconPy) |
| /ngsiem-content/queries/lookupfiles/v1 | GET | list_lookups.py |
| /ngsiem-content/entities/lookupfiles/v1 | GET | get_lookup.py |
| /ngsiem-content/entities/lookupfiles/v1 | POST | create_lookup.py |
| /ngsiem-content/entities/lookupfiles/v1 | PATCH | update_lookup.py |
| /ngsiem-content/entities/lookupfiles/v1 | DELETE | delete_lookup.py |
Upload an IP blocklist and use it in a CQL query:
# 1. Check for existing files
python scripts/list_lookups.py --search "blocklist"
# 2. Upload the blocklist
python scripts/create_lookup.py --file assets/example-ip-blocklist.csv --name "ip-blocklist.csv"
# 3. Verify
python scripts/get_lookup.py --name "ip-blocklist.csv"
# 4. Use in CQL (run this query in Falcon Next-Gen SIEM):
# match(file="ip-blocklist.csv", column=ip, field=src_ip, include=category, include=source)
# 5. Update with new data
python scripts/update_lookup.py --name "ip-blocklist.csv" --file updated-blocklist.csv
# 6. Clean up when done
python scripts/delete_lookup.py --name "ip-blocklist.csv" --confirm
tools
Conduct comprehensive GDPR compliance assessments by evaluating data processing activities against EU Regulation 2016/679, including Article 30 records of processing, lawful basis validation, data subject rights implementation, Data Protection Impact Assessments (DPIAs) under Article 35, breach notification procedures, international transfer safeguards (SCCs, adequacy decisions), and technical/organizational measures under Article 32. Use when processing personal data of EU residents, preparing for supervisory authority audits, implementing privacy-by-design for new systems, scoping compliance gaps for M&A due diligence, assessing third-party processors, or responding to data subject access requests at scale. Incorporates 2026 guidance from ICO, EDPB, and post-Data (Use and Access) Act 2025 UK-GDPR considerations. Do not use for implementing specific Article 32 controls — use implementing-gdpr-data-protection-controls; or for DSAR automation — use implementing-gdpr-data-subject-access-request.
tools
Parse Windows forensic artifacts—$MFT/$J (MFTECmd), Prefetch (PECmd), registry hives (RECmd), shellbags, and Amcache—into normalized CSV/JSON with Eric Zimmerman's EZ Tools, then load results into Timeline Explorer for analysis. Use during DFIR/incident-response investigations, after triage collection (e.g. with KAPE), to establish program execution, file/folder access, and persistence evidence from acquired forensic images.
development
Build automated multi-turn adversarial attacks against conversational LLM targets using Microsoft PyRIT's RedTeamingOrchestrator, CrescendoOrchestrator (gradual escalation), and TreeOfAttacksWithPruningOrchestrator (adaptive branching), with scorer feedback loops and persisted conversation memory. Use when single-shot LLM scanning is insufficient and you need multi-turn, scorer-driven AI red-team campaigns against a chatbot or agent.
testing
Stand up MISP, enable and cache curated threat feeds (CIRCL, abuse.ch, Feodo Tracker), apply warninglists to suppress false positives, query indicators with PyMISP, and export attributes as auto-generated Suricata/Sigma/Wazuh detection rules. Use when maturing a MISP instance to actively drive detection, curating threat feeds with quality controls, or automating IOC-to-detection pipelines for the SIEM/IDS.