The data that are generated by several devices in the IoT realm require careful and real time processing. Recently, researchers have concentrated on the usage of cloud databases for storing such data to improve efficiency. HarperDB aims at producing a DBMS that is relational and non-relational simultaneously, to help journeymen developers creating products and servers in the IoT space. Much of what the HarperDB team has talked about has been achieved, but from a security perspective, a lot of improvements need to be made. The team has clearly focused on the problems that exist from a database and data point of view, creating a structure that is unique, fast, easy to use and has great potential to grow with a startup. The functionality and ease of use of this DBMS is not in question, however as the trade-off triangle to the right suggests, this does entail an impact to security. In this paper, using multiple forensic methodologies, we performed an in-depth forensic analysis on HarperDB and found several areas of extreme concern, such as lack of logging functionalities, basic level of authorisation, exposure of users' access rights to any party using the database, There had to be a focus on preventative advice instead of reactive workarounds due to the nature of the flaws found in HarperDB. As such, we provide a number of recommendations for the users and developers.