OWASP TASC Framework Project - Revision history

Andy Boura: /* Minimum Viable Product */

2015-12-16T14:40:07Z

‎Minimum Viable Product

Pwkpete at 14:36, 16 December 2015

2015-12-16T14:36:16Z

Pwkpete at 14:56, 11 December 2015

2015-12-11T14:56:08Z

Pwkpete at 14:55, 11 December 2015

2015-12-11T14:55:07Z

Claudia casanovas at 15:17, 10 August 2015

2015-08-10T15:17:12Z

Claudia casanovas at 15:13, 10 August 2015

2015-08-10T15:13:59Z

Andy Boura: /* The key deliverables are */

2015-08-06T16:58:02Z

‎The key deliverables are

Andy Boura: /* If I am not a programmer can I participate in your project? */

2015-07-24T10:04:28Z

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

Andy Boura: /* Description */

2015-07-23T16:04:18Z

‎Description

Andy Boura: /* What is OWASP TASC Framework Project? */

2015-07-23T15:32:00Z

‎What is OWASP TASC Framework Project?

← Older revision		Revision as of 14:40, 16 December 2015
Line 159:		Line 159:
	=Minimum Viable Product=		=Minimum Viable Product=

−	A minimum viable product would meet all requirements of the reference implementation and all previous milestones. The reference implementation includes the foundation of the system, the interface layer and example implementations of the interfaces that can be used as a basis for customization by the end user to meet the specific requirements of their system or environment.	+	A minimum viable product would meet all requirements of the reference implementation and all previous milestones (see Road Map). The reference implementation includes the foundation of the system, the interface layer and example implementations of the interfaces that can be used as a basis for customization by the end user to meet the specific requirements of their system or environment.

← Older revision		Revision as of 14:36, 16 December 2015
Line 160:		Line 160:

	A minimum viable product would meet all requirements of the reference implementation and all previous milestones. The reference implementation includes the foundation of the system, the interface layer and example implementations of the interfaces that can be used as a basis for customization by the end user to meet the specific requirements of their system or environment.		A minimum viable product would meet all requirements of the reference implementation and all previous milestones. The reference implementation includes the foundation of the system, the interface layer and example implementations of the interfaces that can be used as a basis for customization by the end user to meet the specific requirements of their system or environment.
−
−	~~=Project About=~~
−	~~<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->~~
−	~~<span style="color:#ff0000">~~
−	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~~
−	~~</span>~~
−
−	~~{{:Projects/OWASP_Example_Project_About_Page}}~~

@@ Line 40: / Line 40: @@
 == Project Resources ==
-[https://github.com/pwkpete Source Code]
+[https://github.com/pwkpete/TASC Source Code]
-[https://github.com/pwkpete Documentation]
+[https://github.com/pwkpete/TASC Documentation]
-[https://github.com/pwkpete Wiki Home Page]
+[https://github.com/pwkpete/TASC Wiki Home Page]
-[https://github.com/pwkpete Issue Tracker]
+[https://github.com/pwkpete/TASC Issue Tracker]
-[https://github.com/pwkpete Slide Presentation]
+[https://github.com/pwkpete/TASC Slide Presentation]
 The framework consists of a coordinator, a key manager, and one or more pairing mechanisms.

@@ Line 39: / Line 39: @@
 == Project Resources ==
-[https://github.com/SamanthaGroves Compiled DLLs]
+[https://github.com/pwkpete Source Code]
-[https://github.com/SamanthaGroves Source Code]
+[https://github.com/pwkpete Documentation]
-[https://github.com/SamanthaGroves Documentation]
+[https://github.com/pwkpete Wiki Home Page]
-[https://github.com/SamanthaGroves Wiki Home Page]
+[https://github.com/pwkpete Issue Tracker]
-[https://github.com/SamanthaGroves Issue Tracker]
+[https://github.com/pwkpete Slide Presentation]
 The framework consists of a coordinator, a key manager, and one or more pairing mechanisms.
@@ Line 126: / Line 119: @@
 * [https://www.owasp.org/index.php/User:Andy_Boura Andy Boura]
-* Pete Ikusz
+* [https://www.owasp.org/index.php/User:Pete_Ikusz Pete Ikusz]
 * Malcolm Boura
 = Road Map and Getting Involved =
@@ Line 166: / Line 158: @@
 =Minimum Viable Product=
-It would also be ideal if the sample text was translated into different languages.
+A minimum viable product would meet all requirements of the reference implementation and all previous milestones. The reference implementation includes the foundation of the system, the interface layer and example implementations of the interfaces that can be used as a basis for customization by the end user to meet the specific requirements of their system or environment.
 =Project About=

← Older revision		Revision as of 15:17, 10 August 2015
Line 36:		Line 36:

	Using an AES library such as: http://forum.arduino.cc/index.php?topic=88890.0 symmetric key encryption of the message payloads to ensure the authentication, integrity, and confidentiality of messages.		Using an AES library such as: http://forum.arduino.cc/index.php?topic=88890.0 symmetric key encryption of the message payloads to ensure the authentication, integrity, and confidentiality of messages.
		+	\| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" \|
		+
		+	== Project Resources ==
		+	<span style="color:#ff0000">
		+	This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc.
		+	</span>
		+
		+	[https://github.com/SamanthaGroves Compiled DLLs]
		+
		+	[https://github.com/SamanthaGroves Source Code]
		+
		+	[https://github.com/SamanthaGroves Documentation]
		+
		+	[https://github.com/SamanthaGroves Wiki Home Page]
		+
		+	[https://github.com/SamanthaGroves Issue Tracker]
		+
		+	[https://github.com/SamanthaGroves Slide Presentation]
		+
		+	[https://github.com/SamanthaGroves Video]

	The framework consists of a coordinator, a key manager, and one or more pairing mechanisms.		The framework consists of a coordinator, a key manager, and one or more pairing mechanisms.

← Older revision	Revision as of 15:13, 10 August 2015
Line 145:	Line 145:


	+	=Minimum Viable Product=
	+	<span style="color:#ff0000">
	+	This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern.
	+	Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap. And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.
	+	</span>
	+
	+	The Code Project Template must specify the minimum set of tabs a project should have, provide some an example layout on each tab, provide instructional text on how a project leader should modify the tab, and give some example text that illustrates how to create an actual project.
	+
	+	It would also be ideal if the sample text was translated into different languages.
	+
	+	=Project About=
	+	<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
	+	<span style="color:#ff0000">
	+	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
	+	</span>
	+
	+	{{:Projects/OWASP_Example_Project_About_Page}}

@@ Line 125: / Line 125: @@
 # Arduino reference implementation and documentation
 # Additional platform ports for both clients and servers
 == Getting Involved ==

@@ Line 90: / Line 90: @@
 ==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. See the getting involved tab for some of the ways you might be able to contribute.
 ==What platforms are supported by the framework?==

@@ Line 18: / Line 18: @@
 ==Description==
-The TASC Framework ('''T'''hings '''A'''uthentication and '''S'''ecure '''C'''ommunications) provides a lightweight abstracted security framework and supporting libraries to provide authentication and secure communications on resource constrained systems. For example developers creating "Internet of Things" (IoT) devices using low power or resource constrained systems such as Arduino who are not security experts.
+The TASC Framework ('''T'''hings '''A'''uthentication and '''S'''ecure '''C'''ommunications) provides a lightweight abstracted security framework and supporting libraries to provide authentication and secure communications on resource constrained systems. For example developers creating "Internet of Things" (IoT) devices using low power systems such as Arduino who are not security experts.
 ==Licensing==

@@ Line 35: / Line 35: @@
 The OWASP TASC Framework looks to address these issues in a way that makes no assumptions about the mechanism of the transmission of the data or commands - whether it be visible light, infra-red, 433MHz, 1-wire, serial, I2C, Bluetooth, WiFi etc. This is done by providing the capability to secure the payload and allowing the device developer the freedom to choose the communication medium.
-Using an AES library such as: http://forum.arduino.cc/index.php?topic=88890.0
+Using an AES library such as: http://forum.arduino.cc/index.php?topic=88890.0 symmetric key encryption of the message payloads to ensure the authentication, integrity, and confidentiality of messages.
 The framework consists of a coordinator, a key manager, and one or more pairing mechanisms.