SentinelOne Singularity Cloud Security Reviews

We use it to monitor Azure and AWS accounts. We also use it to monitor the GitHub account for any data leakage and misconfigurations and also to have proactive configuration checks.

We were looking for a CNAPP solution that could provide details about cloud misconfigurations, compliance, and any risks. PingSafe provides that. The feature of offensive security has been very helpful for us.

We only use agentless scanning. We have not installed agents anywhere. It collects data and provides information.

We use PingSafe's Offensive Security Engine. The analytics features of PingSafe are something that other providers do not provide. They have scanning on the port base and simulation of attacks. It is a very helpful feature to proactively resolve issues. It handles verifying actual exploit paths and prioritizing breach potential very well.

The proactive approach and offensive security have helped us to fix things in advance before they can be exploited.

We were able to realize its benefits immediately. As soon as you configure it, it does its job. It takes a day to configure it and discover the assets. It is easily deployable, and it immediately starts providing inputs.

PingSafe helped reduce the number of false positives. It also helps with our SOC monitoring. The alerts are reduced, and we are in compliance.

We get details about how much we are compliant with different frameworks. It helps us to evaluate the risk posture as well. We use the reports to evaluate our risk posture.

The proactive approach and advanced fixes reduce the number of false positives, but it is difficult to know if PingSafe has reduced our mean time to detect. PingSafe has definitely reduced our mean time to remediate.

PingSafe has not had an effect on the collaboration among various teams because, in our environment, everything is done by IT, but we have visibility across all the domains. We can work together if needed, but it is not yet applicable to our organization.

The offensive security where they do a fix is valuable. They go to a misconfiguration and provide detailed alerts on what could be there. They also provide a remediation feature where if we give the permission, they can also go and fix the issue.

They also support private clouds to a certain extent. It is pretty easy and customizable.

PingSafe's interface is pretty easy and comfortable. They keep on improvising it. When you are configuring, it is pretty easy.

It is a very secluded solution. It works only as CNAPP. It does not bring much threat intel from the outside world. All it does is scan. If it can also correlate things, it will be better. It can discover the threats from the outside world. It can discover the threats or vulnerabilities happening across those assets. If it can bring that in and evaluate, it will be good.

We have been using PingSafe for a year.

It is stable. We have not observed any issues.

We have not increased our assets, so it is difficult to say anything about the scalability part.

I never had to contact their support.

We were not using a similar solution previously.

It was pretty easy. It was very straightforward. They had many things available. We got the scripts on Azure, AWS, and GitHub, so the installation was pretty easy. It took a couple of hours.

It is a cloud solution. It does not require any maintenance.

We implemented it on our own. Only one person was required from our side.

Their support was not required. They offered to help. They assigned a customer success manager, but it was easy to deploy, so we did not require much help from their side.

Its pricing is okay. It is in line with what other providers were providing. It is not cheap. It is not expensive.

We evaluated 2 more products. One was Zscaler, and the other one was Wiz. Offensive security and support for the private cloud were the reasons for going for PingSafe.

I would advise evaluating PingSafe based on the use cases. You should know what is required and how PingSafe can support that. If PingSafe is able to fulfill your cases, it will be good. A thorough evaluation and mapping of the organization's objective should be done before buying PingSafe.

I would rate PingSafe an 8 out of 10. It is good.

I am working with AWS. I'm a junior cloud engineer and on the client side, we use this software for security. We use this just for scanning all across the AWS environment for any bug, vulnerability, or high risk security issues, and we have to resolve these issues. The solution offers us low to critical alerts and our work depends on these alerts. If it is a critical alert, we have to resolve things as soon as possible. 

The scanning is very good. We have an AWS environment and we can scan our whole account very quickly. Once the alerts get analyzed, we can automatically start removing issues. 

It's easy to use. It comes with preconfigured settings. I haven't had to really change anything for months. 

We have used evidence-based reporting. We're able to give reports on AWS, for example, how many data centers are used, et cetera. We can collect all of the information from PingSafe and share all kinds of data which we can share with the database team for analysis. 

The IaC scanning has been good. It's very interesting. 

When I create a stack for any services in AWS, I can scan everything in a robust environment. This enables me to understand the level of protection.

PingSafe can also scan code and provide alerts of there are vulnerabilities.

It's helped us reduce the number of false positives. I've been on the project for 6 months, and it was only until 3 or 4 months in that I received a false alert. Out of 20 alerts coming in, maybe only one or two are wrong. 

The mean time to detect has been reduced. We check PingSafe every day for a project happening 24/7. We check it frequently to ensure issues are being addressed quickly. We try to be consistent, however, the alerts don't come in at a certain time. They come in at varying times; we just work to keep on top of them.

We've had a glitch in PingSafe where it has fed us false positives in the past.

Sometimes, it takes a few hours to detect a misconfiguration. It would be ideal if that happened faster. Detections should happen in minutes, not hours. 

I've been using the solution for 6 months.

I have not noticed any lagging or crashing. The stability seems to be good. 

We have dealt with support in the past. They were helpful.

Neutral

We did not previously use a different product.

We had senior members of the team manage the installation since they had expertise. I'm not sure how long the process itself took. 

I don't have any visibility on the pricing. 

I'd rate the solution 8 out of 10. 

There are a lot of options. It's a good idea to have a team member arrange on at least a quarterly basis, a review so that new team members can get up to speed on the product and everyone stays on the same page. This will help new team members understand the product. 

We have AWS for most of our infrastructure, however, we don't have a dedicated security team. There are a lot of potential vulnerabilities which we are concerned about. We use PingSafe for security. For example, if there are open ports or incorrect configurations, we would get alerted and could fix them.

They have dedicated cloud-based configurations, which are quite helpful. 

The product works well with AWS. It can help us manage AWS security. If there are any groups or details that are incorrect or unsafe, or even misconfigured, it helps protect us. 

The product offers ISE scanning, which basically scans all activities for issues. 

We can pick up on pre-production issues. It's very helpful. They've helped us by providing a lot of CI/CD tools. Everything gets scanned so that we can get a sign-off before a deployment.

The ease of use is very good. I'd rate the ease of use 8 out of 10. They have nice UI and templates and the docmentation is very helpful. It's very thorough. 

They also have a good support system for users. If something is not working, they have a good SLA, and within a day or so, they will reach out and help you with whatever you need. 

The agentless vulnerability scanning is great.

If a protocol is not being properly followed, we'll be alerted. This helps us react faster to any production issues. 

We do use the offensive security engine. It's good for verifying exploit paths and prioritizing items. We have recently started using this. It allows us to see which endpoints, for example, are publically accessible, or what code repositories have vulnerabilities in terms of libraries we are using that may be outdated. For example, if we've noted our NGINX server is very publically exposed we can change things. 

The benefits of the product were felt almost immediately as it allowed us to handle issues in the pre-production phase. We didn't have to make anything live before finding issues. Within an hour, we'd begin to see issues, and within 4 to 6 hours, we'd have a full survey of security vulnerabilities. We also get regular notifications when the system sees something is off. Based on the information we receive, we're able to react and fix things very quickly.

We're able to see both high and low-priority issues so that we can accurately prioritize what to do first. That helps us manage bandwidth in terms of resources. 

PingSafe has helped us reduce the amount of false positives we see. We've reduced false positives by around one-third. 

Our mean time to detect has been reduced, as well as our mean time to respond. We used to rely on a third-party provider to find issues, and now we can do it in-house. This means we no longer have to sync our AWS information on a daily basis. Now, we have a direct integration with PingSafe. We used to have a delay of 36 to 48 hours before we would recognize if there were any vulnerabilities. On top of that, there was a reaction time delay of 4 to 6 hours, meaning issues wouldn't be dealt with until maybe 50 or so hours after the vulnerability was detected. We've reduced all of this down to maybe 8 to 10 hours.

The collaboration between cloud security, application developers, and AppSec teams has been better. It's mostly been positive for us. 

They could improve on their UI.  Sometimes it's not clear where to look when seeking information. Support often can direct us by giving us the correct link to what we are looking for. 

I'd like to see better onboarding documentation. If we want to be able to integrate something new, such as new assets, it can be difficult. 

I've used the solution for more than 2 years now. We started using it around December 2021 or January 2022. 

I haven't faced any lagging or crashing. 

For our use case, it has been scalable. 

The support they provide is good. They give you very detailed information and documentation which they have created internally. They are very informative. They've even shared their own internal documentation in terms of AWS issues or questions. 

They are quick to respond, You can rely on them. 

Positive

We did use a different solution, however, it didn't offer direct AWS integration. Due to this, we had to wait up to 48 hours for information on vulnerability issues. We were already having security issues in that timeframe, so we needed something that could help us detect faster. 

The initial deployment was easy. However, having more initial onboarding documentation would have been better. However, we've created some internal docs that have helped us with our use case. How long it takes to deploy depends on the use case, however, we were able to have it up in 12 to 14 hours. We had 2 people working on the deployment. 

PingSafe did offer some assistance with the setup.

I'm not sure of the exact pricing. However, my understanding is that it is very economical. 

We did explore Crowd Strike at some point. Crowd Strike was a very big platform and we were not sure how much support we'd get. We wanted to make sure we had priority support.

I'd rate the solution 9 out of 10. The usability is very good. Both their new and mature products are good in terms of their overall usability.

We have a wide array of applications. It extends beyond mere container and threat management; in fact, we extensively utilize it across all facets of our cloud data management. It offers comprehensive security for our entire infrastructure, encompassing containers, Kubernetes, cloud services, and more. Its scalability is particularly beneficial for our operations.

We receive Slack alerts for any vulnerable resources within our inventory. These alerts indicate if a particular resource is vulnerable and requires attention, ensuring timely action for remediation. Additionally, critical events are promptly communicated to us, enhancing our overall security posture.

Furthermore, we are provided with compliance metrics, allowing us to gauge our level of adherence to regulatory standards and guidelines.

Cloud Native Security's automation features have revolutionized our approach to cloud-native security, making it a standout solution in the market. With its seamless automation capabilities and timely alert notifications, Cloud Native Security ensures that we stay ahead of potential vulnerabilities, providing peace of mind in our dynamic cloud environment.

One of Cloud Native Security's greatest strengths lies in its ability to streamline compliance management. While specific controls are not directly provided, Cloud Native Security's automated assessment of our cloud and server infrastructure empowers us to maintain compliance effortlessly. The platform offers comprehensive insights into our compliance status, allowing us to identify areas for improvement and scale up our operations with confidence.

During our initial implementation, Cloud Native Security proved invaluable in tackling the challenges posed by our extensive resource inventory. By providing a detailed breakdown of resource utilization and associated vulnerabilities, Cloud Native Security enabled us to take proactive measures to enhance our security posture. The intuitive dashboard interface offers granular control and simplifies decision-making, sparing us the burden of manual inspections.

Cloud Native Security's automated auditing feature sets it apart, offering a comprehensive overview of our cloud resources with minimal effort. The asset inventory feature provides detailed insights into resource usage, ensuring that no stone is left unturned in our quest for security and compliance excellence. While there may be a slight learning curve initially, Cloud Native Security's user-friendly interface makes navigation a breeze over time.

The evidence-based reporting functionality of Cloud Native Security is a game-changer, allowing us to prioritize and address critical security issues efficiently. While occasional false positives may occur, Cloud Native Security's continuous improvement efforts ensure that such instances are minimal and swiftly addressed. Integration with our existing security infrastructure further enhances its capabilities, providing a holistic approach to our security strategy.

Overall, Cloud Native Security has been instrumental in fortifying our risk posture and facilitating our growth trajectory. With a significant reduction in mean time to detect issues and improved visibility for our development teams through DevSecOps integration, Cloud Native Security has truly become an indispensable asset in our security arsenal.

While we do encounter occasional false positives, we appreciate Cloud Native Security's efforts to address this issue.

In terms of improvement, we believe there's room for enhancing the comprehensiveness of their rule sets. Specifically, if we have unique requirements for our cloud security and need to establish custom rule sets, we require more comprehensive options than currently available. While Cloud Native Security has provided a feature for this purpose, its implementation is currently challenging. We see this as an area for improvement where Cloud Native Security could refine its offerings to better meet the diverse needs of its users.

I've been using the solution for 1.5 years. 

We have not found any glitches or suffered any downtime. 

Currently, we have approximately three platform engineers actively utilizing the solution.

The solution demonstrates excellent scalability and offers considerable flexibility.

Technical support is good. They help us out on certain details. We can submit tickets in order to get assistance. 

Positive

Previously, we didn't employ a different solution; instead, we relied on various open-source tools. While these tools weren't direct competitors, their functionalities didn't fully align with what we needed. Since adopting this solution, we've witnessed significant improvements in scaling our security measures effectively.

The initial onboarding process for Cloud Native Security resources presented some challenges, albeit manageable ones. However, the deployment itself was remarkably swift, typically taking only 15 to 20 minutes. Incorporating Cloud Native Security into our original deployment was crucial for establishing permissions effectively. To manage power demand efficiently, we required running scripts consistently.

As a Software as a Service (SaaS) solution, deployment to multiple locations wasn't necessary. Cloud Native Security is hosted on their cloud platform, eliminating concerns about maintenance or internal management on our end. We can rely on the provider for seamless operation without the need for internal intervention.

The pricing is fair, as it is determined by the resources we utilize. We have the flexibility to adjust our resource usage according to our needs.

Prior to implementing this solution, we didn't assess any other options.

Currently, the market offers numerous products for cloud-native security. Despite the abundance of choices, we received excellent guidance with this solution. The support provided was invaluable, demonstrating their strength in customer success.

As end users, we don't maintain a direct relationship with the company.

I highly recommend this solution to fellow users.

In terms of rating, I would give the solution a solid 9 out of 10.

Our Cloud Native Security use cases depend on the type of SQL server we use. Currently, we need to check all cloud-based configurations directly. Cloud Native Security helps us identify SQL configurations on our local PCs.

Cloud Native Security has improved our cloud security monitoring processes. We can now capture all issues and misconfigurations in real-time, allowing us to respond quickly.

It streamlined compliance management for our organization. They schedule a meeting with us every month to discuss any requirements on our end, such as updating the Cloud Native Security version. For example, one time they informed us that we needed to update to Cloud Native Security version four. We inquired with their customer support team, who were very approachable and requested them to implement the cloud version of Cloud Native Security version four into our Cloud Native Security dashboard. They implemented it within five to six days. We were happy to adopt the enhanced security controls of Cloud Native Security version four. The customer success team and the customer-facing teams were very helpful and provided us with the best solution. This is why we chose Cloud Native Security. They are a well-established CSPM company in India with a proven track record of assisting businesses with compliance requirements. By onboarding Cloud Native Security, we gained a cloud-based configuration management system for our workloads.

It's easy to use.

Our cloud security issues are already automated using a common subscription ticketing tool to capture them. Reports are then sent to both the internal DevOps team to identify potential false positives and the business team to assess if resolving the issue aligns with business requirements.

Cloud Native Security's event-based evidence reporting should include proof of exploitability. This would allow users to easily identify misconfigured areas in the graph and click on a provided link to conveniently be redirected to the cloud service provider management console page for more details.

Cloud Native Security's offensive security engine proved valuable recently. When an endpoint was mistakenly exposed, it automatically captured the unauthorized request in the cloud and sent an alert to our email address. This notification allowed us to take swift action and restrict access to the URL on our network.

The AI helps us handle the hundreds of audits each year helping to enhance our security posture.

Cloud Native Security's access to the IIM role in the cloud formation template significantly reduces false positives, thereby maximizing the number of true positives.

Cloud Native Security helps us improve our risk posture, failover capabilities, and compliance levels.

Cloud Native Security reduces our MTTD. We are alerted within seconds on the dashboard and email of the detection.

To assess our MTTR, we need to consult with the DevOps team and conduct an impact analysis. If the impact analysis reveals no disruption to the production application within the AWS network architecture, we can proceed with remediation immediately. However, if the analysis identifies a potential impact, obtaining management approval will add to the resolution timeframe.

Cloud Native Security improves collaboration between our cloud security application developers and AppSec teams. It's particularly helpful for AppSec because we can leverage cloud security controls directly from Cloud Native Security. This also allows us to mitigate cloud misconfigurations.

Cloud Native Security's most valuable features include cloud misconfiguration detection and remediation, compliance monitoring, a robust authentication security engine, and cloud threat detection and response capabilities.

In addition to our telecom and Slack channels, it would be helpful to receive Cloud Native Security security notifications in Microsoft Teams. 

I have been using Cloud Native Security for six months.

Cloud Native Security is stable.

The scalability of Cloud Native Security is good.

The technical support is the best. They can integrate our suggestions for security control into Cloud Native Security within three days.

Positive

The deployment took one week. The deployment was completed by one person from our team along with a tech team from Cloud Native Security.

Cloud Native Security is priced reasonably for our workload.

I would rate Cloud Native Security ten out of ten.

We have a large number of users of Cloud Native Security in our organization.

I recommend Cloud Native Security to others.

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 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.

I work for an insurance company whose infrastructure is on the cloud, so we use PingSafe for security management and vulnerability detection. 

PingSafe is a valuable tool for managing infrastructure security. It offers advanced features like container security management, microservices security management, and Configuration Drift Remediation, which helps identify and address unauthorized configuration changes. These features are comprehensive and adaptable. Even for custom infrastructure modifications, such as XYZ, the PingSafe team can be contacted for guidance and policy adjustments to ensure a smooth adoption process.

Infrastructure as Code is valuable because the code itself defines the infrastructure. This means any vulnerabilities or misconfigurations in the IaC code will be deployed to our infrastructure. However, IaC tools can scan the code and alert us to potential problems before deployment, allowing us to fix them proactively.

We saw the benefits of PingSafe immediately.

It helped reduce the amount of false positives.

It has reduced our mean time to detection and remediation.

PingSafe improved collaboration between our cloud security developers and the application security teams.

The collaboration helped us save time, which is one of the reasons we have continued to use PingSafe.

The cloud misconfiguration is the most valuable feature. It highlights any misconfiguration that can make our infrastructure vulnerable.

I would like PingSafe to add real-time detection of vulnerabilities and cloud misconfigurations.

I have been using PingSafe for almost 2 years.

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

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

The technical support is good. They are knowledgeable and prompt.

Positive

The deployment was straightforward. One person was required from our end.

The implementation process itself was very smooth. The PingSafe team provided excellent assistance in integrating the solution with our existing infrastructure and account. This made the integration process hassle-free. We've also recently integrated a new CDR feature using PingSafe.

I would rate PingSafe 10 out of 10.

No maintenance is required for PingSafe.

Once you've acquired PingSafe, it's essential to review all your existing organizational policies. If these policies are compatible with your infrastructure, you can proceed without modifications. However, if there are any incompatibilities, you'll need to make adjustments to ensure your infrastructure triggers accurate alerts. Skipping this step can lead to a flood of false positives.