You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that the API would be improved if it could return a value for instances based on a vuln_id.
Based on the value shown in the vulnerabilities tab in the UI.
Current Behavior
The current configuration only return instances of vulnerabilities from scan results of individual assets/groups/or sites. These do not focus on the vulnerabilities themselves. It is achievable, but requires much more drill down logic and time-consuming Nexpose::Connection method calls which usually end up in a Timeout Error.
Possible Solution
I'm sure there is an XML value that holds this information that can to be referenced
Just an example of what I'm trying to achieve:
vulns=nsc.all_vulns.select!{ |v| v.title.downcase.include?(filter)}#total unique vulnerabilities matching the specified filtertotalvulns=vulns.sizetotalinstances=0#go through each vuln to get instances, sorted by date publishedvulns.eachdo |a|
a=nsc.vuln_details(a.id)totalinstances += **a.instances** <------ (somethinglikethiswouldbenice)end
Am trying to accomplish a date based representation of vulnerability instances without using scan data.
The text was updated successfully, but these errors were encountered:
This can be done with the new API V3 endpoint /api/3/vulnerabilities/{id}/assets where {id} is a vulnerability id string like cifs-smb-signing-disabled. Documentation for the new API is available in the security console's help menu.
Expected Behavior
I think that the API would be improved if it could return a value for instances based on a vuln_id.
Based on the value shown in the vulnerabilities tab in the UI.
Current Behavior
The current configuration only return instances of vulnerabilities from scan results of individual assets/groups/or sites. These do not focus on the vulnerabilities themselves. It is achievable, but requires much more drill down logic and time-consuming Nexpose::Connection method calls which usually end up in a Timeout Error.
Possible Solution
I'm sure there is an XML value that holds this information that can to be referenced
Just an example of what I'm trying to achieve:
Am trying to accomplish a date based representation of vulnerability instances without using scan data.
The text was updated successfully, but these errors were encountered: