-
-
Notifications
You must be signed in to change notification settings - Fork 233
Add a basic model for Known Exploited Vulnerabilities #1422
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
Conversation
bf982a0
to
2cf5e72
Compare
I think we need a new tab for this, @DennisClark what's your initial thoughts on this ? |
5d90bdc
to
0a2d084
Compare
|
||
@property | ||
def interesting_advisories(self) -> QuerySet: | ||
return [Advisory.objects.all()[0]] |
There was a problem hiding this comment.
Choose a reason for hiding this 8000 comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if this is the right way to just run the improver
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ziadhany Thanks ++
Looking good! see minor nits for your consideration.
Also, please add some tests.
Add a Kev test & function docstrings Change the kev model ( known_ransomware_campaign_use from integer choices to boolean ) Add kev to api Access the vulnerability directly from Alias Add a tooltips and edit kev table Add a kev in a separate tab Solve migration conflict Add a basic improver squash migration files Add a basic Known Exploited Vulnerabilities model Signed-off-by: ziadhany <ziadhany2016@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ziadhany, Merging!
Issue #1028