Spyderisk / domain-network

Network domain model
Apache License 2.0
1 stars 0 forks source link

Deprecate remote processing relationship #127

Closed mike1813 closed 3 months ago

mike1813 commented 5 months ago

The predicate domain#processesRemotely relates a remote access client to data processed by a remote interactive process accessed via the remote access client.

The original reason for introducing this relationship was that the data may go to or from the interactive user via the remote access client, which therefore must have some relationship to the data. For a while, domain#processesRemotely was used in the construction pattern that created a DataAccess asset representing the remote access client accessing the data.

This is no longer done. Nowadays, the remote process has a domain#enablesUserAccess relationship to the data, indicating that its user does interact via the process with the data. If user interactions with the process are via a remote access client, then the DataAccess asset is created. There is no need for an extra, pre-existing relationship between the remote access client and the data.

The domain#processesRemotely relationship is not used in any threat, so it can be removed from the model, along with the construction pattern HuRACuPD+pR that creates it.

It would make sense to fix this in branch 107, along with other changes to the user interactivity construction sequence to address #107.

mike1813 commented 3 months ago

This has been done on branch 107, and is now merged into branch 6a.