Following on Syspeace 4.1 and 4.2, we have been adding new features to Syspeace at a rapid pace. This post is part of a series on what’s new in Syspeace 4.3, just released and available for download now. (Previously: Service ID and Shared IP lists)
Last time, we discussed Shared IP lists – the ability to manually add IP addresses to a list and have that list propagated to all Syspeace services in an account. A similar feature has been even more commonly requested: If server A blocks something, why can’t server B also block it?
With Shared blocks, this idea is coming to Syspeace. When Shared blocks is enabled, that is exactly what happens. When one Syspeace service’s rules detects something and created a block in response, this block is contributed exactly as is, and other Syspeace services within the same account (or optionally within the same license group) will receive this information and mirror the block as is.
Once this feature is enabled, it “just works” and it will make Syspeace’s protection even more responsive. Now, as soon as a block is produced in one place, it can be mirrored in many other places automatically.
Although the feature is automatic, there is still flexibility built in. For example, you can set a max block duration, if one service needs longer blocks but shorter blocks are a better fit elsewhere. And in case a false positive block is triggered by a legitimate user mistyping their password, no worries – you can forgive the block, and decide on a case-by-case basis whether to forgive it on all services or only locally.
We think Shared IP lists and Shared blocks will make Syspeace even more effective. There is one small aspect of both features that is worth covering in its own post, next time: Local network tag.