Office365 users shared hundreds of sensitive docs publicly through docs.com
arstechnica.com
arstechnica.com
"Public on the web Anyone can find it on the web. Search engines will find the doc, giving it a larger audience."
It's not unambiguous. It's very clear. The only way you can't tell what it's doing is if you just pay no attention whatsoever to what you're doing. It's not the default sharing method from either Office 365 (web, traditional or Android/iOS) or OneDrive. You have to opt into using it at all at an IT department level if you have a corporate Office 365 department. You really just can't stop users from footgunning themselves when they're on the open Internet.
It is very clear, to you. To me. To other people? The evidence doesn't support that claim.
So again: was it clear enough? Apparently not.
You can argue about this as long as you want, but interpretation of an interface is not complete until you get the context. Ours is that of someone who's either looking for it, or aware of the possibility of its existence.
If you're neither, perhaps you'd need to be able to see other people's documents as well. Perhaps you need a big ol' warning sign with tick-boxes before you dismiss it.
Maybe the default should be hidden, and sharing made optional. I realise this doesn't make much sense for a "sharing" feature, but maybe it's been labelled wrong. "Sharing" doesn't necessarily (read: "by definition") mean "everyone in the whole world can browse your stuff".
So imo, two parties to blame.
Yes. It's the user's own fault.
No. It's not clear enough.
I'm not sure that's clear? The headline says "hundreds" of sensitive documents are on there. How many documents are on there total?
As for the design here - how about a big red banner with "by ticking here this document will be available to the public and can be found through search engines" or similar?
While they should be able to react quickly, I'm also sure that they have to switch to "able to react quickly mode", and won't always be ready to launch missiles at the push of a single button!
Acceptable defect rate is the defect rate that does not result in an Ars article pointing out the defect rate of your product.
Apparently, for a document uploading service, this case shows an example that's below the acceptable rate.
See it this way; you don't want someone to accidentally trigger a nuclear bomb even once. However you probably don't care that a knife sometimes cuts a finger.
People often assume a level of security at work that doesn't match reality.
Please upload a document to host publicly for anyone on the internet.
Assuming a particular number of users are going to be too stupid, careless or rushed to set the privacy option, I think I'd err on the side of caution. What's worse: Not having the document available to all, but accessible by the link? or having the document available to all and the link unwittingly?
It is of course the users fault, but that doesn't mean the devs can't take extra steps when a flaw is pointed out.
Some people would benefit from more safety features but nobody wants to ride in a car with a full roll cage and a helmet.
Funny you should bring up auto safety when we've now got at least 4-6, and sometimes as many as 13 airbags in the average new car despite the fact they'll often never be used, and all because of the drivers. Certainly lane departure and collision avoidance systems aren't there for the people using vehicles properly.
You've just described a very common type of non-technical user.
As GP said, users got a very obvious warning. It's not like there was a 1000-word long essay greyed out which contained the words "oh and this is all public" in a random location. This isn't about how technical users are, it's just a user error that anyone could make. I would be extremely surprised if you told me that, for example, there are less than a hundred Google Docs with sensitive information that are publicly viewable. In fact, I would probably call anyone above the age of 20 a liar if they said that during their entire life they had never, ever shared something they didn't mean to share. Even when it comes to things we're very familiar with, like our own mouths, we sometimes share more than we intend to.
I think generally non-technical users are just pretty diverse, and I'd wager there's more non-readers than readers...
That said, in this case, I'm not sure what more MS can do beyond simply not offering this service.
Work in tech support, can confirm
A big one was the meaning of "everyone" in OneDrive. Many people thought that it meant "everyone on my team", and posted all sorts of wacky stuff.
No one in my building uses one drive, no one asked for one drive but Microsoft keeps trying to shove it down our throats. It feels like an anti-pattern like the forced windows 10 "upgrade" for home users.
According to word I have Office 365 ProPlus version - I note there is no option to save to docs.com.
I encounter many co-workers though who like to do things "the old way" and just email copies of documents around and then spend time merging them back together instead of sending a link to their OneDrive. Just more files for me to juggle on my computer. No thanks.
Partly because I need to access stuff offline so prefer to have a local copy. For example if I have to take my laptop travelling with between sites I may not have access to a internet connection.
Your right that a large part is familiarity - we use Sharepoint (which I also hate) to share documents between teams rather than email.
You missed the serious suckabe. 3 years ago you could put the sync client on a fresh install of Windows 8 and do nothing with it and it would break itself.
On https://docs.com/docscom the description of the service is "Docs.com by Microsoft is an Internet site for publishing Office documents that anyone can find, browse, and share". The only way this could be clearer is if the word 'anyone' was changed to 'anyone in the world'.
Finally, (for some license types) O365 offers precisely the kind of DLP capabilities that would let users use such a service while blocking the sharing of SSN's etc.
For business accounts, not only has someone actively turned on this capability, they have then failed to communicate its purpose to users. The users themselves have then failed to understand what they were doing.
I'm sorry, but while I can sympathise with people this is clearly not MS' problem.
For the record, my current employer (a university) has not enabled this function.
Even sophisticated users will misuse these services: remember the fad of putting all your dot-files on Github, when a bunch of people uploaded their Amazon credentials? This is giving the same opportunity to much less sophisticated users, with predictable results.
I doubt these people intended to share, in a publicly searchable form, copies of their tax forms, passports, medical records, client lists, etc.
It's easy to call the users careless or stupid, but that expectation should've been baked into the product. For a document to be indexed and publicly searchable should be an explicit setting, not a default.
That's beyond being a UX issue, it's just.. wrong. So wrong that I could see lawsuits from this issue.
It's also a class of bug that I really couldn't imagine happening outside of Microsoft in terms of consumer software services from large-scale companies.
Here's a free idea for Google: Create a safety index service for saas stuff and then apply it to Chrome. I'd use it.
Apart from a "direct link" - who would want to go to docs.com and search for a topic?
I've been able to find lots of interesting documents searching for some medical, business and financial terms. There must be thousands if not tens of thousands of sensitive documents available...
Because it was designed for public sharing of documents and templates, and public sharing without discoverability sucks.
I don't know that there's a "social docs" brand, to figure out what it would call itself; but if MS exerted the minimal effort to understand its audience (which is required of any tech company that sells to domain experts who are more occupied with their work than what the workspace is configured to do), it wouldn't take them long to figure out how to pitch things to those users to accomplish whatever it is they're trying to do.
In the past an insecure shortcut was a unsecured and unaudited consumer grade network-share sitting somewhere on a lan, today it and Internet facing cloud service designed for publication used to collaborate on "internal only" document that should not even have been viable to the entire company.
It's not that the cloud is "insecure" but that it makes it way to easy for those who should not make IT decisions to turn to shadow IT solutions in order to avoid having to adhere to cumbersome bureaucratic processes and corporate governance frameworks and "get stuff done".
Dammit.
If they absolutely want to go the idiotic route of public-by-default, a 'private'/'public switch might be too noisy; a 'create new document'/'create new private document' too redundant... Honestly, I don't see why they would want to go that route anyways. The model is practically handed to them on a silver platter; most users want to keep docs private, unless and until they wish to have a document pool for sharing (easy to build infrastructure for), explicitly share single docs (again, just add a 'share' button and people get it), or make it publically accessible (i.e. "post" or "publish" to a platform.)
As I said in another comment here - everything gets explained away once you assume MS' incompetence in things. (I mean for god's sake, there are so many other solutions in this space that they have all the hard thinking be done for them!)
I would guess this is less of a technical or UI design problem and more of a branding/product concept/positioning problem, i.e., (some) people don't seem to understand the overall concept of the product, possibly because of the name
I can belive the reinvented claim (that's the kind of thing a new, good CEO can influence), but quality goes very deep, into each employee. Any one hire can screw up fatally. It takes a lot of hard work to build a security conscious culture/company hierarchy.
(Edit: Hello Redmond people!)
It's far safer to operate on the assumption that MS is just through-and-through incompetent at this point than try and pinpoint the cause of any one problem in a long history of them. I gave up on them around the mid-IE days (think I might've been particularly miffed when they scrapped the Courier concept) but I haven't looked back and haven't regretted it since.
(Well, I doubt it, but there's at least a theoretical chance, right?)
If the code's retired, it could just as easily be because some inferior process led by devs without the proper guiding vision just swapped it out for some overengineered platform they 'know how to code in better' that's being hailed as the future of such-and-such that doesn't reimplement nearly as completely or robustly features that people had come to expect, and is less stable to boot. ("Secure time" [0] anyone?) But hey, just spitballing here.
MS is like the Hammer Industries of our world; never rely on Hammertech. Though I guess as long as they keep enough enterprise dinosaur contracts they'll keep limping on like Hammer too. shrug