Credit to OWASP Foundation
An ongoing & curated collection of awesome software best practices and techniques, libraries and frameworks, E-books and videos, websites, blog posts, links to github Repositories, technical guidelines and important resources in Cybersecurity Community.
Thanks to all contributors, you're awesome and wouldn't be possible without you! Our goal is to build a categorized community-driven collection of very well-known resources.
OWASP Community Pages is a repository for community contributions for security-related content. The documents here create the website at https://owasp.org/www-community/.
We welcome contributions for new content and updates to current pages. This repository uses a fork and pull model. Here are the steps for becoming a contributor:
- Fork this repository and clone your fork.
- In the
pages/
directory, make your changes or additions. For creating new content, please see below. - Push your changes to your fork, then open a pull request against this repository.
If you are making changes that address an existing issue, please make a comment in the issue so we can assign it to you. This helps to prevent accidentally doubling up on work.
Go into the pages
folder and create a new file.
Place the following front matter and include
tag at the beginning of your file. Feel free to copy and edit this example:
---
layout: col-sidebar
title: "My Page"
author: "My Name"
contributors: ["Additional Contributor Names", "If Any"]
permalink: /MyPageTitle
tags: ["attack", "XSS"]
---
{% include writers.html %}
Write your content here!
The fields contributors
, permalink
, and tags
are optional. When in doubt, it's okay to leave them blank.
- Your contribution must be your own original work. You may not submit copyrighted content you do not own. Please do not plagiarize.
- Please ensure that contributions are vendor and product neutral.
In July of 2020, the repository's git history was rewritten to reduce its size (over 5GB!). If you forked before this date, please delete your fork and local clones, then re-fork or re-clone this repository.