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
There is an issue raised on Threat Dragon : Use OTM as the default file format #850
Threat Dragon can already read OTM files and apples a schema, but is unable to edit them yet
It would be good to identify any gaps in the OTM schema to ensure that Threat Dragon files can be migrated in full to OTM file format
The text was updated successfully, but these errors were encountered:
could I be assigned this issue? as it is down to the contributors of the Threat Dragon project to suggest changes to the OTM spec, so that OTM can provide all the necessary values for Threat-Dragon-type threat model
Thank you for the proposal, @jgadsden! Gathering the Threat Dragon requirements can be a good opportunity to expand the schema and make it more standard. At some point, we will still need to check the proposed changes before including them to avoid breaking the existing integrations, but I'm happy to assign you the issue and start working on it.
There is an issue raised on Threat Dragon : Use OTM as the default file format #850
Threat Dragon can already read OTM files and apples a schema, but is unable to edit them yet
It would be good to identify any gaps in the OTM schema to ensure that Threat Dragon files can be migrated in full to OTM file format
The text was updated successfully, but these errors were encountered: