THE SAFE ADVANTAGE


platforms increased the need to incorpo- rate security into software development. However, security testing was executed late in DevOps, causing delays. As a result, the DevSecOps model emerged (Figure 1).


DevSecOps ensures that security decisions are made at the same time as develop- ment and operational decisions, and that security testing is automated, improv- ing software deployment. In 2020, the best practices of Agile and DevSecOps were described in the DoDI 5000.87. Te DoDI requires capability needs state- ments, user engagement, value assessments and metrics and iterative delivery of capa- bility to users within a year. Te intent of the Software Acquisition Pathway is to deliver effective, resilient, supportable and affordable software solutions to the end user, adhering to safety critical software standards and guidance, ensuring execu- tion at the speed of relevance.


SOFTWARE SAFETY Software safety presents a parallel chal- lenge to rapid software development as cybersecurity posed to DevOps in the 2010s. Software safety is not directly considered during DevSecOps and testing for safety is executed late in the develop- ment cycle or is not executed at all. Tis can result in significant program delays due to the late discovery of software safety defects, urgent fixes to software safety defects, the need for additional testing, delayed delivery of the software product and elevated risk for hazards as a result of software safety defects. Te ability of software to facili- tate safe operations is critical, especially as the Army moves toward human-machine integration of autonomous, artificially intelligent and robotic systems operat- ing with minimal human input. Without proper management, software can create safety hazards that impact personnel and infrastructure. For example, software


34 Army AL&T Magazine Fall 2024


FIGURE 1


COMMUNITY OF PRACTICE


The DevSecOps process aims to unify software development, security and operations. The main characteristic of DevSecOps is to automate, monitor and apply security at all phases of the software life cycle. (Image courtesy of Air Force DevSecOps)


FIGURE 2


SOFTWARE SAFETY ENGINEERING PROCESSES


The DevSecSafOps process builds upon DevSecOps by integrating software safety engineering in the software development process automating safety-significant test cases, implementing continuous safety monitoring during operations and ensuring stakeholder engagement. (Image courtesy of the authors)


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120