No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

The TSM policy checking principle

Publication Date:  2019-07-19  |   Views:  560  |   Downloads:  0  |   Author:  c00222574  |   Document ID:  EKB1000020319


Issue Description

The TSM policy checking principle

Alarm Information


Handling Process


Root Cause

In the the TSM system using process, it often uses TSM illegal statements, in given irregularities statements, the following principles:

Check classifier strategic principles:
Incorporate the results of the inspection, 24 hours a day, for a time range merge, whichever is the earliest that it was reported; illegal information (excluding irregularities time) changes log as illegal information. For example: A user in the case of offline 8:00 check into irregularities time not set the screen saver, 12:00 check to violations of the time not set the screen saver, is reported to 8:00 violations.

Monitoring classifier strategic principles:
The inspection results are not special merge strategy perform find violations will be reported for the first time (monitoring during the same illegal information not reported).

Policy violation data will be reported within 5 minutes after the certification of the boot for the first time, the next every two hours to report once (offline checking irregularities log information to the client, When the by reported violations certification information)