# A Usable Encryption Solution for File-Based Geospatial Data within a Database File System
## 3 Proposed Security Solution for Spatial Files
### A DBFS for Consolidation of File-Based Spatial Data  
A centralised repository provided by a DBFS model delivers three key benefits to spatial organisations: _First_, since a DBFS provides storage for various file formats, namely _documents, web pages, e-mails, and so on_, and ships with various integrated, commonly used protocol servers for accessing these data, it _consolidates_ spatial files previously stored on separate machines managed by separate server applications into a single DBFS repository, which spatial end-users can access through familiar interfaces. This way, spatial organisations can preserve their investments in existing spatial datasets in numerous file formats and significantly reduce the number of integration interfaces GIS users and applications have to make. _Second_, since the DBFS is built on top of a general-purpose database to store and manage files, several features of the database and application server are integrated into the DBFS, providing an alternative to the limitations of traditional standard file systems. ECMSDK, for instance, integrates with the _reliability, disaster recovery, read consistency, replication, scalability_, and _availability_ features provided by the Oracle database [61]. Additionally, for spatial administrators, a single system for file storage and access means single-system management. They only have to maintain, administer, backup, and upgrade a single system, which also simplifies disaster recovery planning [62]. _Third_, a DBFS such as ECMSDK makes use of the relational nature of the database to build upon and provides several content management features missing from traditional file systems that can be used to help business workflow processes in spatial organisations. These important content management features for files include _indexing and searching based on custom attributes, versioning, check-out and check-in operations, change notification, automatic expiration,_ and _locking_[48]. To complement these benefits, a DBFS such as ECMSDK offers a powerful and multi-layered security model. Since spatial files are stored inside the database; database security  
Figure 1: The user interaction model of the storage security solution. GIS users can store sensitive spatial files with various formats centrally within the database and can protect them using authentication, authorisation, and encryption without changing how they work with existing GIS applications. ensures non-database users cannot access spatial files. For legitimate users, ECMSDK ensures proper user authentication using an internal credential manager or, more recently, with an LDAP using the _Oracle Internet Directory_ (OID) [62]. Thereafter, ECMSDK allows user actions to be controlled consistently and logically with its access control model [48]. Since access control is a function enforced from within the database repository rather than protocol servers, it is enforced consistently, regardless of which protocols are used to access files. In addition, a DBFS such as ECMSDK provides full support for Internet security standards, e.g., _SSL_ and _firewalls_, as well as protection against harmful programs, such as viruses [48]. When these features are combined into a single repository, organisations can be confident that valuable spatial files are managed, searchable, and secure at a central location--something not offered by traditional standard file systems. **Access Control Model (ACM):** ECMSDK enforces proper authentication and authorisation mechanism. Users first require a login, and afterwards, their privileges are tightly controlled on files and folders through an associated _Access Control List (ACL)_ that contain users/groups and their privileges. From our investigation into the product's security model, the authorisation controls of the particular OS are incorporated with ECMSDK. Therefore, secure access is double-checked for additional security. After successful authentication, OS users with a corresponding account with ECMSDK are authorised under these accounts and have related privileges.