-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List of NSEs #3
Comments
Actually, it seems like you should be maintaining the NSEs in your own git repo. The point of this service (as i understand it) is that you verify that the NSE works and is not malicious. If you just distribute links, the owner of the link could change the NSE into something malicious after the fact. You need a point-in-time snapshot of the code that your team has vetted. |
That's a link to an external team (nccgroup)'s NSEs. They can change the contents of that link at any time, so I'm not sure what the point of SME is in this context? IMO a service like this should seek to compile vetted NSEs into a single location so someone could check out ONE git repo and then use those NSEs in their scanning. |
Agreed this is very confusing. Great initative but without centrally storing or managing these scripts whats the point. |
Are you planning on offering/linking to/distributing a list of the NSEs somewhere or is the link only going in your blog?
The text was updated successfully, but these errors were encountered: