recommended reading

So What Exactly Is a 'Killer Robot'?

Flickr user Tasayu Tasnaphun

For as long as we’ve been able to make robots, we’ve been worried about them killing us.

In 1942, Isaac Asimov published a short story called Runaround that both coined the term "robotics "and introduced the idea of robots killing humans. Last week, one company set out to assure people that it, too, was worried about this potential threat. 

Clearpath Robotics announced that it would take a stand against killer robots. “To the people against killer robots: we support you,” the company’s press release reads.

Yes, the organized campaign against killer robots has gained momentum as the technology and militarization of robotics has advanced, and the smartest thing the movement has done is pick its name. “Killer robots” still isn’t a well-defined term, but it's clearly a winning one. 

Autonomous robotic systems have indeed come a long way since Asimov. Far enough that, in 2012, Human Rights Watch issued a report making the case against lethal autonomous weapons systems—weapons that can make lethal decisions without human involvement. Except they didn’t call them  “lethal autonomous weapons systems.” The title of the report was “Losing Humanity: The Case Against Killer Robots.”

Mary Wareham, coordinator of the Campaign to Stop Killer Robots, admits it was a bit much. “We put killer robots in the title of our report to be provocative and get attention,” she says. “It’s shameless campaigning and advocacy, but we’re trying to be really focused on what the real life problems are, and killer robots seemed to be a good way to begin the dialogue.” 

Ryan Gariepy, the chief technology officer at Clearpath Robotics, echoed Wareham: “It is a little bit sensationalist, and the engineer side of me thinks it’s a little bit not specific. But if that’s what society needs to address this issue, then that’s the way we’ll talk about it.” 

Naming weapons and missions like this isn’t new. The LGM-118A “Peacekeeper” was a missile that could carry up to 3,000 kilotons of warheads. Israel Aerospace Industries makes a missile named Gabriel, named for the angel. A 2006 Israeli mission to bomb South Lebanon was named Mivtza Sachar Holem, “Operation Just Reward.” When the United States invaded Iraq they called the program Operation Iraqi Freedom. Researcher Charles Kauffman argues that as our weapons get more and more powerful, our names for them get more and more demure, to soften the idea of the damage they could do. But if you’re in the market of making a weapon seem evil, “killer robot” is effective. 

But not everybody defines “killer robot” the same way. For Clearpath, a killer robot is a robot that can make a decision to use lethal force without human intervention. At Human Rights Watch, the definition is broadened to include any robot that can choose to use force against a human, even if that force isn’t lethal.

Really, there's reluctance to pin down a single definition, Wareham says. “In fact there was a push away from that.” That's at least in part because different organizations and agencies have distinct—and sometimes conflicting—goals about what discussion of killer robots might yield.

So while Human Rights Watch is seeking potential rules against “killer robots” that could regulate specific weapons, classes of weapons, weapons systems, or entire attack strategies, groups like Clearpath have to consider their clients—including both the Canadian and U.S. militaries. Once Clearpath hands over robotics technology to those governments, Gariepy acknowledges, the company has no control over how that technology is used. 

For now, this nebulous mass of robotic entities that could kill or harm humans has a name without a solid definition—but it’s a really smart name. After all, Wareham says, “no government wants to be seen as pro-killer-robot.”

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security


When you download a report, your information may be shared with the underwriters of that document.