Logo
Cybersecurity

Security Teams Need to Understand How Software Actually Gets Shipped

Finding vulnerabilities still matters. Preventing weak code, dependencies and configurations from reaching production requires a different set of skills.

ITSEC AsiaITSEC Asia
|
Okt 05, 2026
Security Teams Need to Understand How Software Actually Gets Shipped

A security professional reviews an application and finds a vulnerability. The development team fixes it. Everyone moves on.

Then the same type of problem appears in the next release.

That’s usually a clue that the weakness lives somewhere deeper than one piece of code. Perhaps the build process accepts an unsafe dependency. A security check happens too late. A container configuration is copied from an old template. Developers receive feedback after the release is practically finished.

NIST’s National Cybersecurity Center of Excellence is putting more attention on exactly this part of software security. Its updated DevSecOps resources, published on 24 September, include CI/CD pipeline automation, containerized application deployment and functional scenarios showing security activities throughout the software development lifecycle. NIST

The workforce implication is straightforward. Application security professionals increasingly need to understand how software moves from a developer’s machine into production.

Security Work Is Moving Into the Pipeline

Traditional security testing can happen near the end of development. DevSecOps pushes security activities into the processes developers already use to build, test and deploy software.

That requires people who can work across disciplines.

Useful DevSecOps capability includes understanding:

  • How source code moves through a CI/CD pipeline
  • Where automated security testing should occur
  • How dependencies and software components are tracked
  • How containers and deployment configurations are built
  • Which findings should block a release and which require review
  • How credentials and secrets are handled during builds
  • How security feedback reaches developers quickly enough to be useful

NIST’s DevSecOps project maps practices from its Secure Software Development Framework into a reference model intended to show how security tasks can operate within modern development pipelines. NCCoE

NICE has also added DevSecOps as a formal competency area in version 2.2.0 of its cybersecurity workforce framework. NIST

That puts software delivery knowledge squarely inside cybersecurity skills development.

Automation Still Needs Judgment

A pipeline can run dozens of checks before software reaches production. That doesn’t mean every alert deserves to stop a release.

Someone still has to understand context.

A vulnerable component might be unreachable in the application. Another finding may expose an internet-facing function handling sensitive information. A failed configuration test could indicate a minor deviation or a serious exposure.

The security professional needs enough development knowledge to discuss the finding with engineers and enough risk judgment to decide what deserves immediate attention.

Otherwise, automation simply produces security findings at machine speed. The backlog will be delighted.

Train With the Pipeline Running

DevSecOps is difficult to learn from diagrams alone.

A stronger exercise gives participants source code, a CI/CD pipeline, automated tests, container builds and a deployment environment. Introduce an insecure dependency or configuration, then ask learners to identify where the control should catch it and what should happen next.

Let them change the pipeline, run another build and see the result.

That practical loop fits the learning approach at ITSEC Cyber & AI Academy. Cybersecurity professionals can build technical capability around application security, testing and secure delivery by working with systems that behave like the environments they’ll encounter on the job.

A vulnerability report tells a team what went wrong once.

DevSecOps skills help them change the process that allowed it through.

Explore hands-on cybersecurity and AI learning at ITSEC Cyber & AI Academy.

References

  1. NIST NCCoE, “New NIST NCCoE Resources on DevSecOps and October 28 Webinar on Agentic AI,” 24 September 2026
  2. NIST NCCoE, “Secure Software Development, Security, and Operations (DevSecOps) Practices Live Document,” 24 March 2026, updated on a rolling basis
  3. NIST NICE, “NICE Releases NICE Framework Components v2.2.0,” 28 April 2026
Share this post

You may also like

Employees Want Better Cybersecurity Skills. The Training Has to Keep Up.
Cybersecurity

Employees Want Better Cybersecurity Skills. The Training Has to Keep Up.

Cybersecurity training has an awkward reputation. For many employees, it arrives as an annual module, a collection of familiar warnings and a quiz that strongly encourages remembering whatever appeared on the previous screen. Meanwhile, the workplace has become considerably less predictable. ENISA’s latest Cybersecurity Month data shows that 74% of surveyed employees had received suspicious emails, messages, voice communications or links at work during the previous six months. Phishing remained the most common example, but employees also encountered attempts to steal personal information, passwords, AI-generated scams, malware and ransomware. ENISA [https://www.enisa.europa.eu/news/cybersecurity-month-work-employees-skills-under-the-looking-glass] Yet only 45% said their organization regularly sends cybersecurity awareness information or updates. The interesting part is that employees don’t appear uninterested. Eighty-five percent said they wanted to improve their cybersecurity skills. ENISA [https://www.enisa.europa.eu/news/cybersecurity-month-work-employees-skills-under-the-looking-glass] The gap is partly about how training is delivered. THE BIGGEST TRAINING PROBLEM MAY BE THE CALENDAR Among employees who identified obstacles to developing cyber skills, 26% cited finding time during work, ahead of cost at 16%, followed by limited information about training and insufficient employer support. ENISA [https://www.enisa.europa.eu/news/cybersecurity-month-work-employees-skills-under-the-looking-glass] That matters because

ITSEC AsiaITSEC Asia
|
Okt 02, 2026 — 3 minutes read
AI Is Raising the Bar for Cybersecurity Talent
Cybersecurity

AI Is Raising the Bar for Cybersecurity Talent

For cybersecurity teams, AI is quickly moving from something experimental to something people actually use. The World Economic Forum’s Global Cybersecurity Outlook 2026 found that 77% of surveyed organizations had adopted AI for cybersecurity. It is already being used for tasks such as phishing detection, intrusion response and user-behaviour analysis. That sounds like good news for teams struggling with workload. And mostly, it is. But AI doesn’t remove the need for skilled cybersecurity professionals. It changes what those professionals need to be good at. AUTOMATION CAN DO MORE. SO HUMANS HAVE TO DO MORE TOO. The same WEF research found that 54% of organizations considered insufficient knowledge or skills a barrier to using AI effectively in cybersecurity. Another 41% pointed to the need for human oversight. That second number matters. AI can analyse enormous amounts of information quickly. What it still struggles with is context: whether an unusual event is genuinely dangerous, how a technical issue affects the business and what action makes sense when the available information is incomplete. Cybersecurity professionals increasingly need

ITSEC AsiaITSEC Asia
|
Sep 02, 2026 — 3 minutes read
Protecting Critical Infrastructure Requires a Different Kind of Cybersecurity Training
Cybersecurity

Protecting Critical Infrastructure Requires a Different Kind of Cybersecurity Training

A suspicious connection appears in a corporate network. The security team investigates, isolates the affected system and starts remediation. In a conventional IT environment, that may be a reasonable first response. Now imagine the affected system controls part of an electricity substation, a water treatment facility or an industrial production line. Isolating it without understanding the operational consequences could disrupt a process that needs to remain stable and safe. This is one of the defining challenges of operational technology (OT) security. NIST's Guide to Operational Technology Security explains that OT systems interact with the physical environment and operate under specific performance, reliability and safety requirements. Security decisions must account for those requirements alongside confidentiality and integrity. [https://www.google.com/s2/favicons?domain=https://www.nist.gov&sz=32] NIST +1 For cybersecurity workforce development, that changes the training equation. KNOWING THE NETWORK ISN'T ENOUGH OT environments include industrial control systems, supervisory control and data acquisition (SCADA), building automation and other systems that monitor or control physical processes. Their operating requirements can differ considerably from those of ordinary business IT. [https://www.google.com/s2/favicons?domain=https://www.nist.gov&sz=32] NIST A security practitioner working in this environment needs

ITSEC AsiaITSEC Asia
|
Okt 13, 2026 — 4 minutes read

Receive weekly
updates on new posts

Subscribe