Facebook’s Data Problem: A Few Simple Steps to Avoid the Same Fate
If you’ve read the news lately, you’ve probably caught a clip or two — or fifty — relating to the largest social media network in the world’s recent problem. Because it relates to user data, it immediately stood out to me.
In case you missed it: here’s the official version from the New York Times. In short, the federal government and state prosecutors here in the US, along with politicians in Europe, have begun calling for answers. They want to know how user data has been handled by the network, and, just what data the network has to access and share. There are concerns. There are questions and there’s a great need for answers.
While the focus currently lies on Facebook, it might just be the beginning of the story, the first (and most obvious, largest) target in something that might have larger ramifications. As privacy laws continue to expand, security breaches continue to take down even the most “secure” systems and individuals become more and more educated and concerned about what privacy is, and how their data is used, investigations like this might continue to expand as well.
The Solution is Multi-Faceted
Obviously, preventing similar concerns from arising within your own organization and among your customers requires more than a “quick” fix. But, I think there is a way to start moving toward the right direction as far as easing concerns about the way you work with data goes. Some of it starts with principles that are near and dear to the Zerion team. These include:
- Transparency.
- Clarity.
- Careful research and team selection.
- Solution integrity.
Let Me Explain…
Let me go into what each of these means, and how, when used together, they could help you find balance between the data necessary for efficient operations and optimal levels of data security.
It all starts with transparency. Here at Zerion, that means being clear with our team members, and with our customers. We believe that when relevant information is accessible to those who need it, the results are generally positive. For you — as an organization that works with data, especially customer or user data — it means clearly sharing what data you use, how it’s stored and what purposes it is gathered for. When users and customers understand what is being shared with who, and where the limitations and boundaries lie, trust might slowly begin to grow, eliminating concerns that come from the unknown.
Clarity comes next. In some ways, transparency and clarity are similar, but, there are a few distinct differences worth noting. Clarity is a natural result of transparency. Clear guidelines for data collection ensures your customers, users and internal team members understand the purpose of the data you collect and how it should be used. It prevents misuse and creates a roadmap for moving forward in a way that protects everything. Clarity in data collection, usage and storage prevents miscommunication and misunderstandings that lead to the situation we’re seeing played out in real-time, with Facebook, right now.
Another foundational aspect of avoiding data-related crises, relates to the team involved in any solutions that involve data, from collection to reporting. When roles are clearly assigned internally, based on clearly established guidelines, the potential for misuse can begin to decrease. At the same time, working with an external provider team that has limited data access and understands that data security comes first — taking all applicable measures to accomplish this end — provides an extra layer of protection. The team you work with should be easy to communicate with and clear in what they can — and cannot — do with the data that should belong to your organization alone. If a “team” dynamic is missing or feels off, the provider may not be the right one for your needs.
Perhaps the most important aspect of ensuring the data your organization needs to function efficiently is secure is the solution you use to collect and manage that data. It seems obvious, but, today, many “security” features are misunderstood and taken for granted.
For instance — it’s easy to assume that data protected by a password is safe. However, without a second — even more secure — level of authentication, this is no longer the case. Far too many security features are assumed, when perhaps, more research is due. If a solution cannot boast — and explain — the way data is secured at all points in a given workflow, it may not be as secure as it seems. The integrity of the solutions your team works with should be examined closely to ensure the safeguards that matter most are actually protecting data as they should.
Now’s a great time to evaluate your current data solutions and whether the security measures and safeguards you have in place can truly prevent questions and concerns like those Facebook is currently facing. Where does your organization stand?
