search

Threagile / threagile

Agile Threat Modeling Toolkit
https://threagile.io
MIT License
577 stars 126 forks source link

Stored, sent and received data assets are always processed #58

Closed ezavgorodniy closed 5 months ago

ezavgorodniy commented 5 months ago

The PR is copied and manually applied from https://github.com/Threagile/threagile/pull/18, for any discussions if it help to clarify please take a look at the original

aceg1k aceg1k commented on Jun 29, 2021 Hi,

thank you very much for your great work on this project, I hope it is still active and open for pull requests.

Rationale Whenever data assets are stored, sent or received by a technical asset they are also processed in some way by that technical asset. This leads to tight coupling of data_assets_processed with data_assets_stored, data_assets_sent and data_assets_received (relating to both, outgoing and incoming communication links). IMHO data_assets_processed is of almost no practical use, when a data asset processed is not stored and not transferred somewhere.

Proposal Infer data_assets_processed based on data assets stored and data assets used in outgoing and incoming communication links and do not require data_assets_processed to be set and continuously maintained.

As a stored data asset always implies a processed data asset some of the code became redundant and was removed.

I look forward to your feedback!

ezavgorodniy commented 5 months ago

wrong location