Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scanning Frequency vs Discovered Timestamp #2

Open
planglois925 opened this issue Jul 2, 2019 · 2 comments
Open

Scanning Frequency vs Discovered Timestamp #2

planglois925 opened this issue Jul 2, 2019 · 2 comments

Comments

@planglois925
Copy link

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.

@ginger-anderson
Copy link
Contributor

PL,

Can you please verify which Safeguards you're referring to?

v/r
Ginger

@ginger-anderson
Copy link
Contributor

in hindsight i think these are for Controls v7.1 or CAS v1.0?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants