<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mobile on S3H.com</title>
    <link>https://s3h.com/tags/mobile/</link>
    <description>Recent content in Mobile on S3H.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://s3h.com/tags/mobile/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BYOD Policy Has Produced Security Problems Nobody Wants to Own</title>
      <link>https://s3h.com/2026/03/04/byod-policy-has-produced-security-problems-nobody-wants-to-own/</link>
      <pubDate>Wed, 04 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://s3h.com/2026/03/04/byod-policy-has-produced-security-problems-nobody-wants-to-own/</guid>
      <description>&lt;p&gt;Bring Your Own Device policies were adopted by enterprise IT organizations under pressure from employees and leadership who wanted to use their personal devices for work and did not want to carry two phones. The policies were designed hastily, implemented with tools that were not ready for the management requirements they needed to meet, and left in place with minimal review as the security landscape changed around them. The result is a policy category that most IT security professionals acknowledge as a significant exposure and most organizations decline to address because addressing it requires telling employees they cannot use their personal devices for work.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
