Difference between revisions of "DevSecOps"
From MgmtWiki
(→Context) |
|||
| Line 5: | Line 5: | ||
This particular morph of DevOps seems to have originated in the US DoD to solve problems like Solar Winds where Developers can place code directly into operations without a security check first. | This particular morph of DevOps seems to have originated in the US DoD to solve problems like Solar Winds where Developers can place code directly into operations without a security check first. | ||
* The DoD [https://repo1.dso.mil/users/sign_in Repo One] was created to enable any development org to create app that could run on [https://p1.dso.mil/#/ Platform One] | * The DoD [https://repo1.dso.mil/users/sign_in Repo One] was created to enable any development org to create app that could run on [https://p1.dso.mil/#/ Platform One] | ||
| + | |||
| + | ==Solutions== | ||
| + | * [https://software.af.mil/dsop/ DoD Enterprise DevSecOps Initiative (DSOP)] | ||
==References== | ==References== | ||
[[Category: Best Practice]] | [[Category: Best Practice]] | ||
Revision as of 17:01, 28 April 2022
Full Title or Meme
Development, Security, Operations is like DevOps, except that a security layer if placed between Development and Operations.
Context
This particular morph of DevOps seems to have originated in the US DoD to solve problems like Solar Winds where Developers can place code directly into operations without a security check first.
- The DoD Repo One was created to enable any development org to create app that could run on Platform One
