https://wiki.owasp.org/api.php?action=feedcontributions&user=Schmidt&feedformat=atomOWASP - User contributions [en]2024-03-29T11:26:35ZUser contributionsMediaWiki 1.27.2https://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=253129OWASP SE - Social Engineering2019-07-19T14:34:08Z<p>Schmidt: added glossary + first glossary term social engineering</p>
<hr />
<div>=[[Main]]=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
* Yet another Social Engineering site?<br />
**Yes and no<br />
***Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
***No, we focus on reliable data and discussions about manipulation of people. Others did already a very good job showing how to exploit people.<br />
**You are right to believe, that better tutorials etc. exist. Please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
**Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, you can. That what this project is about. <br />
A good starting point is a look at our description and road map to get an idea.<br />
<br />
= Glossary =<br />
* Social Engineering - "Social Engineering" as a term refers for the purpose as a OWASP Documentation Project at malicious people tricking other people for personal gains.<br />
** This narrow definition enables us to work on methods, while avoiding absolutely necessary ethical discussions, would we use the term in a broader sense.<br />
** One of the most troublesome points with Social Engineering is, we can't control what is essentially happening to the affected person. People are no machines.<br />
<br />
= Acknowledgements =<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
Security researchers, it is always amazing to find out about your work and read about it.<br />
<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
Quoting Sir Isaac Newton in 1675: "If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
<br />
{{Project About<br />
| project_name =OWASP SE - Social Engineering<br />
| project_description = <br />
What is it about? <br />
<br />
The OWASP SE - Social Engineering Project is a documentation project. It aims to connect researchers and practitioners about countermeasures against harmful and manipulative behaviour for those affected.<br />
Web applications like social media etc. are one of the most important tool as well as targets harming users.<br />
<br />
What is the goal? <br />
<br />
Discussing, evaluating and providing easy to use methods and sound context. Most everyone will be able to share thoughts and experiences about maliciously intended Social Engineering. <br />
Let's put our heads together to provide working countermeasures, basic procedures and best practices.<br />
| leader_name1 = Matthias Schmidt<br />
| leader_email1 =matthias.schmidt@owasp.org<br />
| leader_username1 = Schmidt<br />
|project_license=OWASP is licensed under SE Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/.}}<br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=User:Schmidt&diff=240941User:Schmidt2018-05-25T08:03:00Z<p>Schmidt: /* Hi, so you are interested in me, thank you. */</p>
<hr />
<div>== Hi, so you are interested in me. Thank you. ==<br />
====My university education====<br />
MA in linguistics + additional studies in computer science, media science, legal studies and psychology.<br />
<br />
====Me and information security====<br />
As many kids at a certain age, I was being intrigued by criminology, but not tempted by tricksters. <br />
Parallel to my studies, I started working at various companies related to information security.<br />
As I was able to speak reasonably to customers (somebody has to do the job), typical areas were sales national, sales international, project management international.<br />
I got more and more involved and started my own company for information security services. I still enjoy that.<br />
<br />
====Why OWASP?====<br />
Cooperation and sharing knowledge is the key element of OWASP as well as mine.<br />
<br />
====What else?====<br />
I am not seeking any moral high ground.<br />
I recommend the Universal Declaration of Human Rights, which includes article 17 - property. <br />
http://www.un.org/en/universal-declaration-human-rights/index.html<br />
<br />
[mailto:matthias.schmidt@owasp.org Send me an email]</div>Schmidthttps://wiki.owasp.org/index.php?title=User:Schmidt&diff=240940User:Schmidt2018-05-25T08:01:41Z<p>Schmidt: </p>
<hr />
<div>== Hi, so you are interested in me, thank you. ==<br />
===My university education:===<br />
MA in linguistics + additional studies in computer science, media science, legal studies and psychology.<br />
<br />
===Me and information security:===<br />
As many kids at a certain age, I was being intrigued by criminology, but not tempted by tricksters. <br />
Parallel to my studies, I started working at various companies related to information security.<br />
As I was able to speak reasonably to customers (somebody has to do the job), typical areas were sales national, sales international, project management international.<br />
I got more and more involved and started my own company for information security services. I still enjoy that.<br />
<br />
===Why OWASP?===<br />
Cooperation and sharing knowledge is the key element of OWASP as well as mine.<br />
<br />
===What else?===<br />
I am not seeking any moral high ground.<br />
I recommend the Universal Declaration of Human Rights, which includes article 17 - property. <br />
http://www.un.org/en/universal-declaration-human-rights/index.html<br />
<br />
[mailto:matthias.schmidt@owasp.org Send me an email]</div>Schmidthttps://wiki.owasp.org/index.php?title=User:Schmidt&diff=240939User:Schmidt2018-05-25T07:33:22Z<p>Schmidt: </p>
<hr />
<div>Hi,<br />
so you are interested in me, thank you.<br />
<br />
My Education: <br />
MA in linguistics + additional studies (years) in computer science, media science, legal studies and psychology while working.<br />
<br />
My Information security career: <br />
First as employee - sales national, sales international, project management international.<br />
Second as founder of my own company solely about information security services.<br />
<br />
I am not seeking any moral high ground and I recommend the Universal Declaration of Human Rights, yes that includes article 17 - property. <br />
http://www.un.org/en/universal-declaration-human-rights/index.html<br />
<br />
[mailto:matthias.schmidt@owasp.org Send me an email]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=237535OWASP SE - Social Engineering2018-02-14T12:07:35Z<p>Schmidt: restructuring project about</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no<br />
***Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
***No, we focus on reliable data and discussions about manipulation of people. Others did already a very good job showing how to exploit people.<br />
**You are right to believe, that better tutorials etc. exist. Please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
**Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, you can. That what this project is about. <br />
A good starting point is a look at our description and road map to get an idea.<br />
<br />
= Acknowledgements =<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
Security researchers, it is always amazing to find out about your work and read about it.<br />
<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
Quoting Sir Isaac Newton in 1675: "If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
<br />
{{Project About<br />
| project_name =OWASP SE - Social Engineering<br />
| project_description = <br />
What is it about? <br />
<br />
The OWASP SE - Social Engineering Project is a documentation project. It aims to connect researchers and practitioners about countermeasures against harmful and manipulative behaviour for those affected.<br />
Web applications like social media etc. are one of the most important tool as well as targets harming users.<br />
<br />
What is the goal? <br />
<br />
Discussing, evaluating and providing easy to use methods and sound context. Most everyone will be able to share thoughts and experiences about maliciously intended Social Engineering. <br />
Let's put our heads together to provide working countermeasures, basic procedures and best practices.<br />
| leader_name1 = Matthias Schmidt<br />
| leader_email1 =matthias.schmidt@owasp.org<br />
| leader_username1 = Schmidt<br />
|project_license=OWASP is licensed under SE Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/.}}<br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=User:Schmidt&diff=237534User:Schmidt2018-02-14T11:37:24Z<p>Schmidt: minor structure changes</p>
<hr />
<div>Hi,<br />
so you are interested in me.<br />
<br />
Education: <br />
MA in linguistics + additional studies (years) in computer science, media science, legal studies and psychology while working.<br />
<br />
Information security: <br />
First as employee - sales national, sales international, project management international.<br />
Second as founder of my own company solely about information security services.<br />
<br />
I am not seeking any moral high ground and I recommend the Universal Declaration of Human Rights, yes that includes article 17 - property. <br />
http://www.un.org/en/universal-declaration-human-rights/index.html<br />
<br />
[mailto:matthias.schmidt@owasp.org Send me an email]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=237533OWASP SE - Social Engineering2018-02-14T11:31:38Z<p>Schmidt: edited the project about page using the template</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no<br />
***Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
***No, we focus on reliable data and discussions about manipulation of people. Others did already a very good job showing how to exploit people.<br />
**You are right to believe, that better tutorials etc. exist. Please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
**Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, you can. That what this project is about. <br />
A good starting point is a look at our description and road map to get an idea.<br />
<br />
= Acknowledgements =<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
Security researchers, it is always amazing to find out about your work and read about it.<br />
<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
Quoting Sir Isaac Newton in 1675: "If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
<br />
{{Project About<br />
| project_name =OWASP SE - Social Engineering<br />
| project_description = <br />
What is it about? The OWASP SE - Social Engineering Project is a documentation project and aims to connect researchers and practitioners about countermeasures against harmful and manipulative behaviour for those affected.<br />
Web applications like social media etc. are one of the most important tool as well as targets harming users.<br />
What is the goal? Discuss, evaluate and provide easy to use methods and sound context. for maliciously intended Social Engineering. And most everyone will be able to share thoughts and experiences about this catchall phrase "Social Engineering". So let's put our heads together to provide countermeasures and basic procedures.<br />
| leader_name1 = Matthias Schmidt<br />
| leader_email1 =matthias.schmidt@owasp.org<br />
| leader_username1 = Schmidt<br />
|project_license=OWASP is licensed under SE Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/.}}<br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=237532OWASP SE - Social Engineering2018-02-14T10:59:07Z<p>Schmidt: </p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no<br />
***Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
***No, we focus on reliable data and discussions about manipulation of people. Others did already a very good job showing how to exploit people.<br />
**You are right to believe, that better tutorials etc. exist. Please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
**Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, you can. That what this project is about. <br />
A good starting point is a look at our description and road map to get an idea.<br />
<br />
= Acknowledgements =<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
Security researchers, it is always amazing to find out about your work and read about it.<br />
<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
Quoting Sir Isaac Newton in 1675: "If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=User:Schmidt&diff=233836User:Schmidt2017-09-28T18:46:51Z<p>Schmidt: mailadress</p>
<hr />
<div>Hello,<br />
<br />
so you are interested in me.<br />
<br />
Education: MA in linguistics + additional studies (years) in computer science, media science, legal studies and psychology.<br />
<br />
Work life information security: sales national, sales international, project management international, then decided to go swimming with sharks by founding a company solely about information security services - still swimming, with a few more bite marks.<br />
<br />
I am not seeking any moral high ground and I recommend the Universal Declaration of Human Rights, yes that includes article 17 - property. <br />
<br />
http://www.un.org/en/universal-declaration-human-rights/index.html<br />
<br />
[mailto:matthias.schmidt@owasp.org Send me an email]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233536OWASP SE - Social Engineering2017-09-20T14:03:51Z<p>Schmidt: minor acknowledgements</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
Meet me (Herr Schmidt) personally at the trade fair it-sa in Nuremberg, Germany from 10-12.10.2017, just drop me a note.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no<br />
***Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
***No, we focus on reliable data and discussions about manipulation of people. Others did already a very good job showing how to exploit people.<br />
**You are right to believe, that better tutorials etc. exist. Please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
**Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, you can. That what this project is about. <br />
A good starting point is a look at our description and road map to get an idea.<br />
<br />
= Acknowledgements =<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
Security researchers, it is always amazing to find out about your work and read about it.<br />
<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
Quoting Sir Isaac Newton in 1675: "If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233535OWASP SE - Social Engineering2017-09-20T14:02:04Z<p>Schmidt: minor acknowledgements</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
Meet me (Herr Schmidt) personally at the trade fair it-sa in Nuremberg, Germany from 10-12.10.2017, just drop me a note.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no<br />
***Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
***No, we focus on reliable data and discussions about manipulation of people. Others did already a very good job showing how to exploit people.<br />
**You are right to believe, that better tutorials etc. exist. Please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
**Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, you can. That what this project is about. <br />
A good starting point is a look at our description and road map to get an idea.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
Security researchers, it is always amazing to find out about your work and read about it.<br />
<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233534OWASP SE - Social Engineering2017-09-20T13:54:36Z<p>Schmidt: minor faq</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
Meet me (Herr Schmidt) personally at the trade fair it-sa in Nuremberg, Germany from 10-12.10.2017, just drop me a note.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no<br />
***Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
***No, we focus on reliable data and discussions about manipulation of people. Others did already a very good job showing how to exploit people.<br />
**You are right to believe, that better tutorials etc. exist. Please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
**Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233533OWASP SE - Social Engineering2017-09-20T13:53:08Z<p>Schmidt: minor classification</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
Meet me (Herr Schmidt) personally at the trade fair it-sa in Nuremberg, Germany from 10-12.10.2017, just drop me a note.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no<br />
***Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
***No, we focus on reliable data and discussions about manipulation of people, others did already a very good job showing how to exploit people.<br />
**You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
**Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233532OWASP SE - Social Engineering2017-09-20T13:18:55Z<p>Schmidt: minor faq</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
Meet me (Herr Schmidt) personally at the trade fair it-sa in Nuremberg, Germany from 10-12.10.2017, just drop me a note.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no<br />
***Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
***No, we focus on reliable data and discussions about manipulation of people, others did already a very good job showing how to exploit people.<br />
**You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
**Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233531OWASP SE - Social Engineering2017-09-20T13:16:01Z<p>Schmidt: punctuation faq</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
Meet me (Herr Schmidt) personally at the trade fair it-sa in Nuremberg, Germany from 10-12.10.2017, just drop me a note.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no<br />
***Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
***No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
**You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
**Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233530OWASP SE - Social Engineering2017-09-20T13:15:02Z<p>Schmidt: punctuation faq</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
Meet me (Herr Schmidt) personally at the trade fair it-sa in Nuremberg, Germany from 10-12.10.2017, just drop me a note.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
**No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
**You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
**Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233529OWASP SE - Social Engineering2017-09-20T13:13:25Z<p>Schmidt: news</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
Meet me (Herr Schmidt) personally at the trade fair it-sa in Nuremberg, Germany from 10-12.10.2017, just drop me a note.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233528OWASP SE - Social Engineering2017-09-20T13:11:34Z<p>Schmidt: description</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose? <br />
Cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
<br />
Also interesting, is it becoming a type of brand?<br />
<br />
Let's collect material and questions for an exploration and produce results like a cheat sheet: "what we know" and "what we don't know" <br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
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.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233527OWASP SE - Social Engineering2017-09-20T13:09:15Z<p>Schmidt: punctuation faq + altered description</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays, the almost "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, that it is just a vague concept on purpose, cherry picking successful exploitation of people. Perhaps just like snake oil? <br />
Also interesting, is it becoming a type of brand?<br />
<br />
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 Social Engineering.<br />
<br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
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.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
**Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
**We will start collecting input, your input, and publish it subsequently.<br />
Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
**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".<br />
<br />
* There is no such thing as free lunch.<br />
**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. <br />
<br />
* What do you get out of it?<br />
**Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233526OWASP SE - Social Engineering2017-09-20T13:04:03Z<p>Schmidt: /* Licensing */</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays the "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, it is just a vague concept, cherry picking successful exploitation of people just like snake oil? <br />
Also interesting, is it becoming a brand?<br />
<br />
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 Social Engineering.<br />
<br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you, in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
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.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
We will start collecting input, your input, and publish it subsequently.<br />
Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
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".<br />
<br />
* There is no such thing as free lunch.<br />
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. <br />
<br />
* What do you get out of it?<br />
Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233525OWASP SE - Social Engineering2017-09-20T13:03:05Z<p>Schmidt: /* The OWASP SE - Social Engineering Project */</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays the "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, it is just a vague concept, cherry picking successful exploitation of people just like snake oil? <br />
Also interesting, is it becoming a brand?<br />
<br />
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 Social Engineering.<br />
<br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
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.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
We will start collecting input, your input, and publish it subsequently.<br />
Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
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".<br />
<br />
* There is no such thing as free lunch.<br />
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. <br />
<br />
* What do you get out of it?<br />
Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233524OWASP SE - Social Engineering2017-09-20T13:02:18Z<p>Schmidt: road map and involvement</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays the "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, it is just a vague concept, cherry picking successful exploitation of people just like snake oil? <br />
Also interesting, is it becoming a brand?<br />
<br />
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 Social Engineering.<br />
<br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you in the spirit of the initial "O" for Open in OWASP.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
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.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
We will start collecting input, your input, and publish it subsequently.<br />
Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
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".<br />
<br />
* There is no such thing as free lunch.<br />
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. <br />
<br />
* What do you get out of it?<br />
Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
.. Well that about sums it up.<br />
<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
==Road Map==<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
==Involvement==<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
A good starting point for you is a look at our description and road map<br />
<br />
What is always a great way of involvement is support with<br />
*input and data <br />
*subsequently structuring input and data<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233523OWASP SE - Social Engineering2017-09-20T12:54:59Z<p>Schmidt: /*roadmap*/</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays the "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, it is just a vague concept, cherry picking successful exploitation of people just like snake oil? <br />
Also interesting, is it becoming a brand?<br />
<br />
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 Social Engineering.<br />
<br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you in the spirit of the initial "O" for Open in OWASP.<br />
<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
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.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
We will start collecting input, your input, and publish it subsequently.<br />
Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
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".<br />
<br />
* There is no such thing as free lunch.<br />
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. <br />
<br />
* What do you get out of it?<br />
Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
.. Well that about sums it up.<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
<br />
#Setup Wiki – develop guidelines for participation<br />
#Setup mailing list - connect researchers and interested people worldwide<br />
#Improve Wiki – start discussion about ethics <br />
#Improve Wiki – provide methods of Social Engineering<br />
#Improve Wiki – known research, literature and best practices<br />
#Setup working groups – worksheets for consumers<br />
#Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
#Peer review – worksheets for consumers<br />
#Publication – worksheets for consumers<br />
#Presentation at conferences – spread the word, distribute knowledge<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233522OWASP SE - Social Engineering2017-09-20T12:50:35Z<p>Schmidt: /*contributors*/</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays the "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, it is just a vague concept, cherry picking successful exploitation of people just like snake oil? <br />
Also interesting, is it becoming a brand?<br />
<br />
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 Social Engineering.<br />
<br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you in the spirit of the initial "O" for Open in OWASP.<br />
<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
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.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
We will start collecting input, your input, and publish it subsequently.<br />
Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
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".<br />
<br />
* There is no such thing as free lunch.<br />
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. <br />
<br />
* What do you get out of it?<br />
Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
.. Well that about sums it up.<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
--><br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
<br />
1. Setup Wiki – develop guidelines for participation<br />
2. Setup mailing list - connect researchers and interested people worldwide<br />
3. Improve Wiki – start discussion about ethics <br />
4. Improve Wiki – provide methods of Social Engineering<br />
5. Improve Wiki – known research, literature and best practices<br />
6. Setup working groups – worksheets for consumers<br />
7. Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
8. Peer review – worksheets for consumers<br />
9. Publication – worksheets for consumers<br />
10. Presentation at conferences – spread the word, distribute knowledge<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233521OWASP SE - Social Engineering2017-09-20T12:49:00Z<p>Schmidt: /* Main */</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting "Social Engineering" with open accessible and valid data about relevant topics and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics, are there any?<br />
<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays the "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, it is just a vague concept, cherry picking successful exploitation of people just like snake oil? <br />
Also interesting, is it becoming a brand?<br />
<br />
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 Social Engineering.<br />
<br />
==Licensing==<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you in the spirit of the initial "O" for Open in OWASP.<br />
<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->| style="padding-left:25px;width:200px;" valign="top" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
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.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
We will start collecting input, your input, and publish it subsequently.<br />
Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
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".<br />
<br />
* There is no such thing as free lunch.<br />
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. <br />
<br />
* What do you get out of it?<br />
Have you ever been to an OWASP Meeting? Go there and have a good time - same thing here, but from the couch or wherever we are.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
.. Well that about sums it up.<br />
==If I am not a programmer can I participate in your project?==<br />
Yes, that what this is about. A good starting point is a look at our description and road map to come up with something.<br />
<br />
= Acknowledgements =<br />
<br />
Quoting Sir Isaac Newton in 1675<br />
"If I have seen further, it is by standing on the shoulders of giants."<br />
<br />
First of all, thanks to you dear reader for taking your time reading this, perhaps some of it may prove helpful?<br />
<br />
It is amazing to find out and read about security researchers all over the world.<br />
And, as this is an inclusive project, we thank all those undeceiving researchers and hackers laying the groundwork for this.<br />
<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
<br />
We want to make sure to precisely name all contributors, also as a matter of transparency and reliability.<br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
<br />
1. Setup Wiki – develop guidelines for participation<br />
2. Setup mailing list - connect researchers and interested people worldwide<br />
3. Improve Wiki – start discussion about ethics <br />
4. Improve Wiki – provide methods of Social Engineering<br />
5. Improve Wiki – known research, literature and best practices<br />
6. Setup working groups – worksheets for consumers<br />
7. Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
8. Peer review – worksheets for consumers<br />
9. Publication – worksheets for consumers<br />
10. Presentation at conferences – spread the word, distribute knowledge<br />
<br />
<!--<br />
<br />
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. <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
--><br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span>--><br />
Sorry, still in progress.<br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs></headertabs> <br />
<br />
[[Category:OWASP Project]] <br />
[[Category:OWASP_Builders]] <br />
[[Category:OWASP_Defenders]] <br />
[[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233520OWASP SE - Social Engineering2017-09-20T12:20:09Z<p>Schmidt: changed punctuation</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting open accessible and valid data about those and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics?<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays the "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe.<br />
<br />
Could it be, it is just a vague concept, cherry picking successful exploitation of people just like snake oil? <br />
Also interesting, is it becoming a brand?<br />
<br />
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 Social Engineering.<br />
<br />
==Licensing==<br />
<br />
"If I have seen further, it is by standing on the shoulders of giants." Sir Isaac Newton in 1675<br />
<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you in the spirit of the initial "O" for Open in OWASP.<br />
<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| valign="top" style="padding-left:25px;width:200px;" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
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.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| align="center" valign="top" width="50%" rowspan="2"| [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
We will start collecting input, your input, and publish it subsequently.<br />
Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
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".<br />
<br />
* There is no such thing as free lunch.<br />
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. <br />
<br />
* What do you get out of it?<br />
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.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
==If I am not a programmer can I participate in your project?==<br />
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. <br />
<br />
= Acknowledgements =<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
<br />
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]. <br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]<br />
* [https://github.com/sublimino Andrew Martin]<br />
* [https://github.com/Lambdanaut Josh Thomas]<br />
* '''YOUR NAME BELONGS HERE'''<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
<br />
1. Setup Wiki – develop guidelines for participation<br />
2. Setup mailing list - connect researchers and interested people worldwide<br />
3. Improve Wiki – start discussion about ethics <br />
4. Improve Wiki – provide methods of Social Engineering<br />
5. Improve Wiki – known research, literature and best practices<br />
6. Setup working groups – worksheets for consumers<br />
7. Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
8. Peer review – worksheets for consumers<br />
9. Publication – worksheets for consumers<br />
10. Presentation at conferences – spread the word, distribute knowledge<br />
<br />
<br />
<br />
<br />
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.<br />
</span> <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span><br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs /> <br />
<br />
[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233519OWASP SE - Social Engineering2017-09-20T12:18:12Z<p>Schmidt: /* The OWASP SE - Social Engineering Project */</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
This project has the purpose of documenting open accessible and valid data about those and related questions.<br />
<br />
Some of these questions are:<br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics?<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays the "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe. <br />
Could it be, it is just a vague concept, cherry picking successful exploitation of people just like snake oil? <br />
Also interesting, is it becoming a brand?<br />
<br />
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.<br />
<br />
==Licensing==<br />
<br />
"If I have seen further, it is by standing on the shoulders of giants." Sir Isaac Newton in 1675<br />
<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you in the spirit of the initial "O" for Open in OWASP.<br />
<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| valign="top" style="padding-left:25px;width:200px;" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
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.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| align="center" valign="top" width="50%" rowspan="2"| [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
We will start collecting input, your input, and publish it subsequently.<br />
Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
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".<br />
<br />
* There is no such thing as free lunch.<br />
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. <br />
<br />
* What do you get out of it?<br />
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.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
==If I am not a programmer can I participate in your project?==<br />
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. <br />
<br />
= Acknowledgements =<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
<br />
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]. <br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]<br />
* [https://github.com/sublimino Andrew Martin]<br />
* [https://github.com/Lambdanaut Josh Thomas]<br />
* '''YOUR NAME BELONGS HERE'''<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
<br />
1. Setup Wiki – develop guidelines for participation<br />
2. Setup mailing list - connect researchers and interested people worldwide<br />
3. Improve Wiki – start discussion about ethics <br />
4. Improve Wiki – provide methods of Social Engineering<br />
5. Improve Wiki – known research, literature and best practices<br />
6. Setup working groups – worksheets for consumers<br />
7. Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
8. Peer review – worksheets for consumers<br />
9. Publication – worksheets for consumers<br />
10. Presentation at conferences – spread the word, distribute knowledge<br />
<br />
<br />
<br />
<br />
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.<br />
</span> <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span><br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs /> <br />
<br />
[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=OWASP_SE_-_Social_Engineering&diff=233517OWASP SE - Social Engineering2017-09-20T10:01:32Z<p>Schmidt: 1st draft of page in various areas</p>
<hr />
<div>=Main=<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-<br />
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
==The OWASP SE - Social Engineering Project==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* What is Social Engineering? <br />
* Is it malicious manipulation of people? <br />
* Is it influencing people in everyday circumstances?<br />
* What about ethics?<br />
etc..<br />
<br />
This project has the purpose of documenting open accessible and valid data about those and related questions.<br />
<br />
As a platform under OWASP we are free and independent, connecting to researchers and discussing valid data.<br />
<br />
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.<br />
<br />
==Description==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]<br />
'''--><br />
<br />
Almost everywhere nowadays the "mythical power" of Social Engineering is a prominent topic in discussions and often uttered in awe. <br />
Could it be, it is just a vague concept, cherry picking successful exploitation of people just like snake oil? <br />
Also interesting, is it becoming a brand?<br />
<br />
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.<br />
<br />
==Licensing==<br />
<br />
"If I have seen further, it is by standing on the shoulders of giants." Sir Isaac Newton in 1675<br />
<br />
* We ourselves take care not to infringe any copyrights, so you can enjoy open accessible information.<br />
<br />
* Legally speaking, we are licensed under the Creative Commons Attribution-ShareAlike 3.0 license http://creativecommons.org/licenses/by-sa/3.0/ <br />
<br />
* All this is supposed to support you in the spirit of the initial "O" for Open in OWASP.<br />
<br />
For us, the most precious appreciation possible, is your contribution of thoughts, time and recommendation.<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |<br />
<br />
== What is the OWASP SE - Social Engineering Project? ==<br />
<br />
Basically a platform connecting and collecting researchers and data to shed light upon hearsay about Social Engineering or manipulation of people.<br />
<br />
As a dedicated team of volunteers, we (yes your are invited) might be able to produce a knowledge base and references for interested people.<br />
<br />
== Presentation ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to slide presentations related to your project. <br />
</span>--><br />
<br />
<br />
Sorry, no presentation so far.<br />
<br />
== Project Leader ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.<br />
</span>--><br />
<br />
* [https://www.owasp.org/index.php/User:Schmidt Herr Schmidt]<br />
<br />
<br />
== Related Projects ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to other OWASP Projects that are similar to yours. <br />
</span><br />
<br />
* [[OWASP_CISO_Survey]]advocate--><br />
Sorry, working on it.<br />
<br />
<!--== Openhub ==<br />
<br />
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]--><br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
| valign="top" style="padding-left:25px;width:200px;" |<br />
<br />
== Quick Download ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you can link to your repository.<br />
</span><br />
<br />
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.<br />
<br />
However, if you like you may also download the master repository from the following links:<br />
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]<br />
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]<br />
--><br />
Downloads is not ready yet.<br />
== News and Events ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
<br />
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.<br />
<br />
== In Print ==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. <br />
</span>--><br />
<br />
Sorry, no print so far.<br />
<br />
==Classifications==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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. <br />
</span>--><br />
This is project is currently in stage 1 - editing wiki<br />
<br />
{| width="200" cellpadding="2"<br />
|-<br />
| align="center" valign="top" width="50%" rowspan="2"| [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]<br />
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]] <br />
|-<br />
| align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]<br />
|-<br />
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] <br />
|-<br />
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] <br />
|}<br />
<br />
|}<br />
<br />
=FAQs=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.<br />
<span style="color:#ff0000"><br />
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.'<br />
</span>--><br />
<br />
* Yet another Social Engineering site?<br />
Yes and no - Yes, the title of the project references to Social Engineering as it is a more popular term.<br />
No, we focus on reliable data and discussions about manipulation of people, not about "how to" etc. <br />
You are right to believe, that better tutorials etc. exist, please keep in mind we are an open documentation project, not a sales pitch. <br />
<br />
* So, what will I find here?<br />
We will start collecting input, your input, and publish it subsequently.<br />
Thus we are enabled to discuss it and try to separate truth from illusion.<br />
<br />
* Okay, what is that precise?<br />
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".<br />
<br />
* There is no such thing as free lunch.<br />
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. <br />
<br />
* What do you get out of it?<br />
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.<br />
<br />
==How can I participate in your project?==<br />
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. <br />
<br />
==If I am not a programmer can I participate in your project?==<br />
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. <br />
<br />
= Acknowledgements =<br />
<br />
==Contributors==<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
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. <br />
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. <br />
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.<br />
</span><br />
<br />
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]. <br />
<br />
The first contributors to the project were:<br />
<br />
* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]<br />
* [https://github.com/sublimino Andrew Martin]<br />
* [https://github.com/Lambdanaut Josh Thomas]<br />
* '''YOUR NAME BELONGS HERE'''<br />
<br />
= Road Map and Getting Involved =<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
<br />
1. Setup Wiki – develop guidelines for participation<br />
2. Setup mailing list - connect researchers and interested people worldwide<br />
3. Improve Wiki – start discussion about ethics <br />
4. Improve Wiki – provide methods of Social Engineering<br />
5. Improve Wiki – known research, literature and best practices<br />
6. Setup working groups – worksheets for consumers<br />
7. Improve mailing list – Evaluate current structure: is it sufficient or is adjustment necessary?<br />
8. Peer review – worksheets for consumers<br />
9. Publication – worksheets for consumers<br />
10. Presentation at conferences – spread the word, distribute knowledge<br />
<br />
<br />
<br />
<br />
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.<br />
</span> <br />
<br />
<span style="color:#ff0000"><br />
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. <br />
</span><br />
<br />
As of October 2013, the priorities are:<br />
* Finish the referencing for each principle.<br />
* Update the Project Template.<br />
* Use the OWASP Press to develop a book.<br />
* Finish and publish the book on Lulu.<br />
<br />
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!<br />
You do not have to be a security expert in order to contribute.<br />
Some of the ways you can help:<br />
* Helping find references to some of the principles.<br />
* Project administration support. <br />
* Wiki editing support.<br />
* Writing support for the book.<br />
<br />
=Project About=<br />
<br />
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><br />
<span style="color:#ff0000"><br />
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. <br />
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project<br />
</span><br />
<br />
{{:Projects/OWASP_Example_Project_About_Page}} <br />
<br />
<br />
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><br />
__NOTOC__ <headertabs /> <br />
<br />
[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]]</div>Schmidthttps://wiki.owasp.org/index.php?title=User:Schmidt&diff=233516User:Schmidt2017-09-20T09:18:22Z<p>Schmidt: personal information</p>
<hr />
<div>Hello,<br />
<br />
so you are interested in me.<br />
<br />
Education: MA in linguistics + additional studies (years) in computer science, media science, legal studies and psychology.<br />
<br />
Work life information security: sales national, sales international, project management international, then decided to go swimming with sharks by founding a company solely about information security services - still swimming, with a few more bite marks.<br />
<br />
I am not seeking any moral high ground and I recommend the Universal Declaration of Human Rights, yes that includes article 17 - property. <br />
<br />
http://www.un.org/en/universal-declaration-human-rights/index.html</div>Schmidt