Re-design Data in transit and Connection(Rules)

Below are my draft notes during our last meeting:

[x] - Two associations of Data Application: i) AppContainment and ii) DataInTransit
[x] - Then: Network.Applications.DataInTransit to get the (unencrypted) data. This will be called ”Eavesdrop” on Network. And then from DataInTransit you go toRespondConnect.
[x] - Then we do not need an association between Data and Connection
[x] - Rename Connection to ConnectionRule
[x] - Network should have a ”switching” defense that blocks Eavesdrop.
[x] - Data should be possible to be connected to Networks (data that are broadcastly available)
[x] - Add a "disabled" defense on Connections to represent probable connections
[x] - Update also the DoS on Network to do DoS on DataInTransit
[x] - MitM attack step on Network leading to modify on DataInTransit
[x] - Then add an ”Authenticated” defense on Data that will also affect MitM (together with Encryption)
[x] - Take into consideration the DataNotExist defense when handling DataInTransit (!).

mal-lang / coreLang