Checkmarx vs. Google Cloud DNS

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

Google cloud is well suited to access and collaborate on documents where more than 2 people are required to contribute and in instances where feedback from individuals is captured on the document itself. If a team is working on an end of year report for funders, a few key members may need to finalise a report by offering suggestions that can be viewed and resolved by other team members. Housing documents on Google Cloud is the most appropriate platform I have ever used for tasks like these. If minimal collaboration needs engagement from just 2 individuals, it may be easier to simply email the information between each other, rather than using time to create a folder, ensure access control and upload the information to Google Cloud for collaborative input

Incentivized

• Detects security vulnerabilities in source code with accuracy and detail.
• Integrates seamlessly with CI/CD pipelines, IDEs, and repositories.
• Provides clear reports and actionable fix recommendations for developers.

Incentivized

• Interface is user friendly
• It is safe , Secure and reliable
• It has lower pricing plans
• They have good customer support
• They do have good documentation to have fair ideas on their offerings

Incentivized

• Scan duration
• False positives
• Integration with other tools like Jenkins comes with some inconveniences.

Incentivized

• It is hard for first time user to get used to it.
• Support is restricted for 3rd party services who uses it
• Sometimes the support people take more than 24hrs to reply to our queries, But it is not for all issues.
• Search function could have been made easy to search records

Incentivized

Their API based customizations which I leveraged to create an ASPM package, which is developer friendly and can extend above the dashboard features, other ones are UI which is great and feels clutter free. Menu and navigation is also good so as support. Only drawback is sometimes scan takes longer which I feel so can be reduced

Incentivized

This is exceptionally simple to utilize in the event that you are as of now utilizing Google Cloud Services or you are important for the Google Ecosystem as of now. I accept this is likely the primary goal of Google Cloud DNS, to give a more complete set-up of devices to Google Cloud clients. Consequently, I would rate convenience a 9.

In the event that you are utilizing Google Cloud Platform as your cloud supplier, Google Cloud DNS is unquestionably the DNS supplier to utilize.

I haven't required help for it yet, notwithstanding, in my experience, Google Support is incredible.

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

Amazon Route 53 offers almost equal or slightly more features than Google Cloud DNS; we selected Google Cloud DNS because the rest of our projects use Google Cloud Platform.

Also, since AWS is a bigger service provider, their pricing is also higher; since Google Cloud DNS pricing is better, we went for it.

Incentivized

• Improved ability to provide high level of IA confidence
• Improved confidence in application-level security

Incentivized

• We use GCP for all our projects so Google Cloud DNS fits perfectly
• It is proving to scale well so good for us since we are a growing company
• It is easy to use and doesn't require a separate team to maintain

Incentivized