|
 We're likely about a month away from when Apple will launch new iPhone models, and color has been a major topic of discussion. There's going to be a dramatic new color for the iPhone 18 Pro and ?iPhone 18 Pro? Max, but Apple plans to play it safe with the foldable iPhone.
|
|
 In iOS 27, new Shared Albums you create in the Photos app retain full-resolution quality for the first time, but they now eat into your iCloud storage - and that includes any items added by other people invited to contribute.
|
|
 The leaker known as "DuanRui" today shared video and images of cases designed for the iPhone 18 Pro Max, potentially offering an early look at some of the new color options for Apple's official accessories.
|
|
Google has used AI tools to detect and patch 1,072 vulnerabilities in versions 149 and 150 of its Chrome browser, the company announced in a blog post.
That's more vulnerabilities patched than in the previous 23 updates combined, according to Bleeping Computer.
One vulnerability detected by AI had been present in Chrome for 13 years but, for some reason, had never been detected by Google's developers.
To further strengthen security, Google now plans to release new security patches for Chrome every week; down the road, it might even release two updates per week if needed.
|
|
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
|
|
