DevSecOps meaning, in plain words

DevSecOps builds security in from the start of development through operation. What NIST SP 800-204C and SP 800-218 say, and what to ask a contractor who builds your site.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

DevSecOps is the idea of building security in from the start of development through operation. It does not separate Development, Security and Operations. It treats them as one flow. NIST SP 800-204C describes DevSecOps as supported by a CI/CD flow that automatically links building, testing, packaging, deployment and operation, together with the feedback exchanged to verify each step.

How does DevSecOps work?

Compare it with checking a building. You do not wait until it is finished to test earthquake resistance. You inspect at the design stage, during foundation work, and partway through the interior. The earlier a problem is found, the smaller the redo.

In practice, automated checks run when code is saved, when a part is brought in, and just before release. Typical ones are SAST, which examines the source code, dynamic testing, which probes a running app, and SCA, which examines the parts you use.

NIST's SSDF (SP 800-218) notes that many development methods do not address security sufficiently. It asks organizations to add secure development practices to the method they already use. The DevSecOps idea helps carry those practices into the daily flow.

What source-code assessment covers is described on the source code assessment page. Before you talk to a contractor, you can view your site from outside with the free URL check.

Why does DevSecOps matter?

When a hole turns up just before release, the schedule slips and large parts of the work are redone. If checks are part of every run, each small change is confirmed as it happens, and fewer problems are left unseen.

A small company may not have to practice it in house. When you outsource development, asking when checks run, with which tools, and who confirms the results shows how your contractor works.

Related terms

  • SAST: a method of examining source code without running it
  • Dynamic testing: an inspection that tries a running app from outside
  • SCA: an inspection that finds holes in the parts you use
  • Container security: keeping the app's container and its runtime safe

Frequently asked questions

Can I start DevSecOps by buying a dedicated product?

A product alone does not start it. You must decide where in the development flow the checks go, and who reads the results and fixes the findings. Tools are used to run those decisions automatically.

If development is outsourced, what should I confirm?

Ask when the checks run, with which tools, and who reviews the results. Whether checks run before every release, and whether fixes for the findings are recorded, are also useful evidence.

Next step

Your contractor's answers about when checks run, with which tools and who reads the results are the place to begin. To plan how to work through them, contact us.

Frequently asked questions

Can I start DevSecOps by buying a dedicated product?

A product alone does not start it. You must decide where in the development flow the checks go, and who reads the results and fixes the findings. Tools are used to run those decisions automatically.

If development is outsourced, what should I confirm?

Ask when the checks run, with which tools, and who reviews the results. Whether checks run before every release, and whether fixes for the findings are recorded, are also useful evidence.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.