What is your primary use case for PingSafe?

As an engineer, I'm using the solution for managing infrastructure and security posture management. It's primarily for cloud infrastructure, data center infrastructure, and security posture management, but it also provides other capabilities such as infrastructure-as-code scanning and detects hardcoded secrets in the source code, including for EKS, DevOps tools, etc.

As a Security Engineer, I use the SentinelOne Singularity Cloud Security primarily for cloud security posture management. Additionally, I benefit from features such as attack visualization and evidence-based reporting, which help proactively mitigate vulnerabilities, reducing compliance risk and audit pressures. Infrastructure as code scanning is a valuable capability, and while we primarily use the SentinelOne Singularity Cloud Security for cloud security posture management, we also leverage its infrastructure as code scanning, which is vital given the implications of hard-coded secrets in our source code. I personally use the SentinelOne Singularity Cloud Security daily, and I have noticed that the dashboard occasionally gets stuck, potentially due to internet issues, suggesting it could benefit from enhancements to be more robust and smoother.

I am working as an application developer, and SentinelOne Singularity Cloud Security plays a role in the cloud infrastructure where my application is deployed. It provides me with alerts and ensures that I follow best practices in everything.

I personally use this for infrastructure security purposes because it provides alerts for any threat detection or vulnerability detection in my infrastructure. This ensures that these issues are addressed promptly.

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.

I use SentinelOne Singularity Cloud Security to detect vulnerabilities and threats. I use SentinelOne Singularity Cloud Security for continuous monitoring, as it provides constant threat detection with minimal impact on our system's performance compared to other endpoint security solutions.

We use SentinelOne Singularity Cloud Security to maintain security best practices. The platform alerts us to security issues, ranging from low to critical severity, based on our infrastructure. We chose SentinelOne Singularity Cloud Security for its targeted vulnerability recommendations and best practice guidance, which allow us to address alerts effectively and maintain a secure infrastructure.

I use SentinelOne for the traffic flow in my customer's account.

Working in a highly regulated space with stringent security requirements for money movement necessitates robust security measures. SentinelOne Cloud Security effectively secures our workloads, providing peace of mind and significantly reducing stress by addressing both security and regulatory needs.

As a senior IT security director, I oversee the governance and guidance of security deployments, including the development and implementation of use cases. My primary guiding principle, which is shared by my team, is to prioritize visibility. This translates into our use of SentinelOne Singularity Cloud Security to gain comprehensive visibility across our hybrid infrastructure including cloud, on-premises, and end-user workstations. Ultimately, visibility is the main driver of our security strategy.

Singularity Cloud Security helps my organization achieve its goals by providing protection and cloud security posture management for our AWS organization. It offers detailed visibility into any misconfigurations, threats, or other items that come through from the AWS services, and enables my engineers to easily find and get information on how to triage those items.

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.

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.

We are a channel partner of SentinelOne in Brazil. We have a distributor that we use to sell SentinelOne. We are very happy and very proud to represent SentinelOne here.

To address our client's infrastructure vulnerabilities, we implemented Singularity Cloud Security by SentinelOne. This security solution effectively identifies and resolves security issues, streamlining the process of ensuring our clients' infrastructure remains secure. For the past year and a half, we've been managing AWS infrastructure for a client, originally using basic AWS security tools. While these provided a workable solution, Singularity Cloud Security offered a significant advantage. It prioritizes vulnerabilities by severity, high, medium, or low, allowing us to focus on the most critical issues first. This centralized tool gathers information and displays all details on a single dashboard, significantly reducing manual work. The dashboard helps us identify problems, understand their meaning and potential impact, and follow clear resolution steps. This streamlined process enables us to address security concerns quickly and effectively, ultimately enhancing our client's infrastructure security.

We use SentinelOne's Singularity Cloud Security as our Cloud Security Posture Management solution, to proactively identify vulnerabilities within our cloud configurations. Security alerts generated by the platform are then forwarded to our mitigation team for prompt remediation.

SentinelOne's Singularity Cloud Security streamlines our cloud security by minimizing false positives. Previously, we were inundated with alerts from various sources like AWS Cloud and Microsoft Defender, making it difficult to distinguish real threats. Now, with Singularity's cloud-native security, I can confidently address genuine threats and efficiently alert my team about relevant Defender policies. We implemented Singularity Cloud Security to reduce the number of false positive alerts we were receiving.

We have one client, and we need a portal to manage security. We use Singularity to provide security information and identify vulnerabilities or malicious scripts that need to be fixed. It also provides recommendations about each of the vulnerabilities that are helpful.

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.

Our infrastructure is on AWS and we integrate PingSafe with our enterprise accounts to identify misconfiguration on the Cloud.

Our cloud security posture is managed with PingSafe, a tool that identifies and highlights potential security weaknesses in our systems.

We leverage PingSafe for cloud security posture management, which continuously monitors our cloud configuration for vulnerabilities. When PingSafe detects an issue, we prioritize the alert from our cloud-native security solution and route it directly to the DevOps team for remediation. We have PingSafe deployed on AWS, Azure, and GCP.

Our cloud security posture management is handled by PingSafe. To prevent cloud misconfigurations and developer code errors, we implemented PingSafe as a safeguard. PingSafe is deployed as a SaaS.

We use PingSafe for cloud security posture management. It's used for AWS use cases to prevent leaked credentials and unauthorized access to our S3 buckets.

We have multiple applications in our AWS cloud environment. We have a private environment, and we do not disclose it to the Internet. We have configured multiple security alerts, such as for any incoming traffic from a public IP address. We have also set up PingSafe alerts for key rotation of security credentials for the accounts.

We use PingSafe to improve our security posture through evidence-based alerts by detecting and mitigating vulnerabilities. We sought a CSPM solution that could be configured to adhere to the security policies of our required integrations. PingSafe stood out as a strong candidate due to its compliance with industry standards like ISO and its ability to provide valuable security insights. PingSafe is a SaaS solution.

My company is trying to get an ISO certification by the second quarter of 2024, so we have been resolving certain security issues for the past year. I use the solution in my company, where we have alerts coming from PingSafe, especially if any security threats are there. Our company's primary concern in using the tool is to get the ISO certification. My company wants to get our infrastructure to meet ISO standards so that there won't be any issues while getting ISO certification.

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.

We use the solution for security purposes. We deploy it into our infrastructure in the cloud. We want to make sure that all everything is secure, for example,if APIs are getting accessed, that it's by the right people. It's a security hub for us.

Our infrastructure utilizes a combination of cloud solutions and Kubernetes for container orchestration. To ensure the security of these environments, we leverage PingSafe. This platform proactively identifies and remediates vulnerabilities within our cloud deployments. We use PingSafe, which is integrated with our cloud environment. This allows us to receive notifications from PingSafe directly in our Slack channels, according to the notification settings we have configured. We prioritize these alerts and take appropriate actions based on their urgency. To improve our cloud security posture and achieve best practices, we implemented PingSafe. This security tool helps us identify and address vulnerabilities within our cloud environment.

As a financial institution, we rely on PingSafe as our single source of truth for both CSVM and CWPP data. PingSafe provides us with essential security benchmarks, including those for Kubernetes deployments and CSVMs. It also allows us to monitor our overall cloud security posture and identify vulnerabilities for remediation. PingSafe serves as a centralized platform for all our cloud security metrics.

We primarily use PingSafe for compliance purposes because we work with banks and the fintech industry, so we must follow some standards like PCI DSS.

We use the tool for cloud security management. We check the vulnerabilities in the cloud during the configuration phase using PingSafe. We check how many cloud assets are being covered and how many issues have been identified from multiple cloud assets. We check different types of issues. We look into cloud network configuration, Offensive Security, Kubernetes security, and vulnerabilities. We also use the ThreatWatch option to check for active attacks happening worldwide. We can also check compliance, analytics, and asset inventory. We use the tool in multiple locations.

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.

We use PingSafe for our AWS cloud used in my project and to check the account's vulnerabilities.

We use PingSafe to secure our IT infrastructure and fix vulnerabilities. For example, it tells us if our resources have been inappropriately made public. We provision our infrastructure on AWS and GitHub. PingSafe finds vulnerabilities across our entire network and secrets in our GitHub repositories. It also helps us manage our cloud configurations and security groups. PingSafe is integrated with Metabolic, Opsgenie, and Slack for notifications. It's also integrated with our security team. They are using a script to correlate the data from SysTrack.

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

We use PingSafe to identify threats and vulnerabilities in our AWS accounts and the compute resources that are hosted on those cloud accounts. We implemented PingSafe to address network-related issues, such as communication between individual components (part-to-part or node communication). PingSafe's Graph Explorer feature also helped us understand the overall network landscape, including the attack surface. This feature allows us to discover and explore various components within our AWS environment. In essence, PingSafe helped us identify how different networks connect and how microservices within our system interact with each other.

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 use PingSafe as our CSPM. Integrated with our environment, PingSafe scans for vulnerabilities and recommends remediation. We implemented PingSafe to monitor our cloud security for vulnerabilities in the configuration.

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.

We use it in different ways. The number one use case is related to vulnerabilities, which includes cloud misconfiguration, the Offensive Security Engine, and the management screen itself. That is our primary use case. Then comes the graphical representation of interfaces, and the third use case is the inventory that it allows, which is very nice. By implementing this solution, we wanted to watch the security vulnerabilities in our organization. We wanted to watch them in the code that gets checked in. We wanted the latest and refreshed list of vulnerabilities in, for example, Log4j or any other software to be highlighted. PingSafe keeps updating its database and highlighting any issues.

We have onboarded multiple accounts from our organization. We have onboarded Azure accounts, and we have also onboarded GCP accounts. We are using the vulnerability management feature, and we are also using the offensive security feature. We are planning to use IaC in a couple of months.

We did a PoC, but we did not go ahead with PingSafe. It is currently on a test cluster. It is not in production. We were looking for a CSPM tool to monitor all of our AWS resources. We also wanted it to give us an alert in the case of a vulnerability. If, for example, a zero-day vulnerability is there, it should scan all of our tools.

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 are a security-based company. We use PingSafe to put our data planes on it. We have a cloud setup, and we have integrated PingSafe into our environment. It checks for any audit or security-related issues. By implementing PingSafe, we wanted a centralized solution. We have many AWS accounts to manage, so we wanted a single dashboard with analytics. We wanted to be able to view and monitor everything at once. We also wanted to customize the rules on which we wanted the alerts to be set up. PingSafe was a better option for our use case.

We have multiple AWS accounts and we use it for our products and deployments, et cetera, and they are being monitored by PingSafe for best practices and good security. In the past, we've had code exposed to the internet, and PingSafe has been able to catch such instances. Basically, it is for security and monitoring purposes.

We use the solution for security posture management. It's a safeguard for our cloud. It helps flag misconfiguration or any kind of vulnerability. There are also remediation capabilities, although we're only subscribed to alerts.

We use the solution for security and monitoring. It helps maintain compliance standards. Multiple policies can be mapped and evaluated and alerts can trigger your attention.

We use the solution for monitoring the security of our infrastructure. It helps us identify all the vulnerabilities.

We mainly use PingSafe for cloud security.

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.

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.

We use PingSafe as a cloud security posture management tool. PingSafe is integrated with our GCP, Azure, and AWS accounts. It will identify all the misconfigurations and security issues on all these cloud platforms and alert us. In addition to the CSPM capabilities, PingSafe has several other features like vulnerability management, container security, Kubernetes security posture management, and secret scanning All of these features are bundled inside PingSafe. It combines all the telemetry from the cloud, containers, and the Kubernetes platform. The vulnerability scanners are connected to the registries and give us a holistic picture of what else is vulnerable versus all the dummy data others would give.

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.

My company does utility energy disaggregation. We use PingSafe for vulnerability management and to limit our exposure to attacks. PingSafe scans our AWS cloud environment and provides detailed analysis. It can identify enabled ports or anything that isn't completely integrated with our security. PingSafe gives us the details, and we only need to follow their instructions to ensure the vulnerabilities are fixed. My company handles a lot of customer data for US and European clients. GDPR and SOC 2 standards require that we are almost completely free of vulnerabilities. We also have a PingSafe safety score and report that we can provide to our customers. PingSafe is integrated with our AWS environment, and it monitors a few customer-critical applications. Two people at my company use PingSafe. I am on the IT security side, and another person from the platform security side uses it.

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.

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.

The company purchased PingSafe primarily for container security and IoC scanning. We also were looking into image scanning for Docker components. Now, we have enabled secret scanning and the Cisco pipeline as well. We are mostly dealing with code-level security issues the organization might have. There are issues in TerraForm and whatever else we see in our DevOps pipeline.

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

We use PingSafe as our Cloud Security Posture Management tool.

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.

We use PingSafe to identify cloud security misconfigurations, ensuring compliance with Cloud Security Posture Management and Cloud Workload Protection Platform best practices, as well as relevant regulations in India. We also integrate PingSafe with our GitHub repositories that store our hard-coded secrets.

The solution closes the gaps in cloud infrastructure. We can find any gaps that exist and what possible attack factors may be. Everything is gathered together and removed. So we primarily use it for cloud security assessment.

In its all-in-one aspect, we started with Cloud Security Posture Management at the beginning and then added the Offensive Security Engine, Vulnerability Management of CDR. We also use it for compliance. By implementing this solution, we wanted an alerting mechanism and detection of any deviation from our current configuration. We also wanted visibility into Kubernetes and AWS cloud. We wanted something that continuously monitors and gives us updates so that we can take action.

PingSafe offers a variety of functionalities, including cloud configuration assessment and detailed misconfiguration reports. It automates vulnerability scanning, saving us time and effort. Additionally, PingSafe allows us to filter compliance-related findings and provides consolidated reports for a comprehensive view. Furthermore, PingSafe can conduct customized posture management research for Cloud Posture Management initiatives. This eliminates the need for complex, independent research. Finally, PingSafe helps us understand our readiness for specific security certifications.

PingSafe is a cloud posture management solution. Initially, it focused on helping us understand and assess our compliance posture and cloud configuration for workloads, etc. There are three key use cases for PingSafe: * Continuous Configuration Monitoring: This ensures 24/7 oversight of configurations and identifies any issues as they arise. * Asset Visibility: Gain immediate visibility of all cloud assets upon deployment and ensure they are properly tracked within the system. * Container Security: Assess vulnerabilities in Docker clusters and other containerized environments based on compliance requirements.

We currently use PingSafe 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 PingSafe 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 PingSafe was a new entrant in the market, we wanted to evaluate its capabilities. Fortunately, PingSafe's unique features and policies proved valuable. For instance, PingSafe 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.

We are using PingSafe for cloud posture management and cloud workload protection. Apart from this, it also provides alerts from infrastructure as code. If the tool finds any misconfiguration, it triggers that as an alert, and that gets collected in Jira.

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

It's a cloud-based SaaS tool. It's a cloud security partnership management tool. It gives you an overview of misconfigurations, Kubernetes security, Docker security, vulnerability scanning, and secret scanning.

PingSafe offers the flexibility to create a customized solution that fits our specific needs. It's a comprehensive tool encompassing the central elements—PSC, PPP, and more.