SentinelOne Singularity Cloud Security Reviews

Our primary use case is for security purposes. It is deployed on our cloud to handle our security threat detections. It scans our infrastructure to recognize security issues, detect attacks, and provide protection.

SentinelOne offers an intuitive dashboard to streamline and set up processes. It is user-friendly for security and InfoSec teams.

It helps with regular compliance and transparency. They provide a clear rationale for security practices, which helps in gaining stakeholder's trust. The data-driven approach aligns with compliance framework requirements. I also see a reduction in reliance on human judgment.

It has reduced our mean time to detect by 30% to 40%. There is about a 20% to 30% reduction in the meantime to remediate. In case of any threat, we get alerted within milliseconds. It provides me with everything I need.

It scans my infrastructure very well and finds any issues.

The features that stand out are threat detection using advanced artificial intelligence and machine learning, helping to identify and respond to threats in real-time. 

Additionally, the extended detection and response (XDR) provides deep visibility and unified security across our endpoints, network, and cloud environments. 

The areas with room for improvement include the cost, which is higher compared to other security platforms. The dashboard can also be laggy.

I have been using the solution for about one year.

The solution is stable. I would rate it a nine out of ten for stability.

It is scalable. I would rate it an eight out of ten for scalability.

The technical support is excellent. I would rate them a nine out of ten.

Positive

We did not have any similar solution previously. We used AWS services such as GuardDuty and CloudTrail.

By implementing SentinelOne Singularity Cloud Security, we wanted AI-powered scanning and threat detection. SentinelOne stands out due to its ability to provide alerts and documentation without needing to continuously monitor the services. Everything is centralized. It alerts me through an email or a notification if something is happening in our infrastructure. I can look into it and see what I need to do.

It is deployed on the cloud. It took about four days to implement it.

Its maintenance is taken care of by SentinelOne.

Initially, 8 people were involved in deploying the solution. We have about 13 people using this solution.

The implementation of the solution has resulted in a saving of time and resources by around 40%.

SentinelOne is quite costly compared to other security platforms. I would rate it an eight out of ten for costliness.

I would recommend this solution to other users because of its security. 

Overall, I would rate SentinelOne Singularity Cloud Security a ten out of ten.

We use PingSafe as a Cloud Native Application Protection tool to identify anomalies or deviations from best practices in our cloud environment.

We chose PingSafe because it meets our compliance requirements.

We have integrated PingSafe with all of our AWS accounts. By default, when PingSafe identifies an issue, it automatically creates a Jira ticket. Our Security Operations Center team then investigates all these Jira tickets and takes appropriate action.

PingSafe is user-friendly.

PingSafe's evidence reporting is valuable for prioritizing and resolving the most critical cloud security issues. Any issue it identifies, whether it warrants a Jira ticket or not, can be directly accessed through a provided link. The PingSafe dashboard then displays all vulnerabilities, including how the issue was identified, the type of scan used, and the affected code location. This can include details from secret scanning, pinpointing the specific repository, file, and location where a secret was leaked within GitHub. This level of detail makes it very easy to verify and prioritize remediation efforts.

We leverage IaC scanning because our infrastructure is defined using Terraform. This allows our DevOps team to proactively identify potential security vulnerabilities. These vulnerabilities can include accidentally embedding secrets directly in the IaC code, such as committing them to the GitHub repository. By utilizing IaC scanning, we can detect such issues and promptly notify the responsible DevOps team member for remediation.

PingSafe helps identify issues in container configuration files early in the development process.

In the past, we relied on multiple tools for latency scanning and Kubernetes security scanning. This meant using separate portals and logging tickets manually in Jira. Now, with PingSafe, we have a centralized solution. It provides a single point of access for everything, from security issues to the latest threat intelligence reports. This makes it user-friendly and saves our team significant time. We can investigate issues more efficiently and even create Jira tickets directly within PingSafe, eliminating the need for manual logging. Overall, PingSafe offers both time savings and improved accuracy.

The real-time detection offered by PingSafe is crucial because we manage all our data using Kubernetes. This makes it critical to identify any vulnerabilities within the running dependencies.

We rely on PingSafe's comprehensive compliance monitoring to maintain regulatory compliance. We utilize all its features to maximize its effectiveness.

PingSafe has a user-friendly interface. It provides a visual flow diagram that makes it easy to navigate between different AWS accounts and services. When we receive an alert, we can quickly see which account and service it's related to. Overall, it's a well-designed tool.

PingSafe has removed 80 percent of our false positives.

PingSafe has improved our mean time to detection by 100 percent.

PingSafe has reduced our mean time to remediation by 70 percent. This is because we can now quickly obtain a list of all issue tickets logged in Jira, allowing our SoC team to take action on them promptly.

PingSafe improved the collaboration between the cloud developers and AppSec teams.

Having a system that can identify and alert us to misconfigurations in our 3 data storage buckets is helpful for our organization's penetration testers. Since all our company data resides on cloud platforms, PingSafe allows the AppSec team to automatically detect vulnerabilities before manual penetration testing begins. While this automation might seem to reduce the AppSec team's workload for cloud security specifically, it would ultimately benefit both teams. The security operations team would be relieved of the burden of manually logging and ticketing every issue identified within AWS services.

PingSafe has helped save 90 percent of the engineering team's time.

We have successfully integrated PingSafe with AWS and have also integrated the GitHub organization. These integrations were implemented to identify potential issues on our cloud platform. PingSafe is also used for IaC and secret scanning within our organization. Fortunately, these integrations have been running smoothly and haven't caused any problems.

PingSafe's graph explorer is a valuable tool that lets us visualize all connected services. For instance, we can see all running Kubernetes clusters, including their components and nodes. If there are any problems with cluster components or nodes, the graph explorer will highlight them, allowing us to easily address the issues.

The threat intelligence section also focuses on identifying new vulnerabilities emerging in the market. PingSafe scans our existing infrastructure to pinpoint all affected resources. This allows us to easily identify any at-risk resources with a single click.

PingSafe can improve by eliminating 100 percent of the false positives.

Another area of improvement is for PingSafe to auto-remediate the alerts. 

I have been using PingSafe for 6 months.

I would rate the stability of PingSafe 10 out of 10.

I would rate the scalability of PingSafe 10 out of 10.

We connect with the PingSafe technical support on Slack and they are always helpful and knowledgable. They can help with any of our questions and issues.

Positive

In the past, we relied on open-source tools like Terraform scanning and Gitleaks to scan our infrastructure as code and identify secrets. However, this approach demanded significant manpower and time investment, and we were inundated with false positives. To address these challenges, we transitioned to PingSafe.

I would rate PingSafe 9 out of 10.

For our organization, PingSafe must include evidence of exploitability in its evidence-based reporting and it does.

We have 6 people in our organization that utilize PingSafe.

PingSafe does not require maintenance from our end.

I recommend PingSafe to others because it offers several advantages. One key benefit is that it saves a significant amount of manpower. This frees up our security engineers to focus on other assigned tasks. PingSafe is a valuable tool for automating tasks.

We utilize PingSafe for Cloud Security Posture Management and real-time cloud configuration monitoring. PingSafe identifies vulnerabilities at the resource level and generates reports. It also includes defense modules that investigate potential exposure of secrets in public or private repositories. Additionally, the scanning module can identify vulnerabilities and analyze how they correspond to and impact other modules.

We chose PingSafe as our cloud security solution for its ability to identify misconfigurations, both intentional and unintentional, within our infrastructure. Additionally, PingSafe generates reports that facilitate security compliance audits and help us identify inactive user accounts. It further integrates with our Jira instance, allowing for seamless data visualization on our security dashboard.

PingSafe is user-friendly. The portal is well-designed and intuitive. PingSafe boasts excellent customer engagement. They keep us informed with monthly updates on new features and upcoming releases, providing opportunities for learning and raising any challenges we encounter. Their approach is both proactive and professional.

It's evidence-based reporting system prioritizes and assigns reported issues to the appropriate teams based on their severity. This ensures that critical issues are addressed first. Reports are initially delivered to our CTO and then disseminated to the relevant teams for action.

Our agentless vulnerability scanner helps us discover vulnerabilities across our cloud infrastructure by analyzing cloud logs and log flows. It then provides detailed information and guidance on the identified vulnerabilities.

We find the offensive security engine that verifies actual exploit paths and prioritizes breach potentials to be very useful.

Using PingSafe streamlines our cloud configuration validation process. We no longer need to spend excessive time and effort planning or using other tools to ensure our configurations meet industry standards. This reduces the training burden on our team, keeping them current with security best practices. Additionally, PingSafe acts as a safety net, providing peace of mind and increased confidence when deploying updates, rolling out new policies, or making any security-related cloud configuration changes. Our experience and trust in PingSafe are well-founded. Their support has consistently addressed any concerns we've raised throughout the year. This report demonstrates the value of maintaining a compliance center, and PingSafe plays a critical role in making that possible.

PingSafe has been instrumental in reducing false positives during login deployments. For example, when our server load balancer or cluster switches between servers. During this brief window of usually just a few seconds, the DNS isn't mapped to any background resources because it's being transferred from the old load balancer to the new one. While this is a minor, expected occurrence, it was previously flagged as a critical issue. Resolving these false positives took several hours. While PingSafe likely detects these discrepancies in real time, it validates and corrects them based on a specific schedule. This delay in resolving the alerts prompted us to report the issue and request suppression of these expected findings. Highlighting this problem helped draw the attention of our executives and senior management.

PingSafe has significantly improved our security posture. In the past, developers occasionally exposed credentials to the public unintentionally. PingSafe effectively detects and reports these incidents to senior management, allowing us to address them promptly. Additionally, during infrastructure testing, security gateway code might be unintentionally exposed. However, PingSafe helps us swiftly identify and mitigate these issues before any damage occurs.

Thanks to PingSafe, we've significantly reduced our mean time to detection. It delivers the critical data we need, eliminating the need for dedicated full-time staff.

PingSafe has helped us improve our mean time to remediation. Now, we can get prompt support from their team, allowing us to work together to mitigate issues quickly.

PingSafe has improved collaboration between our cloud security team, application developers, and AppSec teams. Notably, secret configuration detection allows us to collaborate effectively with developers to swiftly resolve any emerging issues. Our DevOps team handles cloud security, and all teams are satisfied with PingSafe's implementation. They actively participate in monthly meetings.

The collaboration has freed up some of our engineers' time. Once we enabled the module and it began identifying issues, engineers were able to plan their work more effectively. The analytical dashboard also helps them manage tasks efficiently, eliminating the need to hire additional staff.

PingSafe offers comprehensive security posture management. Its success stems from its ability to analyze DNS mappings. While we may have access to the DNS record itself, the underlying infrastructure associated with that domain might be decommissioned. This creates a potential risk, as the domain could be remapped to a malicious website, leading to data breaches or credential theft. However, PingSafe proactively detects and alerts us to such accidental exposures of sensitive information, including SaaS credentials. These are some of PingSafe's most valuable features.

There is room for improvement in the current active licensing model for PingSafe. As both a customer and service provider, I believe a more comprehensive package could be developed that would be mutually beneficial.

I recommend including endpoint monitoring functionality in a future release of PingSafe. While we currently scan our endpoints manually through an external vendor, integrating this capability within PingSafe would offer significant advantages. Additionally having real-time detection of malicious activity in our network would be beneficial. 

I have been using PingSafe for 2.5 years.

PingSafe is stable.

PingSafe is scalable.

The technical support is responsive and they stay in contact with us.

Positive

As an energy company, PingSafe helps us ensure compliance across our many providers, which is essential for our business expansion.

The pricing for PingSafe in India was more reasonable than other competitors.

I would rate PingSafe eight out of ten.

We have 15 people in our organization that use it. PingSafe is responsible for the maintenance.

It is a sophisticated and fast-growing product with great services. 

PingSafe was being used for cybersecurity and governance. The company where I used to work wanted to secure sensitive information or prevent any data leaks. It provided good protection.

I used it on a daily basis. If any alert came up, or any best practice needed to be followed, I used to look into the alerts and work on the issue so that it did not affect our systems.

PingSafe includes proof of exploitability in its evidence-based reporting. It helps to secure sensitive information saved in the cloud. It provides alerts in the case of any vulnerability. I felt secure when I was using PingSafe.

The alerts had severity levels, such as low, medium, and high. I used to give priority to the ones with a high severity level and then I used to handle the ones with medium or low severity.

Before PingSafe, it was a bit difficult to know all the vulnerabilities. There were some services in AWS, but we had to configure them and check them on a daily basis for any alerts. PingSafe was more reliable. Our InfoSec team used to inform us about any vulnerabilities and then we used to resolve them. PingSafe was more beneficial for our organization for security purposes.

PingSafe improved our security posture. I would rate it a nine out of ten for that.

PingSafe improved our mean time to detect. Its dashboards were helpful, and there was continuous improvement.

It used to guide me about an alert. There is something called an alert guide. I used to click on the alert guide, and I could read everything. I could read about the alert and how to resolve it. I used to love that feature.

Its interface was pretty good. It was very easy to use.

It was also good for compliance, but I was not handling that part. I only used to view the alerts and solve the issues. The other aspects were handled by my seniors.

I used to work on AWS. At times, I would generate a normal bug in my system, and then I would check PingSafe. The alert used to come after about three and a half hours. It used to take that long to generate the alert about the vulnerability in my system. If a hacker attacks a system and PingSafe takes three to four hours to generate an alert, it will not be beneficial for the company. It would be helpful if we get the alert in five to ten minutes.

Another issue was that when there was a new alert, I did not get an email or notification on my personal email. I had to log in and refresh the screen to check if any new alerts came. It would be beneficial if an email or a notification could be sent to a personal email or mobile number.

We had a few false positives. For example, for Amazon EBS volumes, PingSafe sometimes used to give an alert saying that an EBS volume was created in the East US region, whereas no EBS volume was created. It was a false alert. We discussed these false alerts with the PingSafe team and gave them feedback. We muted those alerts, but such a thing should not happen. However, the number of false positives reduced over time. Initially, if we had 10 false positives, then later on, we had only one or two.

They can enhance the dashboard and make it more user-friendly. They can also provide more information in the alerts about remediation.

I used PingSafe for almost 1.5 years.

It is stable. I would rate it a 9 out of 10 for stability.

It is scalable. I would rate it a 9 out of 10 for scalability.

We had approximately 15 to 20 users in our organization. We had multiple departments, but all the applications were deployed only on AWS.

I never used their support in 1.5 years. A different team interacted with them.

I have only used PingSafe.

It was deployed on the cloud and on-premises. Its initial setup was not complex. It was easy to understand.

Its deployment took a few days.

2-3 people were involved in its deployment.

It saved resources. There were 20% to 30% savings.

It is cheap.

I would recommend PingSafe to others. Overall, I would rate PingSafe a 9 out of 10.

I use SentinelOne Singularity Cloud Security as an endpoint security tool. We have deployed it on multiple users' endpoints and multiple servers to protect them from security threats.

As a security engineer responsible for administering the SentinelOne Singularity Cloud Security, Kubernetes, and VR tool, I work in an organization with over 10,000 employees and numerous virtual servers and corporate network machines. To safeguard these systems from security threats, we've deployed Singularity across all endpoints and servers to monitor for and respond to incidents, gathering detailed information about their spread and affected machines.

Any security incident or malware detection is reported to security administrators within a fraction of a second. Basic rules and AI detections drive this rapid response. For example, suppose a file is flagged as suspicious based on its activity and alignment with the MITRE ATT&CK framework. In that case, the system identifies the file's behavior, categorizes it according to MITRE attackers, generates AI-based responses, and provides insights to security administrators for review and further investigation.

Automated remediation is highly effective, responding in mere fractions of a second to block, quarantine, or contain affected files or devices. Additionally, it can isolate endpoints from the network to prevent malware from spreading or containing compromised systems.

The Ranger feature is not exclusive to Linux systems. It scans all devices on a network, providing information about the types of machines and operating systems present within that specific network environment.

Workload telemetry visibility is valuable during incident response, triage, and analysis. Detailed information about the process is provided when an incident is reported, offering deep insights. For example, if a file is flagged as malware, the entire process behind its execution, including accessed files and invoked processes, is displayed. This comprehensive history effectively aids in determining file behavior and accurately classifying it as benign or malicious.

The benefits of SentinelOne Singularity Cloud Security are immediately visible through the quick response time.

The mean time to detection is under half a second.

The mean time to remediate is between one and one and a half seconds.

It provides an automated response, eliminating the need to block and investigate files manually. SentinelOne Singularity immediately blocks suspicious files, and subsequent investigation allows us to whitelist the file completely or maintain the block.

The most valuable features are automated threat response, AI detection, and static and dynamic detection. Monitoring all activities on the server's endpoint provides security administrators with deep visibility into endpoints, servers, and the incidents occurring on them.

I request that SentinelOne investigate this false positive, as SentinelOne has a higher false positive rate than other XDR solutions. While false positives are an expected part of incident response, excessive numbers can indicate accuracy issues with the tool.

I have been using SentinelOne Singularity Cloud Security for two years.

Cloud-based stability is beneficial because it eliminates downtime for business owners, ensuring uninterrupted operations.

Scalability is relatively straightforward as it primarily involves installing agents on additional machines and addressing licensing requirements.

Auto-scaling based on workload demands is beneficial, for example, when a hundred machines are added to the corporate network. We need to deploy the SentinelOne agent to these additional machines and confirm that the license accommodates the increased number of devices.

We previously used Crowdstrike Falcon but prefer SentinelOne Singularity Cloud Security because it is user-friendly. The GUI is easy to understand, operate, and administer.

Due to SentinelOne's cloud-based nature, initial deployment is straightforward. Simply installing the agent on the endpoints we wish to protect is sufficient, making setup within our existing corporate network infrastructure relatively uncomplicated.

The deployment time varies depending on the number of endpoints and servers accessible within the network, but it typically takes one to two months to complete and transfer responsibility.

Two people are necessary for deployment: one to handle administrative tasks and another to manage the SCCM component, such as pushing agents to multiple machines.

I would rate SentinelOne Singularity Cloud Security eight out of ten.

Sometimes, Singularity incorrectly flags legitimate files as malware or suspicious, which can disrupt the work of some project users. However, we understand the importance of protecting against potential threats and appreciate Singularity's proactive approach. We can easily whitelist false positives, minimizing productivity impact and ensuring our system remains secure.

SentinelOne Singularity Cloud Security is a valuable tool for organizations with the budget to invest in it. It offers robust protection for servers and endpoints, which are primary targets for security breaches. Given the critical nature of endpoint security, this software should not be overlooked. SentinelOne has a strong reputation, provides rapid response times, and includes features such as deep visibility into malicious files, enabling security administrators to isolate threats in the cloud through sandboxing directly.

The only maintenance required is for agent upgrades.

My company has around ten AWS accounts, and we use SentinelOne to monitor and see if any risks are there or not in any security groups for VPC endpoints or any other resources that come under severe risk or medium risk, so my company uses the product for calculations concerning the aforementioned area. The tool also creates tickets for our company, which helps us monitor the resources and change them according to the standards applicable to the organization.

The solution's most valuable features are its ability to detect vulnerabilities inside AWS resources and its ability to rescan after a specific duration set by the administrator. It creates a ticket automatically, so you get to know the things in the tool that you need to attend to immediately, making it a core feature of the solution.

I am unsure as to what kind of subscriptions my company has taken from PingSafe. I am not sure about what other things are there in the product that can help our company. Based on whatever subscriptions related to the product my company has taken, I can say that though one of the security groups is open to my company's premises, it still stays that it is open, which, for my company, makes it secure, but for PingSafe, it is not secure, so I am not pretty sure about how it can check and update it. I am not sure if a feature to deal with the aforementioned area already exists in the solution and if my company has not taken a subscription to use it.

Let us assume that there is a ticket that states that one port is vulnerable in the security groups from AWS since it is exposed to the public. When the tool states that it is exposed to the public, it means that it is exposed to the IPs in the company premises and not the public.

Let us assume that there is a database that is exposed to all the IPs in an office. If I have 10 to 12 sets of IPs, I can use them for 10 to 12 Wi-Fi or VPN connections, and it is exposed on the company premises, but the tool states that it is exposed to the public and that the company needs to shut it down. My organization needs to expose the database so that our development team can access it over our office IPs. If you do not expose the database to office IPs, the development team cannot access DBs to manipulate or check data. In general, the database is exposed to the office IPs, not to the public, but the tool states that it is exposed to the public since it cannot identify whether the IP is a public IP or office IP. I am not very sure if there is a setting in the product that allows the office to give its set of IPs to the tool, and scanning can be done through them so that the tool can identify if the resources are inside or outside of the IP range, according to which can state whether it is safe or not. In general, the tool should offer users the ability to mark IPs as public and private ones so that the product can identify them. It would be good if a customer could provide the tool with a set of ten IPs and state that it will be okay and secure if any of the resources are exposed to them since they are inside the office premises.

One of the issues with the product stems from the fact that it clubs different resources under one ticket. If I have 10 resources in 10 accounts, there might be a problem if, from those 10 accounts, 5 resources have the same issues and they get clubbed together under a single ticket, which makes it somehow a difficult process since I have to get inside the ticket to get the resources and the account details.

I have been using PingSafe for 6 months. My company is a customer of the solution.

I never found any stability issues in PingSafe.

In terms of scalability, I have not used the application to its full extent. Right now, I cannot comment on the scalability part of the product.

PingSafe helps identify the resources that are vulnerable to attacks, and if I can fix them up, then my application will be safe at that particular point in time. The tool's aforementioned area has no relation to the product's deployment since it is used to secure my company's resources, applications, and infrastructure.

Though the solution can be deployed with the help of my team, consisting of three people, I can handle it by myself. With PingSafe, the reports come to me, after which I can give or segregate them for different applications while having two different individuals working under me.

I take care of the installation part of the product by myself.

The solution is very user-friendly in terms of ease of use.

I do not use the product's reporting feature because another team in my company handles it. I know that my company uses the product's reporting feature to extract reports on a weekly, bi-weekly, and monthly basis, but I don't deal with it.

I don't use the product's agentless vulnerability scanning. I check the reports that come to me, as I need to further check the resource tests attached to them, especially whatever resources are affected as per the reports. In general, I just go with the report and complete the task.

I have not used Pingsafe's Offensive Security Engine.

Pingsafe's IaC Scanning is a great functionality that is built into the product. It is one of the major functionalities that my company's team uses. With Pingsafe's IaC Scanning, it is easy to monitor and observe areas in a good way.

Pingsafe's IaC Scanning role in identifying pre-production issues in IaC templates or container configuration files is helpful because when in my company, we configure IaC Scanning in our production environment, it gives a brief detail about what the resources and security groups or whatever resources are the most vulnerable, after which they get sorted into four categories, namely, low, medium, high and severe. The tool sorts out the resources into four categories before you go to the production phase, ensuring that they are good and secure.

The main benefit of the use of the product in our company stems from the fact that it provides a vulnerability scanning report, which helps us to maintain the resources mainly, an area for which my team and organization use it.

I experienced the benefits attached to the solution from the first day of using it, and before its use, I was not able to identify the issues in the resources. PingSafe gave me the value and the reports that helped me to identify the issues in resources.

PingSafe's use has helped reduce the false positive rate. In the initial stages, my company had more than 100 severe cases, but within a month, we were able to reduce that to below 10 percent.

With PingSafe, the mean time to detect has reduced because initially, for detection, I had to observe resources end to end. Now, the tool provides me with a regular report because of which I don't need to observe everything inside the resources. I just need to go to a particular resource and check what is stated in the ticket to see which ports are vulnerable, after which it can be changed, so I can directly go and check it, owing to which the tool definitely reduces the mean time to detect vulnerabilities.

With PingSafe, the mean time to remediate is a maximum of twenty-four hours. Initially, in my company, we had to identify the problem and then proceed with remediation, but now we can do it directly since the report is already available.

PingSafe has affected and helped me a bit to deal with the collaboration between cloud security application developers and AppSec teams because it helps me to keep my resources and tell the developers that we cannot expose them to the extent where the application will become vulnerable to attacks. In general, the tool is helpful since it reduces the time needed to connect DevOps and developers.

I found the product to be pretty useful. I directly onboarded the product and started to use it. I did not find any difficulties with the tool.

I rate the tool an 8 out of 10.

We use PingSafe as a cloud-native application protection platform. It scans all our accounts to identify any loopholes or vulnerabilities. We get the results and recommended resolutions. It provides reports with all the minute details. For example, it might tell us there is an admin user with access that might increase the risk. PingSafe gives a comprehensive overview of anything about our cloud posture. 

We scan an Azure or AWS account, and PingSafe tells us the particular route an attacker might take and the risks. We use it extensively because it provides information on everything that could lead to a disaster. We're scanning 20 to 25 database accounts, with no more than 20 users.

PingSafe helped us close the loopholes in most of the services, improve our cloud security posture, and lock down who has access. The solution's reporting helps with auditing and compliance. When we started, our posture rating was around 77 percent. It's now at around 98 percent after we closed the loopholes.

The false positive rate is low. It's accurate 99 percent of the time. If we are doing a continuous scan, we sometimes get false positives, and we used to get much more in the early days of our deployment, but now it's quite effective and efficient.

PingSafe has reduced detection and remediation time by 10 to 20 percent. It has also improved collaboration among our security and application teams. We now get reports every 10 days, which has improved our teams' productivity because they don't need to go back and forth. It has made the DevOps and security teams' work about 20 to 30 percent more efficient. 

With PingSafe, it's easy to onboard new accounts. When there's a major acquisition, we have dozens of new accounts that we need to onboard quickly. It's very easy to use. The proof of exploitability is critical because we must present the results to a developer. Without evidence, they won't understand the problem.

The resolution suggestions could be better, and the compliance features could be more customizable for Indian regulations. Overall, the compliance aspects are good. It gives us a comprehensive list, and its feedback is enough to bring us into compliance with regulations, but it doesn't give us the specific objects. 

I have used PingSafe for nearly 2 years. 

I rate PingSafe 9 out of 10 for scalability. 

Deploying is straightforward and only takes a couple of days. One person did the initial setup, and whoever needs to use it can access it through the portal. It doesn't require any maintenance. 

We've seen a return in the form of time saved. It gives us timely reports, and time is money. 

In some markets, PingSafe is a little on the higher side, but it's just right for us. It's a good value for the money.

I rate PingSafe 9 out of 10 and would recommend it to others. It's easy to use. 

Cloud Native Security helps us identify security issues related to cloud configuration and containers. We leverage cloud synchronization for real-time incident notification.

Cloud Native Security is easy to use. Its user-friendly features make integrating new tools a breeze. Everything can be connected through a simple API. The intuitive dashboard and effortless ticket submission further enhance the user experience.

One of Cloud Native Security's most valuable features is its offensive security engine. This engine excels at identifying vulnerabilities caused by misconfigurations, which could potentially be exploited by external attackers. In these cases, Cloud Native Security's offensive security engine findings are highly accurate, with a proven positive detection rate.

Cloud Native Security has helped reduce the false positive rate. The reduction in false positives has improved our operations.

As a small startup, implementing all security best practices across the organization can be challenging. Additionally, security awareness may not be widespread. However, Cloud Native Security, a cloud-based security tool, helps us address these limitations. Cloud Native Security acts as a vigilant watchdog, continuously monitoring our infrastructure for misconfigurations. This includes detecting unauthorized access attempts, such as someone opening a specific port or granting historical access from an external AWS account. By integrating Cloud Native Security with our Slack channel, we receive immediate alerts whenever such suspicious activity occurs. The notification will highlight the potential risk and provide details, allowing us to investigate and take prompt action. Previously, we unknowingly stored sensitive information, known as hard-coded secrets, in our public GitHub repository. Since integrating Cloud Native Security with GitHub, these secrets are identified immediately and flagged through Slack alerts. This enables us to address the issue swiftly and reduce our overall security exposure.

It is far more effective at reducing our meantime to detection compared to the open-source solution we used previously.

Cloud Native Security's findings have led to increased collaboration with our infrastructure team. While our application is a separate product and doesn't reside in the cloud, Cloud Native Security has still proven valuable in this way.

Cloud Native Security's best feature is its ability to identify hard-coded secrets during pull request reviews. This helped my organization identify nearly 10,000 secrets added across our repositories, many of which had a significant security impact. Integrating Cloud Native Security with GitHub alone allowed us to identify all these secrets. This is a key feature that has been instrumental in improving our security posture through testing.

Secondly, Cloud Native Security's cloud SIEM feature has been essential in preventing our most critical security incidents.

We are experiencing problems with Cloud Native Security reporting. Our organization primarily uses Jira for issue tracking. While Cloud Native Security offers input options for reporting vulnerabilities, the "connect action" it provides to link issues isn't replicating information to Jira. This is happening for approximately half of the company and is causing difficulties for developers and stakeholders in fully understanding the reported issues.

Cloud Native Security's proof of exploitability is not that useful when it relates to container images. More detail should be included in the reporting.

Cloud Native Security can identify hard-coded secrets within our code and tell us if they're valid or not. However, in some cases, Cloud Native Security may flag a valid secret as hard-coded without specifying its exact location within the codebase. This lack of detail makes it difficult for developers to identify where the secret is used. Ideally, Cloud Native Security should provide the specific location of valid hard-coded secrets. This would significantly improve the developer experience by allowing them to easily locate and manage these secrets.

Cloud Native Security integrates with Jira and Slack through APIs, which is great. However, I would also like to see Cloud Native Security offer APIs that allow us to directly build dashboards within the platform. This would be incredibly helpful for visualizing vulnerabilities, security settings, and Cloud Native Security usage reports. Imagine if Cloud Native Security provided these APIs. We could create custom dashboards for specific purposes, like offensive security, cloud misconfiguration monitoring, or even integrating ISS scans. Essentially, any customer could easily build dashboards tailored to their needs. Unfortunately, Cloud Native Security doesn't currently offer this functionality. Other security products provide this level of customization. Adding this feature to Cloud Native Security would significantly improve its overall solution. 

I have been using Cloud Native Security for two years.

Cloud Native Security is extremely stable and we have not encountered any issues.

Cloud Native Security is scalable.

We contact technical support weekly. They are helpful and respond quickly. Additionally, there is a built-in chatbot that allows us to submit support tickets.

Positive

We also rely on AWS built-in features that alert us if there are any misconfigurations along with Cloud Native Security.

Regarding the license model, I believe their approach is appropriate based on the customer workload data we're tracking. It seems like an ideal way to proceed.

For pricing, it currently seems to be in line with market rates. However, I recall Cloud Native Security charging a slightly higher premium previously.

I would rate Cloud Native Security nine out of ten.

We receive notifications from Cloud Native Security whenever maintenance is required, and they provide instructions to complete the process.

New users should be prepared to have a dedicated staff member manage Cloud Native Security. This person will handle alerts, configurations, and integrations. You should continuously evaluate all the findings that Cloud Native Security provides, as it performs daily scans. However, it's possible to miss vulnerabilities that have already been fixed. Therefore, careful attention is needed when raising issues with developers. To optimize your use of Cloud Native Security and potentially reduce workload, consider providing feedback to improve the product. Additionally, try to utilize as many features as possible, as they can all have a positive impact on your organization's infrastructure.