Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added checklists, wargames, osec, auto-audit #40

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions security-checklist.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,12 @@
- [ ] Be prepared for bad actors & DDOS - use a hosting service that has DDOS mitigation.
- [ ] Set up monitoring for your systems, and log stuff (use [New Relic](https://newrelic.com/) or something like that).
- [ ] If developing for enterprise customers, adhere to compliance requirements. If AWS S3, consider using the feature to [encrypt data](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html). If using AWS EC2, consider using the feature to use encrypted volumes (even boot volumes can be encrypted now).
- [ ] Setup and configure a Web Application Firewall (like dotDefender: http://www.applicure.com/download-latest)
- [ ] Setup and configure an Intrustion Detection System (like Snort: https://www.snort.org/)

##### STATIC AND DYANMIC ANALYSIS
- [ ] Static analysis is available for some languages and can trace user input through a system while exposing potentially vulnerable code (eval, exec, fgets sprintf vs snprintf, etc). An example for PHP is RIPS https://www.ripstech.com
- [ ] Dynamic analysis leverages fuzzing (automatically generated user input) and error detection (do we see PHP errors? does the page render our JavaScript? etc) -- the best fuzzers are targeted to the application and created by hand, but some tools like w3af, the professional version of Burpsuite, Nessus, and sqlmap provide a solid base-line.

##### PEOPLE
- [ ] Set up an email (e.g. [email protected]) and a page for security researchers to report vulnerabilities.
Expand All @@ -80,3 +86,13 @@
- [ ] Have your code review done by a fellow developer from a secure coding perspective. (More eyes)
- [ ] In case of a hack or data breach, check previous logs for data access, ask people to change passwords. You might require an audit by external agencies depending on where you are incorporated.
- [ ] Set up [Netflix's Scumblr](https://github.com/Netflix/Scumblr) to hear about talks about your organization on social platforms and Google search.

##### OTHER CHECKLISTS
- [ ] https://www.owasp.org/index.php/Testing_Checklist
- [ ] https://www.owasp.org/index.php/OWASP_Secure_Coding_Practices_Checklist
- [ ] https://www.owasp.org/index.php/Web_Application_Security_Testing_Cheat_Sheet

##### WEB SECURITY WARGAMES
- [ ] http://overthewire.org/wargames/natas/
- [ ] https://www.hackthissite.org/
- [ ] https://www.hellboundhackers.org/