Atlasssian Crucible is a peer review tool for finding bugs and defects in version control tools Subversion, Git, Mercurial, CVS, and Perforce.
N/A
Veracode
Score 8.5 out of 10
Mid-Size Companies (51-1,000 employees)
Veracode is an application security platform that performs five types of analysis; static analysis, dynamic analysis, software composition analysis, interactive application security testing, and penetration testing. Veracode offers on-demand expertise and aims to help companies fix security defects.
Crucible is well suited for situations where development teams follow a branch-based merge process, where new features or automation stories are introduced. It allows more seasoned team members to check newer team members' code to ensure standards are followed. It is probably less appropriate for smaller development teams or smaller projects, where code reviews can be less formal.
Within our organization it is clear that when a codebase is available, and in a language that Veracode supports, the use of Veracode (with a particular focus to the static scanning platform) is a great suggestion. The depth of information it can provide with respect to security flaws is valuable, with very little setup required from the developers. When a codebase is unavailable, say in the instance of third-party applications for which you are creating extensions or some form of module, then static code scanning is not an option but even then dynamic scanning (DAST) may prove to be helpful, though potentially less so.
The pipeline scan is a very fast way to scan code and inform developers if a new flaw is introduced by their pull requests.
Upload & Scan provides an in-depth analysis of the codebase, which features like reporting being made easy.
SCA Scans help us not only identify the vulnerabilities but also in helping fix them and in identifying if our application is using that part of the vulnerable library or not.
Veracode is very easy to integrate into the CI/CD pipelines (especially Jenkins)
Crucible notifications of changes or updates to the code review are delayed as well as loading more source code is slow.
Crucible is formatting could use improvements for viewing customization features. For instance, allowing the user to create a new tab per file to be reviewed would be nice to have.
At this time, and we just renewed a month ago, I dont see any products out there overall that can offer what Veracode does. Yes, its not cheap by any means, but for the money its the best application security scanning tool out there.
- Almost no setup required and easy to configure - Very easy to use, intuitive UI with integrated analytics and learning portals. - Seamless to review the results, triage them, generate reports. - Security progression of the product/application is tracked via successive scans. - Privileges/Roles nicely fine grained and tightly controlled to let teams "view" only their products.
Overall, Veracode support is helpful, community support is great, and documentation is available for self-service. Our Customer Success Manager is very helpful and reaches out regularly to see if we need assistance. We have not utilized many of the other resources offered by Veracode, however, in the future we would like to leverage secure coding training for our Development teams.
We use it as a SAS service, so really just getting our teams to mold the use of Veracode into their SDLC has been a process of years in the making. It comes down to what your teams are ready and willing to accept and change. Management is key in getting their groups on board with using it regularly. If it doesnt have management backing, your security teams have little to no influence in getting this process off the ground fully.
Crucible was first on the market and the price is inexpensive. Crucible integrates with Jira Software and Atlassian Fisheye, providing the ability to track defects efficiently. SonarQube compares code to 'best standards' but not 'internal standards' and does not integrate to issue tracking. GitHub offers effective peer review, and has some integration with GitHub issues but costs more.
Mend.IO formerly WhiteSource software is a product we used prior to Vericode. It did not have all of the capabilities or depth of Vericode. Additionally, Whitesource did not offer automatic scanning as part of their product and there was no Certification program to speak of.
Developers are now realizing that security is there to help them, not just the people saying NO.
When setting up Veracode integrations we found that Devs really like their IDEs and Repos. It's like a personal choice. However, as a company, it was unwieldy without devoting people to Veracode integrations to have so many so we had to slime the available IDEs to 3 and Repos to 3, just to be able to set up and maintain the integrations.
Veracode is paying for itself (though through a different cost category). Our Development costs are going down and releases are getting quicker and more agile.
