How does Airlock Anomaly Shield calculate anomaly values in the first place?
Since there is no general ruling on what a common value of e.g. an acceptable TimingCluster
is, the only way to get an answer is to compare old values with the current values of a session. This is exactly what the unsupervised machine learning models inside Airlock Anomaly Shield are doing.