-
|
The finding documentation states that the I assume this depends on the scanner, and there is no easy way to get to that information. Wouldn't it be helpful to get an attribute |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Yup totally agree that The scan currently doesn't really have a |
Beta Was this translation helpful? Give feedback.
-
|
Would it make sense to add this |
Beta Was this translation helpful? Give feedback.
-
|
The creation timestamp is already on over scan. |
Beta Was this translation helpful? Give feedback.
-
|
The second one. To create something like a |
Beta Was this translation helpful? Give feedback.
-
|
Turned this into a feature request #1109 :) |
Beta Was this translation helpful? Give feedback.
Yup totally agree that
identified_atis usually the more interesting, but as you said we can only really set it if the scanner / the scanners result format includes it.The scan currently doesn't really have a
started_attimestamp, but all kubernetes objects have acreationTimestampset. (metadata.creationTimestamp). This isn't necessarily the timestamp of the actual start of the scan as it might have been in a pending state if the cluster was currently unable to execute it, but it is usually relativly close.