The most recent content from our members.
Hi Why only vendors C or J ? The links are to the same vulnerability database that has all other... Multivendors support is king for NCM
Was noticing that no new recent vulnerabilities are showing up in NCM, so I went to check things out. In my Firmware Vulnerability Settings page, I'm getting the following errors - URL "http://static.nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-recent.xml" is currently inaccessible. URL…
I'd like to see NCM being integrated into the EOC. - Running centralizes Jobs over multiple sites - Running centralizes Compliance Reports over multiple sites - Running Config Snippets over multiple sites - Running Firmware-Update Jobs over multiple sites - Manage Firmware Vulnerabilities over multiple sites - ...
We just can't have anything nice, now can we? Oh, well. We knew there would be new vulnerabilities and ransomware attacks in 2018. However, this time hardware is the culprit, and patching is not going to be a cure-all for the situation. Consider yourself warned: expect more slowdowns in 2018. Stop and think about this for…
With the information from the vulnerability is there a way SW will let me know that switch is at risk or would I just have to look at the text? I ran the latest updates on 3 of my switches and they are still showing at risk. If there a way I set the vulnerabilities to scan my switches each to and send me a report of which…
Does anyone use this NCM for network vulnerabilities? How or where does it get information on if a firmware or OS has a vulnerability? How does this compare to Nessus, OpenVas or other Security programs when it comes to vulnerbilities? By watching the video I like how you can manage the switches all in one rather than…
Hi, We're about to start using solarwinds NCM 7.5.1 for vulnerability management but I have a few questions I'm hoping someone who already uses this can help out with. 1) Is there still an issue with false positives because NCM doesn't detect minor IOS versions, this issue may make it a bit of a non starter, I really don't…
Within NCM (7.4) under Vulnerability Search Settings, I get the following error when running the matching logic. Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation Is there a known solution for this? Any assistance would be greatly appreciated.
I like the Firmware Vulnerabilities section in NCM: But when I hover over any entry under the Target Nodes, I don't have the option to click on anything to list the affected devices: I'd like NCM to open up a report of the vulnerable Target Nodes for each row. Is that feature already present somewhere and I'm missing it?…
It looks like you're new here. Sign in or register to get started.