You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both of these measures are based on the frequency of the scan of the approved vs unapproved software which seems to be based on the process (scanning frequency) vs the outcome (unapproved software are removed).
An alternative method focused on the outcome, which could also accommodate more of the "near real time" data collection could be a comparison between "Initial Discovery DateTime" - "Last Seen DateTime" of unapproved software. This would just require that a date time stamp be added to any asset whenever they're scanned and added to the inventory.
Recommendation
Change the measure from being focused on the Scan Frequency to the difference between Initial Discovery and Last Seen Datetime. Which means the measure would then be based on how many of those fall within the "acceptable" range.
The text was updated successfully, but these errors were encountered:
Controls
Control 1.6
Control 2.6
Comment
Both of these measures are based on the frequency of the scan of the approved vs unapproved software which seems to be based on the process (scanning frequency) vs the outcome (unapproved software are removed).
An alternative method focused on the outcome, which could also accommodate more of the "near real time" data collection could be a comparison between
"Initial Discovery DateTime" - "Last Seen DateTime"
of unapproved software. This would just require that a date time stamp be added to any asset whenever they're scanned and added to the inventory.Recommendation
Change the measure from being focused on the Scan Frequency to the difference between Initial Discovery and Last Seen Datetime. Which means the measure would then be based on how many of those fall within the "acceptable" range.
The text was updated successfully, but these errors were encountered: