Status Date Fields Explained

High-level descriptions of the four status fields.

Status Date Fields Explained

Discovered By dates are populated directly from the scanners, and Ingested By dates are populated from the timestamps in RiskSense’s database. By capturing these date fields, RiskSense can provide a comprehensive view of when a vulnerability was first or last found by a scanner and first or last ingested by RiskSense.

First Discovered On

The earliest date that the scanner explicitly provides for when it identifies a vulnerability on an asset. Scanners may provide a discovery date for each vulnerability. When the scanner does not provide a valid date, the field will be blank in the Finding Detail.

Last Discovered On

The latest date that the scanner explicitly provides for when it identifies a vulnerability on an asset. The Last Discovered On can be the same date as the First Discovered On date; however, the Last Discovered On date will be updated once a later date is ingested.

First Ingested On

The earliest database timestamp on record for when RiskSense ingests a vulnerability. This can be done by manually uploading a scan file or running a connector and pulling the latest scan files into RiskSense.

Last Ingested On

The latest database timestamp on record for when RiskSense ingests a vulnerability. Timestamps are updated when pre-existing vulnerabilities in RiskSense are still present in the most recent scan file uploaded manually or by a connector.

Deprecation of Fields

Discovered On

The distinction of scanner versus RiskSense dates are better understood with the new Discovered and Ingested fields. The Discovered On field will be deprecated by the end of 2021 since the information is more clearly captured by the new fields.

Last Found On

This is the scanner provided date or the last assessment date if not provided by the scanner. The Last Found On field will be deprecated by the end of 2021 since the scanner provided dates are captured by Discovered By dates.