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=</...")
 
(News and Events)
 
(23 intermediate revisions by 4 users not shown)
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.
+
The latest version of wiki is accessible here:
</span>
+
https://www.owasp.org/index.php/Secure_Configuration_Guide
  
  
Line 23: Line 19:
 
==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 Leaders ==
  
 +
* [mailto:alexander.antukh@owasp.org Alexander Antukh]
 +
* [[User:Dvvord|Eduard Kovalets]]
  
== Project Leader ==
+
== Presentation ==
  
 +
[https://www.owasp.org/images/9/92/OWASP_Secure_Configuration.pptx Introduction to OWASP Secure Configuration Project.pptx]
  
  
* [mailto:alexander.antukh@owasp.org Alexander Antukh]
 
  
 +
== Related Pages ==
  
== Related Projects ==
+
* [https://www.owasp.org/index.php/Secure_Configuration_Guide Table of Contents]
 +
* [https://www.owasp.org/index.php/Configuration  OWASP Development Guide: Chapter on Configuration]
 +
* [https://www.owasp.org/index.php/Testing_for_configuration_management  OWASP Testing Guide: Configuration Management]
 +
* [https://www.owasp.org/index.php/Insecure_Configuration_Management  Insecure Configuration Management page ]
  
<!-- 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 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 ==
 
+
* [21 April 2016] NginX Secure Configuration updated. Refer to [https://www.owasp.org/index.php/SCG_WS_nginx]
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
* [20 Dec 2014] Mailing list created
<span style="color:#ff0000">
+
* [19 Dec 2014] First article released
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.  
+
* [25 Nov 2014] Project initiated
</span>
 
 
 
 
 
  
 
== 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 73:
 
==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 89:
  
 
=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 94:
  
 
==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 100:
 
==Contributors==
 
==Contributors==
  
[mailto:alexander.antukh@owasp.org Alexander Antukh]
+
* [[User:Alexander_Antukh|Alexander Antukh]]
 +
* [[User:Dnkolegov|Denis Kolegov]]
 +
* [[User:Makash|Akash Mahajan]]
 +
* [[User:Anant_Shrivastava|Anant Shrivastava]]
 +
* [[User:Dvvord|Eduard Kovalets]]
 +
* [[User:Nishanthkumarpathi|Nishanth Kumar Pathi]]
 +
 
 +
 
 +
We hope you find the information in the OWASP Secure Configuration Guide useful. Please contribute back to the project by sending your comments, questions, and suggestions to the OWASP SCG mailing list. Thanks!
  
 
= Road Map and Getting Involved =
 
= Road Map and Getting Involved =
Line 150: Line 124:
 
=Project About=
 
=Project About=
  
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
{{:Projects/OWASP__Secure_Configuration_Guide}}  
<span style="color:#ff0000">
 
This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager.
 
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
 
</span>
 
 
 
{{:Projects/OWASP_Example_Project_About_Page}}  
 
  
  
Line 162: Line 130:
 
__NOTOC__ <headertabs />  
 
__NOTOC__ <headertabs />  
  
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]]
+
[[Category:OWASP Project]]  [[Category:OWASP_Breakers]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]]

Latest revision as of 08:09, 21 April 2016

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.

The latest version of wiki is accessible here: https://www.owasp.org/index.php/Secure_Configuration_Guide


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 Leaders

Presentation

Introduction to OWASP Secure Configuration Project.pptx


Related Pages


News and Events

  • [21 April 2016] NginX Secure Configuration updated. Refer to [1]
  • [20 Dec 2014] Mailing list created
  • [19 Dec 2014] First article released
  • [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

How can I participate in your project?

All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

If I am not a programmer can I participate in your project?

Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, reviewers, translators, and a project administrator.

Contributors


We hope you find the information in the OWASP Secure Configuration Guide useful. Please contribute back to the project by sending your comments, questions, and suggestions to the OWASP SCG mailing list. Thanks!

Project will help those looking for configuration issues when facing a new web application / framework, and at the same time let developers have all information of correct configuration settings (which are not always perfect by default) for common systems. Cases may vary from how to configure Drupal in order not to let unauthorized attacker to enumerate current users to how to protect your config files from being downloaded to how to forbid unauthorized firmware upload for your device.

The idea is to create the unified source of knowledge (like Testing Guide), where all information will be accessible in one place. As new systems appear and new features are being added, the project will be continuously developed. Any penetration tester/administrator/security consultant can contribute when meeting new (yet undocumented) system.

Initially planned chapters: - Web servers - Frameworks - Network devices / web panels - ... more to come

PROJECT INFO
What does this OWASP project offer you?
RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: OWASP Secure Configuration Guide (home page)
Purpose: 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.
License: Creative Commons Attribution-ShareAlike 3.0
who is working on this project?
Project Leader(s):
  • Alexander Antukh @
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: Mailing List Archives
Project Roadmap: View
Key Contacts
  • Contact Alexander Antukh @ to contribute to this project
  • Contact Alexander Antukh @ to review or sponsor this project
current release
Not Yet Published
last reviewed release
Not Yet Reviewed


other releases