{'fraction_non_alphanumeric': 0.012279355333844973, 'fraction_numerical': 0.0, 'mean_word_length': 5.585858585858586, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Security Gaps in Databases: A Comparison of Alternative Software Products for Web Applications Support

When deploying database-centric web applications, administrators should pay special attention to database security requirements. Acknowledging this, Database Management Systems DBMS implement several security mechanisms that help Database Administrators DBAs making their installations secure. However, different software products offer different sets of mechanisms, making the task of selecting the adequate package for a given installation quite hard. This paper proposes a methodology for detecting database security gaps. This methodology is based on a comprehensive list of security mechanisms derived from widely accepted security best practices, which was used to perform a gap analysis of the security features of seven software packages composed by widely used products, including four DBMS engines and two Operating Systems OS. The goal is to understand how much each software package helps developers and administrators to actually accomplish the security tasks that are expected from them. Results show that while there is a common set of security mechanisms that is implemented by most packages, there is another set of security tasks that have no support at all in any of the packages.