Syspeace licensing – a walkthrough
The licensing model for Syspeace is very flexible and easy to use and has been to designed to keep your administrative tasks to a minimum.
First of all, if you haven’t already, download a free trial and install it. Your servers are protected from brute force and dictionary attacks within minutes.
Regsiter your account with a valid email address and a license number will be emailed to you.
If you decide to continue using Syspeace for protecting your Windows servers, Exchange Servers OWA, Citrix, Terminal Server, CRM, RDWEB, Sharepoint and so on then ..
Simply login to the Syspeace licensing site with the mail address you used upon registration, buy your license and the trial license you’ve used earlier will be automatically converted into live license the next time your Syspeace client validates the license or the service is restarted.
So, there is no need to change the license number , you’ve already got it .
A main feature of the Syspeace licensing model is the flexibility – rethinking application licensing models
Instead of having to buy licenses for instance a 1 year licens at a tme per server (which is not uncommon) or having to buy a new license / upgrade license when a major release is up , you buy licenses based on computer days and for how many servers you want.
As an example. If you’ve got a server today and you want to get a ”classic” one year licese for it (everyone tends to think in terms of one year licenses I guess) , you login to the site, get your license and you’re good to go.
Two months later, you buy another server and of course you want that server also to be protected from brute force and dictionary attacks.
Ususally this would get you into the situation where you’d have two different license renewal-dates to remember and that’s just a hazzle for everyone.
With Syspeace though, you simply login and extend your existing license for 10 months and to two servers, thus enabling you to align your license renewal dates to tha same date and therefore simplifying your administration.
With Syspeace minor and major upgrades and even all new versions and patches are included in the license.
Should we release new features or a new major version, it’s already included.
No need to buy a license for version 1 thinking all is good and when version 2 comes along , you realize you’ll have to get an upgrade license to use all the new features.
Moving Syspeace licenses between servers
Also another feature that makes you life easier.
Within the licensing section of Syspeace, there is a ”Reset license” button. Simply press that and the license is reset from the local server and the server is removed from the central database along with its affilation to the license number.
Next step is to install Syspeace on the new server where you want it, activate your license key and you’re good to go.
Syspeace is an automated brute force prevention / dictionary attack software that protects Microsoft Windows Servers by monitoring the Windows Authentication mechanisms for unsuccessful logins.
This means that you get immediate protection for Microsoft Terminal Server, Citrix, Exchange OWA Webmail , SharePoint, CRM, Terminal Server RDWeb and more, for instance there is also built in protection for Exchange connectors.
Each attack is automatically blocked, tracked and reported and as a system administrator you set up your own rules on when to block and for how long.
Syspeace is easy to install and you’re up & running and protected within minutes of the download. No need for changing your infrastructure, buy costly new appliances or hire specialized consultants.
The Global Blacklist that is shared among all Syspeace installation around the world gives you preemptive protectionfrom well known hackers and ddos attackers, blocking them even before an attack can be initiated.
Syspeace also contain reporting capabilities, giving you the ability to check for failed and successful logins for your servers and separated mail notifcations based on events.
The Syspeace licensing model is very flexible and and targeted to be easily affordable for any company, whether you’re n the SMB segment, a large enterprise or even a large Cloud Service Provider or an outsourcing company.
One of the goals for Syspeace is to become a natural part of every servers installed security mechanisms as part of the baseline security and an important piece of that security work is
A Windows 2003 version of Syspeace is underway to also provide brute force and dictiionary atacks prevention for older servers
Try for yourself and see how easy it is
Other IT Security aspects
If you’re interested in various aspects of server security questions you might want to check out http://syspeace.wordpress.com and this blog where there’s quite a few articles on why and how Syspeace can help you with your everyday battle of brute force and dictionary attacks but also a few other guidelines for IT security.
About brute force protection and Cloud Security and VPS (Virtual Private Servers) and outsourcing or hosted environments
Thoughts on cloud security by Juha Jurvanen @ JufCorp
If you are a Cloud Service provider or an outsourcing company and giving your customers access to various Windows services such as file access, Exchange, Exchange OWA, Sharepoint, Citrix, RemoteApp and Terminal Server services or even VPS (Virtual Private Servers) , there are things you may want to consider.
Cloud security is often debated and it should be. There are pros and cons to each technical solution. Your customers rely on you to have your services reachable, virtually 24/7 and initially, they’ll be happy when that works.
Nowadays though , Cloud Computing has grown to be more accepted and with it a few questions are coming to life.
Your customers will eventually start asking you how you actually deal with various brute force attacks and dictionary attacks to protect their data. You will also , sooner or later, be faced with questions of reporting of these attacks and to be able to gather various reports of when and from where a specific user was logged in,
Remember that you customers have moved from an inhouse hosted environment where they had the ability to gather this intel themselves and they will be expecting to be able to get it from you. They also had the ability to use Syspeace to protect them but once they’ve shifted to your services, they have absolutely no idea of what security mechanisms you have in place for them and these questions will start to come around.
Historically, it’s been very difficult to handle these situations (feel free to read earlier post on this blog to see what I’m getting at for instance http://syspeace.wordpress.com/2012/10/21/securing-your-webmailowa-on-microsoft-exchange-and-a-few-other-tips/ and http://syspeace.wordpress.com/2012/10/16/various-brute-force-prevention-methods-for-windows-servers-pros-and-cons/ ) so many sysadmins have just more or less given up but when we’re moving to Cloud Services and Cloud Computing, people will expect that also these matters should be sorted. The issue is ”why should we move our data to something we can’t even control or know how the security is set up or verify it easily ? ”
Sooner or later, the end users and customers will start testing how your response really is and verify if there are any mechanisms in place (sometimes out of curiosity and sometimes due to internal processes and audits).
Is their attacked account locked out ? For how long ? Is the attacking IP locked out ? Can you as a Cloud Service provider contact the user and let them know that someone tried to user their account from an IP address in China , although you know the customer has no business in China? Do you alert you customers about it ?
No, probably not and it’s easy to understand why.
Because all of this has required a lot manual work so most service providers and outsourcing companies just don’t want to deal with the problem and tend to not talk about the actual problem, being basically, they have no idea on important stuff such as from where a login attempt was made, what username was used and how was it handled? Was it successful or a failed attempt and how many times did the attacker actually try ?
If you are a Cloud Computing Service provider I highly suggest you have a look at Syspeace to enable you to add this service for your customers and protect access to your Cloud services preemptively and actually have these things handled automatically, without increasing your workload but still tightening your security and to a very low cost.
If you’re a VPS provider, consider for instance having the Syspeace software pre installed in your images and let your customers know it’s there so they themselves can decide whether to use it or not. It’s not an extra cost for you but it does show your customers that you’re actually thinking about their security and that you’re thinking ahead.
So far, Syspeace has actually saved 4.3 M US$ in only a few months in costs for the manual workload associated with brute force attacks and dictionary attacks.
I believe that the service providers that start thinking about these things and take them seriously will have an advantage to those who don’t and quite a few will take having a system such as Syspeace in place for granted, as you would with antivirus.
Have a look at the Syspeace website and see for yourself how quickly and easily you can implement a brute force prevention system without the usual costs of appliances or costly consultants.
This is just a geeky, cost calculating experiment really. Nothing scientific or anything. Just a fun thought on how easy it is to calculate the ROI for the low cost of Syspeace licenses.
Yesterday evening we had a really interesting meeting with a future reseller so we thought we’d take a look at the actual numbers of blocked attacks.
Syspeace had blocked over +314 000 brute force attempts on Windows servers worldwide.
This morning I started thinking.
If each attack takes 15 minutes to manage manually with these steps
1. Find the IP address of the attacker in the event viewer, then block the attack (in the internal or external firewall)
2 Trace the origin (using traceroute, nslookup and whois) and log it somwhere
3. Decide if it’s worth following up and making ot a police matter
That would mean we’ve saved 314 000 * 15 minutes = 78 500 man hours of manual work around the world.
The US$ is about 6.8 Swedish Cronas today.
If each tech has a salary of 35 000 (approx. 5100 US$) per month (an average tekkie salary in Sweden) the average hourly salary is 218 Swedish Krona (32 US$) .
For the employer , that number is about the salary time 1,7 (due to taxes and stuff ) so that would basically amount up to 371 Swedish Krona as a cost for the employer.
What we saved in manual labor with Syspeace would be 78 500 * 371 = 29 192 187 Swedish Cronas (or 4 292 968 US$) in actual cost savings bot most of all, we’ve made the life of the sysadmin easier and he can focus on other stuff than managing brute force attempts and let Syspeace do the work.
A lot of IT projects could do with an extra 78 500 man hours..
If you’re up for cutting costs and increasing security at the same time, have a look at the free trial download at the Syspeace website
A thought by Juha Jurvanen @ JufCorp
By Juha Jurvanen
Senior IT consultant in backup, IT security, server operations and cloud
The goal with Syspeace is to simplify security management and prevent brute force hacking, primarily in Microsoft Windows Server environments and is targeted at system administrators that manage servers, either ther own ones or for external customers or even in data centers such as cloud service providers.
Syspeace automates intrusion attempts, brute force attempts, (eventid 4625) on Microsoft Exchange servers (including the OWA interface and protecting the receive connectors) , Microsoft Terminal Servers and basically any Windows server that uses Windows Authentication such as Sharepoint, Exchange, Terminal Server, Citrix, SQL Server and so on.Around the clock. .
Background and history
The background of the product is that within the Swedish-based cloud service, rCloud Office , from Red Cloud IT where I was the Cloud Architect and CTO , the realization of how many excessive login attempts generating eventid 4625 (failed login , unknown username or password ) from all around the world there really was and that this needed to be automated in aspects of the administration of it and to tighten security since no brute force prevention is built into Windows. I also quickly realized that none of the other Cloud Service providers has any of this in place and this scared me.
A single attack could render in 5000-6000 login attempts and go on for 2-3 hours. This was a waste of bandwidth, server RAM and CPU since each login-attempt had to be validated and there was always the fear of someone actually succeeding to login or that a user account could be blocked out deliberately just to cause a DOS for the services.
For each brute force attempt most labour was manual and time consuming
- First, the log files had to be checked in Windows Server eventlog.
- Second , the attack had to be manually blocked the incoming IP adress in the firewall.
- As a third step attacker had to be traced with TRACERT and NSLOOKUP and WHOIS to determine from where it originated and decide when it would be suitable to handle it as a police matter or not.
At night, no one actually could handle an attack so it would be managed the next day which left us vulnerable during off-hours.
Of course this manual labour took quite some time the realization came quickly that it would become an absolute nightmare in the end if something wasn’t done. All customer expect these countermeasures to in place.
The need for something to automatically block the intrusion attempt, notify us the IP address and from where the attack was made popped up
I started searching the Internet for a cost effective, easily administered with graphical interface and yet effective solution.
There were a few simple script solutions out there but unfortunately, none of them really matched what was to be accomplished i.e. block the intrusion attempt based on rules, track down the attacker geographically and unblocking the IP automatically and reporting the attack.
It had to have the ability to easily manage WHITE LISTS, preemptive BLACK LIST, handle SMTP AUTH attacks and quite a few other features as well that just couldn’t be accomplished with scripts. It had to be easy to use with a graphical management interface to keep the administration and the learning process to a minimum and the autoblocker had to run as an integrated Windows service for optimal performance.
The idea and concepts takes shape
I came up the idea and a concept on how to get the job done, wrote down a few technical ideas and specs, wrote some proof of concepts and thought about the idea and how to actually accomplish it and came across the guys of the Syspeace develepment team at Treetop and work began. Since I’m not a developer myself, I thought I’d leave the hardcore development to people who actually know what they’re doing.
I’m the guy with concepts and ideas but when it comes to actually writing code.. well.. I’m not a first hand choice. I’ve got a few a more ideas up my sleeve but let me get back to you on that 🙂
After the first alpha test we also realized quickly we needed to add some more intelligence to it as, for instance, if an IP fails to log in x number of times during x amount of time and then succeeds, the system shouldn’t remember it as a possible attacker and be blocked further down the road for a failed attempt. People are still human and sometimes people type in the wrong password. A lot of work has beent put into the intelligence ”under the hood” of Syspeace.
We also realized that the software works just as well protection your servers from LAN connections, giving you a better understanding of what really goes on woith your users and if someone on your LAN is trying to access resources they’re not supposed to or if someone has been infected with some kind of brute force – virus.
Today, we get an email stating from where the attack originated (the DNS name if found, the IP address and from which country the attack originated). We’ve got reporting, separated mail notifications depending on events and we’re adding more and more features all the time.
We also get username that was tried which is extremely helpful since we immediately can see if it is just ”background noise attack” or if it is targeted specifically or even worse, a competitor tries to login to the central systems without explicit permission or an ex-employee/ex-customer is trying to access an account that they no longer are authorized to.
So far Syspeace has successfully blocked over 2,5 Million brute force attacks worldwide and I dare say it has decreased the workload for quite a few system administrators out there.
Syspeace supports Windows Servers 2003 – 2012 R2.
Senior IT consultant in backup, IT security, server operations and cloud