Syspeace v3’s Remote Status Console supports viewing a few pieces of information from another computer.

Syspeace Console in v4 replaces the local interface and can do everything remotely, and works even if you do not have line-of-sight to the server directly.

Syspeace v3 supports blocking through Windows Firewall or IP Security Policy. If Windows Firewall is disabled or managed by another piece of software, configuration may be required to switch blocking over to IP Security Policy.

Syspeace v4 directly uses the Windows Filtering Platform and is not disabled or ignored when another firewall is in use.

Syspeace v4 supports improved rules that support negative blocking conditions and capable nested logic. A few examples that are not possible in v3:

• Login attempt is not user X
• Login attempt is during work hours on weekdays
• Login attempt is traffic from country X (v3 only supports immediate blocking with Country rules)
• Login attempt is traffic outside/inside a given IP range
• Combinations of the above (like: traffic either from Sweden or the internal IP address range at any time, or during the work hours on weekdays)

With Shared blocks, when activity causes a block based on one of the rules, this block is shared with other Syspeace Services within the account.

With Shared IP lists, shared blocklists and safelists can be set up within an account.