Many mistakes can happen when rolling out communication solutions. In this blog article, we explain what you need to look out for and what you should avoid at all costs.
Mobile workstations are no longer just the order of the day in companies, but also in the official environment and at authorities and organizations with security tasks (BOS). To enable employees to work on the move, they need modern Android or iOS devices and the corresponding communication and collaboration tools with functions such as email, calendar, messenger, contacts and document editing. These applications must be secure and, in an official environment, also meet all security standards such as VS-NfD (classified information – for official use only) and NATO RESTRICTED fulfill.
It is not uncommon for companies and authorities to use an MDM (Mobile Device Management) system to ensure that the communication solution on mobile devices always works perfectly and that the software is up to date. At least that’s the theory. In practice, unfortunately, there are always problems with a comprehensive, cross-platform and user-friendly rollout. We have identified the four areas with the greatest potential for error for you so that you can avoid these problems from the outset.
- TimingLengthy rollouts and delayed updates bring collaboration to a standstill because not all employees are on the same technical level and do not have access to the latest version of Messenger, for example. If they are then forced to switch to insecure alternatives, significant security risks arise.
- Logistics: In times of working from home and mobile working, it is extremely problematic if the rollout can only take place on site and the IT administrator has to update each mobile device individually. A communication solution is therefore needed that enables a location-independent rollout in real time on all mobile devices.
- Policy: IT use is subject to strict requirements in companies as well as in federal authorities, BOS and KRITIS companies. In addition to the GDPR, companies often have their own guidelines that they have to address and authorities have to meet requirements such as multi-client capability or rapid scalability. All of these guidelines and requirements must be taken into account during a rollout.
- SecuritySpecial security requirements apply for many authorities and BOS, up to the classification level VS-NfD. For example, data must be end-to-end encrypted both on the device and in transit. Furthermore, private and business data and applications must be strictly separated from each other and it must be regulated which employee information the IT department can view.
A solution that covers all these security aspects and at the same time offers numerous functions for ultra-mobile working is still of no use if the rollout is lengthy and complicated. Well thought-out rollout management is a must, especially for KRITIS companies and corporate divisions with special security standards. Cost-efficient and quickly deployable container solutions that ensure that private and business data are strictly separated from each other on the mobile device have proven their worth for implementation.
If authorities, BOS and KRITIS companies want to enable their employees to work securely and ultra-mobile in the future, there is no way around a modern communication solution that offers end-to-end encryption, VS-NfD approval and a highly automated, nationwide rollout. Ideally, this rollout should proceed as follows: The IT department stores the security rules for using the communication solution in the management portal in advance, the employee downloads the app from home from the AppStore onto the respective mobile device and can work productively with the solution immediately after logging in.