<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Multi Factor for Mobile apps in Industry News</title>
    <link>https://community.isc2.org/t5/Industry-News/Multi-Factor-for-Mobile-apps/m-p/1295#M141</link>
    <description>&lt;P&gt;It is important to remember to use an Application rather than a Text to receive the second factor for authentication.&amp;nbsp; There are too many exploits available for Text-based multi-factor.&lt;/P&gt;</description>
    <pubDate>Fri, 13 Oct 2017 20:50:28 GMT</pubDate>
    <dc:creator>BrianKunick</dc:creator>
    <dc:date>2017-10-13T20:50:28Z</dc:date>
    <item>
      <title>Multi Factor for Mobile apps</title>
      <link>https://community.isc2.org/t5/Industry-News/Multi-Factor-for-Mobile-apps/m-p/1238#M138</link>
      <description>&lt;P&gt;It is pretty common to use an app on your mobile phone for 2nd factor (Google Auth, OKTA, Microsoft).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is OK as long as we access the apps from a workstation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This changes when&amp;nbsp; more and more apps being accessed from the Mobile Phone so, how are security folks handling this situation&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Oct 2017 16:42:31 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Multi-Factor-for-Mobile-apps/m-p/1238#M138</guid>
      <dc:creator>Martinvj</dc:creator>
      <dc:date>2017-10-12T16:42:31Z</dc:date>
    </item>
    <item>
      <title>Re: Multi Factor for Mobile apps</title>
      <link>https://community.isc2.org/t5/Industry-News/Multi-Factor-for-Mobile-apps/m-p/1275#M139</link>
      <description>&lt;P&gt;You must complete a risk-based analysis based upon the users, risk appetite, the organisation in question and the data secured.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This may include considerations such as;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;- the classification level of the data&lt;/P&gt;&lt;P&gt;&amp;nbsp;- results of the organisation's risk assessments&lt;/P&gt;&lt;P&gt;&amp;nbsp;- any regulatory requirements governing data&lt;/P&gt;&lt;P&gt;&amp;nbsp;- the security maturity of the organisation&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Once this has been completed it's findings should be used to implement an overall policy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Users handling secure data may be disallowed to use mobile phone's at all. Most capable multi-factor authentication systems allow policies that can restrict the ability to install the application on a mobile phone.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Some organisations have granular control, over their user's devices, with a Mobile Device Management applications. In this scenario, it may be prudent to allow corporate users to use their work's mobile phone for authentication with a phone application.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Others may even allow personal mobile phones; if the data handled is not classified or the risk is low.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Oct 2017 14:37:58 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Multi-Factor-for-Mobile-apps/m-p/1275#M139</guid>
      <dc:creator>sdurbin</dc:creator>
      <dc:date>2017-10-13T14:37:58Z</dc:date>
    </item>
    <item>
      <title>Re: Multi Factor for Mobile apps</title>
      <link>https://community.isc2.org/t5/Industry-News/Multi-Factor-for-Mobile-apps/m-p/1295#M141</link>
      <description>&lt;P&gt;It is important to remember to use an Application rather than a Text to receive the second factor for authentication.&amp;nbsp; There are too many exploits available for Text-based multi-factor.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Oct 2017 20:50:28 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Multi-Factor-for-Mobile-apps/m-p/1295#M141</guid>
      <dc:creator>BrianKunick</dc:creator>
      <dc:date>2017-10-13T20:50:28Z</dc:date>
    </item>
    <item>
      <title>Re: Multi Factor for Mobile apps</title>
      <link>https://community.isc2.org/t5/Industry-News/Multi-Factor-for-Mobile-apps/m-p/3121#M318</link>
      <description>&lt;P&gt;We used MDM to push certs to a phone - that's a what you have. Access to the phone is PIN or fingerprint (what you know or what you are) so it's 2 factor. Application being accessed is cert required. This wasn't an easy path to do this, getting certs to work with some apps isn't easy.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Nov 2017 11:20:07 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Multi-Factor-for-Mobile-apps/m-p/3121#M318</guid>
      <dc:creator>Jay_Scheiner</dc:creator>
      <dc:date>2017-11-01T11:20:07Z</dc:date>
    </item>
  </channel>
</rss>

