This policy allows the administrator to set a peak CPU utilization per application. If any application exceeds the set threshold, then the application is terminated using a Unix 'kill' command. The diagram below shows the User Interface for setting the CPU Utilization policy.
Bad Login Attempts
This policy allows the administrator to set the allowed number of bad-logins that are possible before any action is taken. If any user's bad-login attempts exceeds the set threshold, then one of two actions will take place. Either the user account will be locked (moderate severity) or deleted (high severity). The administrator is able to choose the severity settings of a bad-login attempt. The following diagram shows the User Interface for setting the Bad Login Attempt policy.
This policy allows the administrator to automatically listen to port
connections and deny any host IPs that abuse a pre-set network policy. The
administrator is able to define scan port times, and limit connection
times. For example, say an administrator doesn't expect any host to
connect to a server during the midnight hours from 12:00 am until 6:00 am, but
will allow a maximum of 1 minute connection. Therefore, the policy would
be set to scan for connections from 12 until 6 am, and that lasted longer than
60 seconds. The following diagram shows the User Interface for setting the
Connection Listener policy.
NOTE: This policy isn't a preventive method for keeping out intruders and/or unwanted host connections. Rather it presents a secondary defense against unknown IP connections.