Please enable JavaScript.
Coggle requires JavaScript to display documents.
Research and Investigation - Coggle Diagram
Research and Investigation
Securing data
Data Deidentification
Local public API
Public data table showing number of trespassers apprehended
Compliance with Australian privacy act by removing any data that can be used to identify someone
Backend security
Security of the data is analyzed at every layer
API Access
API will be called by the backend
Web App Front end
Login system will have a lock screen
Risks of transferring data
Security
Data must not undergo any alterations during transmission
Monster in the middle (MiTM) attack
Data must only go to the intended recipient and no other parties
Bandwidth Overconsumption
Deflate Lossless Compression Method
Image compression
HTML and CSS Minification
Integrity
Application that is receiving must parse data correctly
MD5 Hashtag (insecure)
SHA-1 Hashing
TCP will be used for Textual Data Components (such as JSON, HTML, XML)
Use of UDP for audio and video (doorbell cam footage)
Dynamic data
Private API's
API Keys
Used as n request Identifier
Potential API's
Cloud image recognition
Cloud audio recognition
Footage management systems
API Security
Certificates
Secure Transfer (HTTPS)
TLS Security
Public API's
Formatting
XML
JSON
Transfer protocol
HTTPS
REST
Data Licensing
Data Availability
Potential API's
Visitor data
Trespasser data
Arrival/Leaving time data
Transportable Data
Trespasser Data
Data exchange components
Data consumer
Data Provider
Standard Date/Time formatting
Trespasser caught on cam
Has begun sign in process in allocated sign in time period(4:00 minutes)
Hasn't begun sign in process in allocated sign in time period
Send home owner an alert with option to alert the police with message and picture of the trespasser with home owners house location
Location data provided to police