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!
Change of Registration:
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 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).
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
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.
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: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
| PROJECT INFO
What does this OWASP project offer you?
| RELEASE(S) INFO|
What releases are available for this project?