tl;dr – Customers should not worry about their Buffer data after the Cloudbleed incident
Several hours ago our team learned of a large security incident at Cloudflare, a service we use for Buffer. The incident, which you may have heard about, has been nicknamed “Cloudbleed.” Many websites, including Buffer, use Cloudflare to help handle web traffic more quickly and efficiently amongst many other things. Cloudflare has contacted us to share that Buffer is not one of the websites that they have discovered leaked data for.
After news like this, it’s a great opportunity to reflect on security and passwords in general. We take security seriously at Buffer and would like to share some helpful account security tips:
- Cycle your passwords every few months – Use a password manager like 1password or LastPass to make keeping track everything easier. ?
- Use strong, unique passwords – Avoid sharing passwords across multiple websites. Password managers can also help generate random, strong passwords. ? Vox recently created an awesome video explainer about this topic.
- Use two factor authentication when available – Using 2FA is an amazing way to add an extra layer of security to any account.
Feeling motivated to update your password or setup 2FA (aka 2-Step Login) on Buffer today? You can do that here. If you’re curious to read more about Cloudflare’s issue itself, check out their blog post.
Have a safe and secure weekend! ?
Try Buffer for free
140,000+ small businesses like yours use Buffer to build their brand on social media every month
Get started nowRelated Articles
Nine years ago, we decided to launch a new free product alongside Buffer. We called it Pablo, and it was a huge hit in our community. Within just seven months of its launch, half a million photos were created using Pablo. Similarly, we had the initial ideas for Stories Creator and Remix many years ago now. All three of these tools have been an important part of Buffer’s story. They’ve taught us lessons and helped us connect with a wider audience. In Pablo’s case, the idea for this tool happene
If you use Buffer, you might have experienced us having more downtime than usual recently. We want to start with an apology for not sharing more transparently along the way what’s been happening. We’ve been caught up in the work and haven’t invested enough in communicating with our community, and we’re so sorry about this misstep. We know some of our customers have had a frustrating time using Buffer recently and we need to do better by you. This past August and September were the months we’ve
As part of our commitment to transparency and building in public, Buffer engineer Joe Birch shares how we’re doing this for our own GraphQL API via the use of GitHub Actions.
