Reassess Identity Controls After Telco Verification Fraud Trend

What happened

Truyu analysed nearly 25,000 Australian identity checks and found a pattern where criminals use telecommunications-provider checks to validate stolen personal details before attempting broader fraud. The most operationally important detail is that a large share of unauthorised checks were preceded by a telco check and confirmed details are often reused quickly; watch for provider-side API changes or monetisation that would alter verification behaviour

Why the category manager should care

Treat telco-based verification as an actionable control point to inventory and constrain contractually, because its exploitation short-circuits downstream fraud controls

Key facts

• Analysis covered nearly 25,000 identity checks flagged through the app
• A sizeable share of unauthorised checks followed an earlier telco check
• The app currently covers about 63% of identity checks in Australia

What happened

HID will showcase converged access and identity products in Australia, including modular Signo Décor readers and cloud-based credential issuance (FARGO Connect). This matters operationally because it enables incremental modernisation without full estate replacement, but it shifts integration, audit and lifecycle responsibilities into supplier scope—buyers should demand API, logging and revocation evidence during procurement

Why the category manager should care

Treat modular hardware and cloud issuance as a real opportunity to reduce replacement scope, but require clear API, logging and revocation guarantees before committing

Key facts

• Showcase highlights Signo Décor readers and Mercury S4 I/O Modules
• Demonstrates cloud-based credential issuance alongside on-prem printing
• Positioned to support incremental modernisation without wholesale estate replacement

What happened

Reporting shows enterprise AI adoption is outpacing governance, producing a growing blind spot where AI agents are embedded into workflows with limited central oversight. Operationally this is real because agents are being connected to HR, finance and customer systems without consistent identity governance; procurement should require discovery and permissioning artefacts from suppliers to prevent agents inheriting excessive access

Why the category manager should care

Make AI-agent visibility an identity and governance requirement in sourcing; require artefacts that show discovery, permissioning and auditability

Key facts

• AI agents are being embedded by employees, developers and business units across core systems
• Agents often interact with HR, finance and customer platforms without consistent identity gov
• Described as a growing 'shadow AI' layer that evades traditional security controls