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"
KateHartmann (talk | contribs) (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;" | | ||
| − | |||
| − | |||
| − | |||
| − | |||
==The OWASP Secure Configuration Guide== | ==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. | |
| − | |||
| − | |||
| − | |||
| Line 23: | Line 16: | ||
==Description== | ==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 [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. | |
| − | <!-- | + | <!-- 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;" | | |
| − | |||
| − | |||
| + | == Project Leader == | ||
| + | * [mailto:[email protected] Alexander Antukh] | ||
| − | |||
| − | |||
== Related Projects == | == Related Projects == | ||
| − | + | * [[OWASP Testing Project]] | |
| − | + | * [[Configuration]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<!-- 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;" | | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | == News and Events == | ||
| − | + | * [25 Nov 2014] Project initiated | |
| − | |||
| − | |||
| − | |||
| − | |||
| Line 88: | Line 63: | ||
== In Print == | == In Print == | ||
| − | + | This project can be purchased as a print on demand book from Lulu.com | |
| − | |||
| − | |||
| − | |||
| Line 97: | Line 69: | ||
==Classifications== | ==Classifications== | ||
| − | |||
| − | |||
| − | |||
| − | |||
{| width="200" cellpadding="2" | {| width="200" cellpadding="2" | ||
| Line 117: | Line 85: | ||
=FAQs= | =FAQs= | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==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, | + | 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:[email protected] Alexander Antukh] | + | * [mailto:[email protected] Alexander Antukh] |
| + | * Here might be you :) | ||
= Road Map and Getting Involved = | = Road Map and Getting Involved = | ||
Revision as of 21:38, 24 November 2014
|
The OWASP Secure Configuration GuideThere 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.
DescriptionAll 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. LicensingThe 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
In PrintThis project can be purchased as a print on demand book from Lulu.com
Classifications
| |||||||
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
- Alexander Antukh
- Here might be you :)
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
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
| PROJECT INFO What does this OWASP project offer you? |
RELEASE(S) INFO What releases are available for this project? | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| |||||||||||||||||||||||||||||||||||||||
