Alan Liefting (talk | contribs) |
Submitting (AFCH 0.9.1) |
||
Line 1: | Line 1: | ||
{{ |
{{AFC submission||ns=2|u=FlippyFlink|ts=20190404031523}} <!-- Do not remove this line! --> |
||
'''Bring Your Own Device''' (BYOD) is a concept where people use a device which is not owned by the [[service provider]]. |
'''Bring Your Own Device''' (BYOD) is a concept where people use a device which is not owned by the [[service provider]].<ref>[http://www.pcworld.com/businesscenter/article/246760/pros_and_cons_of_bringing_your_own_device_to_work.html BYOD on pcworld.com]</ref> |
||
'''Bring''' refers to physically brining the device to the location where the service is provided. But more importantly, it means connecting to the service, regardless of the location. |
'''Bring''' refers to physically brining the device to the location where the service is provided. But more importantly, it means connecting to the service, regardless of the location. |
||
Line 8: | Line 8: | ||
Services include internet, internal, email/calendar/contacts, (work) network, a voip application, etc. |
Services include internet, internal, email/calendar/contacts, (work) network, a voip application, etc. |
||
A common form is when employees bring their own devices (to work) to access their work email (incl. [[E-mail_attachment|attachments]]), calender and contacts. |
A common form is when employees bring their own devices (to work) to access their work email (incl. [[E-mail_attachment|attachments]]), calender and contacts.<ref>[[Mobile application management#The Mobility Invasion and .E2.80.98BYOD.E2.80.99|The mobile invasion]]</ref> |
||
Businesses that fall under compliancy rules such as [[Payment_Card_Industry|PCI]] or [[HIPAA]] must also comply when using the BYOD concept. But defining and enforcing an [[acceptable use policy]] may be tricky on devices which are not owned by the service provider. |
Businesses that fall under compliancy rules such as [[Payment_Card_Industry|PCI]] or [[HIPAA]] must also comply when using the BYOD concept. But defining and enforcing an [[acceptable use policy]] may be tricky on devices which are not owned by the service provider. |
||
With [[Mobile Device Management]] (MDM) and [[Mobile application management|Mobile Application Management]] (MAM) the service providers (partially) manage the devices. Management may include: [[information security]] (e.g. [[antivirus]], [[encryption]]), remote [[backup]], remote wipe, application provisioning, etc. |
With [[Mobile Device Management]] (MDM) and [[Mobile application management|Mobile Application Management]] (MAM) the service providers (partially) manage the devices. Management may include: [[information security]] (e.g. [[antivirus]], [[encryption]]), remote [[backup]], remote wipe, application provisioning, etc. |
||
== References == |
== References == |
Revision as of 03:15, 4 April 2019
Bring Your Own Device (BYOD) is a concept where people use a device which is not owned by the service provider.[1]
Bring refers to physically brining the device to the location where the service is provided. But more importantly, it means connecting to the service, regardless of the location. Your Own refers to employees, contractors, students, etc. Devices include smartphones, tablets, laptops, etc. Services include internet, internal, email/calendar/contacts, (work) network, a voip application, etc.
A common form is when employees bring their own devices (to work) to access their work email (incl. attachments), calender and contacts.[2]
Businesses that fall under compliancy rules such as PCI or HIPAA must also comply when using the BYOD concept. But defining and enforcing an acceptable use policy may be tricky on devices which are not owned by the service provider.
With Mobile Device Management (MDM) and Mobile Application Management (MAM) the service providers (partially) manage the devices. Management may include: information security (e.g. antivirus, encryption), remote backup, remote wipe, application provisioning, etc.
References