Cyber Security Cloud Managed Rules Reviews

I work in the IAM domain, and we combine Cyber Security Cloud Managed Rules with IAM, which allows us to enforce least privilege security posture and automate response to cyber threats. Cyber Security Cloud Managed Rules relate to IAM controls who can access cloud resources, while Cyber Security Cloud Managed Rules dictate how those resources are protected against network level and application level attacks. They eliminate the need for manual firewall creation by automatically blocking web application vulnerabilities and attacks.

I occasionally use the real-time monitoring feature of Cyber Security Cloud Managed Rules because we do not have a regular deployment schedule. Whenever we conduct a major change in production deployment, I use this system to track vulnerabilities, API exploits, and any malware activity. This usage is occasional and depends on the deployment in production.

The best features of Cyber Security Cloud Managed Rules include core features that extend protection specific to CMS platforms such as WordPress and Joomla or framework exploits. These rules are regularly updated against the latest CVEs, botnets, and malware without requiring human intervention. I can specify the range in the system and it will update against the latest botnets or malware without requiring any human intervention. It also includes a specialized rule set which mitigates threats targeting web applications, APIs, and serverless environments.

Cyber Security Cloud Managed Rules help in managing vulnerabilities such as SQL injections and XSS by modeling user and device behavior across the entire cloud estate. If an admin suddenly logs in from a suspicious location or a script makes unusual API calls, Cyber Security Cloud Managed Rules instantly isolates the resource or flags it for review. When a particular threat is recognized, Cyber Security Cloud Managed Rules bypasses the need for human intervention to execute defensive actions such as changing firewall modes, blocking malicious IP addresses, or revoking compromised credentials. I have CI/CD deployment pipelines which are assigned strict scoping to IAM roles, so these roles have the precise permissions required to push updates to Cyber Security Cloud Managed Rules via infrastructure as code. This ensures that every deployment is pre-validated and consistent with the organization's security policies.

I assess the impact of continuous updates provided by threat intelligence as significant because I have set a particular number of alerts. Whenever I see that this alert is triggered, I conduct monitoring. Based on the manage rules defined in AWS and whatever protocol enforcement exists, my model detects and blocks unauthorized access which deviates from standard HTTPS or other standard protocols, and it mitigates sophisticated bot and malware attacks. API gateway or serverless stage is specifically tuned to block API security and serverless threats. These rules can be natively deployed in front of CloudFront or application load balancer and API gateway. For enhanced operational control, these managed rules are commonly paired with WAF-Champ or automated WAF operation service which helps to manage exception and false positive rates.

The detailed logs and analytics from Cyber Security Cloud Managed Rules help when it comes to making informed security decisions, and it totally depends on the decisions and what logs are needed. As long as I have defined all logs related to sign-in logs and audit logs, based on the logs, I decide whether to go with those alerts or whether to minimize that security risk and where to focus.

Cyber Security Cloud Managed Rules has a very high rate of false positives. The pre-packaged rules are often broad, and this can misidentify legitimate or complex user inputs. The false positive rate should be minimized. Additionally, it lacks customization. Cyber Security Cloud Managed Rules does not provide real customization, but it acts as a black box. When false positives occur, security teams often have limited ability to tweak the internal mechanics of the rule. The only option is usually to disable the entire rule or to switch it to count mode, which simply lowers security posture.

I have been using Cyber Security Cloud Managed Rules for the last nine months.

I would rate the stability at ten out of ten as it has good stability.

I would give scalability a rating of nine out of ten.

I would rate the technical support of Cyber Security Cloud Managed Rules at nine out of ten.

Deploying Cyber Security Cloud Managed Rules is moderate in complexity. I encountered no challenges deploying Cyber Security Cloud Managed Rules. It takes almost two weeks to deploy Cyber Security Cloud Managed Rules.

Approximately, I have a particular number of teams that consist of 30 users per team, so the round figure I can state is 150 users.

Regarding return on investment, I estimate around 25%.

Cyber Security Cloud Managed Rules does not require any maintenance explicitly, but if clients want some additional information or additional features, then they can purchase them through Amazon service. I find Cyber Security Cloud Managed Rules to be cost-efficient.

When I compare Cyber Security Cloud Managed Rules with FortiNets, I see that FortiNets is used for both on-premises as well as for cloud, but mostly on-premises; FortiNet is mainly focused on on-premises. Cyber Security Cloud Managed Rules is a natively cloud platform that provides website performance and edge security. Most WAF is related to only cloud-based solutions.

I would advise others looking to implement Cyber Security Cloud Managed Rules that it depends on their requirement. If they want an on-premises solution, then they should go for Fortinet, and if they want a cloud solution, then they should go for WAF Cloudflare.

I would rate this product overall at a nine out of ten.

Public Cloud

Amazon Web Services (AWS)

My main use case for Cyber Security Cloud Managed Rules is the protection of any cyber attack on my API servers and cloud managed rules on my WAF.

A specific example of how I use Cyber Security Cloud Managed Rules to protect my API servers is that we have an AWS WAF at the parameter level where we have implemented the OWASP top 10 attack rule as a cybersecurity managed rule in the parameter. Any traffic coming to our API server passes through the WAF, and the WAF OWASP top 10 rule filters that traffic for any attack.

The best features Cyber Security Cloud Managed Rules offers are mainly that there is less human intervention, which reduces the chances of error, and it is also less time-consuming and more intelligent compared to manual rules.

When I mention more intelligent, Cyber Security Cloud Managed Rules stands out in that these rules are generally updated according to the latest cyber attacks and the latest signatures in the system, so we don't need to manually change the rule, as they get updated mostly in real time, making detection easier.

Cyber Security Cloud Managed Rules has positively impacted my organization because earlier, a complete SOC team was required 24/7 for manually checking the alerts, acting upon those alerts, and doing forensics. With cloud managed rules being automated and intelligent and updating in real time, the manual intervention by the SOC team has been significantly reduced, resulting in a comparatively higher detection rate than before.

I sometimes need to tweak Cyber Security Cloud Managed Rules because it is a predefined rule where I adjust it based on our request sizes. Sometimes a rule states that only a 5 MB request is allowed, but we have requests greater than 5 MB, which causes it to block that traffic. I have to adjust the rule and increase the size of the request or payload above 5 MB to resolve this issue.

Cyber Security Cloud Managed Rules can be improved in that they are mostly general rules and not specific to organizational needs. Being predefined rules, if we have to make any changes, we need to create a rule above or before that cybersecurity rule or a bypass rule. There should be an option to tweak those cloud managed rules to adjust them based on organizational needs, as this has been one challenge we faced.

Cyber Security Cloud Managed Rules is limited to specific scenarios. For example, AWS WAF can only be used in an AWS scenario, which makes it complex to integrate with on-prem systems.

I have been using Cyber Security Cloud Managed Rules for more than five years.

Cyber Security Cloud Managed Rules is stable, and the support is excellent with the cloud service. The after-sales support and technical support team are very reliable, so I have no issues with that.

Scalability with Cyber Security Cloud Managed Rules is not a problem, as we have opted for a BYOL (bring your own license) model where systems automatically adjust during high demand, which is advantageous for scalability.

Customer support for Cyber Security Cloud Managed Rules is great, as it is easy to reach out compared to on-prem vendors, and overall, I am satisfied with the customer support provided.

I previously used an on-prem solution where everything was done manually, which was expensive regarding employee count and time, with higher chances of error. This prompted us to switch to a hybrid environment that includes both on-prem and cloud solutions.

The return on investment is great. Earlier, we had to manage the whole infrastructure on-prem with a different team at every step, which incurs high costs. With cloud infrastructure, we avoid a significant upfront investment, so it operates on a pay-as-we-grow model, which is beneficial.

My experience with pricing, setup cost, and licensing is that it is very transparent and easy to manage the infrastructure in the cloud. The pricing is very clear, allowing us to track costs using the price calculator and the pricing dashboard, making it very straightforward.

Before choosing Cyber Security Cloud Managed Rules, I evaluated other options including on-prem systems and building our servers for automation with tools such as Ansible. I found that the cloud managed rules were easier to set up and better suited for our environment.

My advice to others looking into using Cyber Security Cloud Managed Rules is to maintain a blend of on-prem and cloud solutions, while also performing regular checks and balances on the cloud managed rules to observe their behavior with applications.

My additional thoughts on Cyber Security Cloud Managed Rules are that the effectiveness largely depends on the specific business use case, as it will not fit every business logic. Sometimes, there is over-blocking within the cloud managed rules where valid requests or IPs could be blocked, which should be fine-tuned to reduce over-blocking. I would rate this product an 8 overall.

Public Cloud

Amazon Web Services (AWS)

Our main use case for Cyber Security Cloud Managed Rules is mostly web application because it protects the front end and also with the CDN we are using it, so it protects the CDN exposed applications as well.

A specific example of how we have used Cyber Security Cloud Managed Rules to protect our web applications or CDN is that we have a proper dashboard of all attacks that were attempted on those exposed URLs at the application level and we have clear visibility. Whenever there is some type of IP which is trying to DDoS our domain, then it gets automatically blocked and we have configured alerts as well. We do get a consolidated report weekly and monthly that shows a lot of hits, what the IP was, and that it was automatically blocked.

We also have AI workload, so it is important to consider that in our main use case for Cyber Security Cloud Managed Rules. We are catering to that in our workflow and trying to manage it so that even our AI workflows do not have prompt injections or, if we are having agents, we do not get man-in-the-middle attacks with the prompts.

The best feature that Cyber Security Cloud Managed Rules offers in my experience is the ability to roll it out in a dry run, which would be a useful way of testing things without impacting real user traffic. After implementing the rules, I would need good observability to get an idea of how effective they are and what I should change to make them better.

Cyber Security Cloud Managed Rules has positively impacted our organization because we are a tech company, so we always prefer to get security first. This is a big thing when it comes to exposing any domain. We would want to ensure that we have secure guardrails around it, and whenever we roll it out, we properly ensure that there was a design doc, there was a review, and make sure that it was behind those security gates to avoid any issues after go-live. It is a proper process that we follow to ensure that no new application sneaks through and before go-live, all these checks are done.

Sometimes false positives do come across, and we have incidents where people who are actually trying to access are getting blocked out, which is how I think Cyber Security Cloud Managed Rules can be improved. It is getting better, but sometimes these cases do happen. I would imagine the opposite is also true where there are certain cases where attackers are able to sneak through. For example, we have been using AI workloads and in that, certain times we have had issues where prompt injection can cause problems. We would to incorporate this in all the workflows where we are using AI as well, so possibly more stringent rules around that would be beneficial.

Cyber Security Cloud Managed Rules does the job, and if you have it configured in the correct way as per your requirements, such as IP sets or SQL injection, you are able to get a basic cover, but the workloads are evolving, and I would like to see more flexibility around those rules so that I can make better use of them. Because use cases are increasing, I would to play around with the rules a bit more so that I can say with certainty that my workloads are secure and ingress traffic is secure. That would help me, so I would give a better rating if that can happen.

Cyber Security Cloud Managed Rules are generally stable in my experience, but if a new attack vector rises or if something new comes up, they are not very adaptable, which is my feeling and experience. I would say they are stable, but not very versatile.

We have been using Cyber Security Cloud Managed Rules for a good few years because I have always worked in AWS. We use AWS WAF and generally at that level, we are protecting all our resources from DDoS and other kinds of attacks, so there are managed rules inside WAF that we use. We also use Fastly, and with Fastly, we get Signal Sciences as a tool, which is a next-gen WAF that can be used to protect against any cross-site scripting or SQL injection and other kinds of attacks.

Cyber Security Cloud Managed Rules are generally stable in my experience, but if a new attack vector rises or if something new comes up, they are not very adaptable, which is my feeling and experience. I would say they are stable, but not very versatile.

I think Cyber Security Cloud Managed Rules are quite scalable, and in terms of the traffic we are getting, they are able to filter out any issues or if it is coming from sources that we do not intend them coming from. They are quite stable and scalable in that sense.

The customer support for Cyber Security Cloud Managed Rules is generally good. It depends on the vendor, which is AWS when it comes to AWS WAF and Fastly when it comes to Fastly customer support.

I have not used any other solution before Cyber Security Cloud Managed Rules other than WAF and WAF rules. It has always been that.

Before choosing Cyber Security Cloud Managed Rules, I have always used WAF as a web application firewall and at the network level, we have a network firewall. That is how it has been. At the API Gateway level also we have WAF and even if we expose it via a load balancer, we use WAF. No matter how we expose to the internet, it has always been WAF in the forefront. WAF rules are the thing we have always used.

I would say time saved is a big metric as a return on investment with Cyber Security Cloud Managed Rules because we are not always looking for things manually or stopping attacks manually. This is helpful because we have automated WAF rules, so they obviously come to the forefront and help protect us against any of the attacks. That is a time save. We have alerts configured if there is an issue. We do not have to manually go and find out about those issues; we usually get an idea of what is going on. A big benefit would be time save, which in engineering can be converted to money saved as well.

In terms of how I use dry run mode and observability with the managed rules, we implement it in a count mode. We will only not block any traffic, but just get a count and get an idea of how the rule would work. Observability-wise, generally in Fastly CDN, we do get a dashboard of how the traffic is getting served. If there is some kind of suspicious IPs or any IP set which is coming from a certain country which we do not want the traffic coming from, then it gets blocked. We have proper visibility.

I think the AI space is something really big right now, so I would to see some improvements around those lines.

I am not one hundred percent sure if we purchased Cyber Security Cloud Managed Rules through the AWS Marketplace. We may have, but I have not looked into that.

I have not been involved in the pricing, setup cost, and licensing phase for Cyber Security Cloud Managed Rules. It usually comes via procurement, so I am not involved in the licensing side of things because I am mostly technical and I am someone who implements things. I have not come across looking at the pricing, licensing, or setup cost.

I would give Cyber Security Cloud Managed Rules an overall rating of seven.

In day-to-day security operations, I primarily focus on protecting web applications, APIs, and cloud workloads. From my experience, this product is the most stable option available. It significantly manages applications during cyber-attacks and addresses threats in AWS environments, including traffic patterns from malicious bots and SQL injections. The product is very helpful for managing these scenarios.

The best feature of Cyber Security Cloud Managed Rules is the combination of two capabilities that I appreciate most. The first is automated threat intelligence and rule updates. This solution automatically updates the security signatures to protect against the latest cyber threats, including OWASP attacks, bots, and vulnerabilities without requiring any heavy manual interventions. Automated threat intelligence significantly reduces the operational workload for security teams and improves the overall response time against emerging threats. It also helps organizations maintain stronger security compliance.

The second feature I appreciate most is strong AWS, WAF, and API protection, which is a major strength of Cyber Security Cloud Managed Rules. The seamless integration with AWS and WAF in front of the ALB and API gateway environments provides strong protection against SQL injection or cross-site scripting. In cases of malicious bots and API-based attacks, this solution is highly beneficial for cloud-native and API-driven applications that require scalable and real-time protection.

This product requires skilled people because there is a lot of automation needed to understand all the features in the dashboard. Additionally, there is a need for increased automation in certain areas to improve the overall experience.

The product is stable and does not create major lagging or performance issues during day-to-day operations. This solution is designed to work efficiently with AWS cloud infrastructure, handling traffic interception with minimal latency. Performance is always good, although, in some cases, when multiple complex rules or deep inspection policies are required, there may be lagging when changing security policies. However, this is acceptable, and performance depends on the application architecture, traffic volume, and rule training configurations. Overall, the product performance is stable, and lagging issues are minimal when the rules are properly configured and maintained.

I give a high rating for scalability. Compared to other products, especially for cloud-native AWS-based infrastructures, this solution easily handles increased application traffic, including API requests, and manages multiple workloads with greater performance. It supports scaling across multiple regions based on applications and internet-facing services through centralized management. Since it is a cloud-based infrastructure, the rules are automated, managed, and updates are handled efficiently, maintaining security consistency during business operations. Overall, the product is highly scalable and suitable for organizations with growing cloud workloads and dynamic traffic requirements.

I engage with the technical support team regularly. The support team helps with rule tuning, false positive handling, deployment guidance, and troubleshooting during security incidents. Sometimes we are unable to handle incidents from a security perspective, and even though false alerts regularly occur, we engage with vendor support. For any issues, we need to raise a ticket via the vendor portal. Initially, we write an email, and after the ticket is created, they check the issue and arrange a call. For standard operational issues, the response time is acceptable, and the support documentation is useful. During critical incidents, for complex applications or specific issues, the response is faster, and troubleshooting support is required. Overall, the technical team is knowledgeable about this product and assists effectively in maintaining stable day-to-day operations.

Initial deployment depends on the environment being used. In my case, we are using two cloud environments, and the initial deployment is not very difficult. My organization is a medium-scale organization already using AWS infrastructure. The setup process is simple because the rules can be directly subscribed and deployed with AWS Marketplace in AWS WAF. Its integration with CloudFront, application load balancer, and API gateways is straightforward and can be completed within a short time. The initial deployment is manageable, and this product also provides predefined management rules, reducing the need for writing custom security policies manually.

After deployment, some tuning and monitoring are required to handle false positives related to application-based traffic behavior, where most organizations initially deploy the rules in count mode before switching to blocking mode to avoid impacting genuine users. Overall, compared to traditional WAF deployments, Cyber Security Cloud Managed Rules is easier, faster, and requires less operational effort for implementation.

The pricing is reasonable in terms of value for the features provided. It is not too high, actually, because the features are very stable and scalable. The pricing for Cyber Security Cloud Managed Rules is generally moderate and slightly expensive, depending on the application traffic and AWS usage, mainly based on the monthly subscription cost for processing changes. For small and medium environments, the pricing is reasonable as it reduces the manual operational effort from the security management perspective. However, for larger enterprise environments with very high traffic applications and heavy workloads, the overall cost increases significantly based on the environmental and infrastructure levels. Although operational automation and threat injections reduce manual work, the pricing can be a little high.

Maintaining rules is relatively low compared to traditional WAF because most security rules and threat signatures are automatically updated by the vendor. The day-to-day activities mainly include monitoring alerts, checking the server's behavior, checking disk alerts, and reviewing blocked requests while handling false positives. Regular log analysis and policy reviews are still required to ensure smooth operations based on performance and security compliance. Maintenance efforts related to rules are low compared to traditional WAF. This solution also reduces the dependency on manual patching, which usually requires logging into the server for Windows updates. The process is simple, and the product is straightforward to maintain, helping significantly reduce the operational workload through automation and centralized management where everything can be managed from one dashboard. I would rate this solution a nine out of ten overall.

Public Cloud

Amazon Web Services (AWS)

My main use case for Cyber Security Cloud Managed Rules is to prevent basic cyber attacks that happen most commonly using a Web Application Firewall.

Regarding my main use case and experience, the Web Application Firewall handles basic attacks. There is also a dashboard where I can check how these rules are blocking requests. I can check from which countries are sending more vulnerable requests towards us, which is very useful.

I can give a specific example of a situation where I used the managed rules to block or prevent an attack. In my recent project, the Web Application Firewall prevented attacks such as SQL injection, cross-site scripting, and brute force attempts. I was getting many requests from different servers, which may have been a DDoS attack. I had already written a managed rule for this situation. I created a custom rule in which if many requests come from a specific source, they will be blocked.

The number of incidents and downtime have decreased significantly since implementing Cyber Security Cloud Managed Rules. My team saves considerable time as a result of using this solution.

The best features Cyber Security Cloud Managed Rules offers include tracking the IPs or bots sending requests that try to attack our servers. I can also block them using these WAF rules, Web Application Firewall rules, which is a good feature.

It is very easy for me to track those IPs and bots using the managed rules, and it integrates well with my dashboards and logs.

Regarding valuable features, the ability to see the IP and the country where the request comes from is very useful when I want to find which countries are getting the most malicious requests and which bots are sending malicious requests. This allows me to block them or add them into my blocked IP list.

Cyber Security Cloud Managed Rules has positively impacted my organization; the impact was great. Since I can track all these malicious requests, I was able to block those, and we do not get attacked much lately since I have been using a Web Application Firewall. I also use their bot rules, where it automatically blocks specific bots which are flagged or blacklisted, which really helps.

I did notice changes in the number of incidents, downtime, and time saved for my team since I started using Cyber Security Cloud Managed Rules. We do not get downtimes now since we have been using this, and the impact is quite positive. Everyone should at least use the basic common rule set of these WAF rules.

Cyber Security Cloud Managed Rules can be improved through more research on malicious attack patterns and threats.

I have been using Cyber Security Cloud Managed Rules for approximately 1.5 years.

Cyber Security Cloud Managed Rules is stable.

The scalability of Cyber Security Cloud Managed Rules depends on the rules and what type of rules are being used.

I would describe the customer support for Cyber Security Cloud Managed Rules as pretty average. They provide a link and then disappear, so I have to do my own research. My experience with support was not good.

I have not previously used a different solution; AWS Web Application Firewall was my first.

I can purchase Cyber Security Cloud Managed Rules from the AWS console. I do not have to go to the AWS Marketplace.

My advice for others looking into using Cyber Security Cloud Managed Rules is to definitely consider it.

I have seen a return on investment with Cyber Security Cloud Managed Rules. It really saved my time debugging attacks by showing me where the attack came from, whether it was detected, and how to prevent it. Since I have been using WAF, these incidents are very less frequent than before. It is really helpful for the person in charge of security for the cloud infrastructure.

Amazon provides around five to six rules which are literally free of cost, saving me from many basic attacks such as SQL injection, SSH scripts, or any vulnerable common attacks. I can use these rules free of cost. Some of the rules AWS provides cost some money, around $10. For example, there is a rule which blocks suspicious bots automatically.

I have not evaluated other options before choosing Cyber Security Cloud Managed Rules because I first tried AWS Web Application Firewall since my whole project infrastructure was on AWS, which is why I chose AWS Web Application Firewall.

Everyone should use these rules for better security for their applications and implement them. Additionally, they should learn from the mistakes they make when implementing rules for the future. I give Cyber Security Cloud Managed Rules an overall rating of eight out of ten.

My main use case for Cyber Security Cloud Managed Rules is for the API Gateway and for OWASP security.

I am integrating these WAF rules with the API Gateway and CloudFront to ensure security from cybersecurity issues, minimizing vulnerabilities and mitigating threats from hackers, including the OWASP top 10 web application threat lists. I have configured it for our front end and for the API Gateway.

I am using Cyber Security Cloud Managed Rules for our GenAI applications, specifically for the chatbot I have recently created, which helps tremendously and prevents hackers' exploits in our application.

The best features that Cyber Security Cloud Managed Rules offers include low false positive rates, bot detection, zero-day threats, real-time authentication, and real-time threat intelligence.

In my day-to-day work, I find the malicious bot detection feature of Cyber Security Cloud Managed Rules to be the most valuable.

Cyber Security Cloud Managed Rules has positively impacted my organization by reducing the manual WAF management by fifty percent and accelerating the automated updates and improvement in threat intelligence.

Cyber Security Cloud Managed Rules can be improved by automating the responses, enhancing visibility, providing deeper insights, integrating with DevOps and SecOps, and facilitating real-time analysis.

I have been using Cyber Security Cloud Managed Rules for the last one year.

Cyber Security Cloud Managed Rules is stable; I have been using it for the last two years without encountering any major issues.

Cyber Security Cloud Managed Rules is totally scalable by automatically and elastically adjusting to traffic demands without any manual intervention, supporting horizontal scaling while reducing the operational burden, which is important for my application use case.

I have not had the chance to connect with customer support until now.

I have not used any other solution, and I am continuing with this cybersecurity option.

The experience with pricing, setup cost, and licensing for Cyber Security Cloud Managed Rules is straightforward. I have a dedicated team that takes care of this, and I am not much involved in those activities. I provide them with my requirements, and they provide solutions accordingly.

I have seen a return on investment; it has saved money from hackers who demand bounties for application breaches. Regarding time, it is directly taken from the AWS Marketplace, meaning not much time is needed for configuration.

I have four years of experience in financial matters related to pricing, setup cost, and licensing.

I surely recommend using Cyber Security Cloud Managed Rules for AI applications because, as a cloud engineer and operations engineer, I feel more comfortable using these cybersecurity managed rules without any issues in real-time.

I do not have any additional thoughts about Cyber Security Cloud Managed Rules at the moment, but if I encounter something while developing more agentic AI applications in the future, I hope to find something helpful for improving the cybersecurity managed rules. I have provided this review with a rating of seven.

My main use case for Cyber Security Cloud Managed Rules is to protect from malware like DDoS incidents, against cross-site scripting, against SQL injections, and against geofencing. These are the areas which we majorly use cloud security and our cybersecurity managed rules.

A recent scenario of how I use Cyber Security Cloud Managed Rules to protect against one of those threats is that we have a specific application where only Italy is in-market, which means only Italian people can access that site because our sales are only in the Italian market. However, when we get human traffic from countries like Nigeria, Iran, and Pakistan, where we do not have any sales, the traffic still comes from such countries as DDoS requests. Cyber Security Cloud Managed Rules automatically blocks those countries where we do not have sales.

The best features Cyber Security Cloud Managed Rules offers is that we do not need any manual validation. When it comes to managed rules, it is always tested in my organization and always trusted and authorized in my current infrastructure.

Automatic validation occurs in my organization because we do not need any manual review in my infrastructure. Whenever there is an issue or a particular application we onboard on our web application firewall, we do not need any manual testing when these managed rules are placed as a major role. Whatever rules we apply, the monitoring is always in good health status with good user agents, and we are always getting traffic from reliable sources. We do not need any manual validation on each and every traffic.

Cyber Security Cloud Managed Rules has positively impacted my organization as we have been using it for two years. It has saved us considerable time. We do not need people at that particular time to validate those things. It has been a time-saving solution and we do not need any manual deployment anymore.

Since implementing these managed rules, we have saved time and resources. We have three members working on that, and after implementing Cyber Security Cloud Managed Rules, we have already freed up one more resource from my team. We are now working with two members.

Cyber Security Cloud Managed Rules needs improvement in such a way that whenever the application team or development team is doing any kind of deployments, they need to regularly enable or disable their maintenance page or holding page, as well as internal whitelisting will be required. Cyber Security Cloud Managed Rules should provide or adjust these features for developers or the application team to fulfill those needs.

Currently, it is already performing very well in our infrastructure, and we do not have any additional needs for improvements at this time.

I have been working in cybersecurity and network security for almost five years.

Cyber Security Cloud Managed Rules is fully stable.

Cyber Security Cloud Managed Rules's scalability is good as we always have an active-passive setup from the cloud vendor, making it much more scalable and reliable.

The customer support for Cyber Security Cloud Managed Rules is excellent. Whenever we raise a request, whether it is high critical or small to medium critical cases, the customer support responds quickly. Within just a few minutes, we receive a response from them.

Before choosing Cyber Security Cloud Managed Rules, we did not evaluate other options, though we had some plans to move to Akamai. However, we are satisfied with our current application.

Cyber Security Cloud Managed Rules was acquired as part of Imperva Web Application Firewall.

We use two types of rules. One is manual rules which we use in our day-to-day operations, and Cyber Security Cloud Managed Rules is the other major component.

I have seen a return on investment as we have experienced significant time-saving, which is very good for us. Regarding money saved or return, we have a separate team for that and I am not involved in those calculations.

Regarding my experience with pricing, setup costs, and licensing, this was not handled by my team because we have a separate team for cost factors, setup costs, and licensing. I am not involved in that.

We are only using Cyber Security Cloud Managed Rules for almost two years since I joined this organization.

I would rate Cyber Security Cloud Managed Rules around nine out of ten. I chose nine out of ten because even if it is perfect, I would not give a ten because there is no world called perfection in this world. We are humans, and maximum nine is sufficient for each and every field. I would not rate anything ten out of ten. I would advise others looking into using Cyber Security Cloud Managed Rules to go for this because the world is changing in technology, and for security, there should be no compromise. I always recommend them and advise them to go for Cyber Security Cloud Managed Rules. My overall review rating for this product is nine out of ten.

My main use case for Cyber Security Cloud Managed Rules is to protect against malicious attacks like SQL injection attacks and cyber attacks.

Recently, I discovered malicious IPs which I believed were operating as a botnet and attacking my e-commerce website. Because WAF is for web application security, I used WAF managed rules related to IP and IP injection attacks. There are additional rules available for IP rate limiting based attacks, which allow me to implement a maximum number of attempts from a particular IP within a specific time period. This rate-limiting rule helps prevent unknown IPs from accessing my website.

The general security vulnerabilities provided by AWS WAF through managed rules or custom rules that I can implement will protect my application and enhance the security of my application through these security rules. This is the main use case of implementing WAF rules.

The best features of Cyber Security Cloud Managed Rules are that there are managed rules available for free that I can implement. I can stop SQL injection attacks, which is one significant vulnerable attack that can be stopped by WAF. Bitcoin mining attacks can also be stopped by implementing WAF. Additionally, there are specific rules related to bot control, which are especially helpful when a bot attacks my website. I implemented a framework known as OWASP Top 10, so these ten security critical vulnerabilities can be mitigated by implementing them.

I implemented free managed rules by AWS, which include Cyber Security Cloud Managed Rules. These managed rules control SQL injection attacks and other attacks that are managed by WAF to prevent them from affecting my systems.

Cyber Security Cloud Managed Rules have impacted my organization very positively because my company is security-focused. We are focusing mainly on security-based setups and implementing everything that can enhance security. This is one of the key applications or services I can implement in my company to stop mitigation attacks, which is why I implemented WAF and attached it to CloudFront, API Gateway, and sometimes to a load balancer to stop and mitigate these attacks.

I noticed specific outcomes or metrics from Cyber Security Cloud Managed Rules in the form of reduced attacks. I discovered that there was no system through which I could conclusively determine what happened, but I noticed some IPs in the logs that were attacking my website and trying to exploit Bitcoin through our platform. This activity was reduced by implementing WAF, and this is what I verified from the logs, which were very helpful.

I believe that Cyber Security Cloud Managed Rules can be improved by reducing false positives with traffic-aware tuning. Out-of-the-box managed rules are generic, and sometimes they block legitimate traffic. Improvements can be achieved by running rules in count monitor mode first, reviewing blocked requests using logs, adding custom rules on top of managed rules, and enabling request inspection depth layer seven hardening. These are techniques I can use to improve these rules.

I have been using Cyber Security Cloud Managed Rules for the past one year.

Cyber Security Cloud Managed Rules are stable in the sense that I do not experience issues with availability or performance.

Regarding scalability, I can easily implement them.

I have not previously used a different solution because we are AWS native and implemented this solution only.

Regarding pricing, setup cost, and licensing, I find it a bit more expensive.

Regarding scalability, I can easily implement them.

I have seen a return on investment.

Regarding pricing, setup cost, and licensing, I find it a bit more expensive.

Before deciding on Cyber Security Cloud Managed Rules, we went straight to using these rules. Everything is deployed on AWS, and we want to use AWS. This is the only sole provider for our company, so we are bound to use it.

I would advise others looking into Cyber Security Cloud Managed Rules to use WAF if they want to eliminate security attacks, especially if they are using AWS. I would rate this product 8 out of 10.

Public Cloud

Amazon Web Services (AWS)