January 31, 2020 Blog, Homepage, Insights, Pro Tips

You work hard to create engaging content, build trust, and cultivate a social following. But are you thinking enough about how you secure that trust? A Google search of “social media hack” will reveal a litany of stories that range from embarrassing to disastrous. “I’ve been hacked” is a club that nobody wants to join.

Here are three steps you can take to safeguard your social credibility:

  1. Stop Sharing Passwords!

😬 Sharing passwords is one risky SOP.

There is no way to tell who is responsible when a whole team uses a single password. And you have no control over who is accessing the account. This is especially problematic when you need to restrict access, say when an employee leaves the company.

The process of changing passwords and passing them along to everyone who needs to know is so tedious that people rarely do it. So you end up with a common password for perhaps years at a time.

Pro Tip: SocialFlow pricing is based on the number of social handles, not users. Client admins can easily add and remove access within SocialFlow to keep up with your ever-changing team. There is zero reason to share passwords for SocialFlow logins!

  1. Activate Two-Factor Authentication for ALL users

Two-factor authentication is becoming the norm to help users secure their sensitive data. Since a chain is only as strong as its weakest link, we strongly recommend that you require two-factor authentication for ALL of your social accounts, not just some of them. While not foolproof, two-factor authentication adds a powerful second point of verification to your login. There really is no good reason to allow people to be able to publish social content without first going through a two-factor authentication process.

Pro Tip: Activating two-factor for your SocialFlow account is quick and easy. And if you are a SocialFlow admin, you can easily require it for ALL users. Learn how.

  1. Tie Your Social Publishing to Your Company’s Single Sign-On System

You gain another level of security by using Single Sign-On, which involves tying your social publishing software to your company’s corporate identity system (this almost certainly the same system you use to log in to your company’s email). One fewer set of login credentials means fewer passwords for users, it automatically solves the problem that arises when an employee leaves the company. When a departing employee is “deprovisioned,” their email access is turned off, and then any applications that are tied in via SSO will also be turned off.

Pro Tip: SocialFlow integrates with multiple SSO solutions, including OKTA, Azure, and ADFS. If your team has not yet implemented SSO, please contact your SocialFlow account manager or support@socialflow.com.

 

 

Written by Maura Dailey