After you migrate or upgrade StellarOne to version 3.0, please also upgrade the managed agents to the latest version. Though StellarOne provides backward compatibility to support agents with earlier version, new features or enhanced functionality should not be applicable on some agents with earlier versions.
-
If the original policy setting of the Operations Behavior Anomaly Detection was set to the Detect or Enforce mode, after migrated or upgraded to version 3.0, the StellarOne would retain the previous setting and the Script Behavior toggle would be automatically turned on.
-
After then, if you enable the User Login or Application Behavior, the agent automatically starts learning by collecting the related behavioral patterns performed on the device to establish its baseline fingerprint for User Login or Application Behavior.
Note:The learning of the User Login or Application Behavior does not change the original policy setting of the Operations Behavior Anomaly Detection.
- In the Operations Behavior Anomaly Detection pane,
find and set the Learning time.Note:
-
See the Operations Behavior Anomaly Detection for StellarProtect - Use Case for the recommended practice as you start using the Operations Behavior Anomaly Detection and evaluate the proper learning period for the agent-device.
-
The learning time counts only when the agent-device is powered on.
-
-
Go to the Agents screen. You can find the the learning progress bar displayed in the Operations Behavior Anomaly Detection column for the agent-device. Mouse over the progress bar to check how many days left for learning. See About the Agents Screen for more information.
Note:In addition to the progress bar displayed on the Agents screen, you can also check the learning progress on the General Info page for the agent-device.
-
After learning, the agent-device will automatically switch to the specified mode according to the original policy settings.