| Solutions | Automatic File Self-Destruction capabilities | Data Storage Location | Encryption Method Employed | Strength of Encryption | Login Authentication required | Data recovery in the event of mobile device loss | Access control based on data confidentiality level required | Possible Treats/ Vulnerabilities |
1 | Safe for Huawei | No | Mobile device | Huawei HiSilicon chips | AVERAGE | Yes | No | NO | -Sniffing -Reverse engineering -loss of confidential data due to mobile device loss. |
2 | Samsung Android Mobile Device Security | No | Mobile device | AES 256 | AVERAGE | Yes | No | NO | -Insufficient Authorization and Authentication Controls -Sniffing -Loss of confidential data due to mobile device loss. |
3 | Google cloud storage | No | Cloud | AES 256 | HIGH | Yes | Yes | NO | -Insufficient Authorization and Authentication Controls -Sniffing -Remote code execution -privilege escalation |
4 | Microsoft OneDrive | No | Cloud | AES 256 | HIGH | Yes | Yes | NO | -Sniffing -Insufficient Authorization and Authentication Controls -Remote code execution -privilege escalation |
5 | Signal | No | Cloud | Signal protocol | HIGH | Yes | No | NO | -Insufficient Authorization and Authentication Controls -Sniffing -Reverse Engineering |
6 | CoverMe | No | Mobile device | AES 128 and AES 256 | AVERAGE | Yes | No | NO | -Reverse Engineering -Client Code Security -Insecure communication -Loss of confidential data due to mobile device loss. -Sniffing |
7 | Secret Box | No | Mobile device | AES 256 | AVERAGE | Yes | No | NO | -Sniffing -Reverse Engineering -Loss of confidential data due to mobile device loss. |
8 | Crypt4All | NO | Mobile device and cloud | AES 256 | AVERAGE | YES | YES | NO | -Reverse Engineering -Client Code Security -Loss of confidential data due to mobile device loss. |