InformationWeek: The Business Value of Technology

InformationWeek: The Business Value of Technology
e2 Conference & Expo - Boston 2013
= Member Content
Facebook Twitter Share

E-mail | Print | Permalink | LinkedIn | RSS

FAA Promises Privacy Standards For Domestic Drones


As law enforcement and civilian use of unmanned aerial drones increases, surveillance fears mount.




Military Drones Present And Future: Visual Tour
Military Drones Present And Future: Visual Tour
(click image for larger view and for slideshow)
The Federal Aviation Administration Thursday announced that it will publicly develop privacy policies to cover the use of unmanned aerial vehicles (UAVs), more often referred to as drones, in U.S. airspace.

"The FAA recognizes that increasing the use of [drones] raises privacy concerns," according a letter the agency sent this week to Marc Rotenberg, president of civil rights group Electronic Privacy Information Center (EPIC). "The agency intends to address these issues through engagement and collaboration with the public."

Privacy concerns surrounding the use of drones in American airspace have been intensifying since President Obama signed the FAA Modernization and Reform Act (FMRA) into law in February 2012. The law includes the requirement that the FAA work toward "integrating unmanned aircraft systems (UAS) into the national airspace system (NAS)," and commence a test program at six different test ranges.

[ How will Obama's cybersecurity directive affect you? See White House Cybersecurity Executive Order: What It Means. ]

After FMRA was signed into law, numerous consumer, technology and civil rights groups -- including the American Civil Liberties Union, Center for Democracy and Technology, Electronic Frontier Foundation, and EPIC -- wrote to the FAA administrator, demanding that the agency develop privacy standards to cover the use of drones in U.S. airspace. "Drones greatly increase the capacity for domestic surveillance," they wrote, noting that the devices could carry not just high-resolution video cameras, but also infrared cameras, heat sensors and automated license plate scanners, and be programmed to track dozens of targets.

"Drones present a unique threat to privacy," they wrote. "Drones are designed to undertake constant, persistent surveillance to a degree that former methods of aerial surveillance were unable to achieve."

One year later, the FAA has responded, noting that as its test program moves forward, it will solicit comments on the privacy language to be included in its forthcoming UAV directive, which will govern the activities of all test site operators, and become the blueprint for general drone use across the country.

"Test site operators will be required to establish a privacy policy that is public, and builds confidence and trust," according to an FAA notice released Thursday, "Furthermore, the FAA expects that the information gathered about UAS operations at the test sites will contribute to the dialogue among privacy advocates, policymakers and the industry about how to address broader questions relative to the technologies used."

Aviation experts expect to see continuing drone uptake -- by hobbyists, businesses, law enforcement agencies and more -- in the future, and some have estimated that 30,000 new drones could be launched in the next decade. Already, low-end devices can be had for $300, programmed with GPS coordinates and left to fly themselves.

Civilian drone makers are touting their vehicles as a platform for handling "dull, dirty and dangerous" jobs. "In a world of Google maps, the advantage of aerial views of the world are clear, but satellites and manned aircraft are expensive and the pictures they take are often too far away or too infrequent to be useful," wrote former Wired editor-in-chief Chris Anderson, who's CEO of 3D Robotics and the founder of DIY Drones, last month in Time magazine. "Drones can get better views, more often. And those shots can be of exactly what you want to see -- an anytime, anywhere eye in the sky, controlled by you, not The Man."

The military continues to invest heavily in new drone technology. NASA, meanwhile, predicts that UAVs may one day account for a sizeable number of the commercial aircraft operating in U.S. airspace.

But security and privacy concerns have long accompanied the use of drones. Last year, for example, security researchers demonstrated that with about $1,000 worth of equipment, they could spoof the GPS signals used by civilian drones and redirect a drone one kilometer (0.6 miles) away. The researchers said they're working this year toward intercepting a drone from 10 kilometers (6 miles) away.

UAVs developed for military use, which may also be sold to police forces, aren't exempt from such concerns. Notably, Iran in 2011 claimed to have captured a U.S. military drone by jamming its remote-control communications channel. Since then, Iran said it's been reverse-engineering the captured RQ-170 Sentinel and developing its own drone fleet.

Drone transmissions can also be intercepted. In 2008, for example, "U.S. military personnel in Iraq ... apprehended a Shiite militant whose laptop contained files of intercepted drone video feeds," reported The Wall Street Journal. The insurgents reportedly used a $26 piece of software to hijack the drone camera feeds.

Despite that known vulnerability, by October 2012 only 30% to 50% of all military UAVs -- including widely used Reaper and Predator drones -- were broadcasting encrypted footage, Wired reported.

Federal agencies must eliminate 800 data centers over the next five years. Find how they plan to do it in the new all-digital issue of InformationWeek Government. Download it now (registration required).

Attend Interop Las Vegas May 6-10, and attend the most thorough training on Apple deployment at the NEW Mac & iOS IT Conference. Join us in Las Vegas for access to 125+ workshops and conference classes, 350+ exhibiting companies, and the latest technology. Register for Interop today!




InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS


Advertisement


InformationWeek Reports

report Cloud Implementer's Checklist
Once your agency has completed the business case for a private cloud, how do you actually move ahead with your data center transformation? Our report provides a practical set of steps to get you there, including a "to do" list that will be helpful to anyone on your IT team who's involved in the project. By the time you're done, your data center should be home to a more flexible, on-demand IT services.

report Cloud Compliance in Government
Compute clouds created for government data centers must adhere to a range of specifications designed to support data and system security, privacy, and governance. FISMA, HIPAA, SOX, and SAS 70 are just some of the requirements that have to be taken into account as federal IT pros deploy a shared-services cloud model. In this report, we identify the key specs that need to be factored into any federal cloud architecture.

report Government Cloud Platform Strategy
This report analyzes the key IT infrastructure considerations that must be taken into account for implementing cloud services in federal data centers: software/hardware environment, multi-tenancy, security, virtualization, and management tools. We also explain the key important role that APIs play in supporting hybrid scenarios that tap into public cloud services.

report The Business Case for Government Clouds
This report assesses usage scenarios, barriers, and other variables that factor into the decision of whether and how to implement cloud computing in federal environments.