# Darius Radford

Darius Radford focuses on helping organizations secure how they build and run software. At KnightsWatch Cyber, Radford's posts describe the Secure Software Factory, an operating model that connects software delivery, application security, supply-chain controls, risk management, and protection after deployment.

- Profile: https://b2binfluencer.marketing/creators/darius-radford/
- LinkedIn: https://www.linkedin.com/in/darius-radford-3a3ba3202
- LinkedIn followers: 704
- Topics: artificial-intelligence, supply-chain, ai-governance, software-supply-chain-security, application-security
- Based on 13 dated posts, latest 2026-10-10

## Summary

Darius Radford is most useful for explaining secure software delivery as an integrated operating model with governance and supply chain controls.

- Best for: Cybersecurity vendors running webinars on secure software supply chains for engineering, AppSec, DevSecOps, and platform leaders.
- Not for: CI/CD vendors seeking paid social campaigns with fast build and deploy claims and reach guarantees.
- Check first: Ask for recent impressions and engagement on Secure Software Factory posts plus past webinar attendance.

### Takeaways

- Security tools alone don't solve a decision-making problem.
- Secure software requires connected controls from commit to runtime.
- Evaluate tools by how well they fit the operating model.

## Main ideas

- **Security tools alone don’t solve a decision-making problem**: Radford argues that organizations can own many security products and still face backlogs, developer frustration, repeated vulnerabilities, and bottlenecks. In their view, teams need a system to decide what matters and act across the software lifecycle.
- **Secure software requires connected controls from commit to runtime**: Radford presents the Secure Software Factory as an operating model, not a single product. Its capabilities connect delivery pipelines, developer workflows, software artifacts and dependencies, and risk information to help teams govern software across its lifecycle.
- **Evaluate tools by how well they fit the operating model**: Radford’s tool-evaluation approach shifts attention from isolated performance claims to whether a tool supports secure, governed delivery. Tool choice becomes part of a broader process, not a substitute for one.
- **Faster, AI-assisted software raises the stakes for trust and governance**: In a later description of Secure Software Factory 2.0, Radford connects faster pipelines and AI-generated code with the need to verify dependencies, enforce policy, understand risk, and protect software in production. AI governance spans the framework wherever agents or models help build or operate software.

## Work to read

- [The Secure Software Factory as a four-pillar operating model](https://www.linkedin.com/posts/darius-radford-3a3ba3202_organizations-have-invested-heavily-in-devsecops-activity-7442554466949754880-P8j-)
- [Secure Software Factory 2.0: five pillars and AI governance](https://www.linkedin.com/posts/darius-radford-3a3ba3202_contact-kwcybernet-activity-7510704941389295616-9UWO)
- [The vulnerability problem is really a decision-making problem](https://www.linkedin.com/posts/darius-radford-3a3ba3202_one-of-the-biggest-misconceptions-in-application-activity-7472266651372163072-WoQ0)
- [Five-part tool comparison series for the Secure Software Factory](https://www.linkedin.com/posts/darius-radford-3a3ba3202_pillar1-orchestrated-delivery-tool-evaluation-activity-7508195444498317312-gf_t)
- [WeAreDevelopers question: why more DevSecOps tools have not always meant safer or faster delivery](https://www.linkedin.com/posts/darius-radford-3a3ba3202_im-headed-to-wearedevelopers-in-san-jose-activity-7508308276372180992-pWME)

## Brand relationships

- **KnightsWatch Cyber** (employment)
- **Harness** (mention)
- **WeAreDevelopers** (mention)

## Partnerships

Darius Radford's posts describe no partnership or sponsorship offer. Every call to action in the five posts points to KnightsWatch Cyber's own assets and services: a downloadable Secure Software Factory whitepaper, an assessment conversation, and a five-part tool-comparison video series. No rate card, media kit, sponsorship policy, audience package, third-party brand collaboration, or paid partner is identified. The closest thing to vendor-facing content is the video series, in which Radford compares the Harness AI continuous integration product with Jenkins, Azure DevOps, GitHub, and GitLab, framing the comparison around fit with the Secure Software Factory rather than build speed. The series shows they will evaluate commercial tooling in public, relevant context for a co-marketing proposal, but does not establish that it was sponsored or that they accept sponsored placements. For a vendor planning a co-marketing webinar on secure software supply chains, any partnership would need to be negotiated directly and defined from scratch; the posts present Radford as a subject-matter practitioner promoting an operating-model framework, not a creator with published sponsorship inventory. Before describing partnership formats, ask Radford or KnightsWatch Cyber for a sponsor policy, rate card, or disclosed collaboration.

## Alternatives

- Jim Manico: Pick Jim Manico when the webinar's subject is how AI is changing the economics of application security rather than the artifact side of the supply chain. Manico argues that vulnerability discovery and remediation are both getting dramatically cheaper, that standalone scanners, SAST, DAST, IAST and CVE scanners will increasingly be replaced by AI-native capabilities, and that OWASP ASVS and AISVS matter more than ever because they define what security means and what must be verified. For a vendor whose story is agentic remediation, or security requirements set during specification and threat-modeled continuously, that is a closer starting argument than a multi-pillar maturity model. He also brings current incidents, such as the RubyGems attack by agent swarms, showing that the shift is already underway, and can speak to where human judgment still holds: architecture, business logic and novel attacks.
- Motti Sorani: Pick Motti Sorani when the webinar should be about the last mile: turning findings into fixes at scale without slowing development. The argument, developed in conversation with co-founder Gil Regev, is that the industry over-invests in detection and visibility, engineers do not need more alerts, and remediation has to be integrated into development workflows, borrowing the telecom comparison of solving the hardest part of delivery. If the vendor's product is remediation workflow, triage-to-fix automation or developer-experience tooling, that framing matches the product more directly than a pillars model. Sorani can also open with an origin story that earns attention: learning assembly language to get more control out of a PC, reading computer viruses to do it, and writing a virus generator purely as an intellectual challenge. It's a concrete route into offensive security rather than a credential list.
- Ronen Slavin: Pick Ronen Slavin when the vendor wants quantified, analyst-framed material on the same supply-chain question. Slavin cites the 2026 Verizon DBIR—vulnerability exploitation passing stolen credentials as the top initial access vector, median time-to-patch up 34% year over year, supply chain involvement in 48% of breaches—and Forrester's first Agentic Development Security Landscape, then places the bottleneck at remediation rather than discovery. That is stronger raw material for a data-led opening than a maturity model, and the discussion of AI discovery pipelines (Anthropic's Mythos and Project Glasswing, OpenAI's Daybreak, Microsoft's MDASH feeding Windows CVEs into Patch Tuesday) gives the session a concrete hook: where do these disclosures land once they are public? If the vendor's pitch is triage, exploitability confirmation and closing risk at machine speed, Slavin is arguing on the same ground.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/