|
Back at WWDC 2025, Apple revealed that it was planning to allow CarPlay users to watch video via AirPlay in their vehicles while they are not driving, and the first beta of iOS 26.4 suggests the feature may be nearing availability.
|
|
New trade-in data indicates that Apple's iPhone 17 Pro Max has rapidly become the single most traded-in smartphone.
|
|
With iOS 26.4, CarPlay users will be able to use third-party chatbots with ?CarPlay?. AI services like Claude, Gemini, and ChatGPT will be accessible through the ?CarPlay? system for the first time.
|
|
Apple, Garmin, Samsung, Google or Amazfit? I compared each one against a chest strap for heart rate accuracy and found a clear winner.
|
|
There is a long list of new features in the iOS 26.4 beta, many of which we highlighted yesterday, but we've since discovered several other smaller changes that Apple made in the software.
|
|
In iOS 26.4, Apple added an Average Bedtime metric to the Sleep section of the Health app, letting users better monitor how bedtime impacts sleep quality.
|
|
NEW RESOURCES Fast Company: This simple site makes it easy to track ICE's actions. "The database…includes continuously updating sections that track statistics like the total number of people currently detained by the […]
|
|
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
|
|