The CISA’s new strategy promises to evict hackers before they strike, with nearly 968 fewer staff to do it

Posted in Commentary with tags on October 27, 2026 by itnerd

The CISA released CISA 2030: Defend, Harden, Prevail on Oct 26, committing the agency to move from passive defense to an “aggressive, anticipatory” stance built on three pillars: leading national cyber defense, prioritizing infrastructure security and mobilizing national resilience. The Defend pillar calls for modernizing operational technology, improving asset visibility and anomaly detection, and strengthening supply chain integrity.

Jason Brown, Director of Customer Advisory Counter Fraud Lead, iCOUNTER

“CISA 2030 is an honest strategy. It accepts that intrusions will happen and commits the agency to an anticipatory stance. Detect adversaries early, evict them decisively, and remove footholds before they are weaponized. That is exactly the right goal.

The gap is the third party. The strategy treats supply chain as a question of technology and software integrity, but adversaries are not waiting for a flawed product. They are compromising the service providers, platforms, and partners that organizations already trust, and using that access to reach the real target. Verizon’s 2026 Data Breach Investigations Report found third parties involved in 48% of breaches, up from 30% a year earlier.

CISA is also asking for an intelligence to operations pipeline, and that is the right instruction. Intelligence that only informs is not enough. It has to drive action, with remediation attached, at machine speed. As CISA narrows its focus and pushes more action to the local level, owners and operators will carry more of that mission themselves. The organizations that extend it across their third party ecosystem will be the ones that stop the compromise before the incident reaches them.”

Everyone should take time to read it and doing all things possible to make sure that are not pwned by threat actors. Ever. Even with their staffing challenges.

UPDATE: More commentary has come in:

John Strand, Owner, Black Hills Information Security:

“I like almost everything CISA says in this release. But as always, the devil is in the details. Couple that with the immense budget cuts CISA has had to deal with, and achieving this mission becomes exceedingly difficult.

“We’re talking about thousands of municipalities and critical infrastructure organizations that need protection under this umbrella. Every single one needs money. Every single one needs resources. And every single one needs help upgrading aging infrastructure.

“That takes more than a press release.ㅤ

“I like the direction and the renewed focus on critical infrastructure. But I think everyone should pause, take a deep breath, and wait to see when the money actually starts flowing and how it gets allocated.”

ㅤ

Ryan McCurdy, Vice President of Marketing, Liquibase:

“CISA’s new strategy reinforces an important reality: protecting critical infrastructure requires securing not just the software organizations deploy but the changes that software makes to critical systems.

“Databases underpin essential services across financial institutions, healthcare, energy, and government. Yet database changes often lack the same automated security checks, policy enforcement, and visibility applied to application code.

“As AI accelerates software development, that gap becomes increasingly consequential. Organizations need to validate database changes before deployment, enforce consistent policies, detect configuration drift, and maintain a clear record of what changed, when, and by whom.

“CISA is right to prioritize software security and operational resilience. Extending those principles to the database layer is an important step toward protecting the integrity and availability of the systems Americans depend on.”

Apple Responds To “Crackgate”…. Too Bad There’s A Second Video Out There

Posted in Commentary with tags on October 27, 2026 by itnerd

Apple has finally responded to the iPhone Duo controversy known as “Crackgate”. Which I wrote about here and here. Via 9to5Mac:

“The response to iPhone Duo from early users has been incredibly positive, and we are seeing exciting things from developers who are rapidly updating their apps to take advantage of its unique form factor. We are aware of an issue impacting the inner display on a small number of iPhone Duo units. If users experience issues with their iPhone Duo display, they should contact AppleCare for a replacement.”

Pretty short statement. But honestly, at least they said something. Now it is impossible to say how many units have this issue. Or how it compares to say Samsung in this category. But because of the volumes that Apple tends to sell in terms of phones, if even 1% of units have in issue, it’s a “gate”.

Having said that, YouTuber JerryRigEverything has put out a second video where he clearly lays the blame for this issue on Apple’s doorstep. I won’t spoil things for you but you can watch the video here:

Is “Crackgate” overblown? Sound off in the comments.

Finance AI Hyphenate raises $45M as customer + revenue growth rallies in 1 year

Posted in Commentary with tags on October 27, 2026 by itnerd

The first wave of finance AI helped teams work faster. The next is taking responsibility for the work itself. Hyphenate, the autonomous finance platform for the office of the CFO, today announced a $45 million Series A led by Nexus Venture Partners, with participation from B Capital and existing investors including Foundation Capital, BoldCap and Gaia Ventures.

Inside Hyphenate customers, agents are already reconciling cash, processing sales orders, running invoicing, maintaining subledgers and moving the close forward, with finance teams stepping in only where judgment changes the outcome. The round, which brings total funding to $54 million, comes less than a month after Maximor rebranded to Hyphenate, as customers expand its use across the office of the CFO. The company will use the capital to take its agents deeper across the finance function and into strategic finance.

12 months from seed to 86x

Hyphenate raised a $9 million seed one year ago to take repetitive work off finance teams. Since then, the company has passed multi-million-dollar ARR, its agents have taken on work across hundreds of entities, thousands of bank accounts and millions of transactions every day, and customers report 90% less repetitive finance work and 75% fewer audit exceptions. The more telling number is what customers do next: 40% expand within their first year, several by two to three times, and the average customer runs six modules.Companies are handing the system larger parts of finance once it has proved itself in one workflow.

What that looks like in production

The expansion is now visible in production, at companies where finance errors carry real cost.

Mini Melts USA, the consumer goods company, runs Hyphenate agents on top of its SAP environment for orders, invoicing and refunds. Within three months of going live, the company was getting back 16,640 hours of finance work a year.

HiBid, one of the largest online auction platforms in North America, has run more than $2.5 billion in GMV through full order-to-cash automation on Hyphenate. Invoicing, collections and cash application across that volume now run as a single continuous process, and the company has cut its month-end close from three weeks to one day.

Groupon, the Nasdaq-listed marketplace, is replacing legacy and home-grown systems with Hyphenate across treasury, order-to-cash and more than a dozen subledger processes. “As a public company, we run finance at a scale where every number has to stand up to scrutiny: millions of transactions, multiple currencies and markets, and auditors who need the evidence behind all of it. We’re replacing legacy and home-grown tools with Hyphenate because it’s built for that bar, and we see it becoming the AI foundation for our entire finance organization,” said Rana Kashyap, CFO of Groupon.

How Hyphenate works

Hyphenate sits on top of the ERP, banks and other systems a company already runs and connects them into a single shared finance context. The business keeps its systems of record and gains a layer that can act across all of it.

On that layer, agents work across five areas of finance: order-to-cash, treasury, GL accounting, procure-to-pay, and reporting and insights. In practice that covers revenue recognition, invoicing, collections, cash reconciliation, accruals, subledgers, AP, close and board reporting.

What sets the system apart is that it’s self learning. Instead of relying on forward-deployed engineers to build bespoke agents for each customer, Hyphenate trains on a company’s historical spreadsheets, emails and system logs, then replays past months to pick up the edge cases traditional software never handled: the tribal knowledge that has kept finance manual. From there, it gets better the longer it runs. An exception resolved during one close becomes precedent for the next. A policy decision made once is applied every time the same situation appears. Every action carries its evidence with it, so the output is audit-ready by default. Month by month, the share of routine work handled autonomously rises, and the finance leader’s involvement narrows to the decisions that require judgment.

The trust threshold is moving

Finance has been one of the hardest functions for AI to enter autonomously. Research commissioned by the company earlier this year found that 96% of CFOs saw freeing teams for strategic work as AI’s biggest benefit, while only 14% completely trusted AI to produce accurate accounting data independently. Ninety-seven percent said human oversight was critical.

Hyphenate’s growth suggests a path through that tension. Autonomy does not require giving an AI system unrestricted control. It requires giving it responsibility within clear boundaries, preserving evidence behind every action and involving a human at the moments where judgment changes the outcome.

What’s next

The Series A gives Hyphenate the capital to scale even faster as it pushes its agents deeper into every corner of the finance function. The end state is a company whose finance operations run themselves, continuously and with evidence attached to every action, while the team spends its time on the decisions that actually move the business. And because Hyphenate executes the work itself, it is building something no reporting tool can: a live, verified picture of how money really moves through a business, which the company sees becoming the foundation for forecasting and for every capital decision a CFO makes.

Bitdefender Launches GravityZone Exposure

Posted in Commentary with tags on October 27, 2026 by itnerd

Bitdefender today announced GravityZone Exposure Management, an advanced solution that gives organizations a comprehensive view of threat risk exposure across their internal and external attack surfaces, reveals the most impactful weaknesses, and remediates them. It consolidates findings across the entire environment into a single view, reducing complexity for lean security teams as AI significantly speeds attack cycles.

For many organizations, the challenge is not simply finding vulnerabilities but knowing which ones matter and having the resources to address them without disrupting everyday business operations.

In a global survey of 1,200 cybersecurity practitioners, the top barriers to reducing the attack surface were high overhead in maintaining hardening rules and exceptions (38%), fear of operational disruption (35.4%), and resource constraints (34.6%). Consolidation addresses that burden, and Gartner® predicts, “By 2028, at least half of the exposure management market will consist of unified exposure management platforms (UEMPs).”¹

GravityZone Exposure Management addresses those barriers as an add-on to Bitdefender GravityZone, a unified security, risk management, and compliance platform. The platform delivers advanced endpoint protection, including endpoint detection and response (EDR), extended detection and response (XDR), cloud-native security, and GravityZone PHASR (Proactive Hardening and Attack Surface Reduction), a first-to-market dynamic attack surface reduction innovation. GravityZone also provides deep security context for detections and a direct path to Bitdefender Managed Detection and Response (MDR) services.

GravityZone Exposure Management offers a simple path to discover, prioritize, and mitigate threat exposure. Once enabled, it begins identifying and ranking risk automatically, giving security teams a clear starting point and guided recommendations for remediation and continuous attack surface hardening.

Key Benefits:

  • Increase Threat Visibility and Close Attack Vectors — Proactively discover unpatched operating system and third-party vulnerabilities, insecure settings, and risky user behavior on endpoints. External Attack Surface Management (EASM) monitors internet-facing assets for shadow IT, misconfigured services, and exposed subdomains. Security teams receive risk rankings, prioritization guidance, and posture improvement tracked over time.
  • Trace Attack Paths to Critical Assets — Map vulnerabilities and exposures to possible routes an attacker would follow to compromise sensitive data, privileged accounts, financial, and other core business systems. Link identities to see the potential impact of a breached account, then act on the highest-risk steps first.
  • Apply Dynamic Hardening to Manage Excessive Privileges — Baseline and monitor user behavior to autonomously restrict legitimate tools that living-off-the-land (LOTL) attacks abuse, such as PowerShell and Windows Management Instrumentation Command-line (WMIC). Block these attacks at the source without maintaining static hardening rules.

Cybercriminal use of AI has increased both the speed and volume of attacks, flooding security teams with more alerts than they can properly investigate. GravityZone applies a preemptive approach to critical attack surfaces, including business AI adoption, to close gaps and block threats before they reach detection and response or other defenses.

Availability
Bitdefender GravityZone Exposure Management is available now for new and existing customers on Windows, with support for additional operating systems planned. It comes as an add-on to GravityZone Business Security Enterprise (and higher) or as a standalone offer that runs alongside existing endpoint security, with no separate tool, agent, or console to staff. For more information, visit the website.

¹Gartner, Technology Disruption Curve: Preemptive Strategy and Adaptive Resilience Will Disrupt Exposure Management, Esha Bhatia, 22 April 2026. GARTNER is a trademark of Gartner, Inc. and/or its affiliates.

When security cameras become surveillance tools

Posted in Commentary with tags , on October 27, 2026 by itnerd

When the cameras you install to protect your organization become a way for someone else to watch you, the security implications go well beyond video footage.

Recent reports that hackers accessed Dahua surveillance cameras and recorders in Ukraine, including changing settings and creating unauthorized accounts, raise bigger questions about IoT security, exposed devices and the risks of turning everyday connected technology into an intelligence-gathering tool.

I have four cybersecurity experts offering perspective on the story for your consideration, including why connected devices are so often overlooked, how compromised cameras can expose an organization’s people and security operations, how attackers can exploit the connections between physical and cyber infrastructure, and how camera networks can become powerful intelligence assets when their data is aggregated.

Darin Fredde, Sr. Director of Technical Marketing Engineering, Ridge Security (www.ridgesecurity.ai)

“I’ve seen the broader risk firsthand during several authorized, full-scope adversarial emulation engagements. While the techniques differed from those reported in Ukraine, the principle is the same. Compromising surveillance infrastructure can give attackers visibility into the very systems and personnel responsible for protecting an organization. I call that watching the watchers.


What concerns me is that these systems rarely operate in isolation. Video surveillance, physical access controls, building automation, and alarm systems may be interconnected. For an advanced adversary coordinating cyber and physical operations, that visibility can reveal security procedures, personnel movements, and potential gaps in response. The camera is no longer just watching the door; it may be helping someone figure out when to walk through it.


Manufacturers must take greater responsibility for secure-by-default configurations, strong authentication, firmware maintenance, and independent adversarial testing before and after products reach the market. Organizations should isolate these systems, eliminate unnecessary cloud access, and validate their defenses against realistic attack paths. Installing a security device shouldn’t require taking its security claims on faith.”

John Strand, Owner, Black Hills Information Security (www.blackhillsinfosec.com)

“Watch any spy movie and you’ll see the importance of cameras. They can reveal physical blind spots, capture high-resolution video of someone’s fingers as they type a password, or show sensitive information on a screen.

“What’s interesting about this particular story is how many problems are stacked together. Predictable serial numbers. Easy cloud access. Outdated firmware. It’s amazing to me how bad the entire security ecosystem around some of these cameras is.

“But this isn’t unusual. We see the same thing across connected IoT devices that fall outside traditional endpoint management. Patching is poor, firmware gets forgotten, and there’s often absolutely no security monitoring. These devices can see what people type and what’s on their screens, yet nobody is watching the devices themselves.”

Phillip Wylie, Chief Security Evangelist, Suzu Labs (www.suzulabs.com)

“Security cameras are supposed to help protect organizations, but when they’re compromised, they can become surveillance tools for attackers. Instead of protecting your environment, they’re potentially giving someone else visibility into your operations, personnel, and physical security.

“One of the biggest challenges with IoT devices is that they’re often installed and forgotten. Organizations may not realize these devices are running outdated firmware, using weak credentials, or are accessible from the internet. Attackers look for these weaknesses because they can provide an easy entry point into an organization’s environment.

“Manufacturers need to prioritize security by design, including secure default configurations, strong authentication, and reliable firmware updates. Organizations also need to take responsibility for securing these devices by changing default credentials, limiting internet exposure, segmenting networks, and regularly checking for firmware updates.

“Ultimately, a security camera is another computer connected to your network, and it needs to be treated with the same level of security attention as any other endpoint.”

Donald McFarlane, Board Member, Xcape, Inc (www.xcapeinc.com)

“A camera is a sensor.  A network of cameras (or radios, vehicles, routers or other connected devices) is an intelligence collection system.

“We have been seeing nation states turn privately deployed technology into intelligence assets for a long time. Russian intelligence has been publicly linked to compromising cameras to monitor NATO logistics and to identify Ukrainian personnel. U.S. agencies have assessed that Chinese state actors have penetrated and persisted in American communications infrastructure for years, maintaining access that could support disruption in a future conflict.

“An individual camera gives you an image. Aggregated sensor data gives you pattern of life: where people go, who they meet, which facilities matter, how goods move, and how critical systems operate.

“Hostile intelligence services don’t care what our acceptable-use policies or privacy statutes say. If we let them get the data, they’ll use it for their purposes.

“It isn’t enough to regulate what Flock, a police department, or another legitimate operator may do with aggregated data. We must ask whether Russia, China or somebody else can obtain that same data and build their own intelligence picture.

“When you deploy a nationwide sensor network capable of reconstructing movements and relationships, you have built an intelligence platform whether you intended to or not.

“The security requirement has to follow the intelligence value of the aggregate, not the apparent sensitivity of the individual sensor.

“Policymakers and operators must ask themselves: what collection or effects capabilities have we created, who else wants them, and how well are we protecting them?”

Cameras are things that you need to trust. And if you cannot trust them, the only option is to toss them ASAP.

OpenAI and Anthropic investigations reveal gaps in AI agent monitoring and safeguards

Posted in Commentary with tags , on October 27, 2026 by itnerd

New investigations into OpenAI and Anthropic AI agents have identified failures in monitoring and safeguards that could allow autonomous systems to take unauthorized actions. According to research from METR, independent evaluators discovered vulnerabilities in OpenAI’s internal monitoring system that could allow agents to conceal hundreds of actions, bypass sandbox restrictions and operate with users’ permissions.

Separately, the UK’s AI Security Institute (AISI) found that Anthropic’s Mythos 5 continued pursuing unauthorized attacks against real people during a July evaluation, even when presented with evidence that its actions could cause harm. The agent submitted malicious code to a public GitHub project and created fake identities to pressure a maintainer into approving it.

METR’s findings concerned OpenAI’s monitoring system as it existed in July. OpenAI says it has patched the identified production vulnerabilities, although researchers have not independently verified the fixes. AISI reported no real-world harm from the Mythos incident but warned that flawed AI reasoning could make dangerous behavior harder to detect.

ㅤJohn Strand, Owner, Black Hills Information Security:

“I think we have two separate problems, and the second one isn’t getting nearly enough attention.

“The first is the environment where these agents are being evaluated. We’re talking about sandboxing, but for these highly dangerous offensive AI models, I think an air gap is the only setup we should consider secure. Even then, I’m not completely certain. Models being evaluated for offensive security assessments should have absolutely no internet access.

“People will say they need certain tools. Fine. Give them the tools. We can reasonably predict what they’ll need because they use the same tools security researchers use. Get those tools into an isolated environment and contain the model. A crowbar in a sandbox. That’s what we should be shooting for.

“The second problem is morality and alignment. When you ‘obliterate’ a model and remove its boundaries, those boundaries don’t disappear only for authorized security research. From what’s being described, we’re seeing models attack sites without authorization, including German sites, healthcare sites, and Hugging Face.

“We need better ways to develop and evaluate models that can perform offensive security research within an authorized scope while retaining the boundaries that keep them from hacking unrelated third parties. Permission to attack a lab should not become permission to attack the internet.

“That seems to be a difficult problem for vendors to work through. But it needs to be a much bigger part of this conversation.”

ㅤ

Darin Fredde, Sr. Director of Technical Marketing Engineering, Ridge Security:

“These investigations expose an important gap between what autonomous AI agents can accomplish and what organizations can constrain and verify. The researchers identified different problems, but both reinforce the same principle: an agent’s ability to complete a task doesn’t mean it understands or will respect the boundaries of its authority.

“In offensive security, autonomy is valuable precisely because an agent can explore attack paths that humans might overlook. But that capability must operate within enforceable rules of engagement. Target scope, permissions, network access, and stop conditions cannot depend solely on the model’s interpretation of instructions. They need independent technical enforcement, monitoring, and verification.

“An autonomous agent may be an excellent penetration tester, but it shouldn’t get to rewrite its own rules of engagement.

“I also see something positive here. Independent researchers were given meaningful access to examine these systems, and the findings were disclosed. That’s how security improves. The objective isn’t to slow innovation; it’s to ensure our ability to verify and govern autonomous systems advances alongside their capabilities.

“Ultimately, the measure of security isn’t whether an agent says it stayed within scope. It’s whether we can independently prove that it did.”

ㅤ

Ryan McCurdy, Vice President of Marketing, Liquibase:

“These findings point to one of the most important architectural requirements of the agentic era. AI agents can reason, generate code, and make decisions based on probabilities. That’s incredibly powerful but probabilistic reasoning alone isn’t enough when those agents can take consequential actions in production systems.

“We need deterministic controls around execution. The same standards should apply to every change, whether it originates with a developer, a pipeline, or an AI agent, including authorization, policy compliance, validation, and any required approvals. Those decisions need to be enforced independently of the agent, not left to the agent’s own judgment.

“We also need to know what happened afterward, including what changed, who or what initiated it, whether it complied with policy, and whether the system has drifted from its expected state. Those requirements don’t change just because the actor initiating the change is no longer human.

“Ultimately, the measure of success isn’t how much code agents generate or how many tasks they complete. It’s how much work makes it into production correctly, without constant human intervention. You can’t achieve that at scale without consistent, enforceable controls.”

ㅤ

Seemant Sehgal, Founder & CEO, BreachLock:

“The question of whether agent providers can be the primary line of defense for agent behavior has been open for a while. This research demonstrated that one leading agent could conceal hundreds of actions from its provider’s own monitoring, and another kept pursuing an attack against a real person after being shown evidence of harm. They cannot be the primary line, and organizations running agents in production need their own controls at the orchestration layer rather than inheriting whatever the provider has in place.

“If alignment did not stop the Mythos agent from pressuring a maintainer with fake identities and malicious code after being shown evidence of harm, security teams relying on these models need to ask their providers what alignment actually stops in practice. Pentesting agent deployments against those same conditions, including adversarial inputs and pressure tactics, is the way to find out whether your own agents behave the way you think they do.”

ㅤThis continues to show that AI needs to be under lock and key as letting it run wild doesn’t work out well.

Microsoft issues emergency .NET patches

Posted in Commentary with tags on October 27, 2026 by itnerd

Microsoft has released emergency security updates for .NET 8, 9, 10 and 11 to address multiple vulnerabilities, including a buffer overflow flaw that could allow unauthenticated attackers to access or corrupt application memory.

The critical buffer overflow vulnerability, CVE-2026-111497, affects all platforms and could lead to information disclosure, denial of service or privilege escalation. Microsoft also patched CVE-2026-114148, a Linux vulnerability that could allow local attackers to modify files and gain elevated privileges.ㅤ

Microsoft additionally reissued fixes for two vulnerabilities after discovering that its October 13 updates had not fully addressed them. The company urged immediate patching, noting that organizations running self-contained applications or containers must rebuild and redeploy them rather than simply updating their systems.

ㅤDenis Calderone, Principal / CTO, Suzu Labs:

“Organizations that did everything right on October 13 are still running vulnerable code, and Microsoft’s own advisories say so. The flaw is getting the headlines, but the detail that should stop security teams cold is that CVE-2026-70197, the SocketAsyncEventArgs memory corruption fix, was disclosed in the October 13 advisory but never made it into that release. The Blazor WebAssembly debugger fix the same day, CVE-2026-102870, shipped with a packaging error that kept the corrected component from reaching machines. Unfortunately, we have two vul announcements, but neither got fully delivered.

“This lands in an awkward spot for the patching process most organizations actually run. CVE-2026-70197 is an unauthenticated out-of-bounds write in the socket layer, and the new Brotli flaw, CVE-2026-111497, is an out-of-bounds write in a decompression library embedded across .NET 8 through 11. Anyone relying on a patch report dated October 13 has been carrying a false green light for almost two weeks, and a version check would not have caught it, because on paper those deployments looked current. When the vendor’s release notes are the source of truth and the source of truth was wrong, verification has to mean more than a version number.

“The operational part turns this from a bad afternoon into a bad week. Self-contained applications and containers bundle the .NET runtime inside the artifact, so installing the October 25 update on the host changes nothing for them. They have to be rebuilt and redeployed. Ask yourself whether you can list, right now, which applications in your environment are self-contained versus framework-dependent, and where they run. Most can’t, and that inventory gap is what turns a one-day emergency patch into a two-week project.

“So, you should be updating the runtimes, rebuilding and redeploying every self-contained application and container, and updating the Blazor NuGet packages directly instead of trusting the shared runtime. For anything that can’t be rebuilt this week, the Brotli exposure has a configuration work around. The work around is simple enough. Brotli decompression is off by default, so the first question is whether you turned it on anywhere. If you did, remove “br” from request decompression and drop Brotli from HttpClient automatic decompression. That is a config change you can ship in hours, and it is your bridge until the rebuild lands. Then confirm the runtime version actually running in production, not the one in the change ticket. The teams that verify just had a better two weeks than the teams that checked a box.”

ㅤ

John Strand, Owner, Black Hills Information Security:

“This story almost feels like Microsoft saw the PHP vulnerabilities, looked around, said, ‘Hold my beer,’ and handed us these .NET vulnerabilities.

“It’s been bad. Apparently, Black October isn’t done yet. These critical .NET vulnerabilities look like they’re hitting a large section of the websites that the PHP vulnerabilities missed.

“I do wonder if there were some .NET developers and Microsoft website maintainers feeling a little smug last week, thinking, ‘Well, good thing we weren’t running PHP.’ Now they have their own critical vulnerabilities to deal with.”

ㅤ

Seemant Sehgal, Founder & CEO, BreachLock:

“When vulnerabilities like CVE-2026-111497 are left unpatched, an attacker exploiting this chain can start with memory corruption inside a vulnerable .NET process, escalate privileges against the service account running it, and inherit whatever reach that account has. Enterprises typically grant those accounts more reach than they need.

“Teams that already know what runtime versions are running in production and who owns each one will patch this fast. The rest should start that inventory work now.”

ㅤIf you rely on .NET, you need to patch all the things and do it fast.

New maritime cybersecurity database identifies nearly 30,000 vulnerabilities affecting ships and ports

Posted in Commentary with tags on October 26, 2026 by itnerd

A new maritime cybersecurity initiative has identified nearly 30,000 vulnerabilities relevant to ships, ports and offshore infrastructure, according to the newly launched Blue Initiative, a collaboration led by Cydome Security and maritime industry partners.

The database currently tracks 29,505 vulnerabilities, including 2,004 rated critical and 586 listed in CISA’s Known Exploited Vulnerabilities catalog. It also identifies 37 maritime-specific vulnerabilities affecting systems built for ships and ports.

The initiative categorizes vulnerabilities across navigation, propulsion, communications, industrial controls and onboard IT systems, helping operators identify which flaws affect their equipment. It also provides alerts for newly disclosed critical vulnerabilities and those known to be exploited.

John Strand, Owner, Black Hills Information Security:

“This is another example of how we fail to look at the interconnectedness of all the devices we use. I think this maritime report is fantastic because it examines vulnerabilities from end to end across an entire ecosystem, in an industry that has traditionally been underserved by the security community.

“When we look at ships, cranes, and the systems moving cargo in and out of ports, we tend to treat them as things. We don’t think about whether they need endpoint detection, a firewall, or patches and updates. It’s just a device attached to a widget. We forget about the whole ecosystem that makes it work.

“That’s why this case study matters. Take the same approach to military systems, medical devices, or pharmaceutical manufacturing, and I think we’d probably find very similar problems. We depend on these connected devices, but we still don’t consistently treat them as computer systems that need to be secured.”

ㅤ

Seemant Sehgal, Founder & CEO, BreachLock:

“A database of 29,505 vulnerabilities is noise until an operator knows which of them are actually reachable and exploitable in their environment. Severity counts and KEV listings only answer part of the question. What matters for any single operator is how many of those vulnerabilities an attacker could actually reach on their fleet, their ports, and their offshore assets.

“That question manually at this scale. The combination of distributed assets, long operational windows between port calls, mixed IT and OT environments, and limited onboard security staffing means any approach that depends on human analysts triaging thousands of CVEs will fall behind the exposure before the next voyage begins. The scalable version is continuous testing of what an attacker could actually reach across the fleet, so when a critical CVE lands, the operator already knows which vessels and which systems are exposed and which are not.”

Let’s see how well this works out. I say that because having a database is good. But actioning the information in it on a consistent and quick basis is much better. And actioning it with everything is the best possible outcome.

AI robocalls + NFC relay drained €380K in Dutch bank scam

Posted in Commentary with tags on October 26, 2026 by itnerd

Dutch police arrested two men who drained more than €380,000 from 170 bank customers using AI-generated robocalls. The recordings warned of suspicious account activity, then a live “bank employee” took over and talked victims into installing an app and holding their debit card to the phone. The app captured the card’s NFC data and relayed it to an accomplice waiting at an ATM.

Rohan Gupta, CEO & Co-founder, Diopter Had This To Say:

“Based on the reporting, this was a familiar social engineering playbook with AI running the first step. An AI-generated recording warned people about suspicious activity on their bank account and asked them to press 1 if it wasn’t them, establishing authority and urgency. A live caller posing as a bank employee then took over, said the card had been blocked, and had them download an app and hold the card to their phone. An AI voice was the thing that allowed a two-person crew to run that first step at scale, and it looks like it cost 170 people more than €380,000. Businesses should expect the same approach on their own phone lines, from callers who sound just like their bank or one of their vendors. Any request to install software, move money, or share a login is a red flag even if the caller sounds like someone you know. Your bank should never ask you to tap your card to your phone during a call. If that happens, best practice is to hang up and call the number on the back of your card.”

Social engineering has got a new life thanks to AI. Thus people need to be educated about this new but old threat that is out there.

PHP2Shell security flaws now successfully exploited in the wild

Posted in Commentary with tags on October 26, 2026 by itnerd

Two critical remote code execution vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619, collectively known as PHP2Shell, have now been confirmed as successfully exploited in the wild. Adel Karimi, detection and response lead at Perplexity, captured evidence of successful exploitation against an Apache mod_php installation running PHP 8.4.26, including memory disclosure and subsequent command execution. The findings, corroborated by security researcher Marcus Hutchins, mark a significant escalation from earlier reports of scanning and unsuccessful exploitation attempts.

Bri Frost, Director of Product Management, Cloud Range said this:

“PHP2Shell highlights a challenge that security teams increasingly face: exploitation can begin before defenders have complete information about a vulnerability, its impact or even whether available mitigations are effective. In these situations, the biggest risk isn’t necessarily a lack of security tools. It’s whether the people responsible for responding can make the right decisions quickly under pressure.

“Organizations should be testing how their security teams respond when a critical vulnerability moves from theoretical risk to active exploitation. Can analysts distinguish scanning from successful compromise? Can they identify suspicious activity on affected servers, determine whether attackers have established persistence and coordinate containment without unnecessarily disrupting business operations? These are skills that need to be developed through realistic exercises, not figured out during an actual incident. The faster exploitation timelines become, the more important it is that security teams have already practiced responding to situations where the threat is evolving faster than the available intelligence.”

If you haven’t fixed or replaced any application that uses PHP, now is a really good time to do so. Though based on this, it might be too late already.