SentinelOne Singularity Cloud Security Reviews

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. 

We currently use Cloud Native Security for cloud security posture management, leveraging both the CWP module and the authentication security tab. While we regularly utilize these features, we're planning to onboard the cloud detection and response module, along with the ISIS scanning functionality.

We implemented Cloud Native Security as a secondary control measure to complement our existing security posture. In our Prisma Cloud environment, we have a detection score threshold set at 70 or above. As Cloud Native Security was a new entrant in the market, we wanted to evaluate its capabilities. Fortunately, Cloud Native Security's unique features and policies proved valuable. For instance, Cloud Native Security detected an alert when a developer accidentally committed VS Code files to a public GitHub repository. This helped us promptly remove the VS code from GitHub.

Cloud Native Security is easy to use.

The feature that has been most effective in threat detection for our cloud environment has been the cloud visual attack tab.

Our cloud security is managed by Intel and Azure Entra. We download a report from them and send it to our team to address any identified issues.

I appreciate that Cloud Native Security incorporates evidence of exploitability into their reports, making them more reliable.

Cloud Native Security's offensive security engine excels at validating potential exploit paths and prioritizing the most critical vulnerabilities. This enables us to proactively identify and address these risks, ultimately strengthening our security posture.

Cloud Native Security has helped reduce our false positives. We can investigate and mute any false positives so they don't appear going forward.

Cloud Native Security helps us actively identify threats, ultimately improving our security posture.

Cloud Native Security has reduced our mean time to detect by 10 percent.

Cloud Native Security facilitates collaboration between our cloud security application developers and AppSec teams. This collaboration is further enhanced by a shared console that provides visibility into all active tickets. This transparency helps to reduce redundant requests, saving time.

Cloud Native Security offers a valuable tool called an offensive search engine. This tool has been helpful for us. It allows us to search for vulnerabilities and provides evidence directly on the screen. Additionally, Cloud Native Security offers a feature called Graph Explorer. This feature allows us to drill down into specific resources, search for them on the console, and view details such as open security rules and graph features.

While only 5 percent of our workload resides on the Google Cloud Platform, we would still like Cloud Native Security to be configured with automatic remediation capabilities for GCP.

In Prisma, there's a dedicated tab for managing high and medium-severity alerts. This allows us to easily enable or disable specific policies based on our current needs. With Cloud Native Security, we can't selectively enable or disable alerts based on our specific use case.

I have been using Cloud Native Security for six months.

I would rate the stability of Cloud Native Security 7 out of 10.

The only downtime we had was when switching from V1 to V2 but it was smooth.

I would rate the scalability of Cloud Native Security 8 out of 10.

The technical support is good.

Positive

For the past three years, Prisma Cloud has been our go-to security solution. Recently, we've added Cloud Native Security to our toolkit to further strengthen our security posture.

The initial deployment was straightforward. First, we onboarded the UAT account. Then, we added our product support account and other accounts. We then tested the UAT environment accounts. The entire deployment took one week to complete. Two people were involved in the deployment.   

I would rate Cloud Native Security 9 out of 10.

Our primary cloud security monitoring solution is Prisma Cloud by Palo Alto Networks, with Cloud Native Security as a secondary control measure.

We have 19 users overall in our cloud security team that utilize Cloud Native Security.

The only maintenance required is for updates.

I would recommend Cloud Native Security to others.

We are running the entire cloud base on AWS infrastructure. The major use case for this product is cloud misconfiguration because a lot of changes keep happening in our environment. There are multiple teams and multiple verticals within our organization. We have different verticals across different business units. They have their local IT infrastructure teams, and all these teams are making changes. 

We have IT admins at multiple locations. There is a team of 10 to 12 members. It was a challenge to manage cloud security when they made changes, spun up new servers, or created new instances for new projects. Cloud misconfiguration was one of the major areas where we saw issues because things were not getting created as per the process or security protocol. When they are creating instances, they are not aware of the implications and the security incidents that may happen by keeping certain ports open. They might not be aware of the security issues that may come up. So, cloud misconfiguration was one of the main reasons why we opted for this product.

Another reason was to have a dashboard for the management and for the centralized team. We are a part of the centralized team that is taking care of the entire platform. It is very necessary for us to keep track of the changes and see if any P1 or critical security incidents are open. They are a risk to our organization's security. We wanted to have such visibility. Manually keeping track of those changes and open issues was very difficult for us.

It highlights critical or high-priority incidents. That is helpful. When we have a lot of issues on the dashboard, we can at least prioritize them based on the severity. We target critical incidents first and then move to the high-priority incidents. We still have medium and low-priority incidents on the dashboard. We require some amount of time to fix them. From a reporting perspective, it helps us to prioritize accordingly. We know that at least from a high-impact point of view, we are secure.

We do generic vulnerability scanning whenever there are any new changes or we are building any new applications. We keep the generic vulnerability scanning on whenever any new instances are created, and we run the scan once a week for already created instances.

We have not explored evidence-based reporting much. It is a good feature, but we mostly look at the priority of the incidents. We fix them based on the criticality. The description of the issues and the categorization make it easy to utilize the reports.

It has affected our risk posture. All the critical incidents and high-priority issues have been resolved. We are in a better place now in terms of risk posture. The medium-severity issues still need to be fixed, but earlier, we used to have critical incidents as well. We did not have any visibility into those things. We are now quite confident that we do not have any major security issues. We keep running the scan every week. It helps us to detect any new changes or vulnerabilities in our environment.

We could see its benefits immediately in terms of visibility. Previously, we did not have any visibility into where we were in terms of the security landscape. That benefit was immediate, and then we started fixing the problems and reduced critical issues and high-priority issues. We became confident in our security, and we were able to secure the environment wherever we had an incident. Its benefits were immediate from a visibility point of view, and then it took two to three months to have a direct impact in terms of security.

Singularity Cloud Native Security helped us to reduce false positives. We also have a managed service provider. We took their help to reduce false alarms and other issues. It also helped us to implement some of the best practices while creating any instances or making any changes to any particular instances. We created best practices and standard operating procedures for the infrastructure team. They follow the standard operating procedures while making any changes or creating any instances. We are seeing a drop in the number of issues compared to two or three years ago.

Our remediation time is reduced. Initially, it took some time to identify the remediation steps and what had to be done to fix the problems, but now we know what needs to be done. From a prevention point of view, we now know what we should not do. That has helped with changes that we keep on doing in the environment.

Singularity Cloud Native Security provides us with a platform to scan instances when they are getting created, and the dashboard helps us to identify the critical issues. We created a road map and prioritized the issues based on the criticality of the problem. We have reduced P1s. We have resolved any critical incidents that came up in the dashboard. We still get high-priority incidents, and we keep on prioritizing and fixing them. That is because we have visibility into the open issues that we have. Management is also happy. They are aware of the things that are coming up on the dashboard. They are aware of the impact and the risk. We did not have this visibility previously. All the teams that are a part of IT are aware of the importance of it. It has been included as part of our software development cycle.

It is very easy to use. The user interface or the dashboard is quite simple. It clearly shows you the type of issues that are there. It also breaks down and groups them into the types of issues. If I have 100 issues on the dashboard, it categorizes them. Out of these 100 issues, 50 of them might be related to the same category. If I choose one of the high-priority incidents and fix them, all 50 issues might get fixed. This way, it is a bit easier for us to target specific use cases and resolve a lot of underlying problems. The descriptions are helpful. It gives us information about how to resolve a particular problem. It is easier when the tool itself tells you what you have to do to fix an issue. You can then research more and get it done. It is quite simple. Even the leaders who are not very technical can understand what is the impact and what is causing the problem.

They can provide some kind of alert when a new type of risk is there. There can be a specific type of alert showing that a new type of risk has been identified.

We use Jira for pushing any changes. If any kind of integration is possible between Jira and the Singularity Cloud Native Security dashboard, it will be easier for us to track. Before approving in Jira, I can ensure that any issues in Singularity Cloud Native Security are closed. Such an integration will be helpful.

Its pricing model is a little bit inflexible. Different organizations have different structures. We have multiple business units. Based on the different verticals, we have to create different subscriptions for them. If I create a new subscription and add it to Singularity Cloud Native Security, as per the current licensing model, I have to pay more for that. It should not be like that. It should be based on the number of servers. This kind of flexibility would help customers like us.

It has been close to two years since we have been using this solution. Prior to this, we were working with CrowdStrike, and then we migrated to SentinelOne two years back.

I have not seen any issue with Singularity Cloud Native Security.

If any slowness is there, we will probably wait and run it after half an hour or one hour. Nothing major has been highlighted to me or has been a blocker as such. The pricing model is the only thing that would be a concern. 

We take help from our managed service provider. If we have to fix any particular problem that we are not aware of or do not have the expertise for, we get help from the managed service provider. They have a service team with experts. They get it done for us.

We did not directly use any other solution. We have a managed service provider. We have taken their help, but it was more of a tool that they used at their end, and then they shared a report with us. Based on that report, we took action. It was not a regular thing that we used to do. Once in a quarter, we would probably allow them to scan and send us a report. Based on that, we used to take action. That was the process that we used to follow earlier.

Its implementation was a little bit difficult because it was a new tool that we were using. It takes time to understand the issues, specifically in terms of what has to be done to fix them. Aligning all the teams was a little bit difficult for the initial two to three months, but once we understood the product and what needed to be done for the issues that were getting highlighted in the dashboard, it was easy.

Initially, we had to do a lot of sessions to bridge the gap. That was because this initiative was taken by the Cloud Security team and the DevOps team. We needed a lot of patience to collaborate with the engineering or development team. A lot of the issues required help from the engineering team in terms of making changes at the core level as well. It took one or two months of time to do sessions with the developers and create SOP within the development life cycle itself. Overall, the support from the leadership was quite good. All the leaders agreed that this is a very important change that we are bringing into the organization, and it will be an ongoing thing that we need to follow. We have also added it as part of the SDLC. We use Jira to manage changes and defects. We have added security as one of the flags over there. Someone from the InfoSec team has to give a sign-off for any changes that are happening. If a project is going live, he has to check any open issues in Singularity Cloud Native Security. He has to give a sign-off before the project goes live. That is one of the changes that we have pushed in terms of the product life cycle itself, and that has helped to align different things. Unless they get a sign-off from the InfoSec team, it cannot be deployed. Everyone knows the process now. It is a part of the cycle.

It took at least 45 days to deploy and utilize all the features. We did not do it in one go. We did it phase-wise. We opted for one subscription, and then we slowly deployed it across other subscriptions.

It does not require any maintenance from our side. We have a managed service provider, and they are keeping track of it. There is no additional maintenance as such. We just have to keep track of things. It is more of a process adherence and making sure that we keep a check before we push anything into production.

I am personally not taking care of the pricing part, but when we moved from CrowdStrike to Singularity Cloud Native Security, there were some savings. The price of CrowdStrike was quite high. Compared to that, the price of Singularity Cloud Native Security was low. 

Singularity Cloud Native Security is charging based on the subscription model. If I want to add an AWS subscription, I need to pay more. It should not be based on subscription. It should be based on the number of servers that I am scanning. There should not be an extra charge for adding a subscription, and the pricing should be based on the number of servers that I am scanning.

We are not using Singularity Cloud Native Security's Offensive Security Engine. We used the Infrastructure as Code (IaC) Scanning initially. When the demo was given, we had to use that scanning, but it is not something that we keep running on a regular basis.

Overall, I would rate it a nine out of ten. I am quite happy with the service and the value that it provides. The one point that I am not giving is because of the pricing model. If it had a more flexible pricing model, I would rate it a ten out of ten.

We are using the solution to identify the security vulnerabilities in our AWS infrastructure. Whenever we create a new infrastructure in AWS, if there is a vulnerability, an issue is created in the PingSafe console. There are different severities, such as critical, medium, and high. The product also provides solutions to resolve the issues. PingSafe provides a solution document for AWS. It helps us resolve issues. We have seven to eight AWS accounts. It is all in PingSafe. PingSafe identifies the issues with all the accounts.

Our company has very strict compliance requirements for security. PingSafe has helped us resolve vulnerabilities and issues using best practices. It helps us resolve the security vulnerabilities of the AWS cloud infrastructure. The compliance monitoring capabilities are helpful. The tool identifies issues quickly. It gives us the root cause of the security issues rapidly.

The evidence given by the product helps us resolve the issues. It provides a step-by-step guide to resolve issues. It helps us a lot. PingSafe provides us with a lot of information. It provides us with a document of AWS. We use AWS CloudFormation. If there is an issue with AWS CloudFormation or if the code is rapidly changing, PingSafe will identify the issue.

The number of false positives depends on the requirements of the clients. If the client needs something for their application and it shows as an issue in PingSafe, we must contact PingSafe and close the issue as an exception. The tool has reduced the false positives by 10%.

The solution helps us maintain our risk posture. We use a web firewall in AWS. If we do not have a firewall in any of the resources, the PingSafe console will identify it as an issue. The tool has helped reduce the mean time to detect. We check the PingSafe dashboard daily. We have a checklist. We can identify how many issues are open and how many issues are closed. It helps us reduce the time to identify the issues and open vulnerabilities. PingSafe has helped us reduce our workload and time by 50% to 60%.

PingSafe helps reduce our mean time to remediate by 70% to 80%. The product reduces workload and time. It is very important in every organization to reduce time and find vulnerabilities. PingSafe also provides us with solutions to the issues. Every organization must have a tool like PingSafe. I will recommend the product to others.

The PingSafe team identifies issues when we create the infrastructure. Within two to three hours, they create an issue in the PingSafe console. It helps us resolve the vulnerabilities during the creation of the infrastructure. PingSafe provides us with documents on how to resolve issues with the infrastructure. It saves our time in identifying issues. Integration with our cloud environment was straightforward.

Based on our application requirements, we discussed some improvement points with the PingSafe team. However, after the new updates, what we asked for was not implemented. The exceptions we requested from the PingSafe team were not included in the console. When we request any changes, they must be reflected in the next update.

I have been using the solution for two years.

The product is stable. I rate the stability a ten out of ten.

We have 12 users, including internal users and clients. I rate the scalability a nine out of ten.

The solution is deployed on the cloud. The deployment takes a few days. Our cloud team and the PingSafe team were involved in the deployment process. We need two to three people for the deployment. The tool does not require any maintenance.

I am satisfied with the technical support.

We save a lot of time identifying vulnerabilities. The product gives us the issue and the solution. It reduces our time and workload.

The tool is cost-effective.

The product is easy to use. My colleague provided me with a KT of the tool. I could learn to use it in two to three days. I understood how to check and resolve issues and segregate them into different severities. The ease of use is very helpful.

Overall, I rate the tool a ten out of ten.

We're managing our cloud environment on AWS, and PingSafe is assisting us as a CSPM tool. It identifies vulnerabilities in our configuration and helps prevent malicious attacks.

Our current cloud environment allows independent resource deployment by our six to eight-person team, which increases the risk of misconfiguration. To mitigate this, we implemented PingSafe. This security tool generates alerts for misconfigurations, allowing us to promptly address them and maintain a strong cloud security posture.

Having too many resources with platform access made misconfigurations more likely. PingSafe addressed this by helping us configure everything according to best practices, helping improve our security posture.

PingSafe is easy to use.

Evidence-based alerts help us mitigate the priority issues that are detected.

The proof of exploitability in evidence-based reporting is helpful.

The offensive security engine strengthens our organization's security posture by validating potential attacker paths and prioritizing vulnerabilities with the highest likelihood of being exploited in a breach.

Infrastructure as Code facilitates the identification of pre-production issues within our Cloud Formation Templates and Terraform configurations.

PingSafe has been instrumental in ensuring our strong cloud security posture, effectively helping us manage and mitigate risks. PingSafe helped our team reduce the number of false positives.

PingSafe plays a key role in strengthening our risk posture. By providing alerts, it assists both our information security and security assessment teams in identifying and mitigating potential threats, ultimately improving our overall security position.

It has improved our mean time to detection by 30 percent and effectively reduces our average time to resolve incidents. By providing valuable information, PingSafe empowers our team to quickly diagnose and rectify problems.

It has improved the collaboration of our cloud security application developers and AppSec teams.

PingSafe has helped save engineering time by 50 percent. 

PingSafe offers security solutions for both Kubernetes and CI/CD pipelines. It helps with vulnerability remediation, ensuring timely alerts for misconfigured resources, so we can address security issues efficiently.

While PingSafe offers real-time response, there is room for improvement in alert accuracy. We've encountered instances where misconfigurations created by teammates were not flagged promptly by PingSafe, leading to downstream issues.

I have been using PingSafe for one year.

I would rate the stability of PingSafe nine out of ten.

I would rate the scalability of PingSafe nine out of ten.

The technical support is helpful.

Positive

PingSafe's team clearly explained the implementation process, which our team of three was then able to complete in just one week.

PingSafe falls within the typical price range for cloud security platforms.

I would rate PingSafe ten out of ten.

Our organization has over 35 members across various teams, each utilizing PingSafe according to their specific needs.

No maintenance is required on our end.

I recommend PingSafe to others. It has done a great job of improving our security posture.

We use PingSafe to check for misconfigurations and vulnerabilities in new infrastructure or applications we deploy on AWS. All of our accounts are integrated. When we deploy new services, it highlights any misconfiguration or lack of encryption. We return to our applications and try to fix the issues immediately. The company has about 25 PingSafe users across three teams and five cloud environments, including production. PingSafe covers all five. 

PingSafe saves us time finding misconfigurations and encryption issues. It helps us troubleshoot why data is not encrypted or why it's sitting idle for a long time. We previously had a separate team investigate the environment for security issues, like public IPs or anything like that. PingSafe saves us time equivalent to a whole team. It reduces the time spent on these tasks by about 30 percent. It has reduced our remediation time by around 10 percent.

Another benefit is security compliance. It gives us the security reports, and we implement the recommendations according to best practices provided by the team. We were around 60 percent compliant when we started. Our PingSafe security compliance score is now 99.4 percent. 

Recently, we were migrating a database from on-prem to AWS. After we successfully migrated it, PingSafe discovered that it was using default ports and that no audit or error logs were enabled. It highlighted that issue within 30 minutes. Before we went live, we reconfigured all the databases, and PingSafe helped us. 

The most valuable feature is PingSafe's feedback about the severity and impact of a misconfiguration and the best practices for resolving it. It's helpful to anyone who's using the tool. Even if you're unfamiliar with the issue, PingSafe will give you a detailed description of everything that went wrong and how to fix it. 

If your account is integrated, PingSafe's evidence-based reporting gives you an alert with the severity. Before you go live or pass it off to the other teams, so you know all the issues and misconfiguration in your infrastructure. You can fix it before passing it to the other team, and you are confident you are using the best practices. It reports weekly on the number of issues discovered and how many tickets we've closed. 

The proof of exploitability is critical. There are a few scenarios where I need to explain the misconfiguration to the team. Before PingSafe, I had to provide the evidence and screenshots to demonstrate the misconfiguration on our end, but now PingSafe takes care of all that, saving me time. As someone leading a team, I spend half as much time on these tasks.  

It separates the issues, dividing cloud-based misconfigurations from container-based or web-based ones, so we can forward them to the appropriate team. This separation is required for organizations that have multiple teams.

PingSafe is easy to use. After one login, you can understand everything. The console UI is very user-friendly.

When we get a new finding from PingSafe, I wish we could get an alert in the console, so we can work on it before we see it in the report. It would be very useful for the team that is actively working on the PingSafe platform, so we can close the issue the same day before it appears in the daily report.

We have used PingSafe for nearly 3 years. 

I rate PingSafe 9 out of 10 for stability. 

I rate PingSafe 9 out of 10 for scalability. 

I rate PingSafe support 8 out of 10. 

Positive

Before PingSafe, we were using AWS GuardDuty. We adopted PingSafe because we established a dedicated team for security compliance. 

PingSafe is a cloud-based platform, and the setup was pretty straightforward. They provided all the necessary documentation, and we had a call with the PingSafe team to help us get started. The deployment was fast—it took less than 20 minutes. Four people were involved, including the PingSafe team. After deployment, it requires no maintenance. It's good to go once you set it up. 

You can expect a decent return on investment from PingSafe. It's better to use tools like PingSafe to improve security and compliance. I estimate the ROI is around 25 percent. 

I rate PingSafe 9 out of 10. I would recommend PingSafe to anyone. It saves time, makes your environment more secure, and improves compliance. PingSafe helps with audits, ensuring that you are following best practices for cloud security. You don't need to be an expert to use it and improve your security.

We primarily use PingSafe for cloud security posture management, but the solution also provides other capabilities, like infrastructure-as-code scanning. It identifies hard-coded secrets in the source code and covers Kubernetes security. About 25 members of the security and DevOps teams use the solution. 

We have integrated all of PingSafe's CWPP, CSPM, application security, and container scanning features into Jira. It's more of a vulnerability management tool for us. All the issues PingSafe identifies flow into Jira, and we have several dashboards that provide an overview of open security issues.

We were using open-source tools. Collecting and collating the results from each tool into one dashboard was so difficult, and PingSafe solved this problem. PingSafe gives us greater insight into our cloud security posture. For example, it tells us if buckets are public or ports are open. It can also tell you if a repository is going public or if any hard-coded secrets are pushed into the source code. PingSafe will notify you when permissive users are created in the GCP environment. It offers a better UI and improved visibility compared to our open-source tools. 

PingSafe helped us identify when a developer made our repository public. It identified the issue in minutes. The repository had a few hard-coded secrets that would've caused problems for us because anybody on the internet could access those keys and exploit the systems. PingSafe caught the issue quickly. The same goes for public buckets. One of our DevOps engineers made a bucket public, and it had a lot of files in it. PingSafe was on top of it. The solution has an automated workflow that automatically blocks this kind of misconfiguration.

It has helped us reduce the number of false positives. Sometimes, you get too many false positives because the tool doesn't have enough context. For example, let's say we have a bucket that we want to be public, and CSPM tools will identify the public bucket as a vulnerability. We can make exceptions or mute the alert. PingSafe provides many ways in the UI to mark false positives or mute those tickets so that I don't get them repeatedly. I can also create tags for every issue and put all of the false positives under one tag.

The detection is almost instant. We get Slack or email notifications immediately when issues are detected, reducing our mean time to detect by more than 30 percent. Our remediation time has also improved by about 30 percent or more. We are in the fintech space, so we remedy vulnerabilities right away. The faster our detection, the faster our response. Both have significantly improved. 

PingSafe facilitates collaboration between the application security, cloud, and DevOps teams. These three teams use it, and the security team manages it. When PingSafe flags vulnerabilities, they are forwarded to DevOps for remediation. Previously, we needed to identify and report the issues, but there would be lapses in communication. Now it's a central dashboard. Anybody can look at the dashboard to see the open issues, what needs to be explored, and how the problems can be remediated. It's self-explanatory. Teams can understand the issues and descriptions, and they directly act on the recommendations.

As a frequently audited company, we value PingSafe's compliance monitoring features. They give us a report with a compliance score for how well we meet certain regulatory standards, like HIPAA. We can show our compliance as a percentage. It's also a way to show that we are serious about security.

There is a feature that provides visibility into how an attack could happen. For example, they'll highlight the system vulnerabilities and outline how an attack could be propagated. That visualization helps me prioritize remediation. If I don't know where to start, I can check to see which ones are critical. It provides an exploitability score that enables me to prioritize the issues. 

PingSafe is very easy to use, and they have a responsive support team that is available when we face any problems. We can reach out to them for tweaks, and they're always there to tell us how something works. However, most features are self-explanatory, so we don't typically need support to use the product.  

PingSafe's evidence-based reporting helps us prioritize and solve critical security issues. We have onboarded crucial projects into PingSafe, and issues related to those projects are our top priority. The new visualization features demonstrate how an attacker can enter the system, highlighting potential pathways that can be exploited. It will outline all the steps the attacker could take. With that visibility, we can ensure the perimeter is strong, and an attacker cannot enter. It reduces the risk. PingSafe helps prioritize issues based on the likelihood of exploitation. I have all the evidence of how an attacker can exploit the weaknesses in my parameter.

The proof of exploitability is helpful because we don't need to refer the issues to the security team. The DevOps guys can also use it to understand the various attack vectors and scenarios. The offensive security engine identifies any misconfigured security settings or other issues. That helps us because we are frequently audited and must report these issues to the auditors. audit heavy company. PingSafe gives me these issues in advance so I can close the vulnerabilities before we are audited. It has helped us prepare. 

Infrastructure-as-code scanning is another useful feature. In pre-production, it identifies embedded secrets and misconfigurations. We can also identify issues with Kubernetes or some privileged containers. These features all help us pass the audit. Secure IAC code isn't easily exploitable by attackers. We can be more proactive about identifying and resolving vulnerabilities. 

PingSafe is an excellent CSPM tool, but the CWPP features need to improve, and there is a scope for more application security posture management features. There aren't many ASPM solutions on the market, and existing ones are costly. I would like to see PingSafe develop into a single pane of glass for ASPM, CSPM, and CWPP. Another feature I'd like to see is runtime protection.

We have used PingSafe for more than a year.

I rate PingSafe 9 out of 10 for stability. It's a highly stable product, and we haven't had any issues with reliability. 

I rate PingSafe 9 out of 10 for scalability. Our company is growing, and we don't see any performance slowdown from onboarding multiple projects. There are also no changes to the functionality or visibility that it provides. We're confident that it can scale to the level that we want.

I rate PingSafe support 7 out of 10. Before SentinelOne acquired PingSafe, the support was excellent. I would rate it 9 out of 10. Now, I would rate it 7 because there have been some changes due to the transfer of ownership. It isn't great, but it's okay. They are reachable, but it was much easier when PingSafe was an independent company. Still, we can contact them when we need some customization, and they'll help us. 

Neutral

We previously used a mixture of manual work and open-source tools. However, these open-source solutions couldn't cover CSPM and container security. 

Deploying PingSafe was straightforward. I wasn't a part of it, but I know it was easy to deploy. 

The return on investment is difficult to quantify. We will be fined if we fall out of compliance, but I would only know how much that would cost us once that has happened. PingSafe helps us avoid those fines by proactively mitigating vulnerabilities. 

PingSafe is not very expensive compared to Prisma Cloud, but it's also not that cheap. However, because of its features, it makes sense to us as a company. It's fairly priced.

I rate PingSafe 8 out of 10. I would recommend PingSafe to any company looking for a cloud security solution. It's more than a CSPM. It provides visibility into application security vulnerabilities and container security.

PingSafe is our primary security monitoring tool used for identifying vulnerabilities and misconfiguration.

I would rate the ease of use of PingSafe eight out of ten.

PingSafe offers a variety of dashboards, but the issue dashboard is my favorite due to its clarity and simplicity.

The evidence-based reporting is great and I appreciate the details the reports provide.

The IAC scanning picks everything up and is effective. The IAC scanning is proactive.

The two biggest benefits of PingSafe are the centralized reporting dashboard for all my accounts and providers and the ability to track remediation progress.

PingSafe has helped reduce the number of false positives we receive.

PingSafe helps us manage our risk posture.

PingSafe has reduced our MTTD thanks to its comprehensive coverage and centralized reporting capabilities.

The most valuable feature of PingSafe is its integration with most of our technology stack, specifically all of our cloud platforms and ticketing software.

I wish PingSafe provided clearer solutions or remediation steps. The recommended actions aren't always specific, so it might suggest recommendations that don't apply to the particular infrastructure code I'm reviewing.

I would appreciate the ability to customize the severity levels in PingSafe as the current defaults do not meet my needs.

I have been using PingSafe for one year.

PingSafe is stable. I have not encountered any downtime.

PingSafe is highly scalable.

Technical support is usually great. While it can sometimes be a bit curt or dismissive, for the most part, getting help is easy and responses are quick.

Positive

The initial setup is easy. One person is required for the deployment.

The implementation was completed in-house.

I'm not familiar with PingSafe's standard pricing. While it seemed like a good value, I'm on a partnership plan that offers a discount in exchange for feedback. Therefore, I can't speak to the typical pricing.

I would rate PingSafe nine out of ten.

PingSafe requires monthly updates.

Preparing for PingSafe is fairly straightforward, especially if you're familiar with cloud security posture management tools. However, if this is your first time using such a tool, be prepared for a significant number of findings. PingSafe will uncover security issues that manual efforts might miss.