AWS CloudTrail vs. Vulcan Cyber (discontinued)

It is necessary to enable [AWS] Cloudtrail when using AWS in a production environment, otherwise you will not have any idea what is happening within your accounts. Third party monitoring applications will all require [AWS] CloudTrail to be enabled as well. I would not recommend it solely as a monitoring tool, to get the most out of it you must send the logs elsewhere. Either to Cloudwatch logs or a third party product.

Incentivized

It's really challenging at times to contend with multiple vulnerabilities on a daily basis, and having a way to make sense of what actually needs to be prioritized and what can be shifted further down the task list is extremely helpful. Because the solution suggests what your next step should be in mitigating a specific vulnerability, it helps us save time and research by enabling us to immediately take action after being informed about an issue.

Incentivized

• API Log
• User activity tracking
• Real-time alerts

Incentivized

• Identifies vulnerabilities and they are easily understood.
• Easy to identify remedies in an instant.
• Campaign feature is a true time saver
• Our CSM, Nino, is the best I have ever worked with!

Incentivized

• [In my experience] Cost can easily get out of control with multiple trails on full logging
• Logs can be difficult to decipher

Incentivized

• Deduping of assets could be better.
• The weighting of vulnerabilities is hard to describe to non technical executives.
• The Business Groups and Tagging needs improvement. Or at least allow tags to be removed if not needed. Now they are static from the API feed.

Incentivized

I think in the end, CloudTrail has more features and you can dive deeper inside the logs so it depends on your usage and what you expect in the end to make the right choice, I would say that both tools are really useful and bring a lot of benefits to I.T. companies.

Incentivized

I wasn't here at the time when the company compared different vulnerability management platforms so I'm not sure on the reasoning and difference between the 2. It could be that the team went through different choices and found Vulcan to be the best fit. It's hard for me to say why Vulcan was specifically chosen

Incentivized

• Allows us to investigate any strange api actions
• Increases security
• Audit trail of changes made in AWS

Incentivized

• Allows much better prioritizing of which assets are most vulnerable
• Allow a better understanding of what assets are actually under real threat vs. what is assumed to be vulnerable, but the real world fact is the system would be hard to reach internally, so it's not as vulnerable.

Incentivized