|
 Google today announced new products that compete with Apple devices like the iPhone and the Apple Watch. There are new Pixel smartphones with AI capabilities, a new foldable, and new wearable devices.
|
|
 Google today introduced the Pixel Tag, its answer to Apple's AirTag. Pixel Tag is Google's first item tracker, even though Google implemented an item tracking network two years ago that's been used by third-party devices.
|
|
 With Apple's upcoming iPhone Ultra there's been a lingering question over the exact placement of the selfie cameras in the device's folded and unfolded states - but today we may have stumbled upon the answer.
|
|
There's now an opt-out toggle for something that should have been opt-in to begin with.
|
|
Google announced everything before its actual live event, but there were still plenty of interesting things at the company's Pixel announce event.
|
|
 Elon Musk's SpaceXAI today announced the launch of Grok Bot, a "team of always-on agents" that can complete tasks using tools, websites, and apps. Grok Bot can work in the cloud, so jobs keep running when your laptop is closed. The feature is tied to Cursor, the AI coding company that SpaceX is acquiring for $60 billion.
|
|
Anthropic will begin labeling AI-generated content created by Claude, Claude Code, and the company's API, as well as Claude models via third-party services, according to The Register.
Text generated by future Claude models will be given an invisible watermark. According to Anthropic, the watermark is embedded directly into the generated text without affecting its meaning or readability. For files, Anthropic will instead use signed metadata in accordance with the C2PA standard.
The effort is part of the company's plan to comply with the EU's AI Regulation and transparency requirements regarding AI-generated material. However, the labeling will be implemented globally for all users.
At the same time, Anthropic noted that the technology has its limitations. A label does not guarantee that material was created by Claude. Similarly, the absence of a label is not necessarily proof that the material is not AI-generated.
|
|
It's been 17 years and counting since Nemertes first wrote about the logic of integrating event response in the enterprise: bringing together the security operations center (SOC) and network operations center (NOC) at the organizational, operational, and technological levels. Needless to say, this has not happened at most organizations, although there has been a promising trend toward convergence in the monitoring and data management side of things. It's worth revisiting the issue.
Why converge?
The arguments for convergence remain pretty compelling:
Both the NOC and SOC are focused on keeping an eye on the systems and services comprising the IT environment; spotting and understanding anomalies; and spotting and responding to events and incidents that could affect or are affecting services to the business.
Both are focused on minimizing the effects of events and incidents on the business.
The streams of data they watch overlap hugely.
They often use the same systems (e.g. Splunk) in managing and exploring that data.
Both are focused on root-cause analysis based on those data streams.
Both adopt a tiered response approach, with first-line responders for "business as usual" operations and occurrences, and anywhere from one to three tiers of escalation to more senior engineers, architects, and analysts.
Most crucially: When something unusual happens in or to the environment (that router is acting funny), it can be very hard to know up front whether it is fundamentally a network issue (that router is acting funny - it has been misconfigured) or a security issue (that router is acting funny - it has been compromised) or both (that router is acting funny - it has been misconfigured and is now a serious vulnerability). Having fully separate NOC and SOC can mean duplicative work as both teams pick something up and examine it. It can mean ping-ponging inciden
|
|
