This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "OWASP Secure Configuration Guide"

From OWASP
Jump to: navigation, search
(Created page with "=Main= <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">link=</...")
 
(First edit)
Line 7: Line 7:
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.
 
−
</span>
 
  
 
==The OWASP Secure Configuration Guide==
 
==The OWASP Secure Configuration Guide==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
There are small unclassified parts of info of configuration issues on OWASP currently; this project is to create unified document of issues and solutions to avoid common misconfigurations in popular frameworks, web servers, network devices and more.
−
<span style="color:#ff0000">
 
−
This is where you need to add your more robust project description. A project description should outline the purpose of the project, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, and project leaders should ensure that the description is meaningful.
 
−
</span>
 
  
  
Line 23: Line 16:
 
==Description==
 
==Description==
  
−
There are small unclassified parts of info of configuration issues on OWASP currently; this project is to create unified document of issues and solutions to avoid common misconfigurations in popular frameworks, web servers, network devices and more.
+
All of us know such situations when robust and secure solution makes your defense even weaker if misconfigured.
 +
Nearly in every penetration testing report exists a chapter "Server/Framework/Service misconfiguration".
 +
Whereas using standard up-to-date impenetrable(*) software is certainly a good thing, one should consider proper configuration in order to verify its soundness.
  
−
==Licensing==
+
This project is useful for both defenders, who can learn the proper way of configuring rapidly growing number of different popular software, and attackers, as a good complement to Testing Guide.
  
−
Creative Commons Attribution ShareAlike 3.0 License
 
  
−
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
−
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
  
−
== What is OWASP Secure Configuration Guide? ==
+
(*) Saying "impenetrable" we mean all public vulnerabilities are patched in the most recent version. 0-days are still a threat but it's a different talk.
  
−
There are small unclassified parts of info of configuration issues on OWASP currently; this project is to create unified document of issues and solutions to avoid common misconfigurations in popular frameworks, web servers, network devices and more.
+
==Licensing==
  
−
== Presentation ==
+
The OWASP Secure Configuration Guide is free to use. It is licensed under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
−
<span style="color:#ff0000">
+
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
−
This is where you can link to slide presentations related to your project.
 
−
</span>
 
  
  
 +
== Project Leader ==
  
 +
* [mailto:alexander.antukh@owasp.org Alexander Antukh]
  
−
== Project Leader ==
 
  
  
  
−
* [mailto:alexander.antukh@owasp.org Alexander Antukh]
 
  
  
 
== Related Projects ==
 
== Related Projects ==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
* [[OWASP Testing Project]]
−
<span style="color:#ff0000">
+
* [[Configuration]]
−
This is where you can link to other OWASP Projects that are similar to yours.
 
−
</span>
 
  
−
== Openhub ==
 
−
 
−
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]
 
  
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
| valign="top"  style="padding-left:25px;width:200px;" |
 
| valign="top"  style="padding-left:25px;width:200px;" |
−
 
−
== Quick Download ==
 
−
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
This is where you can link to your repository.
 
−
</span>
 
  
  
  
 +
== News and Events ==
  
−
== News and Events ==
+
* [25 Nov 2014] Project initiated
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
This is where you can link to press your project has been a part of. Appropriate press includes: Project Leader interviews, articles written about your project, and videos about your project.
 
−
</span>
 
  
  
Line 88: Line 63:
 
== In Print ==
 
== In Print ==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
This project can be purchased as a print on demand book from Lulu.com
−
<span style="color:#ff0000">
 
−
This is where you place links to where your project product can be downloaded or purchased, in the case of a book.  
 
−
</span>
 
  
  
Line 97: Line 69:
 
==Classifications==
 
==Classifications==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
Here is where you can let the community know what project stage your project is currently in, whether the project is a builder, breaker, or defender project, and what type of project you are running.
 
−
</span>
 
  
 
   {| width="200" cellpadding="2"
 
   {| width="200" cellpadding="2"
Line 117: Line 85:
  
 
=FAQs=
 
=FAQs=
−
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'
 
−
</span>
 
−
 
  
 
==How can I participate in your project?==
 
==How can I participate in your project?==
Line 128: Line 90:
  
 
==If I am not a programmer can I participate in your project?==
 
==If I am not a programmer can I participate in your project?==
−
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.  
+
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, reviewers, translators, and a project administrator.  
  
 
= Acknowledgements =
 
= Acknowledgements =
Line 134: Line 96:
 
==Contributors==
 
==Contributors==
  
−
[mailto:alexander.antukh@owasp.org Alexander Antukh]
+
* [mailto:alexander.antukh@owasp.org Alexander Antukh]
 +
* Here might be you :)
  
 
= Road Map and Getting Involved =
 
= Road Map and Getting Involved =

Revision as of 21:38, 24 November 2014

OWASP Project Header.jpg


The OWASP Secure Configuration Guide

There are small unclassified parts of info of configuration issues on OWASP currently; this project is to create unified document of issues and solutions to avoid common misconfigurations in popular frameworks, web servers, network devices and more.


Description

All of us know such situations when robust and secure solution makes your defense even weaker if misconfigured. Nearly in every penetration testing report exists a chapter "Server/Framework/Service misconfiguration". Whereas using standard up-to-date impenetrable(*) software is certainly a good thing, one should consider proper configuration in order to verify its soundness.

This project is useful for both defenders, who can learn the proper way of configuring rapidly growing number of different popular software, and attackers, as a good complement to Testing Guide.


(*) Saying "impenetrable" we mean all public vulnerabilities are patched in the most recent version. 0-days are still a threat but it's a different talk.

Licensing

The OWASP Secure Configuration Guide is free to use. It is licensed under the Creative Commons Attribution-ShareAlike 3.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.


Project Leader




Related Projects


News and Events

  • [25 Nov 2014] Project initiated



In Print

This project can be purchased as a print on demand book from Lulu.com


Classifications

New projects.png Owasp-breakers-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files DOC.jpg

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Secure_Configuration_Guide&oldid=185841"