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 Code Pulse Project"
m (Added mailto link) |
m (Announce Code Pulse 2.6.1) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
| − | | | + | | style="border-right: 1px dotted gray;padding-right:25px;" valign="top" | |
==About Code Pulse== | ==About Code Pulse== | ||
| Line 13: | Line 13: | ||
==How it works== | ==How it works== | ||
| − | Code Pulse does its magic by monitoring the runtime of the target application using an agent-based approach. Code Pulse currently supports Java programs, up to Java | + | Code Pulse does its magic by monitoring the runtime of the target application using an agent-based approach. Code Pulse currently supports Java programs, up to Java 11, and .NET Framework programs for CLR versions 2 and 4. It can track code coverage details at the method or source code level to show what's being called and when. Although Code Pulse works for desktop applications, our current focus is on providing the best experience for web application testing. Code Pulse 2.6 incorporates the [https://www.owasp.org/index.php/OWASP_Attack_Surface_Detector_Project OWASP Attack Surface Detector] and helps you see code coverage details for the endpoints of a web application. |
==Why Code Pulse?== | ==Why Code Pulse?== | ||
| Line 19: | Line 19: | ||
Whereas in the past it’s been very difficult to understand which parts of an application a DAST or manual penetration test covered, Code Pulse automatically detects the coverage information while the tests are being conducted and will even make it possible to understand the overlaps and boundaries of the different tools’ coverage. | Whereas in the past it’s been very difficult to understand which parts of an application a DAST or manual penetration test covered, Code Pulse automatically detects the coverage information while the tests are being conducted and will even make it possible to understand the overlaps and boundaries of the different tools’ coverage. | ||
| − | Code Pulse presents the coverage information in a visual form to make it easy to understand at-a-glance which parts of an application have been covered, and how much. The real-time coverage feedback makes it easy to adjust testing activity based on the observed coverage. In addition for testing activities relying on multiple techniques (a variety of dynamic analysis tools for instance) it’s fairly easy to split up the recorded activity to understand which code was covered by each tool independently or | + | Code Pulse presents the coverage information in a visual form to make it easy to understand at-a-glance which parts of an application have been covered, and how much. The real-time coverage feedback makes it easy to adjust testing activity based on the observed coverage. In addition for testing activities relying on multiple techniques (a variety of dynamic analysis tools for instance), it’s fairly easy to split up the recorded activity to understand which code was covered by each tool independently or to view where the coverage overlaps between multiple tools. |
==Licensing== | ==Licensing== | ||
| Line 25: | Line 25: | ||
OWASP Code Pulse project is free to use. It is licensed under the Apache 2.0 License. | OWASP Code Pulse project is free to use. It is licensed under the Apache 2.0 License. | ||
| − | | | + | | style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" | |
== Quick Links == | == Quick Links == | ||
| Line 34: | Line 34: | ||
== News and Events == | == News and Events == | ||
| − | * <span style="background: #66CCFF; font-size:85%;padding:2px;"> | + | * <span style="background: #66CCFF; font-size:85%;padding:2px;">04 Jan 2019</span> [https://github.com/codedx/codepulse/releases/tag/v2.6.1 Version 2.6.1 is out!] |
| − | * <span style="background: #66CCFF; font-size:85%;padding:2px;"> | + | * <span style="background: #66CCFF; font-size:85%;padding:2px;">12 Nov 2018</span> [https://github.com/codedx/codepulse/releases/tag/v2.6.0 Version 2.6.0 is out!] |
| − | * <span style="background: #66CCFF; font-size:85%;padding:2px;"> | + | * <span style="background: #66CCFF; font-size:85%;padding:2px;">08 Aug 2018</span> [https://github.com/codedx/codepulse/releases/tag/v2.5.0 Version 2.5.0 is out!] |
| − | |||
| − | |||
| − | |||
== Contact Us == | == Contact Us == | ||
| − | + | Project Leader: Ken Prole | |
Email: [mailto:[email protected] [email protected]] | Email: [mailto:[email protected] [email protected]] | ||
| Line 52: | Line 49: | ||
== Related Projects == | == Related Projects == | ||
| + | * [[OWASP Attack Surface Detector Project]] | ||
* [[OWASP Zed Attack Proxy Project]] | * [[OWASP Zed Attack Proxy Project]] | ||
* [[OWASP Dependency Check]] | * [[OWASP Dependency Check]] | ||
| Line 59: | Line 57: | ||
{| width="200" cellpadding="2" | {| width="200" cellpadding="2" | ||
|- | |- | ||
| − | | rowspan="2" | + | | rowspan="2" width="50%" valign="top" align="center" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]] |
| − | | | + | | width="50%" valign="top" align="center" | [[File:Owasp-breakers-small.png|link=]] |
|- | |- | ||
| − | | | + | | width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]] |
|- | |- | ||
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] | | colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] | ||
| Line 72: | Line 70: | ||
= Road Map and Getting Involved = | = Road Map and Getting Involved = | ||
| − | The initial version of Code Pulse, version 1.0, was released in early May 2014. Since then, we've pushed out multiple versions to address some usability issues and to include support for Java | + | The initial version of Code Pulse, version 1.0, was released in early May 2014. Since then, we've pushed out multiple versions to address some usability issues and to include support for Java 11, .NET Framework applications, an [[OWASP Dependency Check]] integration, and code coverage details at the source code level. |
Long-term there are a number of things on our roadmap that we’d like to add to Code Pulse. The following is a partial list of features we’d like to add to Code Pulse as we continue development on it: | Long-term there are a number of things on our roadmap that we’d like to add to Code Pulse. The following is a partial list of features we’d like to add to Code Pulse as we continue development on it: | ||
| + | |||
| + | - Web request filter | ||
- Performance improvements | - Performance improvements | ||
| − | |||
| − | |||
| − | |||
| − | |||
Involvement in the development and promotion of Code Pulse is actively encouraged! | Involvement in the development and promotion of Code Pulse is actively encouraged! | ||
Latest revision as of 20:19, 4 January 2019
About Code PulseThe OWASP Code Pulse Project is a tool that provides insight into the real-time code coverage of black box testing activities. It is a cross-platform desktop application that runs on most major platforms.
How it worksCode Pulse does its magic by monitoring the runtime of the target application using an agent-based approach. Code Pulse currently supports Java programs, up to Java 11, and .NET Framework programs for CLR versions 2 and 4. It can track code coverage details at the method or source code level to show what's being called and when. Although Code Pulse works for desktop applications, our current focus is on providing the best experience for web application testing. Code Pulse 2.6 incorporates the OWASP Attack Surface Detector and helps you see code coverage details for the endpoints of a web application. Why Code Pulse?Whereas in the past it’s been very difficult to understand which parts of an application a DAST or manual penetration test covered, Code Pulse automatically detects the coverage information while the tests are being conducted and will even make it possible to understand the overlaps and boundaries of the different tools’ coverage. Code Pulse presents the coverage information in a visual form to make it easy to understand at-a-glance which parts of an application have been covered, and how much. The real-time coverage feedback makes it easy to adjust testing activity based on the observed coverage. In addition for testing activities relying on multiple techniques (a variety of dynamic analysis tools for instance), it’s fairly easy to split up the recorded activity to understand which code was covered by each tool independently or to view where the coverage overlaps between multiple tools. LicensingOWASP Code Pulse project is free to use. It is licensed under the Apache 2.0 License. |
Quick LinksNews and Events
Contact UsProject Leader: Ken Prole Email: [email protected] Related ProjectsClassifications
| |||||||
The initial version of Code Pulse, version 1.0, was released in early May 2014. Since then, we've pushed out multiple versions to address some usability issues and to include support for Java 11, .NET Framework applications, an OWASP Dependency Check integration, and code coverage details at the source code level.
Long-term there are a number of things on our roadmap that we’d like to add to Code Pulse. The following is a partial list of features we’d like to add to Code Pulse as we continue development on it:
- Web request filter
- Performance improvements
Involvement in the development and promotion of Code Pulse is actively encouraged!
You do not have to be a security expert in order to contribute.
Some of the ways you can help:
- Code contributions
- Testing
- Wiki documentation
- Spreading the word about the project!
Visit the Code Pulse GitHub project page to see the source.
Code Pulse is maintained and developed by Code Dx.
Code Pulse is based on research sponsored by the Department of Homeland Security (DHS) Science and Technology Directorate, Cyber Security Division (DHS S&T/CSD), BAA via contract numbers FA8750-12-C-0219 and HHSP233201600058C.
