Threat Enforcement Configuration


The SafeConnect threat enforcement module allows for the ability to configure enforcement policies based on threats that are detected in a system external from SafeConnect. These policies can then be used with any device type and do not require the use of an agent running on the end-user device.

Once configured policies can be set to either audit or quarantine. With any quarantine policy, end-users will receive a browser-based message informing them of the issue. These messages can be customized with instructions on how to remediate and how long they will need to wait before the quarantine will be re-evaluated.On the Identity Publisher tab, complete the following:


Prior to configuring any items in SafeConnect, the system sending alerts will need to be configured to forward alerts to SafeConnect via syslog, to port 30514.

Configure Threat Enforcement Input

After the threat detection system is configured, open the SafeConnect Configuration at ( can be replaced by the manager IP or a branded URL) and choose “Configuration Manager > Threat Enforcement”.

Enable the webapi:

From the dropdown, choose your Vendor and click ‘Add’.


After choosing the Vendor, at least one source must be defined. A source is simply the IP address of the threat detection system. If the threat detection system has multiple interfaces, the IP specified must be the IP that appears as the source address of the alerts. The name can be any descriptive name that is needed.


After clicking ‘Submit’, the Threat Detection source will appear in the list.


Configure Threat Enforcement Policies

After at least one source has been defined, Threat Detection policies can now be created. To create a policy, click the ‘Add’ button.


The first section is used to define what alerts SafeConnect will listen for. If alert details are not configured, SafeConnect will ignore the alert. These values may differ based on the specific format used by the chosen Vendor. Nearly all Vendors will follow a similar format.

  • Severity: Either a numeric or textual value based on the vendor. This field must not be blank. If numeric values are used, a range can be specified. Textual values will look for an exact match in the alert.

  • Event Type: This field will always be a text value and also support regex matching. This field must not be left blank. To match all alerts in this field, simply enter the value ‘.*’.

  • Event Sub-Type: Not all vendors will have a subtype. If the vendor does have a sub-type, this field will always be a text value and also support regex matching. This field must not be left blank. To match all alerts in this field, simply enter the value ‘.*’


The next section defines how SafeConnect will react to the defined alert. Once configured, the policies will be available in the SafeConnect Policy Manager.

  • Policy Name: The name of the SafeConnect Policy. This value will be used to represent this policy in the Policy Manager and in the Device Manager.

  • Policy Duration: Defines how long SafeConnect will enforce the policy when an alert is recieved. Once this time expires, the policy will no longer be enforced unless a followup alert is received for the device.

  • Enforcement: Defines whether SafeConnect will block a device or simply report on the alert.

  • Web Message: The web message that will be displayed to blocked devices for the duration of the enforcement.

Once configured, click ‘Save’.


The resulting Threat Enforcement Policy will now appear in the list and will be available in the Policy Manger.


Add Policies to existing Policy Groups

After Threat Enforcement policies have been defined, they will be available in the Policy Manager. Threat Enforcement policies can be added to a Policy Container just like all other SafeConnect policies.