EMC: Sync 'n' share not all about size, how you do it matters too
Missile-grade authentication to ensure users don't land data in danger
Microsoft's also making more noises about Office integration being an important feature, what with businesses being quite keen on collaboration. Dropbox is also starting to crank out stories about businesses incorporating sync 'n' share into their operations.
EMC's sync 'n' share brand, Syncplicity, is also trying to get more attention for how clever it is rather than just raw size.
The outfit probably wishes it could point to the very fine audit trails it services create as one reason it is a good idea for businesses who like the idea of sync 'n' share. That a fine case study of that feature is EMC suing its own employees after they put confidential data in their Syncplicity bit buckets before decamping to rival Pure Storage probably precludes using that in marketing material.
That effort advanced a little at EMC World today when the outfit announced it now offers “Storage Vaults”, a new feature that allows users to set policies that determine where a document will reside.
“Where” could be a particular storage appliance within the firewall or a cloud storage provider. In either case, Syncplicity reckons knowing just where your data lives is a good idea so you can take into account data sovereignty laws. That's a swipe at Dropbox, by the way, as it stores all files in the USA.
EMC has also added a new “two-man” authentication method for adding new storage resources it says is based on US military missile access regimes that require two operators to use the same authentication key and verify it against a key stored in a sealed envelope. This level of authentication is said to make it impossible for a third-party cloud storage provider to ever peek into a Syncplicity data store.
Also at EMC World, Syncplicity announced the Connector for SharePoint, which lets users of Syncplicity's mobile clients access data managed by Microsoft's heir-to-groupware. ®
Sponsored: Benefits from the lessons learned in HPC