OWASP Secure Configuration Guide

=Main=



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

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.

The OWASP Secure Configuration Guide
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.

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.

Licensing
Creative Commons Attribution ShareAlike 3.0 License


 * valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

What is 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.

Presentation
This is where you can link to slide presentations related to your project.

Project Leader

 * [mailto:alexander.antukh@owasp.org Alexander Antukh]

Related Projects
This is where you can link to other OWASP Projects that are similar to yours.

Openhub

 * OWASP Project Openhub


 * valign="top" style="padding-left:25px;width:200px;" |

Quick Download
This is where you can link to your repository.

News and Events
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.

In Print
This is where you place links to where your project product can be downloaded or purchased, in the case of a book.

Classifications
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.


 * }

=FAQs=

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.'

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

If I am not a programmer can I participate in your project?
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =

Contributors
[mailto:alexander.antukh@owasp.org Alexander Antukh]

= Road Map and Getting Involved =

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 About=

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