Why the US Air Force’s Chief Security Officer Resigned: DevSecOps Hurdles Revealed
The US Air Force’s chief security officer, Nicolas Chaillan, stepped down, citing the daunting challenges of implementing DevSecOps and the Air Force’s failure to prioritize IT security, inconsistent policies, and outdated procurement practices that hinder large‑scale projects.
Recently, Nicolas Chaillan, the Chief Security Officer (CSO) of the US Air Force, announced his resignation, describing the role as the most challenging and infuriating job of his career.
Chaillan, who assumed the US Air Force CSO position in May 2019 after serving at the Department of Defense where he promoted DevSecOps practices, condemned senior Air Force leadership for not prioritizing IT system security, citing a lack of response and policy consistency as key reasons for his departure.
Although Chaillan successfully introduced DevSecOps in parts of the DoD, he encountered institutional inertia when attempting to scale the practice within larger projects. He noted that regardless of seniority or expertise, senior officers are assigned to manage defense procurement projects, often with fixed two‑year terms, leading to costly and inefficient outcomes for initiatives requiring longer timelines.
Chaillan also criticized the Air Force for still using outdated “waterfall‑agile‑procurement” principles for services and talent acquisition, and expressed disappointment that the Joint All‑Domain Command and Control (JADC2) project failed to secure the necessary multi‑million‑dollar funding in the FY2022 budget.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
21CTO
21CTO (21CTO.com) offers developers community, training, and services, making it your go‑to learning and service platform.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
