29 hunts across 12 tactics
From beaconing and DNS tunnelling to DCSync, new persistence, lateral movement and ransomware preparation, mapped to MITRE ATT&CK.
- Runs at 02:00 by default, or on request
Monitoring and threat intel react when something fires. Phynix assumes an attacker may already be inside and goes looking every night, before any alert.
From beaconing and DNS tunnelling to DCSync, new persistence, lateral movement and ransomware preparation, mapped to MITRE ATT&CK.
From new advisories, threats in your traffic, the kill chain, gaps in coverage and changes in your estate. Each hypothesis is tested at once and reported back.
An ATT&CK coverage map and a data-source check. Missing data is never reported as clean.
Each finding shows the records behind it and the attacker's likely next step.
When Phynix cannot decide, the business-service owner and IT decide together, with escalation by severity.
A hunt that proved itself becomes a continuous detection every 30 minutes, after a 30-day back-test of its noise.
Hunts run, findings, dwell time, coverage and decisions, for the board and the auditor.
Your hunting maturity level, from HMM0 initial to HMM4 leading, with what lifts it.
Hunts only read logs, flows and events. The one action that changes anything, a block, is pressed by a person.
Findings are leads for your analysts, not verdicts. Data sources: syslog, NetFlow / IPFIX / sFlow, Windows events and Sysmon, Linux auditd, EDR.
| Threat hunting | Pro | Enterprise |
|---|---|---|
| 29-hunt library every night, findings and triage | ✓ | ✓ |
| Hypothesis register, ATT&CK coverage map, data-source health, campaigns, PDF / Word report | ✓ | ✓ |
| Autonomous AI hypotheses, tested and reported | — | ✓ |
| 30-day retro sweep of new threat indicators | — | ✓ |
| Custom hunts, workbench, continuous detections, block from a finding | — | ✓ |
A 2-day health check, then a 15-day live pilot. Write to us or book a live demo.
office@phynix.co.in