How to Win in the Enterprise Mobility Market
Last year we exhibited SeaCat at the Web Summit in Dublin. On the second day I explored the venue visiting different exhibition booths in the Mobile Enterprise area and talking to the people there. Many of which have already developed mobile applications and other mobile solutions for enterprises and big companies. While these conversations were interesting, one thing in particular stood out. Regardless of the size, industry, or platform of the prospective client, they all had one thing in common — security, or lack thereof.
Surprisingly, the summit attendees had varying backgrounds ranging from developers, startups, and corporations yet they all responded similarly when I asked about the underlying security of their mobile apps and the back-ends. Their position is that they “are as secure as the infrastructure at our customers,” an alarming approach when discussing mobile applications that are more sensitive to security breaches than desktop applications.
CRM or BI data is traditionally accessed from office desktops. In this traditional environment the data remains within the internal network and is safe from threats. However, once CRM or BI data is accessed from mobile devices, it is beyond the protection of the enterprise network because the data is exposed to the outside internet.
Therefore, if you are an enterprise mobility vendor, your customers probably have not solved this particular security issue and rely on you as the developer to anticipate and respond to these threats. There is a potential risk of losing the client deal if you cannot show that have you aware of these threats. Even if you do get the deal, sooner or later you will be requested to fix the security part. That is not an ideal position to be in especially if you do not know to even solve the problem.
All hope is not lost. The solution lies in becoming educating on new security issues and establishing a protocol for addressing the same. Here are a few features you can employ to cover most basic security concerns as it relates to mobile applications and back-ends:
- Backend isolation
- Access control
- Automated client certificate request/renewal
- Protection of private key on mobile device
- Mutual SSL authentication
The above-referenced summit scenario is common given the rapid growth of mobile adoption. At the beginning of the mobile era, user experience and (visible) functionality were the only things that mattered. Today, security is becoming more crucial as more data breaches occur in organizations big and small. Naturally, enterprises try to avoid this kind of publicity so they are seeking developers who are knowledgeable about current security trends and requirements.
If you are in the mobile enterprise market, take security seriously. Do not rely solely on the skills and knowledge of mobile app developers because their underlying focus is on building a beautiful, functional application. Instead, use the best practices available and offer your customers not just functionality but also security.
Send us an email at firstname.lastname@example.org to get a free consulting session on your mobile solution and learn if there will be any potential risk to your data.
Photo credit Web Summit
You Might Be Interested in Reading These Articles
Containerization is an alternative for full machine virtualization. You probably know well-known containerization technology from Docker or Rocket. However, this article addresses the pros and cons of mobile “containerization” or wrapper used to isolate the mobile app from the mobile operating system or other applications installed on the same device. These type of “containerization” work in a different way.
Published on September 27, 2016
With the year on year rise in ecommerce, there is a corresponding rise in online fraud - in fact, according to Financial Fraud Action UK, this type of activity had increased by a quarter to £399.5 million in the first half of 2016. The most recent manifestation of this is the concept of “testing” - this is where the criminals try small purchases to check the validity of card details, before moving in for the kill.
Published on July 04, 2017
In June 2017, two information security firms researching the 2016 hack of the electricity grid in Ukraine announced that they had identified the malicious code used to shut down power stations and leave thousands of households and businesses in darkness for several hours. The malware used to target the Kiev power grid has been named Industroyer, and it serves as a sobering reminder about the dangers faced by the Industrial Internet of Things (IIoT).
Published on September 05, 2017