SecurityInsight settings · Settings > Collection scope & limits
Azure types not treated as assets
| Key | SI_AzureEgNonAssetTypes |
|---|---|
| Where | Settings > Collection scope & limits |
| Type | List |
| Default | Role and policy assignments and definitions, locks and diagnostic settings. |
| Edition | Community |
What it does
Azure resource types from the exposure graph that are settings on other resources, not assets, and are left out of Azure collection.
When set
Replaces the list. Removing a type brings those items back as Azure assets, which can greatly increase row counts and duplicates; adding a type removes it from collection.
When blank or default
Left blank, the default applies: Role and policy assignments and definitions, locks and diagnostic settings.
Risk and how to reverse it
Changes what is collected from the next run: narrowing it means some assets or data are not collected, so they look absent in profiles, CIs and reports (absence is never read as fixed). Reversible: change it back; the next run collects again.
Requires
Nothing else.
Recommended
Keep the default. Change it when: Only if you genuinely want one of these types profiled, or another type excluded.
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack