The Question That Everybody Asks: What’s The Difference Between Seacat and VPN?
One of the most common questions people asked us is “Is SeaCat some kind of a VPN?”
Well it’s not. Virtual Private Network (VPN) extends a private network across a public network, providing secure connectivity from/to a mobile device. Every application on this device, thus now has access to the private network through the channel opened by VPN. This is safe up to a certain level because it is almost impossible to ensure the integrity of every application on the devices. Especially now when there are apps for everything, and users can download them from Google Play and the Apple store.
Recent research from Arxan shows that 97% of the top 100 paid apps on the Google Android platform and 87% of the top 100 paid apps for Apple iOS had been hacked. Does it seem like almost every app has been hacked? As you can see, your data are not secured using applications from bespoke sources. Data being sent to and from your mobile application are easily stolen and used in a harmful way to you and your organisations.
One common hack we often hear about comes from the form of malware. What if you have them in your mobile devices? These malware apps would then, through the VPN channel you have opened, exploit the data residing on servers of your private network. For this precise reason that Gartner’s Janessa Rivera proposes “new models of building security directly into applications; every app needs to be self-aware and self-protecting.”
On the other hand, Seacat is a Mobile Secure Gateway (MSG) providing secure connectivity directly from the mobile application to the gateway entry to the DMZ before allowing any further activity to the sensitive data centre of your organisation. Because of the required mutual authentication, only application with trustable certificates are allowed to access the private network. This is the reason MSG narrows the attack vector to the minimum and keep your data as safe as possible.
Is SeaCat still a VPN? You tell us.
Data encryption tool for GDPRMore information
You Might Be Interested in Reading These Articles
SeaCat requires to specify one TCP port that is eventually used for client-gateway communication. Clients connect to this port to establish TLS channel that is used to exchange requests and related responses. SPDY-based communication protocol is used for traffic in this channel.
Published on May 23, 2014
Starter pack is SeaCat distribution package that is prepared to enable quick evaluation and understanding how SeaCat product works. Also it is a boilerplate for new mobile applications that are equipped with SeaCat.
Published on April 02, 2015
The goal of this article is to create a simple iOS client which generates a simple POST Request which will be read in host written in Node.js and the output generated in the console. The whole comunication will be handled by SeaCat which help us to establish fast and secure connection among our key components.
Published on September 09, 2014