<?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 Protecting mobile accessible content in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/protecting-mobile-accessible-content/m-p/263036#M216166</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Quick question regarding security of content via mobile.&amp;nbsp; Once a user has downloaded content onto the device, e.g to view in QuickOffice, it is then outside the control of an organisation, e.g. if the user loses their device then the content could reasonably easily be accessed if found by a malicious party.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;A lot of organisations want to make their content available to their users, but don't want the risk of sensitive data being lost or stolen if the device gets lost. Are there any standard ways of securing content downloaded from the Alfresco Mobile app so that the information cannot be accessed by an unauthorised user?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Steven&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Apr 2012 16:24:51 GMT</pubDate>
    <dc:creator>steven_okennedy</dc:creator>
    <dc:date>2012-04-25T16:24:51Z</dc:date>
    <item>
      <title>Protecting mobile accessible content</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/protecting-mobile-accessible-content/m-p/263036#M216166</link>
      <description>Hi,Quick question regarding security of content via mobile.&amp;nbsp; Once a user has downloaded content onto the device, e.g to view in QuickOffice, it is then outside the control of an organisation, e.g. if the user loses their device then the content could reasonably easily be accessed if found by a malic</description>
      <pubDate>Wed, 25 Apr 2012 16:24:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/protecting-mobile-accessible-content/m-p/263036#M216166</guid>
      <dc:creator>steven_okennedy</dc:creator>
      <dc:date>2012-04-25T16:24:51Z</dc:date>
    </item>
    <item>
      <title>Re: Protecting mobile accessible content</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/protecting-mobile-accessible-content/m-p/263037#M216167</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Steven&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm sure you're aware that the primary way of securing iPhones and iPads is to set an alphanumeric passcode that must be entered each time the device is woken up. That, coupled with the "wipe after 10 bad attempts" setting is usually OK.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In v1.3 of the app, due out in the Summer (there will be a 1.2.2 maintenance release before then) you'll be able to set the built-in iOS "security flag" which automatically encrypts documents when the device is locked. This stops people using apps such as PhoneView from having access to content via USB.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Apr 2012 16:32:06 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/protecting-mobile-accessible-content/m-p/263037#M216167</guid>
      <dc:creator>mikeh</dc:creator>
      <dc:date>2012-04-25T16:32:06Z</dc:date>
    </item>
  </channel>
</rss>

