The FBI ARTEX Advisory and the Paths to Your Critical Systems 

Author

Justin Kohler

Read Time

6 mins

Published

Nov 19, 2026

Share

The FBI’s November 13 FLASH advisory on ARTEX describes attackers using an agentic penetration testing framework to automate reconnaissance, exploitation, privilege escalation, and other stages of an intrusion. Some attacks progressed from initial targeting to privileged access in under three hours. 

That speed creates an urgent problem for defenders. It also makes an existing question harder to postpone: if an attacker compromises an identity in your environment, what can that identity reach? 

The answer depends on more than the privileges assigned directly to that account. Group memberships, application ownership, delegation, deployment permissions, and cross-platform trust can combine to provide access that no individual permission review makes obvious. Those connections determine how an initial foothold can become control over a critical system. 

The FBI’s ARTEX advisory gives organizations a concrete reason to examine those connections now. 

The techniques described in the advisory span on-premises and cloud environments. They include enumerating identity permissions, abusing application access, and escalating privileges. 

An attacker can use each discovery to choose the next action. A credential provides access to an application. The application’s permissions provide control over another identity. That identity holds authority over a more sensitive resource. 

Microsoft’s analysis of ARTEX activity describes agents accumulating discovered assets and vulnerabilities into a graph as they work. 

ARTEX uses those connections to choose its next move. Defenders can build that view before an intrusion, identify the permissions that expose critical systems, and remove them before an attacker takes advantage. 

For more on reducing this exposure, see our report, AI Security Starts With Eliminating Attack Paths. 

ConnectWise illustrates the consequence of trusted access 

The ConnectWise campaign is a useful example. Microsoft reported attackers using compromised application credentials to authenticate to customer environments through access those applications had already been granted. 

The application’s permissions became the attacker’s permissions. Follow-on activity included reconnaissance and changes to credentials and privileges that could support expanded or persistent access. 

This is why reviewing a vendor application requires more than confirming that the vendor is legitimate. Security teams need to understand the application’s effective authority: 

  • What resources can it access or control? 
  • Can it grant additional privileges or affect other identities? 
  • Who can change its credentials, ownership, or permissions? 
  • What critical systems are reachable through those relationships? 

These questions apply to backup products, deployment identities, business integrations, and other trusted applications. They are also the questions organizations should be able to answer before a vendor reports a compromise. 

Get the ConnectWise tenant review guide to learn how to use BloodHound to examine the applications’ access and paths to critical assets. 

Turning the FBI’s ARTEX recommendations into action 

The FBI’s recommendations cover a broad defensive program. BloodHound Enterprise helps address the identity and access relationships within that program by showing how permissions connect to critical assets and where remediation can break an attack path. 

Four areas deserve attention. 

Application permissions and privileged identities. Review service principals, application ownership, role assignments, and consent grants in the context of what they enable. An application can create significant exposure through its own privileges or through its ability to control another identity. BHE identifies attack paths involving these relationships, including paths from third-party applications with privileged access to the customer’s tenant. 

Deployment and CI/CD authority. The advisory explicitly addresses deployment credentials, publishing interfaces, infrastructure-as-code, and CI/CD pipelines. These systems deserve scrutiny because permission to influence a build or deployment can carry authority over downstream infrastructure. BHE connects GitHub repository and workflow permissions with AWS and Azure permissions and trust relationships, helping teams identify where control over a pipeline creates a path into production. 

Certificate services and administrative boundaries. Review AD CS weaknesses and the relationships that allow identities to cross into more privileged systems. Privilege Zones let organizations focus attack path analysis on selected critical assets, including business systems that require protection beyond traditional Tier Zero / Control Plane infrastructure. 

Remediation priorities. Finding excessive access creates a queue of work. Understanding how that access contributes to attack paths helps teams decide what to fix first. The effective change may sit several steps upstream from the asset at risk: a GitHub permission, an application owner, a group membership, or a cloud trust relationship. 

Reduce exposure before an intrusion 

The FBI notes that ARTEX can generate noisy activity and trigger alerts, yet move fast enough to leave little time for a coordinated response. An alert starts a process: someone still has to investigate, establish the scope, and contain the attacker’s access. When privileged access is possible in under three hours, the permissions already in place can have consequences before that process is complete. 

A path removed beforehand gives the attacker one fewer opportunity and defenders one fewer route to contain. After a decade of simulating advanced adversaries, we know the value of an attacker getting in and finding nowhere to go. Making that outcome more likely requires a practical way to reduce exposure at scale. 

The average BloodHound Enterprise customer starts with over 1 billion attack paths. Addressing them individually is not workable. BHE prioritizes choke points: relationships shared by many paths, where a single remediation can eliminate thousands of individual attack paths at once. That lets teams make meaningful progress without treating every route as a separate task. 

On average, BloodHound Enterprise customers reduce their attack path exposure by 40% within the first 30 days. Teams can also track the resulting reduction in exposure to critical assets and report that progress to the board. Ongoing analysis helps them identify when changes to identities, permissions, or trust relationships introduce new paths, so the work continues as the environment changes. 

Where to start 

Organizations responding to the FBI’s ARTEX advisory can begin with a focused set of questions: 

  • Which third-party applications can reach critical resources or gain higher privileges? 
  • Who can control those applications and their credentials? 
  • Who can influence deployment workflows, and what production authority do those workflows hold? 
  • Which identities have unintended paths into Tier Zero / Control Plane or other sensitive systems? 
  • Which permission changes would remove the most exposure? 

Choose a critical system and work backward through the identities, permissions, and trust relationships that can reach it. Use that analysis to prioritize fixes, then check that those fixes removed the intended paths. 

Our team can help customers conduct that focused review with BloodHound Enterprise. The objective is to reduce what an attacker can accomplish with the access they obtain. 

Justin Kohler

Chief Product Officer

Justin Kohler is Chief Product Officer at SpecterOps, leading BloodHound and other security products. With 15+ years in product and security, he’s led teams at Gigamon, ICEBRG, and Microsoft, and served as a U.S. Air Force cryptologic linguist.

Ready to get started?

Book a Demo