So, why is the iOS Outlook app so risky and possibly a security risk?

---

Who are "you guys"?

---

----


Edited 999 time(s). Last edit at 12:08PM by jdc.

I don't understand why you want an App to handle what the iOS already does very well.

---

C(-)ris
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Throwback Thursday Signature:

I don't understand why no one will answer my question?

---

Quote
C(-)ris
I don't understand why you want an App to handle what the iOS already does very well.

Who said I wanted to use it. Reread my OP.

---

I want to read where you got your info, so I can read it and make an educated answer?

Brown rice tastes delicious, and lots of other people agree, but by ex-wives brother's first girlfriend from 20 years ago said her mom's first husband told her that its risky to eat.

---

----


Edited 999 time(s). Last edit at 12:08PM by jdc.

Quote
Jerry®
So, why is the iOS Outlook app so risky and possibly a security risk?

Are you talking about this? [forums.macresource.com]

---

In tha 360. MRF User Map

I've been using it for the past few days. I like it better than any other iOS email app...except the stock Mail, which I just went back to.

Lack of integration with iOS contacts and calendar are huge drawbacks. Also, it seems to have picked up the name I use for Google, which is a nonsense name I made up, and now can't get rid of in every email I send from Outlook even though I changed it in Google.

Security issues? This I confess I'm not relatively worried about, given that I physically hand my credit card to unknown restaurant waitstaff on a regular basis.

This is what I posted several days back:

"Some businesses (especially sensitive) are blocking the app from its Exchange servers - both iOS and Android versions.

The main concern is that a cloud hosted system is storing the user credentials of individuals who use the application, and the cloud hosted system is temporarily holding copies of email messages and attachments.

Somewhat of a poor design choice for serious systems/users."


The app is great, feature and function-wise, but for real-world business and large entity use, it's too much of a liability, as-is, until some of the design changes. As I said, many are blocking the app from connecting with Exchange servers (I am), and anybody here shouldn't be surprised if one day you receive an error (and an automated email in your account Inbox) stating that the app is unable to connect - especially once more people are hip to this.

This is what an email from a serving blocking the app would send you:

Subject
Your mobile phone has been denied access to the server via Exchange ActiveSync because of server policies.

Body
Your phone won't be able to synchronize with the server via Exchange ActiveSync because of an access policy defined on the server.

Information about your mobile phone:
Device model: Outlook for iOS and Android
Device type: Outlook
Device ID: [removed]
Device OS: Outlook for iOS and Android 1.0
Device user agent: Outlook-iOS-Android/1.0
Device IMEI:
Exchange ActiveSync version: 14.1
Device access state: Blocked
Device access state reason: DeviceRule

Sent at 2/6/2015 8:53:14 PM to [removed].

---

You're wondering about a Microsoft product possibly being a security risk??????


Were you born yesterday or, did you come down in the last rainfall?

Quote
jdc
I want to read where you got your info, so I can read it and make an educated answer?

Brown rice tastes delicious, and lots of other people agree, but by ex-wives brother's first girlfriend from 20 years ago said her mom's first husband told her that its risky to eat.

I don't know about all that, but I still don't know if it's safe to reheat spinach. For the record, I do.

Forget I asked.

---

Not sure what you're missing Jerry, this pretty much sums it up:

Quote
onthedownlow
The main concern is that a cloud hosted system is storing the user credentials of individuals who use the application, and the cloud hosted system is temporarily holding copies of email messages and attachments.

With a normal email client, the email client interacts directly with your mail server. With the new version of Outlook (nee Acompli), you give your email credentials to "them" (the cloud service), the cloud service downloads your email and stores it on their servers, and the Outlook app accesses the email from the cloud service.

The concern is if you are ok with a third party having access to your email.

My general feelings are:

Agreeing to work with Microsoft is like agreeing to a dinner date with Hannibal Lechter. You might as well cover yourself in butter, roll in some spices and jump in the oven.

---

**************************************
MacResource User Map: [www.zeemaps.com]#

Quote
datbeme
I don't know about all that, but I still don't know if it's safe to reheat spinach. For the record, I do.

Well, that's clear as mud.

---

It is what it is.

Quote
C(-)ris
I don't understand why you want an App to handle what the iOS already does very well.

If your email is on an exchange server, Outlook in iOS is FAR superior to Mail/Calendar/Contacts! I figured that out within 10 minutes of using it.

~A

Hmmm, I wonder whether my company will allow this. They probably shouldn't given their new bent on 'information security'.

Quote
sekker
Hmmm, I wonder whether my company will allow this. They probably shouldn't given their new bent on 'information security'.

The default is to allow it.

Your IT guys have to be aware of the problem and change a setting on the Exchange server -- and it has to be a recent Exchange server -- to prevent it.

What you might ask yourself is whether it's appropriate for you as an employee to provide your confidential credentials and correspondence to third parties who won't assume any liability for their own misuse of that information or their disclosures to others.

---

Quote
Onamuji

Quote
sekker
Hmmm, I wonder whether my company will allow this. They probably shouldn't given their new bent on 'information security'.

The default is to allow it.

Your IT guys have to be aware of the problem and change a setting on the Exchange server -- and it has to be a recent Exchange server -- to prevent it.

What you might ask yourself is whether it's appropriate for you as an employee to provide your confidential credentials and correspondence to third parties who won't assume any liability for their own misuse of that information or their disclosures to others.

Good points.

If I could control what gets SENT to my inbox like I control what goes out, I'd have no worries!