{'fraction_non_alphanumeric': 0.014109347442680775, 'fraction_numerical': 0.0, 'mean_word_length': 4.942408376963351, '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}}
Assessing optimal patch release time for vulnerable software systems

Every failure in a software system demands for a repair or fixation process so as to deliver an intact system. In terms of IT industry, a patch intercepts users from getting exploited by the unknown complex defects which are termed as vulnerabilities. Many of the cyber attacks are due to the vulnerabilities and unacceptable management of the patches. One of the management issues is when one should apply a patch, since early patching results in instability aroused by bugs in the patches and behind patching may install malware in the system. The second key challenge is to maintain the quality of the software while releasing the patches. Despite of prevailing challenges, management has to deal with market potential. Thus in this paper, we have proposed a generalized framework to find a solution for mentioned problems. The framework identifies the optimal patch release time and optimal cost, and retains the reliability of the software. Further, the model elaborates the role of hacker, user and tester in different phases of a vulnerable software system.