Overview
Signatures catch what someone has already seen. Reputation catches what someone has already listed. A new tool, a fresh botnet or a scraper written last week has neither, and that is the traffic Cortex's models are for.
Each model answers one narrow question on the host, with nothing leaving the machine: is this fingerprint malicious, does this flow behave maliciously, what kind of traffic is this. Their answers become ordinary rule fields, so a rule decides what a verdict is worth.
When you see this
- Traffic gets through that no signature fires on and no feed lists.
- Clients rotate addresses faster than any list can follow.
- You want to rank what to investigate by model confidence rather than by alert volume.
Steps
- 01
Install an -ml build
The models ship in the -ml packages, and inference runs on Linux. On other platforms the agent still builds, but the models return errors instead of scores.
- 02
Turn the models on
Platform-managed models only need enabled: true; the model is downloaded and its paths default. Models arrive with a signed integrity manifest and are swapped at runtime without a restart. The traffic classifier is early access.
/etc/synapse/config.yaml ml: fingerprint_classifier: enabled: true flow_classifier: enabled: true traffic_classifier: enabled: true - 03
Watch the verdicts before acting
The models are alert-first: they emit a verdict, and a rule opts in to acting on it. Start with a log rule, which records what it would have done and enforces nothing. Model probabilities in rules are integers from 0 to 100.
Smart firewall rule, action log ml.flow.label eq "malicious" and ml.flow.malicious ge 80 - 04
Set your own threshold
Probabilities are uncalibrated. The right cut-off depends on how common malicious traffic is in your environment, not on 50.
DecisionDid the log rule flag traffic you know is legitimate?Yes Raise the threshold or narrow the rule, and watch again.
No Move on to enforcement.
- 05
Require a second signal
A model verdict is not a standalone block. Pair it with reputation, IDS context or a second model, so a rule drops only when two agree. Per-class traffic probabilities let a rule fire on a class that was not the top one.
Smart firewall rule, action drop ml.flow.malicious ge 80 and threat.score ge 50Smart firewall rule, action drop ml.traffic.c2 ge 90 and ids.alert_count > 0 - 06
Read the model card
Every model has a card covering training data, evaluation and limits. The fingerprint classifier's 0.996 accuracy is a ceiling measured under favourable conditions, not a prediction for your traffic: validate against your own before setting policy on it.
Common mistakes
- Blocking on a model verdict alone.
- Using 50 as the threshold because it looks neutral: the probabilities are uncalibrated.
- Treating the traffic classifier's seven classes as a block decision. It is a parallel signal by design.
Escalate when
- A source the flow classifier and the IDS both flag.
- A verdict on traffic from a host that holds credentials other systems trust.
Where this stops working
- Expect distribution shift: on out-of-distribution malware samples the classifier misclassifies some as benign.
- A fingerprint is not a person. Many legitimate clients share one.
- The severity model currently ships trained on synthetic data.