Integrating Vulnerability Data with an Identity Services Framework
With Tenable’s Nessus, security and compliance teams can audit and inventory devices and software to identify what is malicious, abnormal or out-of-compliance. However, do you ever need to pinpoint the offending system or software to its user?
At Tenable, we’ve heard from customers who are looking for a unified framework that enables multi-vendor, cross-platform network system collaboration among IT infrastructure, network policy, identity and access management, and other IT operations.
For example, once a vulnerable system is identified, possible next steps are to:
- Track the offending users and inform them to fix/update the device.
- Initiate action to modify user behavior to avoid future security issues.
- Update corporate security policies to prevent future occurrences.
This is made possible by implementing an identity services framework that a) Adds user context to Nessus to get more granularity to scan data, b) Provides a consolidated view of vulnerability event, identity, and device data for prioritization of vulnerability, and c) Identifies which vulnerabilities require immediate action and provide this context to deployed devices.
Such an identity services framework can offer the following benefits:
- Reduce time to isolate issues across multiple technologies
- Obtain accurate results by obtaining additional context from other devices
- Expedite response and remediation to security and compliance issues
We believe this is just one example of what is needed in the industry and are planning on integrating with a leading platform in the network policy space, Cisco Identity Services Engine (ISE), to serve these use cases.
What about you? Forward your thoughts to me at [email protected] on the following:
- Do you have any need to pinpoint the device or software vulnerability back to its user or owner?
- Does integrating with a product like Cisco ISE make sense for your systems?
- What other identity services products do you use? What would you like Nessus to integrate with?
We’d love to hear from you on your thoughts, challenges and recommendations…
Related Articles
Cybersecurity Snapshot: 6 Best Practices for Implementing AI Securely and Ethically
May 31, 2024Like many organizations, yours is likely using AI – or at least thinking about deploying it soon. But how can you ensure you use it securely, responsibly, ethically and in compliance with regulations? Check out best practices, guidelines and tips in this special edition of the Tenable Cybersecurity Snapshot!
Taking IBM QRadar SIEM One Step Further Using Tenable.ad
September 30, 2021If you can't continuously monitor Active Directory, it's impossible to achieve full visibility into your evolving attack surface. Here's how combining Tenable.ad with IBM QRadar can help. It's no sec...
Active Directory Under Attack: Five Eyes Guidance Targets Crucial Security Gaps
November 21, 2024A landmark global report from cybersecurity agencies emphasizes 17 attack techniques against Microsoft Active Directory and cautions organizations to step up protections. In the first of our two-part series, we offer five steps you can take today to shore up your AD defenses.
Five Cyber Agencies Sound Alarm About Active Directory Attacks: Beyond the Basics
November 21, 2024A landmark global report emphasizes 17 attack techniques against Microsoft Active Directory and cautions organizations to step up protections. In the second of our two-part series, we take you beyond the basics to highlight three key areas to focus on.
Volt Typhoon: What State and Local Government Officials Need to Know
November 19, 2024Increased activity from the state-sponsored threat group Volt Typhoon raises concerns about the cybersecurity of U.S. critical infrastructure. Here’s how you can identify potential exposures and attack paths.
- Integrations
- Nessus