Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Immutable asset numbers #150

Open
2 tasks
chgerkens opened this issue Dec 3, 2024 · 2 comments
Open
2 tasks

[FEATURE] Immutable asset numbers #150

chgerkens opened this issue Dec 3, 2024 · 2 comments

Comments

@chgerkens
Copy link

Describe the feature

When a new asset is created, numbers of existing assets should not be updated in assets table so that numbers can be used to refer to an asset outside the threat composer model.

Use Case

Adding assets to a diagram by using its number only.

Example Diagram

Proposed Solution

No response

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change
@chgerkens
Copy link
Author

Could be labeled as a bug, since threat numbers for instances to not change when new threats are added.

@jessieweiyi
Copy link
Contributor

Hi @chgerkens ,

Thank you for your feature request and your interest in Threat Composer. Let me explain the current behavior: Asset Ids are dynamically generated during threat model report creation, based on how they appear within the threats. This means the IDs may change when threats are added, deleted, or modified.

While we've added your request to our product backlog, there are a few technical challenges to consider:

  • Implementing this change would require breaking changes to our schema
  • This could impact dependent downstream applications
  • We need to carefully evaluate how to maintain compatibility with:

We'll continue to evaluate this request and provide updates here. Please feel free to follow this issue for any developments.

Thanks for helping us improve Threat Composer!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants