Armor vs. Checkmarx

Armor gives you what you need to be successful regardless of technical ability. If you can maintain the systems yourself, you are definitely ahead of the game with their service. If you're not prepared to configure and maintain the systems, they do a pretty good job of getting it set up during the onboarding process so that you don't need to dig into the technical guts too much. If you find yourself in over your head, their support staff can handle it for you in most cases.

Incentivized

If you are going with SAST process or want to improve overall security posture then go for it like integrating it with post deployment steps. If you are more concerned about proactive controls better choose other options such as pee-commit hooks and CI security. Also choose other tools for DAST and API scans.

Incentivized

• Security - we have requirements met right out of the box and the implementation of new resources is done with security in mind.
• Speed - We can scale resources easy and the infrastructure is fast and efficient.
• Responsiveness - Support tickets are handled very fast with almost immediate solutions.

Incentivized

• Supports a large number of languages
• Finds a large variety of potential risks

Incentivized

• Authentication and access against the secure messaging portal is overkill when the response I'm logging in to see merely says, "yes, we have your message. An agent will respond shortly". There should be an option to receive updates like this through email.
• The online portal that allows us to clone servers is very slow to respond. More than once I've spun up an additional server due to the lack of visual feedback on the initial request.
• The web application firewall does not seem to be sophisticated enough to differentiate between logged in administrators and end users. We use a CMS system which allows admins to create scripts. These often get barred by the WAF even though they are not malicious.

Incentivized

• DAST capability can be the one where it does not support native use case of using OTP based arch
• API Scanning is something that lacks a bit due to not much customizations
• Branch wise reports for SAST is not available

Incentivized

Checkmarx's usability is generally good, but it can be a bit complex for new users. The interface may take some time to get used to, especially for those unfamiliar with security tools. Once you become familiar with it, it’s effective and integrates well into development workflows.

Incentivized

Approximately 50% of all messages we receive are automated. Either that an agent will be assigned, has been assigned, or a ticket is closed. I'd like to see more 'real' interaction, and less box ticking, though I appreciate process has to be followed. That's the one point off. Everything else is very good.

Incentivized

Checkmarx is easier to integrate with development tools and gives quick feedback during coding, which is helpful for developers. Veracode is more focused on scanning and reporting for compliance, but it’s more complex to set up. We chose Checkmarx because it fits better into our development process, offering faster scans and more useful suggestions for fixing problems

Incentivized

• Great diversity of vulnerabilities covered.
• Quicker scans
• They are feature rich compared to other tools I used in the past.
• Dashboards are not customizable enough.
• High number of false positives take up time and sometimes make our report look bad.

Incentivized