What is your primary use case for Tenable SC?

The primary use cases are vulnerability management and dashboard creation. I utilize it to exhibit the current security posture to higher management, prioritize which paths to fix first, and identify vulnerabilities. Additionally, I escalate issues to management based on their criticality and business rating.

It's a management tool. We are more scalable with the Tenable.io product. They are a security vendor with more than one cloud level. Now there are multiple products in my area.

I use the solution in my company for vulnerability risk assessment, and we are quite happy with it.

We use Tenable Security Center for vulnerability assessment purposes within our security infrastructure. The solution helps identify management-related issues and automatically forwards the ticket to our stakeholders, as well as an auto-alert mechanism. Additionally, we have integrated it with our SI solution. The primary use case involves automated scheduled scans. We have established an asset inventory, and there is a scheduled quarterly automated scan. This process sends the results, thereby reducing manual tasks. The more automation we implement, the fewer errors occur, resulting in a faster and more efficient process. We also use it for continuous network monitoring. We scan network devices such as Cisco routers, load balancers, and WAN devices. If any suspicious network activity arises, the system saves the results. Our organization also uses Power BI. There are a lot of scripts that are already integrated to check compliance within the organization. We aim for at least 75% of the benchmark. Tenable's solution assists in representing the level of compliance achieved, whether it be 70%, 80%, 90%, or 95%. We have installed agents on various server types, and adding them to the scan does not require manual credential entry each time. The solution provides comprehensive results on the dashboard for each service by simply clicking on the play button.

We use the product to scan threats and conduct risk assessments for NCA.

We work as System Integrators and my team has experience in using Tenable Security Center. We provide solutions to work for various customers in BFSI, Telcos, and the Government sector. We use this solution mainly for vulnerability assessment and management. With the scanning feature set, we do the reporting and provide easy operation and implementation for our customers.

We use the product as a security tool for VMs and web applications.

We use it to scan both our workstations and servers for vulnerabilities. This includes vulnerabilities related to software, operating systems, and package vulnerabilities. It helps us gain an overview of our organization's security status, which in turn guides our patching strategies and decision-making. We use agents for scanning and authenticated logins, but we do not utilize the scanner part that performs web scanning.

Our customers use the product for scanning their network for vulnerabilities.

We use Tenable.sc to conduct vulnerability scanning for our networks, and applications, and for the data protection we need in our environment. We are customers of Tenable and I'm the assistant manager of network security.

The tool helps with vulnerability assessment and vulnerability management.

Tenable.sc customers use when they need a complete in-house vulnerability management environment. It enables you to identify the applications and infrastructure within your organization, giving you greater control over your environment. Tenable.sc isn't on the cloud. Tenable.sc is deployed on a private cloud and used when regulations prevent keeping things on a public cloud. Two of my customers are using it currently.

I primarily use Tenable.sc to search availability and for our workstation server and data center.

In our organization, we only use Nessus for vulnerability assessment. We are using Tenable.sc and Nessus as threat scanners.

We primarily use the solution for vulnerability scanning across the network . A few months back, I conducted a training on Tenable SecurityCenter for a Reputed Bank. I had to teach the Usage and features and then show them how the scan things work and how results can help analyze and report. also helped developing some use case like Scheduling scan and email that to specific users for mitigation, Generating Alert for particular level of vulnerability etc.

I primarily use Tenable for scanning and reporting.

We use Tenable SC for internal vulnerability scans with agents, and agentless scanning in the cloud. For example, we're scanning the AMI in the cloud and making it part of the base image.

I primarily use Tenable SC for vulnerability management i.e. to detect vulnerabilities in servers, workstations, and some IoT, produce, prioritize, and validate a mitigation strategy, and keep the mitigation on track so the CISO can detect changes in the posture.

I am using Tenable SC for vulnerability management and for the dashboards.

I am using Tenable SC to detect vulnerabilities, and we are in the process of testing the solution.

We use Tenable SC for compliance and vulnerability scans. We are fully updated in terms of the version, and we have its latest version.

In my previous company, we were using both Tenable IO and Tenable SC. We had the on-prem and the cloud versions. IO was a cloud version, and SC was on-prem. In my new company, they do use Tenable, but I'm not part of that team. They have the latest version.

Tenable SC can be used in any company for vulnerability management life cycle.

We had a requirement to connect multiple branches into one console. We installed Nessus at multiple locations and then connected Nessus. We did the service scan and got the report on the central site with Tenable SC.

At work we use the enterprise version of Tenable, Tenable.io, and I also use Tenable.sc — which I refer to as SecurityCenter — for local scanning. I use Tenable SecurityCenter every day to scan our entire environment for vulnerabilities. I use a local license during the discovery process for penetration testing. So I'll do an en masse scan, and then also do a scan with Tenable to scan for IPs and vulnerabilities. User-wise, with Tenable SecurityCenter, there's different roles. We have security analysts, admin, etc. I'd say there's probably four or five different roles from people that can just go in and view. Security analysts can upload manual scans and create dashboards and download reports. Then administrators can create accounts, assign roles and responsibilities, and things like that.

I'm a pre-sales engineer and we are resellers of Tenable.

We are a reseller and Tenable SC is one of the products that we implement for our clients. The primary use case is to check for compliance against a specific framework, like NIST, CIS, or something similar. Tenable will check compliance on the assets against that specific framework and give that visibility to the technical staff, top management, and the risk management team. In turn, this will enable them to evaluate the risk that they are facing for non-compliance issues. The second use case is helping the technical staff that handles updates and upgrades to the operating system. It means that they have the most urgent upgrades that they need to cover the high-risk vulnerabilities that can be found and exploited. Beyond this, Tenable SC assists with malware detection and similar functionality.

Our primary use case is for vulnerability assessment of our internal network.

Our primary use case is compliance for our audits, for our customers. We were exposed in that we were not meeting contractual obligations. We are monitoring our infrastructure: servers, switches, storage, routers, SAN storage, operating systems, and applications to the extent that the tool is able to see into them. We use it to hit the high ones like Adobe or Microsoft Office and the like. Some of the more niche products that we use may not be in their inventory of vulnerabilities.

I use this solution to perform vulnerability assessments and then patch my systems using third-party tools. The vulnerability scan is pretty fast and once you give it the right access privileges on the target system, you get very clear and precise details of the vulnerabilities.

Vulnerability assessment and compliance auditing are our primary use cases. That includes baseline configuration scanning. We use it to protect everything in the enterprise environment: servers, workstations, pretty much all operating systems, networking gear. We are doing cloud and we are doing some IOT. We are not using their web application scanning tool.

I'm the one who scans and performs assessments on clinical and medical equipment in our environment. I manage the clinical endpoint devices: MRI systems, bedside monitoring, Alaris pumps, fusion pumps, CTUs, EEGs, EKGs, wireless defibrillators, and a lot of IP cameras that are part of operation room labs. My colleague handles all the regular enterprise IT, database servers, etc. From a scanning standpoint, I do everything from discovery scanning to full-credential auditing and anything and everything in between. That's just for the medical space in a 24/7 production medical environment. We're also using a bit of the Passive Vulnerability Scanner and, eventually, I want to get to using the agents, but we haven't gotten to that stage yet.

The primary use case is to perform vulnerability assessments across the entire network.

I primarily use this solution for vulnerability assessment on the assets that we have. This includes servers, network equipment, appliances, routers, firewalls, and switches.

Basically it reviews our threat landscape vulnerability. So, we just want to be sure that we check compliance in terms of our configuration and compliance to our policies. But, the key is to make sure that we are not exposed to non-vulnerabilities that can be exploited. So, it's more of just securing our threat landscape.

I use SecurityCenter currently to investigate daily network security events from reports I receive. Our network support team uses it to track, manage, and remediate system vulnerabilities. It works well for the latter, not so much for the former.