-
Notifications
You must be signed in to change notification settings - Fork 26
"lumin" command
Casey Reid edited this page Jul 17, 2021
·
5 revisions
Adjusting Asset Criticality using context is a key component of a risk based vulnerability management program. Since Tagging is the foundation of grouping assets, it makes since to use these groupings to apply Asset criticality.
- --acr --> The new ACR value (1-10)
- --c --> The Tag Category to use
- --v --> The Tag value to use
- --note --> Justification for ACR change
- -business', '-b' Add Business Critical To ACR Change Reason(s)")
- -compliance', '-c' Add Compliance To ACR Change Reason(s)")
- -mitigation', '-m' Add Mitigation Controls To ACR Change Reason(s)")
- -development', '-d' Add Development To ACR Change Reason(s)")
Tag your assets with "NO:UPDATE" if you don't want to be affected by bulk ACR changes
Category = NO
Value = UPDATE
navi lumin --acr 10 --c "Applications" --v "Core Business" --note "Main application"
navi lumin --acr 9 --c "Corporate Apps" --v "Jira" -d
navi lumin --acr 8 --c "Corporate Apps" --v "Confluence" -development -b -c