Re-design Data in transit and Connection(Rules)

[skatsikeas]

Below are my draft notes during our last meeting:

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

[skatsikeas]

Addressed on 007a5c6