Difference between revisions of "OWASP Robot Security Project"

Latest revision as of 05:49, 17 April 2019

TBMain
FAQs
Acknowledgements
Road Map and Getting Involved
Project About

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. The project must also address robots acting together in singularity.

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

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

TBD.

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

TBD

In Print

TBD

Classifications

Builder

TBD

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.

Contributors

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: 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?

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

pending
last reviewed release
pending

other releases

Projects/OWASP Robot Security Project

@@ Line 1: / Line 1: @@
-=Main=
+=TBMain=
 <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
@@ Line 36: / Line 36: @@
 '''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
+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.
 ==Description==
 <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
+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).
-	This section must include a shorter description of what the project is, why the project was started, and what security issue is being helped by the project deliverable. This description will be used to promote the project so make sure the description represents your project in the best way possible.
-</span>
+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.
-'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]'''
+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.
-Over the course of my career, I have come across and collected a number of security ''aphorisms.'' These aphorisms constitute the fundamental principles of information 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.
-None of the ideas or truths are mine, and unfortunately, I did not collect the citations. Initially, I would like to identify the correct citations for each aphorism.
+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.
-Additionally, many are re-statements of the same idea; thus, the 'collection of ideas' defines a fundamental principle. As such, I would also like to reverse engineer the principles from the aphorisms where appropriate, as well.
+'''We invite interested parties to join us!'''
 ==Licensing==
@@ Line 57: / Line 57: @@
 <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 <span style="color:#ff0000">
-	A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses OWASP Licenses]. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects.
+	TBD based on our activities.
 </span>
 '''The OWASP Security Principles are free to use. In fact it is encouraged!!!'''
-'' Additionally, I also encourage you to contribute back to the project. I have no monopoly on this knowledge; however, we all have pieces of this knowledge from our experience. Let's begin by putting our individual pieces together to make something great. Great things happen when people work together.''
 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.
@@ Line 68: / Line 67: @@
 | valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
-== What is OWASP Security Principles Project? ==
+== What is OWASP Robotic Security Principles Project? ==
 <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
+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).
-	Here you should add a short description of what your project actually does. What is the primary goal of your project, and why is it important?
-</span>
-The end goal is to identify, cite, and document the fundamental principles of information security. Once this is well organised, I think it would be great to publish this through the [http://scriptogr.am/dennis-groves/post/owasp-press OWASP Press]. Of course, it will always remain freely available, and any money collected will go directly into the project to absorb costs with any remaining funds going to the OWASP Foundation.
-This document should serve as a guide to technical architects and designers outlining the fundamental principles of security.
 == Presentation ==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->* "[https://www.hvl.net/pdf/Legally%20Identifying%20Robots%20Feb%202019.pdf Legally Identifying Robots (Robot Identification)]"
-<span style="color:#ff0000">
+* [https://www.hvl.net/pdf/Rapidly%20Scaling%20Robot%20Identification%20Feb%202019.pdf "Rapidly Scaling Robot Identification?]"
-	This is where you can link to slide presentations related to your project.
+* "[https://www.hvl.net/pdf/Legal%20Person%20March%202019.pdf Legal Person: Humans, Clones, Virtual and Physical AI     Robotics – New Identity Principles]"
-</span>
+* [https://scholar.google.com/scholar?as_ylo=2018&q=robot+legal+person&hl=en&as_sdt=1,5 Robot legal person - google scholar]
+* other?
-AppSec USA 2013 [https://github.com/OWASP/Security-Principles/tree/master/Presentations/AppSec%20NYC%202013]
 == Project Leader ==
+* [https://ca.linkedin.com/in/ghuntington Guy Huntington]
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+* Hopefully there will soon be more leaders for  each subject!
-<span style="color:#ff0000">
-	A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.
-</span>
-* [https://owasp.org/index.php/User:Yunsoul Yunsoul]
 == Related Projects ==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->* What should we link to?
-<span style="color:#ff0000">
-	This is where you can link to other OWASP Projects that are similar to yours.
-</span>
-* [[OWASP_CISO_Survey]]
 == Openhub ==
@@ Line 119: / Line 99: @@
 <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 <span style="color:#ff0000">
-	This is where you can link to your repository.
+	TBD.
 </span>
@@ Line 132: / Line 112: @@
 <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 <span style="color:#ff0000">
-	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.
+	TBD</span>
-</span>
-* [20 Nov 2013] News 2
+*
-* [30 Sep 2013] News 1
 == In Print ==
@@ Line 142: / Line 120: @@
 <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 <span style="color:#ff0000">
-	This is where you place links to where your project product can be downloaded or purchased, in the case of a book.
+	TBD</span>
-</span>
-This project can be purchased as a print on demand book from Lulu.com
 ==Classifications==
@@ Line 151: / Line 126: @@
 <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 <span style="color:#ff0000">
-	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.
+	Builder</span>
-</span>
     {| width="200" cellpadding="2"
@@ Line 172: / Line 146: @@
 <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 <span style="color:#ff0000">
-	Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'
+	TBD</span>
-</span>
@@ Line 180: / Line 153: @@
 ==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, we are looking for researchers, writers, graphic designers, and a project administrator.
+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.
 = Acknowledgements =
@@ Line 187: / Line 160: @@
 <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
+'''Thanks JIM!!!!!!'''
-	The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project.
-Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project.
-Be sure to provide a link to a complete list of all the amazing people in your project's community as well.
-</span>
-The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project  [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].
 The first contributors to the project were:
-* [https://owasp.org/index.php/User:Yunsoul Yunsoul]
+* Jim Manico
 = Road Map and Getting Involved =
+'''We need to hash this out as a team'''
 ===Define Robot's Security Area===

Difference between revisions of "OWASP Robot Security Project"

Latest revision as of 05:49, 17 April 2019

The OWASP Robotic Security Principles

Description

Licensing

What is OWASP Robotic Security Principles Project?

Presentation

Project Leader

Related Projects

Openhub

Quick Download

News and Events

In Print

Classifications

How can I participate in your project?

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

Contributors

Define Robot's Security Area

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

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Reference

Tools