About Overriding Inherited TID Settings
To override an inherited setting, change the setting at the child level; see Edit Threat Intelligence Director Actions at the Source, Indicator, or Observable Level and Pause or Publish Threat Intelligence Director Data at the Source, Indicator, or Observable Level. After you override an inherited setting, the child object retains that setting despite changes to the parent object(s).
For example, you might start with the following original settings, with no overrides set:
Setting |
SourceA |
IndicatorA |
ObservableA1 |
ObservableA2 |
---|---|---|---|---|
Publish |
|
|
|
|
If you override the setting for IndicatorA, the settings would be the following:
Setting |
SourceA |
IndicatorA |
ObservableA1 |
ObservableA2 |
---|---|---|---|---|
Publish |
|
|
|
|
In this case, any changes to the Publish setting for SourceA no longer cascade automatically to IndicatorA. However, inheritance from IndicatorA to ObservableA1 and ObservableA2 continues, because the observable settings are not currently set to override values.
If you later override the setting for ObservableA1:
Setting |
SourceA |
IndicatorA |
ObservableA1 |
ObservableA2 |
---|---|---|---|---|
Publish |
|
|
|
|
Any changes to the Publish setting for IndicatorA no longer cascade automatically to ObservableA1. However, those changes continue to cascade to ObservableA2, because it is not set to an override value.
At the observable level, you can revert from an override setting to the inherited setting, and the system resumes cascading setting changes automatically from the parent indicator to that observable.