80 percent of the customers are using AWS GuardDuty, and we recommend it due to its low cost, especially for small customers, ranging from five to ten dollars a month. In our policies, we enforce the usage of this service, making it a recommended practice for security. The responsibility also lies with the customer. We obtain written confirmation from them, stating that if they choose not to use it, they accept responsibility for any potential attacks. In such cases, we refrain from enabling it, and any financial repercussions resulting from incidents are their own accountability.
IT Controller at a outsourcing company with 11-50 employees
Real User
Top 20
2024-01-17T07:22:19Z
Jan 17, 2024
I have heard that the solution's price is quite high. Sometimes, they need to fine-tune the service on AWS. For example, Amazon Simple Storage Service (S3) is used for static content because it is cheaper.
I prefer to have something on demand for myself. That's why I haven't been paying for GuardDuty specifically. AWS provides a wide range of offerings, especially in the security area. They have various services that integrate into a centralized Security Hub, offering insights into different aspects of security issues, especially in networking and the cloud. The findings from GuardDuty would be integrated into the Security Hub service, incurring some small costs. I haven't delved into the specifics of these costs, but I know they are minimal. It's like flipping a switch – you integrate GuardDuty to report to the centralized hub, and if something needs attention, you check the GuardDuty findings. This integration is part of the main central service for security, along with many others, perhaps five or ten. For example, one service scans files in your storage service. Different services may have various agents scanning for different things, like tokens or exposed personal data. It's a unique security issue. Each service detects findings, and you can integrate them into the Security Hub to keep an eye on all aspects of security. GuardDuty is just one of them. Cost-wise, you pay for what you use, without the need to install or spin up servers. You simply tell the cloud that you want these services integrated for immediate on-demand use. The pricing may be complex, based on dimensions like the number of findings and protections used. However, maintaining a smaller infrastructure results in fewer findings, reducing costs and eliminating the need for constant investments and running infrastructure all the time, essentially going serverless.
The platform is inexpensive; It costs approximately $50 a month. However, its pricing is subjective based on the company's requirements. It can go from $10 to $30 to a maximum of $50.
I rate the pricing a seven out of ten. The price of the solution is exactly right. It is neither high nor low. It is a pay-as-you-go model. The more number of accounts we integrate, the more the price will increase.
Director Of Engineering and Data Science at a computer software company with 51-200 employees
Real User
Top 10
2023-07-12T04:25:40Z
Jul 12, 2023
On a scale of one to ten, where one is a high price, and ten is a low price, I rate the pricing a four or five, which is somewhere in the middle. I provided the rating for AWS GuardDutya as four or five out of ten because the pricing would have seemed pretty good if it had more functionalities. Right now, the protection engine isn't that perfect in AWS GuardDuty.
Licensing of GuardDuty is part of the AWS license. The pricing model is pay as you go and is based on the number of events per month. When you first look at the price it seems reasonable but if you look at it holistically the cost can be improved.
Amazon Guard Duty is a continuous cloud security monitoring service that consistently monitors and administers several data sources. These include AWS CloudTrail data events for EKS (Elastic Kubernetes Service) audit logs, VPC (Virtual Private Cloud) flow logs, DNS (Domain Name System) logs, S3 (Simple Cloud Storage), and AWS CloudTrail event logs. Amazon GuardDuty intuitively uses threat intelligence data - such as lists of malicious domains and IP addresses - and ML (machine learning) to...
80 percent of the customers are using AWS GuardDuty, and we recommend it due to its low cost, especially for small customers, ranging from five to ten dollars a month. In our policies, we enforce the usage of this service, making it a recommended practice for security. The responsibility also lies with the customer. We obtain written confirmation from them, stating that if they choose not to use it, they accept responsibility for any potential attacks. In such cases, we refrain from enabling it, and any financial repercussions resulting from incidents are their own accountability.
I have heard that the solution's price is quite high. Sometimes, they need to fine-tune the service on AWS. For example, Amazon Simple Storage Service (S3) is used for static content because it is cheaper.
I prefer to have something on demand for myself. That's why I haven't been paying for GuardDuty specifically. AWS provides a wide range of offerings, especially in the security area. They have various services that integrate into a centralized Security Hub, offering insights into different aspects of security issues, especially in networking and the cloud. The findings from GuardDuty would be integrated into the Security Hub service, incurring some small costs. I haven't delved into the specifics of these costs, but I know they are minimal. It's like flipping a switch – you integrate GuardDuty to report to the centralized hub, and if something needs attention, you check the GuardDuty findings. This integration is part of the main central service for security, along with many others, perhaps five or ten. For example, one service scans files in your storage service. Different services may have various agents scanning for different things, like tokens or exposed personal data. It's a unique security issue. Each service detects findings, and you can integrate them into the Security Hub to keep an eye on all aspects of security. GuardDuty is just one of them. Cost-wise, you pay for what you use, without the need to install or spin up servers. You simply tell the cloud that you want these services integrated for immediate on-demand use. The pricing may be complex, based on dimensions like the number of findings and protections used. However, maintaining a smaller infrastructure results in fewer findings, reducing costs and eliminating the need for constant investments and running infrastructure all the time, essentially going serverless.
The platform is inexpensive; It costs approximately $50 a month. However, its pricing is subjective based on the company's requirements. It can go from $10 to $30 to a maximum of $50.
I rate the pricing a seven out of ten. The price of the solution is exactly right. It is neither high nor low. It is a pay-as-you-go model. The more number of accounts we integrate, the more the price will increase.
On a scale of one to ten, where one is a high price, and ten is a low price, I rate the pricing a four or five, which is somewhere in the middle. I provided the rating for AWS GuardDutya as four or five out of ten because the pricing would have seemed pretty good if it had more functionalities. Right now, the protection engine isn't that perfect in AWS GuardDuty.
Licensing of GuardDuty is part of the AWS license. The pricing model is pay as you go and is based on the number of events per month. When you first look at the price it seems reasonable but if you look at it holistically the cost can be improved.
Pricing is determined by the number of events sent. It's fine, and it's not a problem from our perspective.
I don't have all the details in terms of licensing for Amazon GuardDuty, but my organization does have a license set up for it.
We use a pay-as-you-use license, which is competitively priced in the market.