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 SE - Social Engineering"

From OWASP
Jump to: navigation, search
(Created page with "=Main= <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">link=</...")
 
(1st draft of page in various areas)
Line 7: Line 7:
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
  
−
<!-- 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.
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
 
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.
 
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.
−
</span>
+
</span>-->
 +
==The OWASP SE - Social Engineering Project==
  
−
==The OWASP Security Principles==
+
<!-- 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.-->
 
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
 
This is where you need to add your more robust project description. A project description should outline the purpose of the project, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, and project leaders should ensure that the description is meaningful.
 
This is where you need to add your more robust project description. A project description should outline the purpose of the project, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, and project leaders should ensure that the description is meaningful.
−
</span>
+
</span>-->
−
 
 
−
Inevitably applications are designed with security principles architects knew about, security folks included. However, as this project demonstrates there are far more than just a 'few' principles, most of which never make it into the design.
 
  
−
For example, security design happens with perhaps a handful of principles:
+
* What is Social Engineering?
 +
* Is it malicious manipulation of people?
 +
* Is it influencing people in everyday circumstances?
 +
* What about ethics?
 +
etc..
  
−
* Least Privilege
+
This project has the purpose of documenting open accessible and valid data about those and related questions.
−
* Perimeter Security
 
−
* Defence in Depth
 
  
−
However, we regularly see designs without '''separation of privilege'''!
+
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.
  
−
Think about that, most web applications today have all their eggs in a single basket. The business logic, the identities, passwords, products, policy enforcement, security rules are all found in the same application database that makes up the typical website! It is little wonder then, that attacks on the database have been so completely devastating, since there is no separation of privilege!
+
Let's start to document the unexplored areas of "people and security" (Hic sunt dragones) on the world map of security research with knowledge and affiliated areas.
−
 
 
−
The aim of this project, is to identify and describe a minimum functional set of principles that must be present in a secure design.
 
  
 
==Description==
 
==Description==
  
−
<!-- 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.
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
 
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.  
 
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.  
Line 41: Line 38:
  
 
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]
 
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]
−
'''
+
'''-->
 +
 
 +
Almost everywhere nowadays the "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.
 +
Could it be, it is just a vague concept, cherry picking successful exploitation of people just like snake oil?
 +
Also interesting, is it becoming a brand?
  
−
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.
+
If you heard about Social Engineering, let's collect material and questions for an exploration and produce f.E a cheat sheet "what we know" and "what we don't know" about it.
  
−
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.
+
==Licensing==
  
−
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.
+
"If I have seen further, it is by standing on the shoulders of giants." Sir Isaac Newton in 1675
  
−
==Licensing==
+
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/  
−
<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.
 
−
</span>
 
  
−
'''The OWASP Security Principles are free to use. In fact it is encouraged!!!
+
* All this is supposed to support you in the spirit of the initial "O" for Open in OWASP.
−
'' 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.
+
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.
  
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
  
−
== What is OWASP Security Principles Project? ==
+
== What is the OWASP SE - Social Engineering Project? ==
−
 
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
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.
+
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.
  
−
This document should serve as a guide to technical architects and designers outlining the fundamental principles of security.
+
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.
  
 
== Presentation ==
 
== 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.
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
 
This is where you can link to slide presentations related to your project.  
 
This is where you can link to slide presentations related to your project.  
−
</span>
+
</span>-->
  
  
−
AppSec USA 2013 [https://github.com/OWASP/Security-Principles/tree/master/Presentations/AppSec%20NYC%202013]
+
Sorry, no presentation so far.
  
 
== Project Leader ==
 
== Project Leader ==
  
−
<!-- 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.
 
<span style="color:#ff0000">
 
<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.
 
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>
+
</span>-->
  
−
* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
+
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]
  
  
 
== Related Projects ==
 
== 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.
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
 
This is where you can link to other OWASP Projects that are similar to yours.  
 
This is where you can link to other OWASP Projects that are similar to yours.  
 
</span>
 
</span>
  
−
* [[OWASP_CISO_Survey]]
+
* [[OWASP_CISO_Survey]]advocate-->
 +
Sorry, working on it.
  
−
== Openhub ==
+
<!--== Openhub ==
  
−
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]
+
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]-->
  
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
Line 113: Line 106:
 
== Quick Download ==
 
== Quick Download ==
  
−
<!-- 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.
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
 
This is where you can link to your repository.
 
This is where you can link to your repository.
Line 123: Line 116:
 
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]
 
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]
 
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]
 
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]
−
 
+
-->
 +
Downloads is not ready yet.
 
== News and Events ==
 
== News and Events ==
  
−
<!-- 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.
 
<span style="color:#ff0000">
 
<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.  
 
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.  
−
</span>
+
</span>-->
  
−
* [20 Nov 2013] News 2
+
If you would like you may meet me personally at the trade fair it-sa in Nuremberg, Germany from 10-12.10.2017, just drop me a note.
−
* [30 Sep 2013] News 1
 
  
 
== In Print ==
 
== In Print ==
  
−
<!-- 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.
 
<span style="color:#ff0000">
 
<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.  
 
This is where you place links to where your project product can be downloaded or purchased, in the case of a book.  
−
</span>
+
</span>-->
  
−
This project can be purchased as a print on demand book from Lulu.com
+
Sorry, no print so far.
  
 
==Classifications==
 
==Classifications==
  
−
<!-- 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.
 
<span style="color:#ff0000">
 
<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.  
 
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.  
−
</span>
+
</span>-->
 +
This is project is currently in stage 1 - editing wiki
  
 
   {| width="200" cellpadding="2"
 
   {| width="200" cellpadding="2"
Line 166: Line 160:
 
=FAQs=
 
=FAQs=
  
−
<!-- 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.
 
<span style="color:#ff0000">
 
<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.'
 
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.'
−
</span>
+
</span>-->
 +
 
 +
* 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?==
 
==How can I participate in your project?==

Revision as of 10:01, 20 September 2017

OWASP Project Header.jpg

The OWASP SE - Social Engineering Project

  • What is Social Engineering?
  • Is it malicious manipulation of people?
  • Is it influencing people in everyday circumstances?
  • What about ethics?

etc..

This project has the purpose of documenting open accessible and valid data about those and related questions.

As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.

Let's start to document the unexplored areas of "people and security" (Hic sunt dragones) on the world map of security research with knowledge and affiliated areas.

Description

Almost everywhere nowadays the "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe. Could it be, it is just a vague concept, cherry picking successful exploitation of people just like snake oil? Also interesting, is it becoming a brand?

If you heard about Social Engineering, let's collect material and questions for an exploration and produce f.E a cheat sheet "what we know" and "what we don't know" about it.

Licensing

"If I have seen further, it is by standing on the shoulders of giants." Sir Isaac Newton in 1675

  • We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.
  • All this is supposed to support you in the spirit of the initial "O" for Open in OWASP.

For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.

What is the OWASP SE - Social Engineering Project?

Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.

As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.

Presentation

Sorry, no presentation so far.

Project Leader


Related Projects

Sorry, working on it.


Quick Download

Downloads is not ready yet.

News and Events

If you would like you may meet me personally at the trade fair it-sa in Nuremberg, Germany from 10-12.10.2017, just drop me a note.

In Print

Sorry, no print so far.

Classifications

This is project is currently in stage 1 - editing wiki

New projects.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files DOC.jpg
  • 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:

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


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


Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&oldid=233517"