{"id":32,"date":"2012-09-07T17:09:00","date_gmt":"2012-09-07T17:09:00","guid":{"rendered":""},"modified":"2022-04-06T20:23:29","modified_gmt":"2022-04-06T20:23:29","slug":"byod-program-controls-requirement-ii","status":"publish","type":"post","link":"http:\/\/mayanktrivedi.net\/technotes\/2012\/09\/07\/byod-program-controls-requirement-ii\/","title":{"rendered":"BYOD Program & Controls Requirement – II"},"content":{"rendered":"
\n
As I wrote the previous Post – BYOD Program & Controls Requirement<\/a> I received the comment on WFH, but I am certainly not covering that in this article, as that is a separate topic of discussion. What is more interesting that broke out as a discussion point with a colleague over a cup of coffee.  The discussion actually presented a counter argument to the Jump Server configuration.  <\/span><\/span><\/div>\n

<\/span><\/span><\/div>\n
While in the discussion, I was very much inclined to and well still am that an organization as the first step to BYOD program should define the set of machines that they would allow.  It is pretty much important for the organization to define whether they are going to allow.  The Deep Dive on the topic reveals that the selection of devices would prompt additional thought process or should I say depending on the Support Strategy for the BYOD program the organization needs to define what devices would be allowed.<\/span><\/span><\/div>\n

<\/span><\/span><\/div>\n
The various strategies would revolve around user experience v\/s technological deployments. If an organization would like to restrict user experience and go with technological deployments that would ensure Data Security and related controls, the organization would then need to restrict the BYOD to Laptops and Desktops (may be or when its WFH). In this case the controls would be around the set of controls that have already been discussed in the previous post as mentioned above.<\/span><\/span><\/div>\n

<\/span><\/span><\/div>\n
In case the organization would select User Experience then the organization would need to ensure that they provide support to any device and enhance the Mobility aspect of the user.  This decision however needs to be based on the following decisions – <\/span><\/span><\/div>\n
<\/div>\n
    \n
  1. What applications would be supported for BYOD and what level of modifications \/ application changes would need to be carried out?<\/span><\/li>\n
  2. What level of Security would be needed to extend the support to the devices?<\/span><\/li>\n
  3. What would be the application support, would it be Browser based only or Client based with a part of the program sits on the client side<\/span><\/li>\n
  4. Would VPN security be extended to these Devices that would be supported?<\/span><\/li>\n<\/ol>\n
    There are many more questions that need to be answered for a Successful BYOD program. The Organization would additionally need to check if One Device One Number sort of Program be adopted or not. If the organization would decide to implement this program for increased mobility they need to ensure the Soft Phone Support. <\/span><\/div>\n

    <\/span><\/div>\n
    The BYOD Program as it seems is not actually an easy decision to take as the organization would require to answer many other questions and Specifically that would help them ensure mitigating Risks and meeting Compliance Requirements in Operationally Effective and Efficient Manner<\/span><\/div>\n

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

    <\/p>\n


    <\/span><\/span><\/div>\n
    <\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

    As I wrote the previous Post – BYOD Program & Controls Requirement I received the comment on WFH, but I am certainly not covering that in this article, as that is a separate topic of discussion. What is more interesting that broke out as a discussion point with a colleague over a cup of coffee.  The discussion …<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25,4,17,26,31],"tags":[],"class_list":["post-32","post","type-post","status-publish","format-standard","hentry","category-data-confidentiality-integrity-and-availability","category-data-privacy-and-protection","category-governance-risk-and-compliance","category-information-security-controls","category-information-security-risks","entry entry-center"],"_links":{"self":[{"href":"http:\/\/mayanktrivedi.net\/technotes\/wp-json\/wp\/v2\/posts\/32","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/mayanktrivedi.net\/technotes\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/mayanktrivedi.net\/technotes\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/mayanktrivedi.net\/technotes\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/mayanktrivedi.net\/technotes\/wp-json\/wp\/v2\/comments?post=32"}],"version-history":[{"count":2,"href":"http:\/\/mayanktrivedi.net\/technotes\/wp-json\/wp\/v2\/posts\/32\/revisions"}],"predecessor-version":[{"id":173,"href":"http:\/\/mayanktrivedi.net\/technotes\/wp-json\/wp\/v2\/posts\/32\/revisions\/173"}],"wp:attachment":[{"href":"http:\/\/mayanktrivedi.net\/technotes\/wp-json\/wp\/v2\/media?parent=32"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/mayanktrivedi.net\/technotes\/wp-json\/wp\/v2\/categories?post=32"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/mayanktrivedi.net\/technotes\/wp-json\/wp\/v2\/tags?post=32"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}