Threat Intelligence

Fix Identity Gaps in Software Development Before Rolling Out AI

Dark Reading · 21 Oct 2026
Key Takeaway Before adopting AI in your software development, review who and what has access to your development systems and close any identity gaps you find.

Artificial intelligence is making security more complicated across the software development lifecycle, according to a Dark Reading roundtable. As businesses adopt AI tools to build and ship software, the question of who and what has access to development systems becomes harder to answer.

The roundtable concluded that there is a practical way forward for security leaders. It pointed to three areas: stronger collaboration between teams, better visibility of identities involved in development, and reduced testing costs. Closing identity gaps first, the discussion suggested, puts organisations in a better position before AI is widely adopted in their development work.

The summary available does not give further detail on specific tools, findings or recommendations. Even so, the message is clear for businesses that build or customise software: know who has access to your development environment before adding new AI-driven processes.

Building or buying AI systems? Governing them under ISO 42001 ->

Summarised by CISO AI from Dark Reading, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.