<p>In my experience, the purpose of the "DevSecOps" (or whichever order you prefer) has mostly to do with including Security as a first-order concern of software delivery.  Security is commonly treated as a "bolt-on" (often meaning <em>optional</em>,) non-functional requirement.  DevSecOps attempts to describe a process where security concerns are folded into the delivery process at every step of the value stream.</p>

CC BY-SA 3.0
2017-06-20T17:53:11.107Z
2017-06-20T17:53:11.107Z
Dave Swersky
<p>Or rather marketing slang? 
Currently, I am not always sure how to build a consense which words deliver informational value and which are thought to attract customers.
So, DevOps would include security testing if required without calling it DevSecOps? Otherwise we will have DevPerfOps,  DevDevOpsOps etc</p>

<terminology>
Is DevSecOps indeed a new practice worth a professional term?
Ta Mu
# Is DevSecOps indeed a new practice worth a professional term?

(Asked by: username_0 on 2017-06-19)

Or rather marketing slang?
Currently, I am not always sure how to build a consense which words deliver informational value and which are thought to attract customers.
So, DevOps would include security testing if required without calling it DevSecOps? Otherwise we will have DevPerfOps, DevDevOpsOps etc

**Tags:** terminology


---

## 1 answers

### Answer by username_1 on 2017-06-20. Score: 5

In my experience, the purpose of the "DevSecOps" (or whichever order you prefer) has mostly to do with including Security as a first-order concern of software delivery. Security is commonly treated as a "bolt-on" (often meaning *optional*,) non-functional requirement. DevSecOps attempts to describe a process where security concerns are folded into the delivery process at every step of the value stream.


---

