Skip to content

"lumin" command

Jump to bottom
Casey Reid edited this page Aug 8, 2021 · 5 revisions

Purpose

Asset Criticality is one of the most important aspects of any Risk Based vulnerability management program. In Lumin, your Asset Criticality Score(ACR) is determined automatically without context. Since the ACR calculation lacks network and business context it's important you have a scalable way to adjust the ACR value on your most important assets.

Command Options

Bulk Adjust ACRs based on a Tag - navi lumin

  • --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)")

Note - ACR Exceptions?

There are some Assets that should be updated manually in special cases. The time it takes to update assets manually is worth preventing the hard work from being overwritten by a mistake or a bulk update to a group of tags. To avoid this you can tag your assets with "NO:UPDATE" to protect them from bulk ACR changes using navi.

Tag your assets with "NO:UPDATE" if you don't want to be affected by bulk ACR changes

Category = NO
Value = UPDATE

Examples

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
Clone this wiki locally