Topic starter
09/07/2026 3:30 pm
TL;DR: AI-assisted software creation is accelerating SaaS sprawl, shadow IT, duplicate contracts and unmanaged risk, according to Efecte, while Gartner cited in the source warns that organisations without central SaaS lifecycle management will be five times more likely to suffer cyber incidents or data loss by 2027. Visibility and lifecycle control, not innovation speed, now define the governance problem.
Editorial analysis by NHI Mgmt Group, based on content published by Efecte: “AI and the New Era of Software Control: Why 2026 Demands a Shift in Mindset”.
By the numbers:
- Organisations that fail to centrally manage SaaS lifecycles will be five times more likely to suffer cyber incidents or data loss by 2027, according to Gartner research cited by Efecte.
- At least 25 percent of SaaS spend will be wasted on unused licenses and overlapping tools, according to Gartner research cited by Efecte.
Key questions
Q: What breaks when AI-assisted SaaS creation happens outside governance?
A: The first thing that breaks is ownership.
Q: Why does SaaS sprawl create security risk as well as cost pressure?
A: SaaS sprawl increases the number of accounts, roles, permissions, and integrations that must be governed.
Q: How do organisations know if SaaS lifecycle automation is actually working?
A: Look for evidence that provisioning, approval, and revocation happen in the same workflow and that stale licenses disappear after role changes or departures.
Practitioner guidance
- Build a single SaaS inventory as the system of record Track every approved, pilot, and shadow application in one place with owner, business purpose, data classification, renewal date, and offboarding responsibility.
- Tie access reviews to application lifecycle events Trigger reviews when a SaaS app is first adopted, changed, renewed, or retired so that orphaned access and duplicate tools are surfaced early.
- Inventory non-human identities inside SaaS tools Record service accounts, API tokens, delegated credentials, and app-to-app connections for every SaaS platform so machine access is visible and reviewable.
Bottom line: AI-assisted software creation is expanding the SaaS estate faster than many governance processes can inventory it.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
09/07/2026 3:51 pm
SaaS sprawl is now an identity governance failure, not just a software inventory problem: AI-assisted creation multiplies the number of applications that can be brought into use without a formal intake path. Once that happens, the organisation loses reliable ownership, approval, and offboarding signals. The practitioner conclusion is that SaaS governance must be treated as a control surface in its own right.
A few things that frame the scale:
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to the State of Secrets in AppSec.
A question worth separating out:
Q: What is the difference between SaaS access governance and SaaS inventory management?
A: SaaS inventory management answers what applications exist and who approved them. SaaS access governance answers who can use each app, what they can do inside it, and whether that access is still justified. Both are necessary. Inventory without governance leaves permissions unchecked, while governance without inventory misses shadow IT and hidden application risk.
👉 Read our full editorial: AI-driven SaaS sprawl is exposing a new governance gap