Learn & Share

 Audience: SOC Analysts, Threat Intelligence Analysts, Security Operations LeadersProduct Module:Threat Intelligence Management (ThreatQ Platform)Last Updated: December 18, 2025KB ID: KB‑20251218‑ThreatQ‑Scoring‑ExpirationTags: Threat Intelligence, Lifecycle Management, Scoring, Expiration, Indicator Management, ThreatQ, SOC OperationsProblemOrganizations often ingest large volumes of threat intelligence but still experience security gaps, alert fatigue, and false positives. Without a way to prioritize and retire data, threat intelligence becomes noisy instead of actionable.ObjectiveHelp security teams understand how scoring and expiration can be used to manage the full threat intelligence lifecycle—from ingestion to retirement—so analysts can focus on intelligence that is relevant, timely, and ali

 Grouping in Securonix is a two-fold process: Create Data Sources (DS) correctly — Syslog and API logs must be separated into their own DS so that grouping is clean and meaningful. Use functionality and Spotter searches — Once DS are created properly, Securonix automatically groups the logs and allows you to search, drill down, and correlate them easily. Both steps together form the basis of how grouping works end-to-end. Creating Data Sources Correctly (Foundation of Grouping) A. Syslog When onboarding syslog data, for example Palo Alto firewall data, we can use separate Data Sources to maintain zone-based segmentation such as Trust, Untrust, DMZ.Example using different ports:Palo_Untrust → TCP 514 Palo_Trust → TCP 515If using multiple ports is not an option, we can use Syslog filters to sp

During an undetermined number of executions of my playbook, it crashes. Is there a way to validate how many executions have been performed and whether they are causing instability in my service?

ThreatQ provides a comprehensive REST API documentation and an extensive Swagger collection, making it easy to explore available endpoints and parameters. However, we’ve heard that developers and analysts could benefit from use-case–based documentation — examples that walk through common workflows and best practices for interacting with the API.This type of documentation could help: Understand best practices for using the API effectively Avoid inefficient or unsupported methods for common operations Get started faster with real-world, task-based examples We’d like your input on what would be most helpful: What API use cases do you find yourself repeating or struggling to document?

Securonix Threat Research (STR) Monthly Newsletter– November 2025 Edition – Welcome back to another newsletter by the Securonix Threat Research Team!November has been a month of a LOT of reverse engineering. The team has been grabbing malware samples from multiple sources to find novel and interesting techniques and indicators to share with the community. Our team has also been featured and seen this month during the FS-ISAC EMEA webinar where Shikha Sangwan presented her findings for CHAMELEON#NET. We provided commentary on the latest Kimsuky & Lazarus Tooling, Evolving ClickFix Attacks, the recent Government Compromise, CISA 2015 Reauthorization, Chinese using Claude to “AutoAttack”,  XWiki CVE-2025-24893, and Legacy Firewall Attacks. We also now have Securonix Connect to share these ideas and updates in a more streamlined way! Oftentimes, news outlets summarize a lot of our commentary but now we h

When searching in Spotter AI, entering a generic field name like “hostname” may not return results from all related attributes. Currently, Spotter AI appears to select one matching field (e.g., hostname) instead of searching across all similar variations such as: devicehostname sourcehostname destinationhostname host This means a query like:“Provide me all violations involving the hostname XYZ.acme.com”may return only a subset of results instead of all logs where that hostname appears in any related field. We’d like to better understand how you’d want Spotter AI to interpret these kinds of queries: Should Spotter AI automatically include all fields with a common root term (e.g., “hostname”) in a

Currently, the ThreatQ platform can parse Snort, Suricata, and YARA signatures, extracting metadata and indicators of compromise (IOCs) for use in investigations and automation workflows.At this time, Sigma Rules are not supported for parsing.We know Sigma is a widely adopted detection format across many environments. If Sigma parsing would help improve your threat detection workflows, we’d like to hear your perspective: How do you currently manage Sigma Rules in your threat intelligence processes? What would you expect from a Sigma Rule parser in ThreatQ — e.g., extracted fields, metadata, or IOC types? How might this integration benefit your day-to-day investigations or automation? Your feedback will help shape potential ideas for future development.👉

Current StateCurrently, the ThreatQ user interface does not allow users to create new Indicator Types.While users can create ad-hoc types for other objects such as Events or Attachments, defining new Indicator Types currently requires the ThreatQ API. Some users have leveraged this API to create types such as:    •    Routing Number    •    Bitcoin Address    •    Account Number    •    Phone NumberAlternatively, it’s possible to achieve similar outcomes with Custom Objects, though those typically require more configuration and are not as seamlessly integrated across the platform.We’d like to better understand what would be most useful to you:    •    How important is it for your team to create new Indicator Types through the UI?    •    What kinds of custom indicators do you need to track most often?    •    How would you expect to manage these custom types (na

Current State Currently, when creating a new object in ThreatQ using the Create Object modal, users can set a limited set of fields: Value Type Status Source (and, for some object types, a description) The APIs already allow additional details — such as Tags and Attributes — to be added when creating objects. However, these options aren’t currently available in the UI, which means users often have to go back and edit the object later to add context. We’d like to hear how expanding the Create Object modal could improve your workflows: What extra fields or context would be most helpful to capture at creation time? Would being able to add Tags,

Currently, ThreatQ does not display UI notifications or alerts when a newer version of an installed integration is available in the Marketplace. Users need to manually check for updates and then download and upload the new integration files to update their environment.We’re exploring how to make this experience more seamless and would love your input: How would you like to be notified that an integration is out of date — a badge, alert, or status message? Would you prefer to see version information (installed vs. latest) directly on the Integrations page? How useful would a one-click “Update” option be for your workflows? Would automated or scheduled updates fit into your organization’s change control process? Your feedback will help us understand what kind of update visibil

When a feed fails—or while developing a new feed—users often download Feed Run files to troubleshoot and understand what went wrong.Currently, these files are automatically zipped and password protected. This design helps prevent the files from being flagged by security tools, since they may contain data that appears malicious.However, some organizations (such as financial institutions) have strict security policies that prohibit downloading password-protected files, since they can’t be inspected by endpoint protection tools. This can make troubleshooting feeds more difficult.We’d like to better understand how you’d prefer to handle this scenario: Would you want the option to toggle password protection for Feed Run files directly from the UI? Would it be more useful to view the file contents securely in-platform,

Following from our announcement re DPM Flex Consumption, our mechanism to all our customers to optimize their data ingestion for effectiveness, efficiency and efficacy - here’s a sneak preview of the billing dashboard that is expected to ship in the December platform update.  You’ll be able to see both total consumption in absolute GB/d, and also billed consumption in terms of the weighted “cost” of each pipeline, giving you visibility of how your DPM effectiveness changes over time and plenty of warning if you are approaching your committed limit.  More information to come and always happy to answer questions.   

For all our customers who participated in the Search Agent Early Access that ends Dec 31 2025 -  I’d like to extend my sincere thanks for your participation in the Search Agent Early Adopter Program over the past ten months. Your engagement and thoughtful feedback have been instrumental in shaping this capability - helping us deliver three progressive releases, the most recent in September R1 2025.Your input has driven tangible improvements in accuracy, performance, and user experience, transforming the original concept into a robust and intuitive feature.As we prepare to close the Early Adopter phase in December 2025 and transition Search Agent to general availability, we’d greatly value your final feedback to help us fine-tune the GA experience.Please take a few minutes to share your perspective by answering the brief questions below - we are happy to talk through your experience if you’d rather discuss: Does your team

Almost all Securonix SIEM customers are now enabled for Security Alert Center, and with it (as long as you have approved AI components) the Response Agent - have you tried it yet? Any feedback welcome. We estimate it averages about 20min time saved per violation - do you agree?   

You can find the tile to access TQ Marketplace on the main page. Or use this link: https://marketplace.threatq.com/

Why Network Visibility MattersMany security teams rely on Proxy and Web Application Firewall (WAF) logs for visibility, but that’s only part of the picture.🛡️ Firewalls, especially their allowed traffic logs, reveal critical activity that other tools can’t see.🔍 They’re essential for detecting, investigating, and preventing threats across the entire attack lifecycle, from the first probe to the final exfiltration attempt. ✨ Where to StartTo unlock this visibility and close detection gaps, focus on the following six best practices.We’ll begin with the foundation: capturing Layer 3/4 network visibility. 🌐 1. Capture Layer 3/4 Network Visibility