Difference between revisions of "OWASP Robot Security Project"

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!

Identification:

• 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

Registration:

• 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    

Description

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!

Licensing

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 http://creativecommons.org/licenses/by-sa/3.0/ 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).

Presentation

• "Legally Identifying Robots (Robot Identification)"
• "Rapidly Scaling Robot Identification?"
• "Legal Person: Humans, Clones, Virtual and Physical AI Robotics – New Identity Principles"
• other?

Project Leader

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

Related Projects

• What should we link to?

Openhub

• OWASP Project Openhub

Quick Download

This is where you can link to your repository.

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:

• .zip file.
• .tgz file.

News and Events

This is where you can link to press your project has been a part of. Appropriate press includes: Project Leader interviews, articles written about your project, and videos about your project.

• [20 Nov 2013] News 2
• [30 Sep 2013] News 1

In Print

This is where you place links to where your project product can be downloaded or purchased, in the case of a book.

This project can be purchased as a print on demand book from Lulu.com

Classifications

Here is where you can let the community know what project stage your project is currently in, whether the project is a builder, breaker, or defender project, and what type of project you are running.