SafeRemote - Secure Access to Remote Desktop
- Storing sensitive data and your customers ask about security?
- Moving to Cloud servers that seem too unprotected?
- Logon to the servers' Remote Desktop being too insecure?
- Tried security products that have a huge scope and wants to do everything
under the sun?
- Microsofts own two-factor solution is in the future (and maybe you have to
stick to older server versions anyway)?
Here's the solution: SafeRemote,
a two factor logon product that is focused specifically on
Remote Desktop logon to Windows Servers.
Install SafeRemote, enter your username/password,
get your code via SMS,
type it in at Remote Desktop logon. Ready!
Insufficient security
Many internet-facing servers have insufficient security today, especially
for admins' logon. Your development project hopefully remembers to add good security
for the normal users but often forget about safe admin access via Remote Desktop (RDP).
More internet-facing servers
The strong trend towards Cloud services makes this problem even bigger.
Many more internet-facing servers get added and they all need admin access.
SafeRemote is very suitable for RDP to virtual Windows Servers in
Amazon EC2, Microsoft Azure VM and a large amount of other Cloud services.
Focused product
There are some good products on the market that can add proper logon security, but
usually they are very expensive, complex and difficult to understand and configure. These products solve
a large amount of security issues and can be used for a wide range of tasks.
But often it is just protection for RDP access
that is needed. SafeRemote is a product that is focused on this and is really simple to
understand and maintain.
Customer story
is an organisation where Swedish municipalaties cooperates to
improve efficiency and use IT in new and powerful ways. One of Sambruk's services handle social security
data that of course are very sensitive. SafeRemote protects this server.
.
SafeRemote Technical Info
SafeRemote is a small ASP.NET web application which is easy to install in the server
to be protected. The application consumes a very small amount of resources in the server.
An emergency procedure exists, in the event that ASP.NET should crash.
Simple data store is used for registering the users and for logging—neither SQL nor noSQL is needed.
Backup is simple.
No additional software licenses are required.
No demanding, special "NT Services" are needed to be installed.
No separate gateway server etc. is needed.
Only https is required through a firewall between the person logging on and the server.
Complicated client certificate procedures are not needed.
All Windows Servers supporting at least ASP.NET 2 can be used,
including Windows Server 2003, 2008 and 2012.