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
(First edit)
(Project About)
Line 113: Line 113:
 
=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}}  
 
  
  

Revision as of 21:53, 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