Social-media bans miss the mark

Three reasonable steps could help agencies avoid categorical bans that undermine security and collaboration

White House spokesman Robert Gibbs recently noted that Twitter is blocked on White House computers. Later, news upstart Mediaite discovered that the new media team at the Old Executive Office Building could indeed access Twitter, but others on the White House staff do not necessarily share the same privileges.

The story serves as a cautionary tale for the rules governing social-media tools for the thousands of employees who work for the federal government.

Often without explanation or transparency, different agencies and even offices within agencies have different policies about the use of social-media platforms on the Web. Even when public affairs employees are allowed to use tools such as Twitter and YouTube to communicate, they are sometimes blocked by different authorities at work. So, in a gray area, they employ workarounds with personal laptop PCs, iPhones and the like.

Such internal contradictions cannot last long. As the average workforce age decreases and lines between the professional and personal increasingly blur, employees will demand greater access to such sites. Administrators might have legitimate reasons for blocking some of those sites, but the hodgepodge of rules is often confusing, which possibly makes the overall situation worse. I propose two arguments for not blocking most social-media sites on most government computers.

First, blocking social-media sites does little for safety and security. Saying that Twitter is blocked typically means that the domain Twitter.com is rendered inaccessible from a government computer. But there are simple mechanisms for alternatively accessing the underlying software. Twitter.com can be accessed from TweetGrid.com, YouTube.com from videos.google.com and so forth. Official computers can access the same sites through different portals, or employees might turn to nearly ubiquitous personal devices such as BlackBerrys to use social media during work hours — all of which is harder to monitor.

Second, blocking sites does little for government efficiency, transparency and citizen engagement. True, when used poorly, sites such as Twitter and YouTube are a distraction and a time sink. But the same can be said about phones, e-mail and even the cafeteria. When used responsibly, social media provides real-time information about critical news, helps employees working on similar topics within the government find one another, helps people better understand how technology is influencing overseas incidents such as the Iranian election protests, and serves countless other worthwhile functions. Blanket social-media bans let information fall through the cracks rather than getting it to people who could use it.

The government should take three reasonable steps. First, government information assurance analysts need to determine what security risks various social-media Web sites pose to the government. They should be assigned to categories such as "Use only on nonmilitary computers" or "Not for government system use."

Second, policies must be transparent, consistent and well-publicized throughout government — no double standards.

Third, employees and contractors must be educated about the positive and negative aspects of using social-media Web sites just as they are about other elements of cybersecurity and other government procedures.

Those three steps should counteract potentially less secure employee workarounds and go a long way toward a more open, transparent and participatory government.

About the Author

Mark Drapeau is director of public-sector social engagement at Microsoft. 

Featured

  • FCW PERSPECTIVES
    sensor network (agsandrew/Shutterstock.com)

    Are agencies really ready for EIS?

    The telecom contract has the potential to reinvent IT infrastructure, but finding the bandwidth to take full advantage could prove difficult.

  • People
    Dave Powner, GAO

    Dave Powner audits the state of federal IT

    The GAO director of information technology issues is leaving government after 16 years. On his way out the door, Dave Powner details how far govtech has come in the past two decades and flags the most critical issues he sees facing federal IT leaders.

  • FCW Illustration.  Original Images: Shutterstock, Airbnb

    Should federal contracting be more like Airbnb?

    Steve Kelman believes a lighter touch and a bit more trust could transform today's compliance culture.

Stay Connected

FCW Update

Sign up for our newsletter.

I agree to this site's Privacy Policy.