Skip to content

Keep drivers.json information up to date (version) #236

@ggbce

Description

@ggbce

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 ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions