You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on navigator v4.5.4, and trying to get data from ATT&CK Workbench v1.1.0.
I have configured navigator integrate workbench address, accroding to this guide.
I created user-defined technique, mitigation, group, software, datasource one for each in workbench. after a while, i tried to find them in Navigator(The Navigator should sync all the new items i created in workbench as i understand).
But threat group and datasource can not be found there (technique, mitigation, software are synchronized correctly)
I suppose maybe some errors happened when handling group and datasource.
The text was updated successfully, but these errors were encountered:
There appears to be a small bug when importing of Group objects from the Workbench. This issue is being tracked in the REST API repository here.
For data sources to appear in the Navigator, they must have at least one data component and at least one of those data components must have a relationship with a technique in the Enterprise domain. Otherwise, the data source will not be pulled in from the Workbench REST API, since there are no relationships with Enterprise techniques. Data sources currently exist only in the Enterprise domain.
Hi,
I'm working on navigator v4.5.4, and trying to get data from ATT&CK Workbench v1.1.0.
I have configured navigator integrate workbench address, accroding to this guide.
I created user-defined technique, mitigation, group, software, datasource one for each in workbench. after a while, i tried to find them in Navigator(The Navigator should sync all the new items i created in workbench as i understand).
But
threat group
anddatasource
can not be found there (technique, mitigation, software are synchronized correctly)I suppose maybe some errors happened when handling group and datasource.
The text was updated successfully, but these errors were encountered: