Morning edition · Friday, October 23, 2026

This morning on the Wire: Friday, October 23

16 CISO Voices posts, 5 new guides and 1 security leadership opening since yesterday morning.

Covers 09:30 UTC on Thursday, October 22 to 09:30 UTC on Friday, October 23. Generated Oct 23, 2026, 09:47 UTC.

Every item below was already published on the record and links to its own page. How we work

CISO Voices

LinkedIn post · October 22, 2026
Rinki Sethi, Chief Security Officer (CSO) at Upwind
On CISO engagement with sales and leadership
Read on LinkedIn ↗
Podcast appearance · TNW | Contributed · October 20, 2026
CJ Moses, Chief Information Security Officer and VP of Security Engineering at Amazon
On an AI-driven cybersecurity podcast launch featuring a prominent security executive
Listen at TNW | Contributed ↗
Our takeOpinion
The CISO and VP of Security Engineering at Amazon is the seat behind this opening episode of a new AI-focused cybersecurity podcast. The episode covers how AI compresses the time between initial access and takeover, honeypot intelligence feeding patching priorities, security scanning inside delivery pipelines, North Korean applicants using AI-built personas, and measuring exposure rather than counting vulnerabilities. We agree that the useful metric is time from discovery to mitigation, and we would go further by tracking it per exposure class, since a quick fix to an edge service says little about a slow one in a legacy system. Mitigation should be pre-authorised: if blocking access or isolating a host needs a committee, the window closes before anyone convenes. The identity thread deserves more attention than it usually gets, because hiring screens, access provisioning and insider-risk work often sit in different teams, and AI-built personas exploit exactly those seams. We would also test the claim that continuous validation can run without slowing delivery against your own pipelines before copying the model. Watch whether later episodes show how speed of response is measured in practice.
Written from the episode's published description. How we write these
Podcast appearance · The San Francisco Tribune · October 20, 2026
CJ Moses, Chief Information Security Officer and VP of Security Engineering at Amazon
On security leadership lessons from a major tech company's security chief
Listen at The San Francisco Tribune ↗
Podcast appearance · CyberWire Daily · September 1, 2026
Heather Ceylan, Chief Information Security Officer at Box
On Windows 11 security concerns
Listen at CyberWire Daily ↗
Podcast appearance · Business Security Weekly (Audio) · August 26, 2026
Leslie Nielsen, Chief Information Security Officer at Mimecast
On linking cyber risk management to board-level decision outcomes
Listen at Business Security Weekly (Audio) ↗
Our takeOpinion
The CISO of Mimecast, in the seat since the announcement in September 2025, arrived from SVP and CISO at Klaviyo. The episode covers connecting cyber risk to board outcomes, with a guest discussing ransomware as extortion and data theft, third-party and cloud dependencies, and claims research, alongside conference interviews on agentic AI as human risk and on ransomware targeting managers. Our view on the board thread: translating cyber into resilience, financial exposure, regulatory impact and reputation is the right frame, but it only works if the numbers behind it are ones the CFO would also use, so build scenarios with finance and the risk function before the board meeting, not in it. We would add that dependency-driven interruption deserves its own line in board reporting, because outages that start at a supplier or cloud provider rarely show up in a control-maturity score. On agents as an extension of human risk, we agree in practice: giving each agent a named owner, scoped access and the same lifecycle controls as a person is a faster start than waiting for a new product category. Where we would push further is accountability, since an agent holding a human's credentials makes the deploying employee's access review the real control point. Watch whether boards begin asking for agent inventories the way they now ask about third parties.
Written from the episode's published description. How we write these
Podcast appearance · Defense in Depth · July 9, 2026
Rinki Sethi, Chief Security Officer (CSO) at Upwind
On human-machine speed mismatches in security operations
Listen at Defense in Depth ↗
Podcast appearance · CyberWire Daily · June 1, 2026
Heather Ceylan, Chief Information Security Officer at Box
On artificial intelligence integration in military command structures
Listen at CyberWire Daily ↗
Our takeOpinion
Box's CISO appears on this CyberWire Daily Industry Voices segment. The guest segment covers governed AI and the unstructured data problem, set inside a news roundup that also touches battlefield AI, a Netlogon flaw under active attack, and CIRCIA reporting debates. We think the pairing is apt: most governance programmes for AI agents begin with policy and model approval, yet the exposure sits in the sprawl of documents, messages and files that an agent will happily retrieve. Permissions on that content are usually inherited from years of loose sharing, so an assistant simply surfaces what people were always technically able to see. We would start by inventorying where unstructured content lives and who can reach it, and fix oversharing before switching on any retrieval feature. Classification labels only help if the agent's access layer honours them at query time, so test that directly rather than trusting vendor claims. Watch whether agent identity and audit logging mature quickly enough to let teams reconstruct what an agent read and why.
Written from the episode's published description. How we write these
Podcast appearance · CISO Series Podcast · April 14, 2026
David Nolan, Chief Security Officer at Trimont
On gaps between theoretical security controls and real-world attacks
Listen at CISO Series Podcast ↗
Podcast appearance · CISO Series Podcast · March 24, 2026
Julie Myerholtz, Vice President – Chief Information Security Officer at Brunswick
On inclusion efforts in cybersecurity hiring and leadership
Listen at CISO Series Podcast ↗
Our takeOpinion
The guest is the CISO of Brunswick, listed with the title Vice President, Chief Information Security Officer. The episode's description lists four topics: shared responsibility in cloud, retiring long-held security practices, AI changing vendor economics, and receiving feedback. Cloud ownership is the one we would act on first: write down, per service, which controls sit with the provider and which sit with you, and test that map during incident exercises, because the gaps surface under pressure. On retiring long-held practices, we would add that every legacy control deserves a stated purpose and an owner, and anything that cannot name either should be scheduled for removal on a date. If AI is shifting what vendors can offer, renewal reviews should ask what the product does that a capable in-house team could now assemble, and what happens to your data if the vendor is acquired. We respectfully note that feedback culture is easiest to endorse and hardest to fund, so build a recurring channel for it rather than relying on goodwill. Watch whether vendor pricing and security questionnaires change as AI features become standard.
Written from the episode's published description. How we write these
Podcast appearance · Business Security Weekly (Audio) · February 25, 2026
Elyse Gunn, Chief Information Security Officer (CISO) at Nasuni
On aligning security strategy with business risk and leadership
Listen at Business Security Weekly (Audio) ↗
Podcast appearance · CISO Series Podcast · January 6, 2026
Leslie Nielsen, Chief Information Security Officer at Mimecast
On automation amplifying security scaling mistakes
Listen at CISO Series Podcast ↗
Our takeOpinion
The CISO of Mimecast, in the seat since September and previously SVP and CISO at Klaviyo, joined a live CISO Series Podcast recording in New York. The episode covers automating dysfunction, leading without dominating, unglamorous wins and code without comprehension. We read the first topic as the one that matters most to programmes this year: automation does not repair a process, it repeats it at speed, so a muddled triage queue or a vague ownership model simply produces bad outcomes faster and in greater volume. Our advice is to document the manual workflow, name its owner and set a measure of what good looks like before any tooling is added, and to keep a human checkpoint on steps that touch access or customer data until the output has earned trust. Code without comprehension deserves the same discipline now that generated code reaches production quickly, because a team that cannot explain what shipped cannot defend or patch it. Reviewers should be able to state what a change does and why, not merely that tests passed. The unglamorous wins theme is a useful counterweight, since boring fixes such as asset inventory and clean offboarding usually pay back more than a new platform, and they are the processes worth getting right before anything is automated. Watch whether boards begin asking for the process behind an automation rather than the headline gain from it.
Written from the episode's published description. How we write these
LinkedIn post · October 21, 2026
Eric Freeman, Chief Information Security Officer at WRITER
On security professionals' shared experiences and camaraderie
Read on LinkedIn ↗
LinkedIn post · October 21, 2026
Natalia Oropeza, Global Chief Cybersecurity Officer at Siemens
On cybersecurity
Read on LinkedIn ↗
X post · October 21, 2026
Michael Coates, Chief Information Security Officer at Solana Foundation
On AI-driven vulnerability discovery and exploitation trends
Read on X ↗
LinkedIn post · October 20, 2026
Rinki Sethi, Chief Security Officer (CSO) at Upwind
On cybersecurity awareness and blue team practices
Read on LinkedIn ↗
LinkedIn post · October 15, 2026
Sean Malone, Chief Information Security Officer (CISO) at BeyondTrust
On a security leadership topic
Read on LinkedIn ↗

Guides

GuidePublished October 23, 2026
CISO Job Description: Duties, Qualifications and Reporting Terms Employers Ask For
A chief information security officer job description asks for one leader who sets security strategy and owns policy, budget and risk decisions.
GuidePublished October 23, 2026
CISO vs CIO vs CSO vs CTO: Who Owns What
The chief information security officer (CISO) owns cyber risk and the security program; the chief information officer (CIO) builds and runs the systems.
GuidePublished October 23, 2026
How Long Do CISOs Stay? Average CISO Tenure and What the Record Shows
Chief information security officers typically stay 2 to 3 years at one company, per IANS, though large enterprise CISOs average 10 years in the role overall.
GuidePublished October 23, 2026
CISO Salary and Compensation in 2026: What the Public Surveys Show
Average total pay for a US chief information security officer (CISO) was $1,447,000 in the Heidrick & Struggles 2025 survey, down 12% on lower equity.
GuidePublished October 23, 2026
CISO Reporting Structure, the Five Models and What the Filings Show
Most security chiefs report into technology leadership (64%), the rest to business leaders. The five models, their trade-offs and what 10-K filings show.

Security leadership openings

First seen Oct 23, 2026, 03:52 UTC · posted Oct 22, 2026, 22:59 UTC
CISO (opens the employer's posting)
Verkada · San Mateo, CA United States

All security leadership jobs →

This morning on the Wire: Friday, October 23

CISO Voices

Guides

Security leadership openings

Other editions