indicator--274afa14-7c40-5921-5d1b-ae74e430c62c · TLP:CLEAR
Skills
Written the way I'd describe anything else I track, then each one tied to the work where it was used.
rule dheeraj_maram : analyst cti{meta:role = "IT Security Analyst, threat intelligence researcher"focus = "ransomware affiliates, exposure tracking, detection coverage"tlp = "CLEAR"strings:$collect_1 = "OpenCTI" // own collection, STIX 2.1$collect_2 = "Censys"$collect_3 = "VirusTotal"$map = "MITRE ATT&CK"$detect_1 = "Sigma"$detect_2 = "KQL" // Defender XDR, Sentinel$code = "Python"$cloud = "Google Cloud"condition:any of ($collect_*) and $map and any of ($detect_*)}
where each one was used
Exposure tracking
Censys, Hunt.io host history
CTI reporting
Sourcing, confidence, limitations, indicators
Detection writing
Sigma rule for the ARTEX backdoor execution path
ATT&CK mapping
Techniques, campaigns, Navigator layers
Threat feed ingestion
ThreatFox, Feodo, MalwareBazaar, URLhaus, YARAify, CISA KEV
Indicator enrichment
VirusTotal API v3, MITRE D3FEND lookups
Detection coverage analysis
Sigma rule libraries, gap ranking
Python
CLI tools, pipelines, FastAPI
Text attribution
Stylometry, sentence embeddings, HDBSCAN
Public data visuals
CERT-In advisories, incident reporting
Service engineering
PostgreSQL, Redis, Celery, Docker Compose
Cloud and identity security
Google Cloud, Firebase Auth
Privacy and LLM safety controls
FERPA consent, aggregate-only reporting, crisis escalation