Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 8 subscribers
  • Views 11023 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Security Advisor incorrectly identifies my phone encryption status

recursiveQWERTY
I'm using the mobile security app version 4.0.1435 (12) on my Nexus 6 and the security advisor identifies my encryption status incorrectly. The phone arrived with Lollipop 5.0.0 installed and encryption turned on by default. I'm currently rooted and running a custom ROM (Lollipop 5.0.2) but I haven't disabled the forced encryption and the device settings show the phone is encrypted. I'm curious about how the security advisor determines the encryption status - especially since it contradicts the other encryption status indications I have seen on my phone.
:1020127


This thread was automatically locked due to age.
  • 0
    A little more information:

    It seems that in order for security advisor to recognise that my phone is encrypted, I also need to set a pin, pattern, or password to be requested at startup.

    It seems that although device encryption is forced on new devices such as the Nexus 6, the need for a pin, pattern, or password at startup is not.

    Without the passcode requirement at startup, Security Advisor doesn't recognise that the device is already encrypted. The prompt given by security advisor to correct the problem forwards the user to the encryption setup in device settings. However, in this case that doesn't help in fixing what is actually preventing security advisor from recognising that the device is already encrypted.

    It would be helpful to know that security advisor requires this in order to have the encryption recognised and instead of forwarding to the encryption setup, forward the user to the screen lock settings instead.

    Is it possible to have this addressed in future versions of the app?
    :1020144
  • 0
    Having same problem. Just installed Sophos on HTC M9 with 5.1. Phone is encrypted, and requires pin code access. I know the phone is encrypted but I am directed to the phone encryption section.

    Slightly off topic I also get a warning that my wifi is insecure. I am on my home secured network, not sure what is indicating it is insecure. The 'Security Advisor' in this app needs some work.
  • 0

    Same problem here. Sophos Mobile Security 6.0.1789(15), Android 6.0.1, Kernel 3.10.73-ga12dd8b. 

    Thanks  for the tip about the pin number feature.

  • 0

    It is worth noting that even if you configure a screen lock pin in conjunction with encryption, if you subsequently enable an accessibility provider (for example the LastPass autofill feature) the encryption pin will be disabled and you receive this warning. This seems to be an issue in Android.

    code.google.com/.../detail