Code Monkey home page Code Monkey logo

Comments (4)

hammackj avatar hammackj commented on May 31, 2024

I am adding host/plugin black listing soon, right now you have to tailor the queries to exclude specific IPs/plugins

i have a script i run on the dataset before i generate reports to do it something like this

downgrade_vulns = [41028, 10264]
#41028 = snmp public
#10264 = snmp default
#

downgrade_vulns.each do |plugin_id|
    items = Item.where(:plugin_id => plugin_id).all
    items.each do |item|
        item.severity = 1
        item.save
    end 
end

for lowering rating on plugins that are poorly reported.

Only solution I have for now, I started work on black listing but it is not done yet. I am waiting for nessus 5 to release the next version.

On Jan 4, 2012, at 10:23 AM, emory wrote:

Ignoring a plugin

Is there a way to ignore a list/array of plugin IDs at report generation or in a template?

Ignoring an ip address

Is there a way to ignore a list/array of IP addresses at report generation or in a template?


Reply to this email directly or view it on GitHub:
#47

from risu.

ebdavison avatar ebdavison commented on May 31, 2024

I think this is an interesting workaround. I am concerned (as I have the same need) that if I do this then I lose the original severity and my boss and client will want this preserved somehow.

How hard would it be to just add a new column with called "ignore" that can be set to 1 to ignore and defaults to 0? Then the query engines could just add a new "item.ignore = 0" clause.

from risu.

hammackj avatar hammackj commented on May 31, 2024

That's an interesting idea. I will see what I can do to get something usable.

Sent from my Phone

On Jan 9, 2012, at 3:19 PM, ebdavison
[email protected]
wrote:

I think this is an interesting workaround. I am concerned (as I have the same need) that if I do this then I lose the original severity and my boss and client will want this preserved somehow.

How hard would it be to just add a new column with called "ignore" that can be set to 1 to ignore and defaults to 0? Then the query engines could just add a new "item.ignore = 0" clause.


Reply to this email directly or view it on GitHub:
#47 (comment)

from risu.

hammackj avatar hammackj commented on May 31, 2024

I will be added a more complex filtering option in 1.5, this should take care of these issues.

from risu.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.