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 Security Knowledge Framework"
Johestephan (talk | contribs) (→Contributors) |
(→Contributors) |
||
| Line 186: | Line 186: | ||
;Tom wirschell | ;Tom wirschell | ||
;[[user:johestephan|Joerg Stephan]] | ;[[user:johestephan|Joerg Stephan]] | ||
| + | ;Mihai Roman | ||
<br/> | <br/> | ||
Revision as of 09:50, 29 November 2016
OWASP Security Knowledge FrameworkThe OWASP Security Knowledge Framework is intended to be a tool that is used as a guide for building and verifying secure software. It can also be used to train developers about application security. Education is the first step in the Secure Software Development Lifecycle. The 4 Core usage of SKF:
DescriptionThe OWASP Security Knowledge Framework is an expert system web-application that uses the OWASP Application Security Verification Standard and other resources. It can be used to support developers in pre-development (security by design) as well as after code is released (OWASP ASVS Level 1-3). Why Use The OWASP Security Knowledge Framework?Our experience taught us that the current level of security the current web-applications contain is not sufficient enough to ensure security. This is mainly because web-developers simpy aren't aware of the risks and dangers are lurking, waiting to be exploited by hackers. Because of this we decided to develop a security tool in order to create a guide system available for all developers so they can develop applications secure by design. The security knowledge framework is here to support developers create secure applications. By analysing proccessing techniques in which the developers use to edit their data the application can link these techniques to different known vulnerabilities and give the developer feedback regarding descriptions and solutions on how to properly implement these techniques in a safe manner. The seccond stage of the application is validating if the developer properly implemented different types of defense mechanisms by means of different checklists such as the application security verification standards. By means of the answers supplied by the developer the application again generates documentation in which it gives feedback on what defense mechanisms he forgot to implement and give him feedback regarding descriptions and solutions on how to properly implement these techniques in a safe manner. LicensingThis program is free software: you can redistribute it and/or modify it under the terms of the link GNU Affero General Public License 3.0 as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
Donate<paypal>Security Knowledge Framework </paypal> |
Project DownloadGithub/source-code: Installation guide: Installation guide with Chef: Installation guide for AWS: Project Online Demousername: admin password: test-skf Project website: Video demoProject OWASP-SKF PebbleReleased OWASP-SKF Pebble in the Appstore for free Related Projects
Project LeadersGlenn ten Cate Classifications
| ||||||
For detailed information, documentation, tutorials and guide's please visit:
https://skf.readme.io
OR
https://www.securityknowledgeframework.org
Slides of workshop DevOpsDays 2015 Amsterdam:
https://www.owasp.org/images/5/54/Skf-design-workshop.pptx.pdf
Roadmap
Check out the: Online Scrum Board
- Add code examples -> relevant knowledge-base items in results - Add generic Selenium test cases for the pre-development and post-development security controls. - Add current code examples and refer them in the advices of the pre-development and post-development items. - Add CWE to checklists - Add Python code examples - Add Java code examples - Explain the SDLC more in-depth on our website and OWASP wiki page. - Add Go/Ruby/??? code examples
Getting Involved
Submitting a Pull Request on Guthub:
Fork it. Create a branch (git checkout -b my_markup) Commit your changes (git commit -am "Added Snarkdown") Push to the branch (git push origin my_markup) Check Travis status if build is still working Open a Pull Request
One of the authors will check your sample code or knowledge-base item and add it to the master repo.
SKF uses the following services to provide quality over the code and releases.
Travis-ci.org:
Test and Deploy with Confidence. Easily sync your GitHub projects with Travis CI and you'll be testing your code in minutes! SKF Build details:
https://travis-ci.org/blabla1337/skf-flask
Coveralls.io:
DELIVER BETTER CODE. We help developers deliver code confidently by showing which parts of your code aren't covered by your test suite. SKF Coveralls details:
https://coveralls.io/r/blabla1337/skf-flask
Scrutinizer-ci.com
Why to use Scrutinizer. Improve code quality and find bugs before they hit production with our continuous inspection platform. Improve Code Quality. SKF Scrutinizer details:
https://scrutinizer-ci.com/g/blabla1337/skf-flask/
Uptimerobot.com
Monitor HTTP(s), Ping, Port and check Keywords. Get alerted via e-mail, SMS, Twitter, web-hooks or push. View uptime, downtime and response times.
ssllabs.com & sslbadge.org
ssllabs.org: Bringing you the best SSL/TLS and PKI testing tools and documentation. https://www.ssllabs.com/ssltest/analyze.html?d=securityknowledgeframework.org
sslbadge.org: Creates a nice badge for your website SSL/TLS security settings based on the Qualys SSL Labs testing.
- Glenn ten Cate
- Riccardo ten Cate
- Alexander Kaasjager
- John Haley
- Daniel Paulus
- Erik de Kuijper
- Roderick Schaefer
- Jim Manico
- Martijn Gijsberti Hodenpijl
- Bithin Alangot
- Martin Knobloch
- Adam Fisher
- Tom wirschell
- Joerg Stephan
- Mihai Roman
Thank you to my colleagues at Schuberg Philis for helping and giving feedback.
