Apple’s Rumored ADT Tie-Up Signals Serious Smart Home Ambitions

Apple stands on the verge of a major move into professional home installation and security. Rumors point to a partnership with ADT, the largest U.S. home security provider, that could be announced as soon as Tuesday. The timing aligns with Apple’s “Welcome home” media event in New York. And the clues come from an unusual source: recent ADT job postings and new technician hires.

According to MacRumors, the company has posted “Low Voltage Technician” positions across multiple U.S. cities since July. New employees received iPhones for work. Standard ADT technicians use Android devices. Several hires signed nondisclosure agreements. The level of secrecy matches Apple’s typical practices. One new hire expected role details in September. Management pushed that back to October. That delay lines up with Apple’s repeated postponements of its smart home hub launch.

Some of these technicians learned their roles would involve home automation and in-home installation. The connection seems clear. Apple plans to introduce a new smart home hub with both tabletop and wall-mounted versions. The wall-mounted model could prove tricky for average consumers. Professional installation by ADT technicians would solve that problem neatly. The Apple Post reported the same pattern of clues, noting the hires appear geared toward supporting Apple’s upcoming products rather than traditional ADT security work.

But the partnership hints run deeper. ADT struck a deal with Google in 2023 for home security services tied to Nest devices. That agreement reportedly expires this year or next. People familiar with the matter say it won’t be renewed. Features once offered on Nest hardware were dropped earlier this year. The door now opens for ADT to align with Apple instead. Whether the arrangement stops at installation or extends to full security monitoring remains unknown. Either way, it would give Apple instant access to a nationwide network of trained professionals.

This potential ADT collaboration doesn’t arrive in isolation. Apple has also teamed with LG Electronics on an array of smart home accessories. The Japan Times, citing Bloomberg reporting by Mark Gurman, detailed the unusual arrangement. The companies co-developed products that will carry the LG brand. LG will handle manufacturing and customer support. The lineup includes an LG Video Doorbell Wired, LG Floodlight Cam, LG Outdoor Cam Plug-In, LG Indoor Cam Plug-In, LG Smart Deadbolt Lock, LG Smart Thermostat and LG Temperature Sensor. These devices will work alongside Apple’s new hub, an upgraded HomePod mini and a refreshed Apple TV 4K.

The hub itself promises more than basic control. It should manage smart home accessories, handle security monitoring, display calendars and photos, play music and support FaceTime calls. A screen-equipped version could even recognize users and tailor its interface accordingly. Such features represent a reboot for HomeKit, the platform Apple introduced in 2014 that has struggled to gain broad traction against Amazon and Google offerings.

Professional installation makes strategic sense here. Wall-mounted hubs and outdoor cameras often require wiring expertise. Many homeowners prefer not to tackle that themselves. ADT’s existing infrastructure could lower barriers to adoption. Customers might buy the hardware and add professional setup as an option at purchase. The approach mirrors how some premium appliance brands offer white-glove service.

Yet questions linger about scope. Does Apple want ADT only for setup? Or does it see value in monitored security services? Earlier reports suggest Apple eyes its own privacy-focused home security offerings for 2027. Those could include AI-based sensors that monitor environments without constant video recording. A dedicated monitoring service might follow. Partnering with ADT could accelerate that timeline or provide backup expertise while Apple builds internal capabilities.

Competition in this space runs hot. Amazon’s Ring and Google’s Nest dominate consumer mindshare. Both offer cameras, doorbells and professional monitoring options. Apple has emphasized privacy in its HomeKit Secure Video, which stores footage end-to-end encrypted in iCloud. Recent upgrades add Apple Intelligence features like motion summaries, though they come at a steep subscription cost. A tie with ADT could blend Apple’s software strengths with established monitoring operations.

The “Welcome home” event carries symbolic weight. Apple rarely hosts product launches in New York these days. Choosing that location for a home-focused announcement suggests confidence. Media invitations went out last week. Expect hardware reveals alongside any partnership news. Even if the ADT deal stays unmentioned on stage, the groundwork appears laid.

Investors have watched Apple’s services business grow. A successful smart home push could add recurring revenue through hardware, subscriptions and installation fees. The company already charges for iCloud storage tied to HomeKit cameras. Expanded monitoring would create another stream. But execution matters. Past smart home efforts faced criticism for limited third-party support and complex setup. Professional installation might address one key pain point.

ADT gains from any deal too. Its Google partnership showed signs of strain. Aligning with Apple offers fresh technology and access to millions of iPhone users already inside the Home app. The company’s technicians could shift toward supporting premium smart home ecosystems. That might command higher service fees or create upsell opportunities.

Of course, nothing is confirmed until Apple speaks. The clues, while compelling, remain indirect. Job postings and delayed briefings could point elsewhere. Yet the pattern fits too well to ignore. Multiple reports cite the same sources. New hires carry Apple devices. Their training aligns with upcoming product launches. The Google contract window closes at the right moment.

Tuesday’s event will clarify much. A simple announcement could reshape how consumers think about smart homes. No longer just apps and DIY gadgets. Instead, a polished experience with expert installation and reliable monitoring. Apple has spent years refining its approach. This moment feels like the culmination of that work. The company doesn’t enter markets lightly. When it does, it aims to set new standards.

Watch for details on pricing, availability and exact partnership terms. The wall-mounted hub may drive initial demand for professional help. LG accessories could expand the appeal. And if monitoring enters the picture, Apple would challenge established players directly. The smart home has long promised convenience and security. For many households, that promise went unfulfilled. Apple’s latest effort, backed by ADT’s reach, may finally deliver on it.

from WebProNews https://ift.tt/YNkpuC8

Ubuntu Weathers Second DDoS Strike in 2026 as Web Infrastructure Takes Another Hit

Canonical’s web properties went dark for more than four hours last week. Users seeking documentation, download links or security notices found error pages instead. The company confirmed a sustained distributed denial of service attack hit its public-facing systems on October 8.

But this time the damage stayed contained. Package repositories continued to serve updates. The Snap Store stayed online. Launchpad and ISO mirrors kept functioning. Only the main ubuntu.com and canonical.com domains, along with developer portals and certain security APIs, suffered intermittent outages.

Phoronix first reported the disruption as users complained of inaccessible sites and download failures. Michael Larabel noted that Canonical’s IT team had already begun mitigation efforts. The company’s status page tracked the incident in real time. Phoronix also pointed readers to the official Ubuntu Discourse post for confirmation.

That Discourse announcement pulled no punches. “Canonical’s websites are under a sustained distributed denial of service attack,” it stated. “Our team is working diligently to resolve the incident. Please refer to our status page for up-to-date information. Some services may be intermittently unavailable.” Later updates on the same thread reported most services restored while recovery continued for a few remaining pieces. Ubuntu Discourse.

OMG! Ubuntu provided the clearest picture of scope and impact. The attack lasted four hours and twelve minutes. Canonical domains, the blog, developer.ubuntu.com, assets.ubuntu.com and the Ubuntu Security API all felt the effects. Yet critical infrastructure for actual software delivery remained untouched. PPAs, the CD image server, Launchpad, Snap Store and Ubuntu SSO continued operating normally. OMG! Ubuntu.

The contrast with May’s assault stands out.

Earlier in 2026 a far broader outage crippled more than a dozen services for days. That incident took down Launchpad PPAs, signing keys, mailing lists and the Snap Store alongside the websites. Hacktivists claiming affiliation with the 313 Team, also known as Islamic Cyber Resistance in Iraq, asserted responsibility and even attempted to extort Canonical via Telegram. TechCrunch covered the claims and the prolonged disruption.

After that spring event Canonical conducted a thorough review. Engineers hardened systems, adjusted traffic handling and improved detection. The October attack tested those changes. This time the blast radius stayed smaller. No package updates failed for users already on supported releases. Automated systems that query the security notices API experienced temporary hiccups but recovered faster.

Ubunlog highlighted one notable detail. The Ubuntu Security API and Livepatch services, tools many administrators rely on for automated vulnerability checks and kernel patching, faced disruption. Systems that poll these endpoints for advisories saw delays. Yet the company avoided the wider cascade seen in May. Ubunlog.

And the source of the latest attack? Canonical has released no attribution. No hacktivist group stepped forward on Telegram or X. The traffic pattern pointed to a volumetric assault. Automated tools flooded endpoints with junk requests until protection layers absorbed or filtered the load. Exact botnet origins or command-and-control details remain undisclosed.

Slashdot aggregated the news on October 11, driving more attention to the confirmed incident. Community discussion on X reflected a mix of frustration and relief. Many noted the quick recovery compared with the spring ordeal. Some system administrators reported they never noticed the outage because their mirrors and local caches kept working. Slashdot.

The episode exposes a persistent reality for open-source stewards. Ubuntu powers millions of servers, desktops and cloud instances. Its infrastructure draws constant probes. High-visibility domains make tempting targets for anyone seeking attention or testing tools. Yet the distribution’s decentralized nature, with mirrors worldwide and package managers that tolerate brief central outages, limits real-world harm.

Canonical has not published a detailed postmortem. No new technical blog has appeared detailing the mitigation techniques that succeeded this round. The status page now shows all systems operational. Discourse threads have quieted.

Still, questions linger. How much of the improvement came from better DDoS scrubbing services? Did changes to edge caching or anycast routing play a role? Will future releases include stronger rate limiting on API endpoints that administrators query frequently? Enterprise customers who pay for support likely received more private answers.

One thing appears clear. The May lessons produced measurable gains. Four hours beats multiple days. Narrow impact beats widespread failure. For an organization that ships software to a global audience and maintains the most popular Linux distribution, that counts as progress.

But the attacks keep coming. Whether from script kiddies, hacktivists or more organized actors, public infrastructure faces ongoing pressure. Canonical will almost certainly continue refining defenses. The rest of the Linux world watches. Because when Ubuntu stumbles, even briefly, the ripple touches countless deployments.

from WebProNews https://ift.tt/UD9Z6ri

California’s New 3D Printer Law: A Conditional Bid to Block Homemade Guns

California has added another layer to its long fight against untraceable firearms. On September 26, Governor Gavin Newsom signed Assembly Bill 2047 into law. The measure, now Chapter 461 of the Statutes of 2026, does not ban 3D printers. It sets up a future requirement for new machines sold in the state to carry built-in safeguards against printing gun parts.

Yet the safeguards do not exist yet. The entire scheme hinges on an industry standards body called ASTM International. Only if ASTM publishes technical standards for firearm-blocking technology will California’s Department of Justice move forward with rules. And even then, years will pass before any sales ban takes effect. Existing printers stay untouched. So do machines used to create movie props.

The law arrives at a moment when homemade firearms appear regularly in California crime scenes. Law enforcement recovered dozens of 3D-printed guns and machine-gun conversion devices in recent cases across counties from San Jose to Madera. These weapons lack serial numbers. They evade traditional tracing. State officials see them as a growing threat that earlier bans on ghost-gun kits failed to contain.

But the solution lawmakers chose raises hard questions. Can software reliably spot a firearm blueprint among thousands of legitimate designs? Will the added hardware slow printers or raise their price? And what happens when determined users find ways around the blocks? Those issues surfaced during legislative debate. They remain unresolved as the clock starts ticking.

Under the statute, the Department of Justice must begin quarterly checks no later than July 1, 2027, to see whether ASTM has published or adopted relevant standards. If standards appear, the department has 24 months to issue its own guidance spelling out minimum performance criteria. One year after that guidance, it becomes unlawful to sell, offer for sale, or transfer for consideration any 3D printer in California that lacks compliant blocking technology. California Legislative Information lays out the exact language.

Firearm blocking technology receives a precise definition. It means hardware, firmware or integrated measures that stop a print job unless the file has been scanned by a detection algorithm and cleared as non-firearm. The algorithm must catch designs for complete firearms or machine-gun conversion devices. Details on false-positive rates or scanning methods stay undefined for now. That task falls to future regulations.

The bill’s final form looks far narrower than its first draft. Early versions carried criminal penalties and tighter deadlines. Amendments removed some mandates after industry pushback and concerns from the Department of Justice itself about technical feasibility. The result is a conditional law. If ASTM stays silent by July 1, 2029, the department’s duty ends. No standards, no new rules. The requirement could simply expire.

New York passed similar legislation earlier. California now becomes the second and by far the largest state to try this approach. Everytown for Gun Safety praised the move. The group called California’s action a signal to the 3D-printing industry that companies bear responsibility for how their products get used. In a statement after the signing, the organization highlighted recent recoveries of 3D-printed guns and conversion devices across the state. PublicNow via Everytown.

Printer makers face practical hurdles. Many consumer machines already ship without any content-scanning capability. Adding reliable detection would demand new sensors, processors and software libraries trained on vast datasets of gun files. False positives could block legitimate prints. A hobbyist creating an e-reader case shaped like a pistol, for instance, might trigger alarms even if the object has no functional firearm parts. Articles from The Verge have illustrated exactly this problem with real designs.

Critics from gun-rights groups argue the law amounts to compelled speech and prior restraint. They note that shapes alone do not commit crimes. During hearings, opponents pointed out that existing statutes already criminalize unlicensed manufacture of firearms with 3D printers. Penal Code 29185 makes it a misdemeanor for unlicensed persons to use such machines for gun making. Yet enforcement remains difficult when production happens behind closed doors.

Even as AB 2047 moves forward, related legal action continues. On October 5 San Diego County sued filament maker Polymaker. The complaint treats certain plastic spools as firearm precursor parts because of how the company markets them to users interested in printing gun components. The suit relies on newer statutes that ban aiding unlicensed manufacture. It does not ban filament outright but tests how far marketing can stretch the definition of regulated material. AmmoLand reported the filing and its legal theories.

Industry voices worry about unintended consequences. High-end industrial printers used in aerospace or medical manufacturing could face compliance costs even if they rarely print gun files. The law allows the Department of Justice to create additional exceptions by regulation. Entertainment-industry props receive an explicit carve-out. Whether other legitimate sectors win similar treatment remains to be seen.

Supporters counter that the law targets future sales only. Owners of the millions of 3D printers already in California homes and workshops face no retrofit mandate. No one must install blocking software on machines bought last year. The focus stays on what enters the market after the rules activate. That grandfathering softens the immediate blow but leaves current devices free to print whatever their owners choose.

Technical experts remain skeptical that perfect detection is possible. Firearm files can be rotated, scaled or split across multiple prints. Clever users can rename files, encrypt them or run them through simple transformations that defeat hash-based filters. Defense Distributed founder Cody Wilson has already released tools designed to bypass similar requirements in New York. He calls one such workaround “Hochulization” after the state’s governor. Coverage in The Verge from August detailed the emerging cat-and-mouse dynamic.

California’s law explicitly references machine-gun conversion devices alongside complete firearms. That addition reflects real-world seizures where plastic switches turn legal semiautomatic guns into illegal full-auto weapons. Yet the same detection challenges apply. A small printed part may look nothing like a finished gun yet still enable illegal function.

So the state bets on standards that do not yet exist. ASTM International, known for materials testing and manufacturing protocols, now holds unexpected influence over consumer 3D printer design. If the organization produces a workable standard that balances safety and usability, California will codify it. If not, the law could fade quietly after 2029.

Either outcome will shape national debate. Major printer manufacturers sell across all states. A California rule, once active, could push them to adopt blocking technology everywhere to simplify production lines. Or they could create California-specific models. The added cost and complexity might slow innovation or drive some companies to avoid the state’s market altogether.

For now the calendar is set. January 1, 2027, the law takes effect, though no immediate obligations arise. July 1, 2027, quarterly checks begin. The next few years will test whether industry can deliver detection technology that satisfies regulators without crippling legitimate uses. Early signs suggest the path will not be smooth.

And the printers already in circulation? They keep running. Their owners face the same legal prohibitions on unlicensed gun making they faced before. The new statute simply tries to make violation harder for the next generation of machines. Whether it succeeds depends on code that has yet to be written and standards that have yet to be agreed.

Recent coverage shows the conversation continues. TechRadar noted on October 9 that existing machines remain exempt and full compliance awaits ASTM action. TechRadar. 3DPrint.com outlined the exact timeline and the bill’s evolution from stricter proposals. The additive manufacturing community watches closely. So do gun-control advocates and Second Amendment groups. The experiment has begun.

from WebProNews https://ift.tt/RA8wYxD

Ransomware Recovery Executive Accused of Secretly Paying Attackers While Charging Victims Premiums

Zohar Pinhasi built a business on the promise of rescue. His company, MonsterCloud, positioned itself as a sophisticated alternative to capitulation. Victims facing locked servers and encrypted data heard claims of proprietary decryption technology. They paid handsomely. Many walked away with restored files.

But federal prosecutors allege something different. Pinhasi, also known as Zack Silver and Zack Green, didn’t crack the code. He simply paid the criminals. The scheme allegedly ran for five years. From June 2018 through June 2023, according to an indictment unsealed this week.

Pinhasi, 50, faces one count of conspiracy to commit wire fraud and two counts of wire fraud. A federal grand jury in the Eastern District of New York returned the indictment on Sept. 23. He appeared in Brooklyn federal court for arraignment on Oct. 8. The BleepingComputer report laid out the core accusation in stark terms: the MonsterCloud owner defrauded ransomware victims by secretly paying attackers for decryptors while claiming to use in-house technology.

The numbers tell a story of marked-up desperation. Prosecutors say Pinhasi and co-conspirators facilitated more than $8 million in ransom payments to various ransomware operators. They charged hundreds of U.S. and Canadian companies more than $19 million for recovery and remediation services. One example cited in the indictment stands out. Pinhasi allegedly paid a gang about $8,200. The victim paid approximately $150,000. Another case saw a $236,000 payment to attackers met with a $380,000 bill to the client.

But the deception ran deeper than pricing. MonsterCloud contracts sometimes disclosed the possibility of communicating with or paying cybercriminals. That language offered a thin layer of transparency. Yet the company’s marketing told a different tale. Customers believed they bought advanced technical recovery. Instead they funded direct ransom transfers dressed up as innovation.

And the proof-of-recovery tactic? Prosecutors claim MonsterCloud used decrypted sample files provided by the ransomware groups themselves. These “recovery proofs” convinced panicked executives that proprietary tools had succeeded. The files came straight from the attackers. No magic algorithm. Just a transaction.

The Register first highlighted the case with a focus on the fixer who claimed decryption power but allegedly defrauded clients instead. Its coverage noted how the scheme preyed on organizations already reeling from attack. The Register article captured the human cost. Victims sought help. They received what amounted to an expensive middleman service.

Recent developments add context to a troubled industry. On Oct. 7, news emerged of another alleged double-cross inside ransomware circles. An affiliate of The Gentlemen ransomware operation reportedly diverted victims to his own leak site, keeping proceeds. CloudSEK researchers detailed the betrayal, which involved novel use of AI tools in attacks. The Cybernews story from Oct. 7 described exposed infrastructure holding 50TB of data from more than two dozen victims.

These incidents expose fractures in the ransomware economy. Recovery firms occupy a gray zone. Some deliver genuine technical breakthroughs. Others act as paid intermediaries. The line blurs when marketing emphasizes secret sauce that doesn’t exist. Organizations under duress make decisions fast. They rarely pause to verify capabilities.

Pinhasi’s alleged operation exploited that pressure. Companies hit by ransomware often face immediate operational collapse. Downtime costs mount by the hour. Insurance policies sometimes cover ransom payments but push for professional negotiators or recovery specialists. MonsterCloud filled that role for many. Its pitch sounded legitimate. The results looked successful. Files returned. Systems restarted.

Yet the indictment paints a picture of systematic overcharging. The gap between ransom paid and fees collected created substantial profit. Prosecutors documented the pattern across numerous victims. Hundreds of organizations. Millions in alleged excess charges. The scheme didn’t require sophisticated malware development. It required trust. And access to desperate customers.

Broader patterns emerge when examining related cases. Earlier this year, a ransomware negotiator received a 70-month prison sentence for feeding confidential client information to the BlackCat gang. Angelo Martino betrayed victims while employed by DigitalMint. He helped extract higher payments. The Justice Department detailed how his actions contributed to more than $75 million in ransoms from five victims. That case, reported across outlets including PYMNTS in July, revealed insiders working both sides.

The MonsterCloud allegations differ in method but share a theme. They involve profiting from fear. They erode confidence in the very services meant to mitigate harm. Ransomware groups thrive when victims see no alternative. Recovery providers who secretly collaborate with attackers reinforce that perception.

Free decryption tools exist for certain families. Projects like No More Ransom have released dozens of working decryptors over the years. Law enforcement operations occasionally yield master keys. The FBI provided one after disrupting BlackCat. Yet many strains remain resistant. Victims without backups face stark choices.

Industry observers note the lack of regulation around ransomware recovery services. Anyone can advertise decryption expertise. Few mechanisms exist to verify claims before payment. Contracts may include disclaimers. Marketing materials often do not. The result leaves room for exactly the conduct prosecutors now allege.

Pinhasi has not yet entered a plea. His attorneys did not respond to requests for comment in initial coverage. The case remains in early stages. Trial dates have not been set. If convicted, he faces significant prison time. Wire fraud carries up to 20 years per count.

The charges arrive at a moment of heightened scrutiny. Ransomware incidents continue despite law enforcement wins. Groups rebrand. Affiliates shift between operations. Recovery firms multiply. Some provide real value through negotiation expertise, forensic analysis, and restoration support. Others appear to function primarily as payment processors with premium pricing.

Organizations evaluating recovery partners now face additional questions. Does the provider maintain independent technical capabilities? Can they demonstrate decryption without attacker involvement? What exactly does the contract permit regarding communication with threat actors? The MonsterCloud case, if proven, shows how easily those distinctions can be obscured.

Short-term relief. Long-term consequences. Victims pay for speed. They may sacrifice transparency. The alleged fraud didn’t prevent data recovery. It simply made the process far more expensive than necessary. And it undermined the premise that technical solutions could replace ransom payments.

So the indictment lands as both specific accusation and broader warning. The ransomware recovery market demands skepticism. Claims of proprietary decryption deserve examination. Organizations in crisis still need help. They just need to understand exactly what kind of help they’re buying.

Prosecutors built their case on transaction records, communications, and victim statements. The pattern allegedly repeated across years and hundreds of incidents. Pinhasi didn’t invent the model. He stands accused of perfecting it at scale. The outcome of his case could shape how the industry polices itself. Or how regulators step in.

from WebProNews https://ift.tt/HsxY6Ml

Anthropic’s $100 Million Bet on Human Capital to Unlock Enterprise AI

Anthropic announced last week it would commit $100 million to train 10,000 engineers capable of turning its Claude models into production systems inside large organizations. The initiative, named Claude Frontier Academy, targets what the company sees as the primary obstacle to widespread corporate AI adoption: a shortage of skilled people who understand both frontier models and the messy realities of enterprise technology, security and operations.

The program draws directly from medical residency models. Participants, nominated by their employers, begin with multi-day in-person training in San Francisco, New York or London. They work through a simulated enterprise deployment. That exercise covers selecting the right use case, conducting security reviews and managing handover. A graded practical assessment follows. Those who pass earn a Claude Resident Engineer badge and advance to a 12-week residency. During that period they lead a real Claude implementation at their own company. Anthropic engineers provide support. Peers in the cohort share lessons. A final assessment determines who receives the Claude Frontier Deployed Engineer credential. The first badges are expected in early 2027.

“Claude Frontier Academy trains people the way our own engineers learn, and we want those who graduate to set the standard for how AI gets built inside a business,” said Steve Corfield, Anthropic’s global head of business development and partnerships, in the company’s official announcement.

The first cohorts already run in those three cities. They include engineers from Accenture, Bain, Capgemini, Commonwealth Bank of Australia, Deloitte, McKinsey, Morgan Stanley and Novo Nordisk. Accenture alone plans to train roughly 30,000 professionals using the academy’s resources and related tools. That number exceeds Anthropic’s own 10,000 target for Frontier Deployed Engineers by the end of 2027. The scale signals serious intent from consulting giants to embed Claude deeply into client work.

Shambhavi, Anthropic’s head of strategy and operations for partnerships, told CNBC that customer feedback drove the effort. “We hear our customers and partner organizations say, we need more people who can bring together familiarity with the enterprise tech and business context and combine that with the highest level of AI fluency to solve the problems that need solving.”

This focus on deployment talent isn’t new. Palantir popularized the forward-deployed engineer role years ago. Those specialists embed directly with clients to translate technology into operational results. Anthropic now applies a similar concept to generative AI. The difference lies in the model. Claude represents one of the most capable systems available. Yet models alone don’t deliver value. Integration, governance, risk management and measurable business outcomes do. Few engineers possess that full combination of skills.

Anthropic has already issued more than 175,000 Claude certifications across 46,000 companies through its broader partner network, according to a TechRadar report published Tuesday. The new academy goes further. It aims to create a smaller cadre of elite practitioners who meet the same standards as Anthropic’s internal team. Graduates won’t simply prompt the model. They will design secure, scalable systems that fit inside regulated environments.

The timing carries weight. Anthropic continues rapid growth. A leaked IPO prospectus cited in Dealroom News showed nearly $4.6 billion in revenue last year alongside an operating loss exceeding $8 billion. The company prepares for what could become one of the largest public offerings in technology. Success depends on converting hype into contracted revenue from enterprises. That conversion happens through implementation, not demonstrations.

Consulting and financial firms stand to gain the most. McKinsey, Deloitte, Bain and Morgan Stanley already nominate participants. They see an opportunity to offer AI transformation services at scale. Trained engineers become force multipliers. One certified specialist can lead projects that influence dozens of clients. Accenture’s ambitious internal target hints at the multiplier effect the industry anticipates.

But questions remain. The $100 million commitment sounds substantial. Spread across 10,000 engineers it suggests roughly $10,000 per person. That figure comes from arithmetic in FourWeekMBA’s analysis and assumes the entire sum goes directly to training. Actual costs likely include instructor time, facilities, ongoing support and credentialing infrastructure. Anthropic has not detailed the breakdown.

Nor has the company explained selection criteria beyond nomination. Not every engineer will succeed. The residency demands proven ability to deliver under real constraints. Failure rates in similar medical-style programs can run high. Those who drop out still consume resources.

Competitors watch closely. OpenAI, Google and others face the same enterprise friction. Some partner with consulting firms. Others build internal services organizations. Few have pledged this level of direct investment in customer talent. The move risks creating a moat. Engineers credentialed on Claude may prefer to keep using it. They bring institutional knowledge back to their firms. That knowledge favors Anthropic’s models in future decisions.

Recent coverage highlights the program’s potential reach. A Channel Insider article from last week noted the implications for channel partners. Trained engineers inside consultancies could drive significant Claude usage across thousands of client projects. The credential itself, issued by the model provider, carries unusual weight. It signals both technical proficiency and alignment with Anthropic’s safety and deployment philosophy.

Discussions on X reflect a mix of optimism and realism. One post noted the narrowing performance gap between leading U.S. and Chinese models. If capabilities converge, deployment expertise becomes the differentiator. Another highlighted that Anthropic chose to spend on people rather than additional compute. The constraint has shifted. Models improve. The bottleneck now sits in organizations that lack the know-how to use them responsibly and effectively.

Anthropic’s earlier $100 million commitment to the Claude Partner Network, mentioned in several reports, focused on training, support and joint development. The academy appears additive. It concentrates on the highest-skill tier. Together they form a funnel. Broad certifications create awareness. The academy develops experts who drive actual adoption.

Success will show in measurable outcomes. How many of the 10,000 complete the program? How many deployments follow? Do those projects deliver clear return on investment? Those metrics will matter more than the headline number. For now the announcement sends a clear signal. In the race to dominate enterprise AI, Anthropic bets that investing in the humans who deploy the technology matters as much as improving the technology itself.

The first Frontier Deployed Engineers should earn their badges in the coming months. Their work will test whether this residency model translates from medicine to software. If it does, other AI companies may follow. The talent shortage isn’t going away. Someone has to train the people who make the models useful.

from WebProNews https://ift.tt/AVNWI7m

Diesel at $6.53 a Gallon Pushes 16 Trucking Firms Into Bankruptcy in 30 Days

Expensive fuel. Thin margins. A sudden wave of court filings. Sixteen trucking companies sought bankruptcy protection in a frantic 30-day period this fall as diesel prices shattered records. The failures hit small operators hardest. Yet they signal deeper trouble across an industry that moves the majority of America’s goods.

One carrier after another walked into federal court. From single-truck owners in California to fleets with dozens of power units in Texas and Illinois. The filings came as the national average diesel price climbed to an all-time high of $6.53 per gallon on Sept. 22, according to AAA. That’s up more than 70% from a year earlier. A full tank for an 18-wheeler suddenly topped $900 in many places. Some drivers reported paying over $1,000.

The Breaking Point for Small Carriers

Xoco Transport filed Chapter 11 on Sept. 16. The Hidalgo, Texas produce hauler listed assets of $2.2 million against $3.3 million in liabilities. Its annual revenue had already slipped from $15.4 million in 2024 to $11.3 million in 2025, reported Securitas Global Risk Solutions. The company hauled for Mirasoles Produce USA. Fuel costs simply overwhelmed its ability to pass increases to shippers fast enough.

Globemaster Incorporated followed the next day. The Bolingbrook, Illinois carrier with 51 power units reported liabilities between $1 million and $10 million. It filed in the Northern District of Illinois. Other Chapter 11 cases included Jett Transport & Materials in Somerset, Texas, CLJ Transporting, an Amazon delivery partner in Florida, Mill Creek Logistics-Illinois, RP Hay Hauling, Truckload LLC operating as Expedite Express, and Pacer Transport. Eight companies took this reorganization route. Eight more chose Chapter 7 liquidation.

But the numbers tell only part of the story. The American Transportation Research Institute put average truck operating costs at $2.336 per mile in 2025. That marked a 3.4% jump from the prior year and the highest figure in its records. Trucking profit margins often sit below 1%. There’s no cushion when fuel, the largest variable expense, spikes without warning. And this spike carried geopolitical weight. Disruptions tied to conflict with Iran and related oil market turmoil drove much of the increase, multiple outlets noted.

Drivers felt it immediately. At a Flying J Travel Center off Interstate 10 in Orange, Texas, one operator paid $944.44 to fill 151 gallons. A year earlier the same purchase ran about $500. “We have to do what we have to do,” he told a reporter. “I can’t sell the truck. What am I going to do if I sell the truck?” The Wall Street Journal captured that exchange in early October reporting on the crisis. Some truckers parked rigs altogether. Others ran fewer loads. The Owner-Operator Independent Drivers Association warned more failures loomed if prices stayed elevated.

California operators faced even steeper pain. Local diesel reached $8.44 per gallon in spots. Southern California truckers grimaced at the pump. Vendors stretched payments to 30 or 60 days, starving carriers of cash flow. A&B Transportation in Lake Elsinore, Alvand Transportation in Glendale, and Rothchild Transportation in South Gate all filed recently, according to Orange County Register. Eric Sauer, CEO of the California Trucking Association, pointed to high state taxes and regulatory burdens compounding the fuel shock.

This cluster of failures followed an earlier wave. At least 21 transportation and logistics companies filed between late July and late August. Overall U.S. corporate bankruptcies stand at a 16-year high. Trucking employment has dropped too. The sector counted 1.47 million workers in August, down 118,000 from its 2022 peak, per Bureau of Labor Statistics data cited by industry analysts.

Yet freight rates have begun to rise. Cass Information Systems reported its Truckload Linehaul Index up 8.6% year-over-year in July and 11.3% in August. Spot and contract rates firmed after years of weakness. The problem? Many carriers operate under contracts set months earlier. They can’t adjust pricing quickly enough to match today’s fuel costs. Excess capacity from prior years still lingers in parts of the market. Smaller players lack the scale to weather the mismatch.

The driver shortage adds another layer. Companies struggle to find qualified operators even as payrolls shrink. Those who remain demand higher pay. Insurance premiums climb. Maintenance costs follow. All of it lands on balance sheets already stretched by fuel. One industry report after another ties the bankruptcies directly to this combination. FreightWaves first tallied the 16 filings by reviewing court records and carrier data. Subsequent coverage in Newsweek, Food Trade News, and others expanded on the pattern.

Texas felt the impact sharply. At least five trucking firms there filed since tensions escalated with Iran. Governor Greg Abbott declared a diesel disaster across all 254 counties late in September. The order eased rules on dyed diesel, truck weights, and emissions to free up supply. State diesel averaged around $5.86 per gallon at the time. Still high. Still damaging.

Broader economic ripples appear inevitable. Higher transportation costs flow into the price of food, consumer goods, building materials, and fuel itself. Groceries already reflect some pressure. Supply chains tighten when capacity disappears. If more carriers park trucks or exit, a genuine shortage of hauling power could develop before rates fully adjust.

Some survivors hunt every efficiency possible. They idle less. They optimize routes with better software. A few negotiate harder with shippers for fuel surcharges. But the smallest operators enjoy few such options. They pay at the pump today and hope for payment from customers weeks later. When diesel jumps 70% in a year, the math fails fast.

Recent coverage shows the distress continues. Raw Story highlighted how drivers adopt extreme cost-saving measures while bankruptcies mount. X posts from early October echoed the concern. One noted Texas’s disaster declaration alongside ongoing fuel exports. Another tallied the job losses at more than 250 from the initial 16 filings alone.

The industry has seen volatility before. Fuel spikes. Rate crashes. Driver turnover. This episode stands out for its speed and concentration. Sixteen carriers in 30 days. Many with long operating histories. Their departures remove equipment and expertise from the road at a moment when demand signals show tentative improvement.

What comes next depends on how long prices remain aloft. G-7 nations agreed to release oil from emergency stocks. Refineries push to maximize distillate output. Yet seasonal maintenance and regional stockpile issues, especially in the Midwest, limit quick relief. Carriers that endured the past few difficult years now face a test many won’t pass.

One thing looks clear. The trucking sector’s fragile balance between revenue and expenses has broken under current fuel pressure. Consolidation likely accelerates. Larger players with hedging programs or stronger balance sheets may absorb routes left behind. Smaller outfits, the backbone of much specialized and regional hauling, face an existential squeeze. And every American who buys groceries, clothes, or electronics will pay the eventual price.

from WebProNews https://ift.tt/wud4gVL

AWS DevOps Agent Gains EventBridge Hooks and OpenSearch MCP Ties for Automated Incident Loops

AWS has released two new integration patterns for its DevOps Agent. One routes investigation events to third-party systems through Amazon EventBridge and Lambda. The other connects the agent directly to Amazon OpenSearch observability data via the Model Context Protocol. Both arrived on October 2. They address a common pain point. Teams run autonomous agents yet still copy findings into Jira tickets by hand or wait for humans to chase logs at 3 a.m.

The first pattern, detailed by AWS DevOps & Developer Productivity Blog, uses the agent’s native EventBridge output. AWS DevOps Agent emits events with source aws.aidevops. Detail types include Investigation Created, Investigation In Progress, Investigation Completed, and others. A simple prefix match on “Investigation” captures the lifecycle. An EventBridge rule then invokes Lambda. The function creates a Jira issue on creation and appends comments on every subsequent update. No polling. No manual handoff.

Toshihiro Furuno, the post’s author, notes the design stays generic. “I use Jira as the example, but the same pattern applies to other tools with an API.” ServiceNow, PagerDuty, or any REST endpoint works with minor changes to the Lambda handler. The CDK sample deploys the rule, the function, and necessary permissions in minutes. Production teams already familiar with EventBridge see immediate value. They route the same events to Step Functions for automated mitigation or SNS for on-call alerts.

But. The real shift appears in the second pattern.

Closing the Observability Loop with OpenSearch

The companion post, “Closed-loop incident response: connect AWS DevOps Agent to OpenSearch” from the same AWS blog, shows how an OpenSearch alert becomes the trigger and the data source. Instead of paging an engineer, the alert fires a webhook to the agent’s Event Channel. The agent then uses an MCP server to query the exact indices that generated the alert. It pulls logs, traces, and metrics. It correlates them against CloudTrail events and CloudWatch data. Root cause analysis follows without human context switching.

Authors Sitaraman Vijay Krishna and Prateek Sethi outline three ways to host the MCP server. Self-managed on ECS Fargate behind a Network Load Balancer and VPC Lattice. One-click CloudFormation with Amazon Bedrock AgentCore where available. Or the built-in MCP endpoint in OpenSearch 3.3 and later. All rely on the official opensearch-mcp-server-py package. Fine-grained access control in OpenSearch limits the agent’s IAM role to read-only views of relevant indices. The setup prevents over-privileged agents while giving them live data access.

Verification uses a controlled failure. Inject a synthetic error. Watch the alert flow through SNS, the webhook forwarder, the agent, and finally the generated root cause summary. The loop completes in the same system that detected the problem. No separate dashboard. No ticket created only to be updated later.

These patterns build on capabilities released earlier in 2026. The agent reached general availability in March with support for Datadog, Dynatrace, New Relic, Splunk, GitHub, GitLab, ServiceNow, and PagerDuty. EventBridge integration and additional MCP options arrived as part of ongoing expansion. A September audit trails post on the same blog showed how to capture the agent’s full reasoning using its internal journal, EventBridge events, and CloudTrail for compliance. Teams now combine all three: trigger, investigate with live data, update external systems, and retain immutable records.

Recent coverage reinforces the momentum. An October 3 update to AWS documentation expanded EventBridge examples and clarified supported event types. No major new launches appeared in the past 48 hours, yet X discussions show practitioners already testing the Jira pattern in sandbox accounts. One thread highlighted how the prefix match on investigation events avoids noise from custom agent invocations.

The implications stretch beyond single incidents. Organizations running complex microservices or multicloud workloads gain consistent investigation depth. An alert in OpenSearch no longer starts a scavenger hunt across consoles. The agent queries the source data directly, reasons over correlated signals, and writes its findings back to the ticketing system that operations teams already monitor. Mean time to resolution drops. Context stays intact. Human reviewers focus on high judgment decisions instead of data gathering.

Security and governance teams will examine the IAM-to-FGAC mappings closely. The patterns require careful scoping. Read-only access for investigation. Explicit capability registration for each MCP server. EventBridge rules limited to specific detail types. Done right, the agent becomes a reliable extension of the operations team rather than an opaque black box.

AWS continues to ship these patterns as reference implementations rather than managed connectors. Customers adapt the CDK templates and Python MCP servers to their own stacks. That choice keeps flexibility high. It also places integration work on the user. Teams with strong platform engineering groups will move fastest. Others may wait for partners to package the patterns into Terraform modules or managed services.

Either way, the direction looks clear. Autonomous agents need two-way connections to existing tools. Outbound events for workflow continuity. Inbound data access for accurate analysis. With these October updates, AWS DevOps Agent now demonstrates both in production-ready form. Operations leaders evaluating agentic incident response will test them next. The gap between detection and resolution just narrowed again.

from WebProNews https://ift.tt/bo0rRKx