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 SEDATED"
(Updated SEDATED wiki) |
(SEDATED updates) |
||
Line 37: | Line 37: | ||
== Project Resources == | == Project Resources == | ||
− | |||
− | |||
[https://github.com/owasp/SEDATED Source Code] | [https://github.com/owasp/SEDATED Source Code] | ||
− | What's New (Revision History) [ | + | What's New (Revision History) [[https://github.com/OWASP/SEDATED/releases Version 1.1.2 is now available!]] |
− | Documentation [ | + | Documentation [[https://github.com/OWASP/SEDATED SEDATED README]] |
== Project Leader == | == Project Leader == |
Latest revision as of 17:44, 11 July 2019
Project About
DescriptionThe SEDATED Project (Sensitive Enterprise Data Analyzer To Eliminate Disclosure) focuses in on preventing sensitive data such as user credentials and tokens from being pushed to GitHub. Developers are constantly pushing changes to GitHub and will most likely eventually try pushing a commit that contains sensitive information and we want to help catch and prevent that. The SEDATED application will run on the Git server and review all incoming code changes. If it identifies sensitive data it will reject the push otherwise it will allow it. LicensingTBD RoadmapTBD Getting InvolvedInvolvement in the development and promotion of OWASP SEDATED is actively encouraged! You do not have to be a security expert or a programmer to contribute. Some of the ways you can help are as follows: |
Project ResourcesWhat's New (Revision History) [Version 1.1.2 is now available!] Documentation [SEDATED README] Project LeaderSimeon Cloutier Related ProjectsClassifications
|