This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP ICS / SCADA Security Project"
(→Road Map and Getting Involved) |
|||
(6 intermediate revisions by the same user not shown) | |||
Line 14: | Line 14: | ||
==The OWASP Security Principles== | ==The OWASP Security Principles== | ||
− | + | This project deals with all the attack vectors and defences that we can have for ICS / SCADA systems.Attacks on SCADA systems have drastically increased since the addition of Ethernet to embedded devices.The project also deals with the governance, web application security and architectural security | |
− | |||
− | This | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Description== | ==Description== | ||
− | A concrete list of Top 10 Vulnerabilities | + | A concrete list of Top 10 Vulnerabilities for ICS/ SCADA /Embedded device. ICS is an area that is still untouched.There are a lot of protocols in which the research is in progress and a lot of ICS/SCADA protocols vulnerabilities |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | You can add yourself to the SCADA Security Community | |
− | + | https://groups.google.com/forum/#!forum/cyber-security-for-industrial-control-systems-scada--iot/new | |
− | + | https://docs.google.com/spreadsheets/d/1QjVHWr4GgZcQaMuwDGDkG9nj-qTDBJeJiLDUJBH9MX0/edit#gid=1745338935 | |
==Licensing== | ==Licensing== | ||
Apache 2.0 License | Apache 2.0 License | ||
− | |||
− | |||
− | |||
− | |||
− | |||
'''The OWASP Security Principles are free to use. In fact it is encouraged!!! | '''The OWASP Security Principles are free to use. In fact it is encouraged!!! | ||
Line 195: | Line 166: | ||
The first contributors to the project were: | The first contributors to the project were: | ||
− | * [ | + | * [https://www.owasp.org/index.php/User:SCADA007 Avinash Sinha] |
− | |||
− | |||
− | |||
= Road Map and Getting Involved = | = Road Map and Getting Involved = | ||
Line 204: | Line 172: | ||
Vulnerabilities- Remediation->Protocol level->Ethernet (web)->Tools in later stage to locate vulnerabilities and fix as well | Vulnerabilities- Remediation->Protocol level->Ethernet (web)->Tools in later stage to locate vulnerabilities and fix as well | ||
− | + | 1.TOP 10 Vulnerabilities in SCADA | |
− | + | --Gathering data | |
− | + | --Segregating data | |
− | + | --Publishing | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=Project About= | =Project About= |
Latest revision as of 08:37, 11 March 2016
Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project. The OWASP Security PrinciplesThis project deals with all the attack vectors and defences that we can have for ICS / SCADA systems.Attacks on SCADA systems have drastically increased since the addition of Ethernet to embedded devices.The project also deals with the governance, web application security and architectural security DescriptionA concrete list of Top 10 Vulnerabilities for ICS/ SCADA /Embedded device. ICS is an area that is still untouched.There are a lot of protocols in which the research is in progress and a lot of ICS/SCADA protocols vulnerabilities
https://groups.google.com/forum/#!forum/cyber-security-for-industrial-control-systems-scada--iot/new LicensingApache 2.0 License 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. |
What is OWASP Security Principles Project?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? 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 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. PresentationThis is where you can link to slide presentations related to your project.
Project LeaderA 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.
Related ProjectsThis is where you can link to other OWASP Projects that are similar to yours. Openhub |
Quick DownloadThis 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: News and EventsThis 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.
In PrintThis 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 ClassificationsHere 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. |
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.'
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, we are looking for researchers, writers, graphic designers, and a project administrator.
Contributors
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.
The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project contributors is found here.
The first contributors to the project were:
A bit of help will be required to gather information on all ics/ SCADA protocol level vulnerabilities Vulnerabilities- Remediation->Protocol level->Ethernet (web)->Tools in later stage to locate vulnerabilities and fix as well
1.TOP 10 Vulnerabilities in SCADA --Gathering data --Segregating data --Publishing
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? | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|