Cyber Defense eMagazine September Edition for 2022 #CDM

More documents

Recommendations

Info

Low-To-High-Side Development in The Public Sector Low-to-High-Side Development By Marc Kriz, Strategic Account Leader of National Security Programs, GitLab The stay-at-home orders put in place at the start of the COVID-19 pandemic were a catalyst for the rapid – and previously unprecedented – adoption of remote work in the public sector. This was particularly challenging for the intelligence community, and other departments working in primarily classified, or highside environments. For decades prior, software development in the public sector could only occur on-site. When the stay-athome orders were put in place, government leaders were forced to either slow down development by utilizing a reduced team of essential personnel, until all teams could return back to the office, or adjust to the new way of working – through low-to-high-side development enabled by the adoption of DevOps technology and culture. Cyber Defense eMagazine – September 2022 Edition 90 Copyright © 2022, Cyber Defense Magazine. All rights reserved worldwide.
Government agencies varied broadly in their approaches to implementing remote work. The agencies that focused on low-side – or unclassified – development were able to keep their missions going, and found an increased ability to develop code on the low side much faster than they could ever before. As remote work continues to solidify its place as the new way of working, it’s critical to create new processes that allow developers to work remotely while still being part of the development process. Let’s walk through how to bring low-to-high side development to life, and the tools and organizational shifts necessary to do so. Why Implement Low-to-High-Side Development? Low-to-high development is critical to improving speed-to-mission, developer productivity and experience, and most importantly, creating more innovative products, all while remaining secure by design. Many government agencies today work across a number of classified and siloed networks, which can make collaboration extremely challenging, and at times, nearly impossible. As these organizations attempt to scale, each point solution tool must be configured, managed, troubleshooted, and maintained in order to work with the other point solutions tools within that toolchain. With each duplication, toolchains become even more complex, turning toolchain management into its own time consuming, and cost prohibitive task. These legacy tools and processes oftentimes result in siloed teams, poor collaboration, and increased bottlenecks – ultimately slowing delivery time and halting results. Adopting a consolidated, singular end-to-end software development platform can enable faster low-side development. This approach allows developers to stay in one interface throughout the cycle and get more work done without having to rely on disparate tools, stitched together to make a disjointed toolchain and inefficient software development cycle. A comprehensive software development platform also enables developers to collaborate within the solution with government leadership and program management, keeping everyone on the same version of the truth. All of this can be accomplished within distributed teams, without needing to be on-site. Best Practices for Low-to-High Side Development A typical low-to-high side environment has one team of developers, UX/UI designers, and project managers working on the low side. They are able to build out the initial code, create issues, and collaborate in a non-classified environment. From there, they are able to pass the work over to the classified environment, or high side, within the same platform to finalize the work. By using a consistent toolchain across environments, all relevant context to the code is passed over from the low side, including artifacts, versioning, audit trails, reviews, and testing results. Typical application segmentation leads to segmented environments that are similar, but built through different processes. Although this works in theory, in practice it is made challenging when each environment has the same parent organization, resulting in redundancies and inefficiencies. In these Cyber Defense eMagazine – September 2022 Edition 91 Copyright © 2022, Cyber Defense Magazine. All rights reserved worldwide.
Page 1 and 2:
Critically Important Organization?
Page 3 and 4:
How Can Businesses Build Customer C
Page 5 and 6:
@MILIEFSKY From the Publisher… We
Page 7 and 8:
Welcome to CDM’s September 2022 I
Page 9 and 10:
Cyber Defense eMagazine - September
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Critically Important Organization?
Page 25 and 26:
• Factors and metrics to consider
Page 27 and 28:
Zero Trust Momentum Seventy-six per
Page 29 and 30:
Information Warfare and What Infose
Page 31 and 32:
Influence: Surface and measure the
Page 33 and 34:
ecording a 10% hike from 2020 findi
Page 35 and 36:
5G Technology - Ensuring Cybersecur
Page 37 and 38:
on a great scale, the newness of th
Page 39 and 40: Are Cyber Scams More Common and How
Page 41 and 42: Antivirus Software Keeping your com
Page 43 and 44: Avoiding the Risks of Ransomware St
Page 45 and 46: • How are you protecting home fie
Page 47 and 48: Black Hat Trip 2022 - Perception Po
Page 49 and 50: compared to legacy sandboxing solut
Page 51 and 52: Building A Layered Plan for Battlin
Page 53 and 54: The Challenge of Hyperconnected Fra
Page 55 and 56: Can Cloud Telephony Services with M
Page 57 and 58: software with an organization’s c
Page 59 and 60: Crack The Code Cybersecurity Workfo
Page 61 and 62: Photo Cred: Photo Cred: UofL Cybers
Page 63 and 64: More information on the Cybersecuri
Page 65 and 66: Virtual training addresses the high
Page 67 and 68: How Can Businesses Build Customer C
Page 69 and 70: associated access entitlements. A z
Page 71 and 72: have been able to quickly get servi
Page 73 and 74: How To Guard Critical Infrastructur
Page 75 and 76: 2. Control endpoint privileges. No
Page 77 and 78: especially when maxed out on events
Page 79 and 80: It Isn't Your Daddy's Oldsmobile An
Page 81 and 82: Full and Systematic Vehicle Cyberse
Page 83 and 84: Long-Term Impacts A Data Breach Can
Page 85 and 86: Encrypt data and update software re
Page 87 and 88: Perception Point has been built as
Page 89: company developed a 24/7 managed In
Page 93 and 94: About the Author Marc Kriz is a Str
Page 95 and 96: Looking at the two studies over a f
Page 97 and 98: Patch Zero Days In 15 Minutes Or Be
Page 99 and 100: Advanced SQL Behavioral Analysis fr
Page 101 and 102: New normal, new problems The “new
Page 103 and 104: About the Author Ivar Wiersma is th
Page 105 and 106: world attacks on open-source softwa
Page 107 and 108: Protecting The Enterprise in The Di
Page 109 and 110: About the Author Anurag Lal is the
Page 111 and 112: Market potential GitHub claims to h
Page 113 and 114: The Implications of Zero Trust for
Page 115 and 116: Integrating Zero Trust at the Data
Page 117 and 118: Threat Modeling: Bridging the Gap B
Page 119 and 120: What’s next for threat modeling?
Page 121 and 122: 2. Adopt trust security Consider ho
Page 123 and 124: 7. Secure your dependencies As you
Page 125 and 126: Top Trends in Cyber Security Post-P
Page 127 and 128: improve cybersecurity. As the conne
Page 129 and 130: The migration of electronic healthc
Page 131 and 132: About the Author Coley Chavez is th
Page 133 and 134: A tool to make money Cybercriminals
Page 135 and 136: Using Identity for Access Is a Huge
Page 137 and 138: Never make your own keys - physical
Page 139 and 140: What We Have Learnt Building a Glob
Page 141 and 142:
Businesses transact with, rely upon
Page 143 and 144:
Why CSOs Are Decluttering Their Cyb
Page 145 and 146:
The Middle Ground To effectively co
Page 147 and 148:
• Surge in utilization of cloud s
Page 149 and 150:
trustworthiness and accountability.
Page 151 and 152:
Why Throwing Money at Cybersecurity
Page 153 and 154:
2. Automated Analytics The human pr
Page 155 and 156:
SSL VPNs are available as stand-alo
Page 157 and 158:
About the Author Timothy Liu is Co-
Page 159 and 160:
Preparing Having never been to mult
Page 161 and 162:
Overall, this was a great conferenc
Page 163 and 164:
One of the unique things about DefC
Page 165 and 166:
Of where I was able to spend time a
Page 167 and 168:
In the end, DefCon was by far one o
Page 169 and 170:
they have. I was happy to share my
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
CyberDefense.TV now has 200 hotseat
Page 191 and 192:
Books by our Publisher: https://www
Page 193 and 194:
Page 195:
show all

Cyber Defense eMagazine September Edition for 2022 #CDM

Create successful ePaper yourself

Delete template?

Save as template?