Reassess Contracts and Controls for Agent, Telemetry, and App Changes

What happened

Corma, a defensive-AI startup, says its agent models can detect and block live attacks and reported a $60 million seed round. The company ran vendor-run tests where offensive runs implanted persistent backdoors in a majority of scenarios while detection rates were much lower, which makes the vendor claims operationally real but derived from controlled exercises. Watch for independent validation or pilot results that confirm those response improvements in buyer environments

Why the category manager should care

Treat the vendor as a maturing category signal; require pilot-based proof points and clear rollback/authorization clauses before accepting live automated blocking

Key facts

• Company announced $60 million seed funding
• Vendor test matrix ran dozens of model-vs-model engagements and reported implant vs detection
• Early enterprise deployments cited by the vendor claim reduced response times

What happened

An unnamed supplier managing a Scottish government data maturity assessment exposed names, roles, and work email addresses for roughly 300 prosecution service staff after suspicious activity was detected. The affected organization says its core systems were not breached, which makes this operationally real as a supplier-handled PII incident rather than a platform compromise. Watch whether similar assessment or survey suppliers lack encryption, retention, or incident-notification controls

Why the category manager should care

Classify low-touch assessment suppliers as data handlers in contracts and require minimum security baselines and notification SLAs

Key facts

• Incident involved employee names, roles, and work email addresses
• Supplier-detected suspicious activity triggered an investigation
• Affected organisation stated core systems were not compromised

What happened

OpenAI launched Computer History, an opt-in feature that records clicks and typing as local event files and uses them to create memories by sending summaries to OpenAI servers. The vendor warns local files may be unencrypted and are kept briefly before deletion, which makes this an operational data-capture vector that increases token costs and forensic surface area. Watch for employee opt-ins that bypass corporate policy and for platform changes to retention or transport behavior

Why the category manager should care

Require vendor disclosure of what is captured, how it's transported and stored, and who can access it; build those requirements into procurement terms

Key facts

• Computer History records input events and saves local files for a short window
• Events are sent to vendor servers for summarization and may be retained
• Feature is opt-in but increases token usage during summarization

What happened

Microsoft is merging the consumer Copilot app and Microsoft 365 Copilot into a single Copilot app and will move content from the old standalone app into OneDrive while removing some consumer features. The vendor set a rollout effective date and recommended users download content they want to keep, which makes migration and entitlements operationally relevant for buyers. Watch for feature gaps, forced storage moves, and whether Microsoft provides automated preservation or export tools for impacted content

Why the category manager should care

Assess entitlements, data migration impacts, and whether paid tiers are required to retain agent features or higher usage limits

Key facts

• Merge of consumer Copilot and Microsoft 365 Copilot into a single app
• Files from the old standalone Copilot will be moved to OneDrive
• Vendor recommended users export messages and content they want to keep