2015 at GSW
GUI Config Tool
Windows Explorer style interface allowing provisioning and configuration management. Familiar to use operations such as copy, paste, rename, delete, export, import are applied to configurations on a user or system basis. Create templates and quickly view summary configuration data.
TEAM SERVICES provides your mobile device users a breakthrough in Telnet/SSH2 technology that shatters all prior usability and efficiency standards by allowing unprecedented user collaboration. Now mobile device users are empowered to share resources, transfer, swap, share and recover dropped sessions. All from the mobile device, no system administrator necessary. All operations can be performed in under 60 seconds.
Team Services the first feature set to offer Video overviews. We are excited to provide additional methods to meet customer expectations. Visit the GSW Video Channel!
Request a Webinar
FIPS 140-2 Compliant SSH Server and Client
Federal Information Processing Standards "FIPS" 140-2
GSW's SSH Server and SSH Client provide a "FIPS" 140-2 compliant option for those entities with requirements to meet cryptographic module security standards to protect sensitive and valuable data. FIPS certification standards are either mandated or recommended for use in federal government information technology (IT) systems. In addition to all the security benefits of the GSW SSH Server you can also have FIPS 140-2 compliance.
Under contract with the United States Military, GSW developed an End-to-End SSH FIPS 140-2 compliant solution, Client and Server to meet their requirements.
GSW is able to make this FIPS 140-2 compliant solution commercially available for other Federal and State agencies, as well as institutions and private enterprises with the need to comply with government grade security requirements.
Many companies have strong security requirements such as SSH encryption or FIPS 140-2. If you have demanding security requirements, the GSW SSH with the FIPS 140-2 compliant option may be of interest to you. Secure Shell (SSH) version 2 provides a secure channel for remote access to your Windows host.
End to End Security - If it's not End to End it's Not Secure!
The GSW FIPS 140-2 compliant SSH Server, includes FIPS 140-2 compliant clients, at no extra cost. Your don't have to take chances, GSW provides the End to End security you can count on. Ensure END to END compliance by permitting only GSW FIPS 140-2 compliant clients to connect! Its configurable!
The GSW SSH Server with FIPS 140-2 compliance option provides both TRUE client and server compliance for organizations that must meet these high standards. Please be sure to review the associated documents to get a better understanding of the importance of End to End security.
Sometimes vendors of incomplete solutions will claim that since the devices' operating system is FIP 140-2 compliant that any SSH client running on it is FIPS 140-2 automatically compliant too.
This is NOT TRUE
Do not believe it. The SSH client does not automatically inherit all the operating system qualities. Just as having a 64-bit operating system, does not make all the applications 64-bit applications, a FIPS 140-2 compliant OS does not make the client FIPS 140-2 compliant.
However it is true that a FIPS 140-2 client must run on a FIPS 140-2 compliant operating system or internally contain all FIPS 140-2 certified cryptographic modules./p>
These are critical distinctions, that make the difference in being FIPS 140-2 compliant or not.
The GSW FIPS Compliant SSH Server and clients are FIPS 140-2 compliant when running on FIPS 140-2 compliant operating systems.
|GSW UTS Server||7.50+||#918|
|GSW SSH Server||7.50+||#918|
|GSW Desktop Client||7.50+||#918|
|GSW CE/Mobile Clients||7.50+||#560,#825|
|Required Device Operating System for Mobile/CE Clients||Certificate|
|Windows CE 5.0||#560|
|Windows Mobile 5.0||#560|
|Windows CE 6.0||#825|
|Windows Mobile 6.0||#825|
|Windows Mobile 7.0|
With respect to the client device operating system, the significant aspect is that the version of the cryptographic module rsaenh.dll must be NIST(National Institute of Standards and Technology) certified, which begins with build 143188.8.131.52. With Windows CE 5.0 extra attention should be taken to ensure the correct version of rsaenh.dll is present. Per information from Microsoft support early versions of Windows CE 5.0 did not come with a FIPS 140-2 certified version of rsaenh.dll. This may require contacting the device vendor to determine the correct version number of that cryptographic module.
- Additional material on FIPS 140-2 is available below.
|View our flyer on End to End Security|
- Additional material on GSW SSH and UTS Security is below.
|Yes, security is serious business. Keep alert to some common
"Weasel words", ambiguous or misleading terms that give you a false
sense of security.
Here are some questions to consider
|VERY POWERFUL TOOL
Minimize problems from the start. If they are not supposed to be on your server - Don't let them on!
If they are allowed on to perform a job, let them perform the job and not be distracted with other options.