Topic starter
10/06/2026 12:35 am
TL;DR: Malcolm Harkins has been inducted into the CSO Hall of Fame for decades of work in cybersecurity, risk management, and responsible AI adoption, with formal recognition planned at the CSO Cybersecurity Awards & Conference in Nashville, according to HiddenLayer.
Editorial analysis by NHI Mgmt Group, based on content published by HiddenLayer: “HiddenLayer’s Malcolm Harkins Inducted into the CSO Hall of Fame”.
Key questions
Q: How should security teams govern AI transformation across identity and access programmes?
A: Start by treating AI use cases as governed identities rather than isolated tools.
Q: Why do AI programmes need IAM and PAM oversight as they scale?
A: Because the real security exposure often sits around who can configure, connect, or extend the system.
Q: What are the signs that AI data security controls are too reactive or too narrow?
A: A narrow program usually shows up as blind spots around unsanctioned tools, a high alert volume with low signal, and repeated risky behavior getting the same fixed response every time.
Practitioner guidance
- Define AI security ownership across governance and identity teams Assign clear accountability for AI risk decisions, access governance, and operational oversight across the teams that already manage security and identity.
- Map AI access paths into existing IAM and PAM controls Review which users, services, and integrations can configure, query, or extend AI systems in production.
- Review AI lifecycle checkpoints for governance coverage Check whether discovery, supply chain assurance, deployment approval, and runtime monitoring are all covered by a single programme view.
Bottom line: The article signals that AI security leadership is now judged by governance, risk management, and operational resilience, not by technical novelty alone.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 day ago by NHI Mgmt Group
11/06/2026 2:19 am
AI security recognition is increasingly a proxy for governance maturity. The article is not about a breach or a product launch, but it still reveals where the market is heading: leadership in AI security is being recognised for risk management, resilience, and operational discipline. That is significant because enterprises do not just need tools, they need executives who can align identity, data, and AI controls under one decision model. Practitioners should read this as a signal that AI governance is becoming a board-level accountability issue, not a narrow technical specialty.
A few things that frame the scale:
- 1 in 4 organisations are already investing in dedicated NHI security capabilities, with an additional 60% planning to do so within the next twelve months, according to The State of Non-Human Identity Security.
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, which shows that confidence remains far behind deployment pressure.
A question worth separating out:
Q: What is the difference between AI security controls and NHI controls?
A: NHI controls focus on identities such as service accounts, keys, tokens, and certificates. AI security controls extend that model to systems that can reason, select tools, and sometimes act autonomously. In practice, the strongest programmes use NHI discipline as the baseline and then add governance for runtime decision-making.
👉 Read our full editorial: HiddenLayer CSO Hall of Fame induction underscores AI security leadership
12/06/2026 3:53 am
AI security leadership is now a governance discipline, not a niche technical specialty. The article recognises a career built around security risk management and responsible AI adoption, which reflects where the field is heading. Organisations are no longer asking only whether AI works, but who governs its use, how risk is assigned, and how resilience is maintained across the business. The practical conclusion is that AI security leadership now belongs inside enterprise governance, not beside it.
A question worth separating out:
Q: What should teams do when AI adoption reaches critical business functions?
A: They should move AI security into the same governance model used for other enterprise-risk domains. That means aligning controls, escalation paths, and accountability with the business processes the AI now supports, rather than treating the system as an isolated technical initiative.
👉 Read our full editorial: HiddenLayer CSO Hall of Fame induction underscores AI security leadership
This post was modified 1 day ago by NHI Mgmt Group