{"id":9642,"date":"2018-11-06T10:37:19","date_gmt":"2018-11-06T09:37:19","guid":{"rendered":"https:\/\/beispielwebsite.com\/allgemein\/what-does-byod-bring-your-own-device-mean\/"},"modified":"2026-04-30T23:21:10","modified_gmt":"2026-04-30T21:21:10","slug":"what-does-byod-bring-your-own-device-mean","status":"publish","type":"post","link":"https:\/\/www.virtual-solution.com\/en\/blog\/what-does-byod-bring-your-own-device-mean\/","title":{"rendered":"What does BYOD – Bring Your Own Device – mean?"},"content":{"rendered":"
\n
\n
\n
\n
\n

What is behind the abbreviation BYOD<\/a>? The revolution in the workplace or just the next security loophole? Read on to find out what it’s all about and the advantages and disadvantages of this model. <\/strong><\/p>\n

 <\/p>\n

What does BYOD – Bring Your Own Device – mean?<\/h2>\n

“Bring Your Own Device”,<\/strong> or BYOD for short, describes the possibility for employees to use private mobile devices such as laptops, tablets and smartphones for work purposes. In addition to the abbreviation BYOD, terms such as BYOT <\/strong>(“Bring Your Own Technology”) or BYOA <\/strong>(“Bring Your Own Application”) are also commonly used to describe a similar model. However, it is always about the use of private resources for business purposes. The diversity of terms on this topic also reflects the diversity of opinions, possibilities, opportunities and risks of this way of working. Companies can use their organizational guidelines to determine how private end devices can and may be used to access company data or internal networks. The advantage of BYOD is that it gives employees a great deal of freedom of choice, which takes personal needs into account. On the other hand, the own device at work model is associated with security risks, as internal company data is used on external devices. <\/p>\n

 <\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n
\n
<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
\n

Basic requirements for BYOD<\/h2>\n

In order to create the right framework conditions, BYOD can be viewed from two perspectives <\/strong>, that of the company and that of the user. The basic requirements for a good BYOD model can be described in seven steps<\/strong>: <\/p>\n

    \n
  1. Data protection<\/a><\/li>\n
  2. Application software<\/a><\/li>\n
  3. Operating system<\/a><\/li>\n
  4. Hardware<\/a><\/li>\n
  5. Physical security<\/a><\/li>\n
  6. Processes and safety awareness<\/a><\/li>\n
  7. Areas of responsibility, organization and policies<\/a><\/li>\n<\/ol>\n

     <\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

    \n
    \n
    \n
    \n

    1. data protection<\/h3>\n

    Companies should always determine how and whether company-related data can and should be stored on a device, especially if it is a private device. It is important that the company is responsible for ensuring the protection of company data, even if the data is stored or processed on private devices. Encryption is an important aspect here. It must be ensured that the data is encrypted on the mobile device and during transmission. In addition, it has been clear since the GDPR<\/a> came into force that private and business data must be strictly separated. <\/p>\n

    <\/div>\n

    2. application software<\/h3>\n

    The company must specify which applications and apps may be used to access company data. For example, it should be ensured that employees only have access to the infrastructure via a secure browser. The so-called container principle goes one step further. This uses a container app that provides a secure area on the mobile device for company data. This means that there is no interaction with data or applications outside this protected area. One such application is SecurePIM<\/a>. It must also be ensured that employees only use applications for their work that the company has licensed. Otherwise, this would be a violation of copyright law. <\/p>\n

    <\/div>\n

    3rd operating system<\/h3>\n

    To ensure further security within the BYOD model, the operating systems of the devices should always be up to date. The updating of private devices that move within the company network is usually the responsibility of the users. For this reason, it makes sense to sensitize them to always keep their applications and operating systems up to date. With the help of solutions such as SecurePIM or a mobile device management<\/a> system, these updates can be enforced and are therefore on the safe side. <\/p>\n

    <\/div>\n

    4. hardware<\/h3>\n

    Companies should think about whether they only allow certain devices to be used in the BYOD concept or leave the employee full freedom. Consideration should also be given to which security mechanisms are specified for the hardware (e.g. password policies or encryption mechanisms). It is particularly important to ensure that usability does not suffer too much from the security measures. <\/p>\n

    <\/div>\n

    5. physical security<\/h3>\n

    In addition to security in the use and transfer of data, the security mechanisms for physical access to the system must not be neglected. This includes, for example, the prohibition of transferring company data to external storage media. While the interface can simply be blocked on company-owned devices, within the BYOD framework, user awareness or an MDM policy must be used or only certain applications (such as a container app) must be approved for access to company data. <\/p>\n

    <\/div>\n

    6. processes and safety awareness<\/h3>\n

    As already mentioned several times, security awareness is an important component of a successful BYOD concept. Without the willing and reliable cooperation of employees, the success of a BYOD model is inconceivable. However, good security processes are also an important measure. These should include an option for remote data deletion and logging on and off within the BYOD system. <\/p>\n

    <\/div>\n

    7. areas of responsibility, organization and policies<\/h3>\n

    Of course, the areas of responsibility must also be clearly defined. The definition of a BYOD company policy is also essential. Possible framework conditions for such a BYOD agreement follow in the next paragraph. <\/p>\n

     <\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

    <\/div>\n
    \n
    \n
    \n
    \n

    BYOD agreement<\/h2>\n

    Since employees can use their private devices during working hours, an agreement should be made in advance. This should include the following points: <\/p>\n