Archive for October 27, 2026

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.

Leave a comment »

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.

Leave a comment »

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.

Leave a comment »

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.

Leave a comment »