Orca Security CNAPP Cloud Security Platform - GovCloud

I use Orca Security  to have a complete view of our cloud environment at the company.

I needed to know what assets were vulnerable and how to fix them, and it was very helpful to have Orca Security  because it has some AI features that helped our developers fix the vulnerabilities while coding and understand which vulnerabilities require more attention and resources.

OrcA Security automates remediation because we could install a plugin in the developer's IDE , so while they were coding, it actually helped them fix vulnerabilities in real time, which was very helpful.

The AI fix for vulnerabilities that we found is the best feature because it gives us more time to focus on other things.

The dashboards were very helpful, and I could personalize them for our case, which helped me show my leadership where the main points were and how to address them, allowing us to focus on what was really important. It was very easy to change the dashboards and personalize everything.

OrcA Security improved our collaboration because we could explain better to everyone at the company what we were doing and how it positively impacts our security posture. We could also measure our risks and vulnerabilities better, enabling us to think more strategically about improving our cybersecurity posture.

We have faster fixing of vulnerabilities with our DevOps team, and we could have fewer attacks.

It was really good because we could see threats coming before they materialize, which I think is a really good way to protect ourselves, our resources at the company, and all our assets.

We are a small team, and I did not feel any difficulty in the work using Orca Security, so I believe it saved us more employees and other costs, helping us save in different ways.

Some dashboards could be a little more personalized for each company and have more options to show the real data we need for our leadership.

I have been using Orca Security for a year.

I believe it is stable, and we did not have any availability problems with them.

It is very scalable. We have a small environment, but it was very scalable when the Orca Security engineers were explaining the tool to us.

It was really good. We had direct access to some commercial people and also the engineers, and they helped us every time we needed.

It was Prisma Cloud, and we stopped using it because of the costs, and the results were not that organized or easy to use as Orca Security.

We jumped directly to Orca Security without comparing it with any other platform.

We installed the Orca Security plugin in the developers' machines, and when they were coding, they could see the vulnerabilities with the Orca Security plugin and fix them in the code before it was put into the production environment. This allowed us to fix vulnerabilities before they reached our productive systems, which was very helpful.

We are not working with a partner or reseller.

Eight out of ten.

I believe it can be improved, but it is also a really good platform to use.

Someone asked me on LinkedIn to talk about Orca Security.

It was really accurate and gave us the right answers.

The advice I give is to talk with the support team. They help us and listen to us about features and things that made sense for our environment and our specific case, and they consider applying them to the final product.

I rate this product a 10 out of 10.

My main use case for Orca Security  is cloud security, and we integrated AppSec in the last year.

Orca Security  offers good security as a CSPM, runtime security with the real-time security agent on Kubernetes , and excellent visual representation to see what is really going on. The visual representation helps me understand where our gaps are and what needs to be fixed through remediations. In terms of AppSec, it provides entire connectivity with some missing parts, but mainly the Git  parts with the repos allow me to see everything, how it is integrated, and to assess its risks. The SCA  with the SAST  is also crucial.

The feature that stands out the most for me is that it is agentless, so I have simple connectivity where I can see everything in one place. If there are misconfigurations, security risks, or misconfiguration gaps, I can be alerted and set up custom alerts and non-custom alerts, allowing our security team to observe these alerts and take action.

Orca Security has positively impacted my organization mainly through use by the security team, but we also use it for compliance reports. We can set the compliance standards we want to adhere to in Orca Security, and then I can check in which areas of each resource or organization-wide efforts comply with those standards. This is really useful to know where our compliance gaps are.

Risk detection and identification capabilities of Orca Security are great and really useful. They had too many false positives in the past, but over time, with their improvements, probably due to UBA  or something similar, it has really improved.

Orca Security can be improved by adding more connectivity and more integrations because the world is moving so fast that having integrations is really poor compared to other vendors.

What is also missing with Orca Security is more robust AI security. Even though they have something, it is still really immature. We need better observability, and not only for cloud-based issues but also for any AI LLMs to ensure real security over AI.

Regarding Orca Security's AI capabilities, I think it is still immature and we are missing some introduction to it. In terms of Orca Security's accuracy and reliability of output, I find that it is still immature, so I have a gap over there.

I have been using Orca Security for the last four years.

I find Orca Security stable.

Orca Security's scalability is great and I have not seen any faults.

The customer support from Orca Security is the best and it is really good. I would rate the customer support a ten.

We did not previously use a different solution. We conducted a POC with other solutions, and at the end of the day, after checking everything, it was my choice to go with Orca Security.

I purchased Orca Security through the AWS Marketplace .

Orca Security has helped my organization reduce the time it takes to address cloud security alerts, and it does so very fast. Its visualization of the alerts, including custom alerts, makes it really efficient. Today, it is integrated with our SOC team.

I have utilized Orca  Sensor for Cloud Detection and Response, CDR, and it has been effective in providing runtime visibility and security. This was the main part because we started with CDR straight at the beginning before doing anything else, and it was good.

Orca Security has helped in preventing risks and attacks across my application lifecycle if it is about secrets, exposed secrets, or vulnerable packages within the CI/CD pipeline, which were detected through the pipeline. It has full integration with GitHub  or other tools such as Azure DevOps .

Before choosing Orca Security, we evaluated other options, including Prisma Cloud, which is now in Cortex , Wiz , and Uptime.

I rate Orca Security a ten out of ten. I chose this rating because we started with Orca Security when it was a new kind of competition to Wiz . We went with Orca Security because of its support, which is one of the best third-party supports we have. They made a really big jump over the last two years, especially in the last year where they changed almost everything, from visualization to reducing false positives, and now they categorize alerts separately compared to what it was earlier, making this really useful. My advice for others looking into using Orca Security is to really consider them. I have given this advice before, and I know that some have taken my advice and moved forward with Orca Security. My overall rating for Orca Security is ten.

I have used Orca Security  for continuous cloud assessment visibility, identifying and prioritizing vulnerabilities and misconfigurations. I also monitor compliance against frameworks, whether it's NIST or SOC 2. Additionally, I use it for detecting cloud security risk and supporting incident response because it provides context around affected cloud resources.

Risk detection in Orca Security  is strong, mainly because it provides agentless visibility across the cloud environments I work in. My job involves identifying vulnerabilities, misconfigurations, identifying risk or exposed assets, and Orca Security does a great job helping to prioritize those risks on their potential business impact. It helps me align very well with the type of risk and the type of work I do in an AWS  environment.

I have used Orca Security's Cloud Cost Optimization feature in one of my recent projects to help identify underutilized cloud resources or cloud resources that have been idle for a long time. That feature allows me to identify those resources. My main focus is security, but I find it useful because if I'm able to see those resources that are not being used, I can adjust them. If I have to reduce their size, depending on what the case might be, or if I have to get it decommissioned, I can do so to help reduce unnecessary cloud spending while maintaining a secure environment. As much as my part of the job is security, I think overall, making sure that we are not just spending money on resources that we're not taking full advantage of is definitely a role that I would have to play. It also helps support conversations with the infrastructure team about balancing cost, performance, and security, to be able to get more data to have those conversations with those teams.

Regarding the Cloud to Dev feature, I personally have not used that. However, I do know about it. Orca Security has the capability to help developers identify and remediate security issues early in software development life cycles by connecting cloud risk back to the code, repositories, or development responsibility. Although I have not used it personally, I have had a conversation with the software team where it helps to bridge the gap between security and development by mapping cloud security findings back to relative code repositories and development teams. It makes it easier to identify root causes and prioritize remediation early in the development cycle, which helps with collaboration between engineers and the security team.

Orca Security has helped significantly to reduce the time it took to identify or prioritize cloud security alerts because of the way it provides a centralized view of risk and correlated findings across the cloud environment. Instead of manually investigating every alert, I am able to focus on high-risk issues first based on factors such as exposure, exploitability, or business impact. This definitely significantly improves response time and makes the remediation process more efficient. Taking that manual factor out of it overall reduces the time for everything.

Orca Security has been very helpful in preventing risks and attacks across my application life cycle by providing continuous visibility into the cloud workload. This also allows my team to prioritize and remediate issues before they could be exploited in production. It has also helped strengthen collaborations between security and development teams by providing actionable findings, which reduce the overall attack surface and improve security posture.

The features of Orca Security that stand out to me from my experience are that it allows agentless deployments. Since it is integrated into my AWS  environment, it gives me comprehensive visibility across my whole AWS environment. With that kind of visibility, I am able to detect vulnerabilities or misconfigurations. I can do risk prioritizations and compliance monitoring through that. These capabilities of Orca Security align closely with the work I do when it comes to vulnerability management or security, cloud security assessments, or even regulatory compliance. Those features help with my day-to-day activities.

Orca Security goes beyond just basic vulnerability detection when analyzing risks contextually and holistically. I think it adds a strong contextual understanding. Instead of treating each finding in isolation, it correlates risk across cloud assets, identities, network exposures, or workload configurations. That really helps provide a more holistic view of the attack path and potential business impact.

From my perspective, Orca Security is a really good tool. I would say one area I would like to see CNAPP  platforms get is more intelligence when it comes to risk prioritization, which correlates with vulnerability, exposing assets, identities, and active threats to help the security team focus on risks that are more likely to be exploited. I am a huge advocate for automation. I also think deeper automation for remediation or stronger integration with ticketing and CI/CD pipelines or more customization would help. Executive reporting would help the security team respond significantly faster and communicate risk more effectively if those kinds of improvements are made.

I have relatively hands-on experience with Orca Security for about three to four years. I have worked more hands-on with cloud security projects, and some of them are integrated with Orca Security.

I think the state of stability with Orca Security is impressive. It generally provides strong availability and scalability compared to a traditional on-premises security tool. I think the agentless part of it and the fact that it integrates directly with a cloud provider such as AWS helps to reduce operational overhead and potential points of failure that come with managing agents across multiple systems. From what I have seen, the architecture can support consistent visibility and create a very good, reliable risk detection across environments, even as a cloud workload scales.

Before Orca Security, I used different solutions for the same use cases because of my expertise in those areas. I have used Amazon Web Services Security Hub, IAM , native logging and monitoring tools, Nessus, and a lot of SIEM  platforms such as Splunk or QRadar. Overall, those tools together helped with vulnerability detection. They also helped with incident response or compliance monitoring and security alert triage. However, when it comes to more correlated data across multiple systems, Orca Security streamlines that by centralizing and correlating the risk all in one place.

With my previous agent-based solutions, I have encountered performance issues when identifying risks. The challenges came more with the scalability of risk analysis across the multiple tools. Each solution provided a valuable insight on its own. For example, Nessus for vulnerability scanning and Splunk or QRadar for log analysis. However, the main limitation was that the findings were often siloed because they are different platforms. That meant I had to do the manual correlation of the data across the different platforms to understand the full context of the risk, which could slow down triage or investigation overall, especially if I was working with a larger environment with higher volume alerts.

Before Orca Security, I used different solutions for the same use cases because of my expertise in those areas. I have used Amazon Web Services Security Hub, IAM , native logging and monitoring tools, Nessus, and a lot of SIEM  platforms such as Splunk or QRadar. Overall, those tools together helped with vulnerability detection. They also helped with incident response or compliance monitoring and security alert triage. However, when it comes to more correlated data across multiple systems, Orca Security streamlines that by centralizing and correlating the risk all in one place.

With my previous agent-based solutions, I have encountered performance issues when identifying risks. The challenges came more with the scalability of risk analysis across the multiple tools. Each solution provided a valuable insight on its own. For example, Nessus for vulnerability scanning and Splunk or QRadar for log analysis. However, the main limitation was that the findings were often siloed because they are different platforms. That meant I had to do the manual correlation of the data across the different platforms to understand the full context of the risk, which could slow down triage or investigation overall, especially if I was working with a larger environment with higher volume alerts.

I did not participate in the initial setup and installation process of Orca Security personally. When I joined the team, it was already set up. I was not directly involved in the initial installation or setup. However, in my previous role, I did support some onboarding of other tools. I have a good understanding of how certain platforms are implemented or operationalized in an enterprise environment, but I did not set up Orca Security that I work with now.

This is somewhat out of my scope because I do not see the exact pricing structure of Orca Security. However, from what I know through research, I think it is good. I think it is fair pricing in my opinion. I have that in place of multiple tools. Orca Security kind of replaces multiple tools that help improve efficiency. So when it comes down to it, if it is cost-effective in terms of overall security operation, I think the price point is reasonable. However, I do not know the exact amount or the exact pricing.

That personally would not be a decision I made before choosing Orca Security. However, I have been collaborating with a bunch of other people in my team, and I think they have considered other options. Depending on what the environment is being used for and the use case in general, they like to look for something that will mix with cloud-native tools. Any third-party solution, whether it is Prism Cloud or Wiz , is something that I have heard of. However, the decision usually comes down to factors such as coverage across the multi-cloud environment or how easily it is to deploy or signal-to-noise ratio. Many factors come in before selecting what CNAPP  they want to get. I feel that across everything, Orca Security stands out. The main thing that many people appreciate is the agentless visibility and the contextual risk prioritization, which is a good benefit that it has over competitors.

Regarding Orca  Sensor, I personally have not used it, but I do know of it. I have not used it directly, but my experience has been more about how it collaborates with the AWS environment, which is my strong field. However, I know it has been useful when deploying sensors and agents. I do not know how in-depth that goes because I have never done that personally, but I still feel that overall, it does what it needs to do. It still provides visibility into workloads and vulnerabilities, whether it is misconfigurations or exposed assets, in whatever environment they are running it in.

I have used the official documentation offered by Orca Security a few times. I have used the documentation and guidelines in the context of IAM  management workflows, particularly around single sign-on, multi-factor authentication, and user provisioning. The documentation from Orca Security is structured really properly. It got all the points across really great. It made it easy for me to read and understand. It was very straightforward. I was able to understand what was put across in the documentation without having to do multiple research or over-explanation. I appreciate that.

I would rate this review as an eight out of ten.