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.7 out of 10
Mid-Size Companies (51-1,000 employees)
Veracode provides advanced application security solutions, trusted by enterprises to develop and maintain secure software. Its platform identifies exploitable risks, speeds up vulnerability remediation, and reduces security debt at scale using a proprietary AI-assisted remediation engine.
N/A
Pricing
Crucible
Veracode
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Crucible
Veracode
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Developer pricing options available
More Pricing Information
Community Pulse
Crucible
Veracode
Considered Both Products
Crucible
Verified User
Anonymous
Chose Crucible
Not exactly an apples to apples comparison. Back when we were using SVN, Crucible was the go-to solution for code review. As we started moving to use Git and using pull requests (via Bitbucket), code review is now performed by using pull requests exclusively.
Crucible has a better look and feel for developers because it is web compatible and works well with IE or Chrome. Being that it is a web browser friendly, using Crucible is seamless and user-friendly. Github is an external tool on a different environment that requires more …
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 …
I think Crucible isn't quite as clean as Stash/Bitbucket, but it does some things better, like seeing individual commits easier. I also like how stash groups all comments on the overview of the Pull Request.
Gitlab and Github are very comparable to Crucible, and would probably be my first choice if those were the tools used for versioning as they are directly linked to git. Crucible was chosen by a current client and I had no choice in its selection. I would probably have chosen …
We selected Veracode after testing these tools with 3 important solutions and Veracode had a great ratio of findings, with low false positive, and the best price between the tools that were good enough.
I found SonarQube to have some decent data for code quality checks but it underperformed for code security.
Snyk is a decent product and strong competitor to Veracode for SCA. Snyk's SAST offering is not as good as Veracode and does not support as many languages.
Sonatype only identifies and scans third-party dependency and not custom-developed code—at least that's what it was doing back in 2018 when I used to utilize its services. Interface-wise, too, Veracode looks much cleaner and easier to navigate than Sonatype. Support and …
As mentioned previously, we're always considering other options. Veracode is what we need right now, and I don't think it would be fair to competitors to compare them to what we need right now. Tomorrow, we might need something else and not require Veracode—that isn't a change …
Veracode seems to provide better support and good scan coverage. Veracode also provides multiple scan types like Dynamic, Static Code, Software Composition which others may only offer 1 or 2. I might be missing it but some others like Sentinel provide schedule monthly, …
Veracode is slower with scan results however the flaws discovered and sites crawled are almost the same. Rapid7 InsightAppSec only does dynamic scans. Veracode did find more links on a site crawl. Rapid7 InsightappSec has more out of the box reports than Veracode. Both …
Veracode was brought in to supplement services previously provided by other vendors. As our org recently acquired another organization, we identified Veracode as a 'go-forward' system needed to consolidate security tooling in the organization.
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.
The maturity of the Veracode and the continuous improvements in its products it's one of the principal characteristics of chosee it, Veracode it's a SaaS platform and was born in the cloud, so this is a great option for our clients to be quick to implement also the easy of …
Checkmarx and Veracode have a few common points and some features which are different. Checkmarx UI is more user-friendly, but the level of detailing in Veracode reports is better. Veracode is a good choice for static analysis of code. if the user interface can be made smoother …
As the developer, not the business stakeholder, I did not select Veracode specifically. However, after using the application I believe it was the right choice. Veracode is thorough in its analyses, in its database of flaws, in its methodology of uncovering vulnerabilities, and …
Depends on the version control and devops process your development teams adopt. Git (via Bitbucket, GitHub, GitLab, etc...) has become the new industry norm, and using pull requests can often provide the same code review features Crucible is used for. However, if you require code review beyond change/diff based (i.e. via pull request), then Crucible allows you to review code with more granular control, such as on per file basis.
* (+) Report generation for our clients: reports are very comprehensive and look professional. * (-) Veracode pipeline scan: takes too much time, need to split our application so that it can fit within the timeout (2h). Currently we're not able to use it, we still use "upload & scan" functionality in our CI pipelines. This is a showstopper to be able to break the build in case of new vuln, and also to use Fix AI based tool.
It can sometimes be a bit slow to load. A server reboot for us tends to solve that issue. I'm not sure if it is a server issue, or maybe Crucible may have some caching issues.
I wish that you could easily stop the review creation process, rather than abandoning it.
We would like to see Veracode continue to improve the integrations available, particularly with respect to .NET IDEs. Part of our development team uses JetBrains' Rider which is, as of this time, unsupported for static integration.
We would also like to see Veracode continue to improve their dynamic scan offerings; with the recent addition of DAST Essentials we feel this improvement may come sooner than later.
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.
Gitlab and GitHub are very comparable to Crucible, and would probably be my first choice if those were the tools used for versioning as they are directly linked to git. Crucible was chosen by a current client and I had no choice in its selection. I would probably have chosen GitHub if given a say.
Sonatype only identifies and scans third-party dependency and not custom-developed code—at least that's what it was doing back in 2018 when I used to utilize its services. Interface-wise, too, Veracode looks much cleaner and easier to navigate than Sonatype. Support and consultation with how-to guides and documents make Veracode easier to use.
I am not involved in the acquisition of Crucible so I cannot comment on the financial investment but I believe it is a necessary tool to have in any software shop, small or big.
As a developer, having Crucible as the code review process is a great asset and will save time and reduce risks which I believe is a positive return of investment.
Positive: Scanning all our applications on Veracode provides us an overview of our cyber security posture for the organization as a whole.
Positive: Performing the SAST, SCA and DAST scanning for all the applications at the early stages of the SDLC helps us identify and mitigate security vulnerabilities early, reducing the risk of data breaches and cyber-attacks.
Negative: Sometimes Veracode SAST scanner closed and reopens some findings, leading to reliability issues on the scanner itself.