Difference between revisions of "OWASP SE - Social Engineering"

• Yet another Social Engineering site?

Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term. No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch.

• So, what will I find here?

We will start collecting input, your input, and publish it subsequently. Thus we are enabled to discuss it and try to separate truth from illusion.

• Okay, what is that precise?

Scientists openly publish their results, that we can use to point out to and connect the dots about "what we know" and "what we don't know".

• There is no such thing as free lunch.

You are right, someone has to pay for it - thanks to your contributions for OWASP, it is possible to stay independent and encourage volunteers around the world to contribute.

• What do you get out of it?

Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever it is we are sitting.

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:

• Dennis Groves
• Andrew Martin
• Josh Thomas
• YOUR NAME BELONGS HERE

1. Setup Wiki – develop guidelines for participation 2. Setup mailing list - connect researchers and interested people worldwide 3. Improve Wiki – start discussion about ethics 4. Improve Wiki – provide methods of Social Engineering 5. Improve Wiki – known research, literature and best practices 6. Setup working groups – worksheets for consumers 7. Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary? 8. Peer review – worksheets for consumers 9. Publication – worksheets for consumers 10. Presentation at conferences – spread the word, distribute knowledge

A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.  

Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.

As of October 2013, the priorities are:

• Finish the referencing for each principle.
• Update the Project Template.
• Use the OWASP Press to develop a book.
• Finish and publish the book on Lulu.

Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:

• Helping find references to some of the principles.
• Project administration support.
• Wiki editing support.
• Writing support for the book.

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