# Investigating the Privacy and Security of the SimpliSafe Security System on Android and iOS
## 2 Related Work  
In this section, we discuss some of the related work in mobile application forensics of smart home devices, smart home forensic investigations, and home security system investigations. An overview of the reviewed research and its shortcomings are presented in Table 1.  
There have been several previous efforts in recovering forensic artifacts from smart home IoT devices. For example, [PERSON] et al. [7] conducted a forensic investigation of various smart home devices in a lab setup and discussed possible threat scenarios. They were able to recover several private pieces of information such as email, full name, OAUTH credentials, etc., from the smart home devices and their companion apps and discussed the privacy concerns and security vulnerabilities when using these smart home devices. [PERSON] et al. [8] analyzed client-centric and cloud artifacts stored within companion apps of the Amazon Echo. [PERSON] et al. [9] investigated the forensic artifacts produced by Nest ecosystems such as Nest thermostats and Nest cameras. Other studies have looked at smart devices' ecosystems and their interaction with each other. In [10], [PERSON] et al. investigated the August Smart Doorbell Cam and Lock devices and the interaction between these devices to determine what information could be acquired. Although forensic investigations into home security systems and specifically SimpliSafe has been limited, there are a few previous works that have investigated security and privacy issues that we describe in this section. [PERSON] et al. [11] evaluated the susceptibility of 19 common security cameras and doorbells to a persistent attack after access revocation, in situations when multiple users share a single account. Specifically, they looked at design flaws that failed to revoke a user's access that was requested to be removed by the account owner. In their study, they also included SimpliSafe Doorbell and Camera, and their results showed that the video stream on the Android companion app was still available for over 30 min after the account's password was changed. [PERSON] et al. [12] studied the design and implementation flaws of twenty smart home device companion apps. Their results showed that sixteen of these vendors suffered from some form of a design flaw that failed to properly validate certificates or protect the integrity of the message traffic. In particular, they showed that they were able to manipulate or clear alarm log files for SimpliSafe. Through IoT and network forensics, [PERSON] et al. [7] also investigated the network traffic for over 10 IoT smart devices including the Google Nest Hub Max, Amazon Fire TV Cube, and the August smart lock and smart doorbell [10]. By investigating both the mobile applications and network traffic of these devices, the authors highlighted the serious security risks that threatened these devices' users. For instance, although some of the information found such as zip code, the make and model of the devices used, etc., may not be useful to a forensic investigation, they can be used as reconnaissance to gain further access into the home network which can lead to spear-phishing or blackmail. Additionally, ref. [13] showed how Wireshark could be utilized for network protocol diagnosis and aid in network forensics. This was done by conducting multiple attack scenarios such as covert FTP and IRC channels, ICMP-based attacks, and distributed denial of service (DDoS) attacks while running Wireshark concurrently to capture network traffic. The traffic was then analyzed to identify the attack vectors. In [14], the authors used recognizable network traffic patterns to predict incoming distributed denial-of-service (DDoS) attacks. More specifically, they used Wireshark's I/O graph tool to discover five unique network traffic patterns that emerged when their home IoT environment was under a DDoS attack. The authors also provided guidelines to filter for specific traffic such as the TCP error flags and protocols used in Wireshark.