Threat Hunting
What's New in Threat Hunting v1.2.0
- Eyeglass and ML VM Alarms — Monitor connectivity and health with new alarms that let you know when the ML VM requires attention or troubleshooting, so you can identify and resolve issues more quickly.
- Integration Payload Improvements — The SIEM anomaly payload has been reorganized to group Threat Hunting-related fields under one category, improving payload structure and readability.
- Jobs Visibility — Monitor training jobs in the Threat Hunting module in real time, track their progress, and review completion status and success for improved operational visibility.
- Optimized OVA for Kubernetes — Deploy an updated OVA that's better aligned with Kubernetes deployment requirements, improving resource allocation and simplifying deployment.
Getting Started with v1.2.0
Ready to deploy Threat Hunting with the automated installation workflow? Start here:
Before You Begin
Review prerequisites, system requirements, and gather the necessary configuration details before starting installation.
Automated Installation
Follow the automated installation process to deploy Threat Hunting v1.2.0 with simplified configuration.
Learn More
Understanding Threat Hunting
If you're new to Threat Hunting or want to learn more about its capabilities:
Managing Threat Hunting
After installation, learn how to configure and operate your Threat Hunting deployment:
Configuration Guide
Configure threat detection settings, access controls, and integration parameters.
Operations Guide
Monitor threats, investigate anomalies, and respond to detected security events.
Need Help?
Encountering issues during installation or operation? Our troubleshooting guide can help:
Troubleshooting Guide
Find solutions to common installation and configuration issues, including automated installation troubleshooting.
Alarm Codes Reference
Look up ML VM alarm codes, severity levels, and recommended actions.
Upgrading from Previous Versions
If you have an existing Threat Hunting installation and want to upgrade to v1.2.0, please contact Superna Support for upgrade guidance and procedures specific to your deployment.