{'fraction_non_alphanumeric': 0.007032348804500703, 'fraction_numerical': 0.0014064697609001407, 'mean_word_length': 5.085470085470085, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Collaboration in a Secure Development Process Part 2

Overview In the first part of this series we examined the software development life cycle and specific ways that security can participate in the development process as a proactive stakeholder. We explored the Analysis phase in detail showing how security can be a meaningful partner in the analytic activities of software development rather than a passive policy-making body. In this part we will trace the software development life cycle through the Design phase activities looking for what artifacts and processes already exist in common development methods today. We will also consider gaps that exist in the development process and how to address these.