Please enable JavaScript.

Coggle requires JavaScript to display documents.

Brisbane Events App Data - Coggle Diagram

- - - - Pros
        
        Easier to write
        
        Quicker to edit
        
        Shorter than XML which saves disk space
      - Cons
        
        More ambiguous than XML when a human reads the raw data.
  - - - To ensure data confidentiality, the user's data will be stored encrypted server side which can only be decrypted with the key stored on the user's device
      - Two factor encryption can be used
      - Keep access control lists on the server backed up so that in the event of a malicious user modifying it, a backup with the correct permissions can be used temporarily
    - - APP12: Users will be able to see their saved events list at any time.
      - APP13: Data will be continuously pulled from online to compare with the saved data. If there are any data conflicts, the user can be notified of the change.
      - APP11: Users can only access data if the device they made the request on is the same. This is to prevent unauthorised users from gaining access to other people's saved list.
      - APP2: The app does not collect any personal data except for the device ID which is used to validate access to the user's saved list.
    - - Data can have availability measures by having key parts of the data stored offline, in app.
      - RAID disk drives can be used to mitigate the impact of a DDoS attack on the server
      - Keeping a local backup of the downloaded events can be useful in the event of a DDoS attack on the server or app allowing the user to still access their data
    - - Checks the API to make sure the data is being sent through a https network to mitigate the risk of false data (making sure the data is authentic from the source) from prediction attacks.
      - Usage of version controls and data logs can be used to prevent alterations