-
Notifications
You must be signed in to change notification settings - Fork 179
Open
Description
I observed in the JSON file (used for KQL request) the "CreationTimestamp" field in the "KnowVulnerableSamples" main section tell: "2022-03-28 02:31:12"
I was thinking we was using a old reference file to validate our known vulnerable signed drivers, but it seem you had injected recent driver (more recent than 2022). It's hard to confirm in the reference file if this one is keep up to date. The only trigger is to keep a look in GitHub page the modification date.
Please, if this value is coming from outside data or for compatibility, could you add a somewhat "CreationTimestamp" value and/or add a serialized version number in the JSON file main header section when the file is re-generated to easly follow the versioning ?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels