This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

OWASP Robot Security Project

Jump to: navigation, search
OWASP Project Header.jpg

The OWASP Robotic Security Principles

The OWASP Robotic Security Project has the following principles:

I, Guy Huntington, have listed these principles below to get the discussion going. They aren't yet written in stone!


  • Each robot created, virtual or physical, will have a unique "Robot Identification Unit" (RIU)
  • The RIU will be unique to the robot from any other robot created in the past, present or future
  • Each RIU used will be instantly, globally checked to confirm its unique identity or, be issued by a recognized RIU issuing authority which can confirm its global uniqueness
  • The RIU must be able to show the robot is a robot
  • RIU's should be able to allow the robot to act anonymously, i.e. show the robot is registered but not reveal more details about the robot unless legal consent from its creator/owner is obtained
  • The RIU code repository will be secure
  • It won't allow for others to obtain the RIU and then masquerade as another or, allow a different RIU to be inserted into it to portray itself as another


  • Each robot created should be registered with a new age civil registration service
  • The process of creating a registered robot identity MUST be highly automated
  • The registration process must involve confirmation the robot identity being registered doesn't already exist in some other new age civil registration service on the planet
  • If the robotic registration process involves creation of a unique registered robotic identifier, then this must be securely passed back to the robotic creator/owner and then inserted into the RIU
  • Registration processes used by new age civil registration services MUST be the same to avoid potential robotic identity collisions as well as to easily provide global robotic registration from the local new age civil registration service

Change of Registration:

  • Any change of registration must follow globally accepted business and technical processes
  • A robot's RIU CANNOT be changed unless under specific legal direction using globally accepted legal, business and technical processes as set forth in laws and regulations

Robotic Termination:

  • Robotic termination should follow global laws and regulations pertaining to the termination of a robot
  • All robotic terminations should be registered with the local new age civil registration service
  • A robot who's created in Jurisdiction X that's terminated in Jurisdiction Y should have Jurisdiction Y doing a global search for the robot, determining it was created in Jurisdiction X and then automatically notifying Jurisdiction X of the termination

Other Robot Security Principles:

We need to insert here a detailed list of other robot security principles. These should detail out virtual and physical security principles for robots. The project must also address robots acting together in singularity.    


The OWASP Robotic Security Project is meant to create bottom up driven robot security standards applied globally. It includes robot identification, registration, change of registration, robot termination (and other robot security - we need to flesh this out).

With the advent of both virtual and physical robots, the number being created will shortly grow from millions to billions. They can and will easily cross existing nation state borders. The robots' actions will have legal implications ranging from contracts and operations through to personal interactions with people and/or other robots. This results in potential civil and criminal liabilities. Thus there is a need to legally register the identities of the robots, in a manner such that all jurisdictions are involved.

The potential aspect of malicious people, organizations or states taking advantage of a robot must be addressed. This ranges from identity, consent, data to potential operation of the robot. It also must include cloud based security for the robot. Thus, global security best practices need to be developed regarding robotic security.

This project is results driven. Thus, it starts with robot creation through to termination, generating practical code and business practice security which industry can readily adopt with new laws and regulations referencing them.

Since technology changes very quickly, the security principles and best practices also needs to be designed to rapidly change. Thus, the robot security project is creating a framework with which to then rapidly change as and when required.

We invite interested parties to join us!


TBD based on our activities.

The OWASP Security Principles are free to use. In fact it is encouraged!!!

The OWASP Security Principles are licensed under the Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.

What is OWASP Robotic Security Principles Project?

It's a group of industry, government, security and privacy experts wanting to establish bottom up driven robot security standards. These range from robot creation, identification, registration and termination standards through to operational security (we need to flesh this out).


Project Leader

  • Guy Huntington
  • Hopefully there will soon be more leaders for each subject!

Related Projects

  • What should we link to?


Quick Download


The home of the OWASP Security Principles is on GitHub. You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.

However, if you like you may also download the master repository from the following links:

News and Events


In Print




New projects.png Owasp-builders-small.png
Project Type Files DOC.jpg


How can I participate in your project?

All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

If I am not a programmer can I participate in your project?

Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, beyond the programmer, technical and security folks we are looking for people with skills sets in legal, government and privacy.


Thanks JIM!!!!!!

The first contributors to the project were:

  • Jim Manico

We need to hash this out as a team

Define Robot's Security Area

  • define a robot
  • define robot's security layer
  • define attack surface
  • define attack vector
  • make threat modeling

Make a Security Guideline(interface, communication, authentication, etc)

  • define countermeasures of attack vector
  • define robot's identification spec. and methods
  • guideline for robot hardware/sensor development
  • guideline for external interface of robot
  • guideline for software development
  • guideline for robot OS
  • guideline for robot's communication/transport layer
  • guideline for robot's (dynamic) authentication
  • guideline for robot's cloud layer

This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager. Example template page:

What does this OWASP project offer you?
What releases are available for this project?
what is this project?
Name: N/A
Purpose: N/A
License: N/A
who is working on this project?
Project Leader(s): N/A
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Key Contacts
  • Contact the GPC to contribute to this project
  • Contact the GPC to review or sponsor this project
current release
last reviewed release

other releases

Projects/OWASP Robot Security Project