Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Usage of published_timestamp #2

Open
mokaddem opened this issue Nov 14, 2024 · 1 comment
Open

Usage of published_timestamp #2

mokaddem opened this issue Nov 14, 2024 · 1 comment

Comments

@mokaddem
Copy link
Contributor

https://github.com/MISP/VulnerabilityLookupSighting/blob/cf3a1cd89b8416685942a72612f800c3308a981e/vulnerabilitylookupsighting/publish.py#L99

I'd rather use published_timestamp to only feed data that has been published. Generally, published data should be considered with a higher confidence level than non-published one.

@adulau
Copy link
Member

adulau commented Nov 16, 2024

I would tend to agree with you if we were expecting data to published. In many cases, there are many automatic event adding vulnerability attributes with a timestamp which is the closer timestamp to the actual sighting. Maybe we could have the option in the tool to decide what to take depending of the use-case.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants