Connected & Protected
24/7 Support
HomeBlogICE and CBP’s Face-Recognition App Can’t Actually Verify Who People Are
Security
#Security
#Security / National Security
#Security / Privacy
#Security / Security News
#Politics / Policy
#Mobile Fortify
#ICE face recognition app
#CBP technology privacy
#facial recognition limitations
#DHS identity verification
#biometric data collection
#privacy rights
#immigration enforcement technology
#face scanning app
#surveillance technology concerns

ICE and CBP’s Face-Recognition App Can’t Actually Verify Who People Are

ICE has used Mobile Fortify to identify immigrants and citizens alike over 100,000 times, by one estimate. It wasn't built to work like that—and only got approved after DHS abandoned its own privacy rules.

D
Dell Cameron, Maddy Varner
Content Author
Content Specialist

Dell Cameron and Maddy Varner are investigative journalists specializing in privacy rights and technology's impact on civil liberties, with a focus on government surveillance practices.

Expertise: Investigative journalism, privacy rights, technology ethics, immigration enforcement, government surveillance
Published: February 18, 2026
Updated: May 10, 2026
14 min read

Quick Answer

The Mobile Fortify app deployed by ICE and CBP lacks reliable identity verification capabilities, leading to significant privacy and operational transparency concerns.

TL;DR

The Mobile Fortify app, used by ICE and CBP, is criticized for its inability to accurately verify identities, despite claims of efficiency. The app's rollout has raised serious privacy concerns due to a lack of scrutiny and transparency in its operation.

Key Takeaways

  • 1Mobile Fortify does not reliably identify individuals, despite being marketed as a verification tool.
  • 2The app's deployment has faced criticism for bypassing privacy safeguards and scrutiny.
  • 3DHS's methods for using facial recognition technology have raised significant ethical and transparency concerns.
ICE and CBP’s Face-Recognition App Can’t Actually Verify Who People Are

The face-recognition app Mobile Fortify, now used by United States immigration agents in towns and cities across the US, is not designed to reliably identify people in the streets and was deployed without the scrutiny that has historically governed the rollout of technologies that impact people’s privacy, according to records reviewed by WIRED.

The Department of Homeland Security launched Mobile Fortify in the spring of 2025 to “determine or verify” the identities of individuals stopped or detained by DHS officers during federal operations, records show. DHS explicitly linked the rollout to an executive order, signed by President Donald Trump on his first day in office, which called for a “total and efficient” crackdown on undocumented immigrants through the use of expedited removals, expanded detention, and funding pressure on states, among other tactics.

Despite DHS repeatedly framing Mobile Fortify as a tool for identifying people through facial recognition, however, the app does not actually “verify” the identities of people stopped by federal immigration agents—a well-known limitation of the technology and a function of how Mobile Fortify is designed and used.

"Every manufacturer of this technology, every police department with a policy makes very clear that face recognition technology is not capable of providing a positive identification, that it makes mistakes, and that it's only for generating leads," says Nathan Wessler, deputy director of the American Civil Liberties Union’s Speech, Privacy, and Technology Project.

Records reviewed by WIRED also show that DHS’s hasty approval of Fortify last May was enabled by dismantling centralized privacy reviews and quietly removing department-wide limits on facial recognition—changes overseen by a former Heritage Foundation lawyer and Project 2025 contributor, who now serves in a senior DHS privacy role.

DHS—which has declined to detail the methods and tools that agents are using, despite repeated calls from oversight officials and nonprofit privacy watchdogs—has used Mobile Fortify to scan the faces not only of “targeted individuals,” but also people later confirmed to be US citizens and others who were observing or protesting enforcement activity.

Reporting has documented federal agents telling citizens they were being recorded with facial recognition and that their faces would be added to a database without consent. Other accounts describe agents treating accent, perceived ethnicity, or skin color as a basis to escalate encounters—then using face scanning as the next step once a stop is underway. Together, the cases illustrate a broader shift in DHS enforcement toward low-level street encounters followed by biometric capture like face scans, with limited transparency around the tool’s operation and us

CrowdStrike
Related Product

CrowdStrike Advanced Defend

by CrowdStrike$15.41/mo

CrowdStrike provides advanced cloud-native platform protection for endpoints, cloud workloads, identities, and data with a single lightweight agent.

Learn More
e.

Fortify's technology mobilizes facial capture hundreds of miles from the US border, allowing DHS to generate nonconsensual face prints of people who, “it is conceivable,” DHS’s Privacy Office says, are “US citizens or lawful permanent residents.” As with the circumstances surrounding its deployment to agents with Customs and Border Protection and Immigration and Customs Enforcement, Fortify’s functionality is visible mainly today through court filings and sworn agent testimony.

In a federal lawsuit this month, attorneys for the State of Illinois and the City of Chicago said the app had been used "in the field over 100,000 times" since launch.

In Oregon testimony last year, an agent said two photos of a woman in custody taken with his face-recognition app produced different identities. The woman was handcuffed and looking downward, the agent said, prompting him to physically reposition her to obtain the first image. The movement, he testified, caused her to yelp in pain. The app returned a name and photo of a woman named Maria; a match that the agent rated “a maybe.”

Agents called out the name, “Maria, Maria,” to gauge her reaction. When she failed to respond, they took another photo. The agent testified the second result was “possible,” but added, “I don’t know.” Asked what supported probable cause, the agent cited the woman speaking Spanish, her presence with others who appeared to be noncitizens, and a “possible match" via facial recognition. The agent testified that the app did not indicate how confident the system was in a match. “It’s just an image, your honor. You have to look at the eyes and the nose and the mouth and the lips.”

Agents described the Oregon operation as part of “Operation Fortify the Border” and referred to enforcement in the Pacific Northwest specifically as “Operation Blackrose.”

“Facial recognition can be wrong, and it has been wrong in the past,” says Mario Trujillo, a senior staff attorney at the digital-rights nonprofit Electronic Frontier Foundation. “Here, the safeguards you’d expect—confidence scores, clear thresholds, multiple candidate photos—don’t appear to be there.”

The appearance of multiple identities is not an error but a feature of how Mobile Fortify operates in the field: Regardless of how agents use it, the system is built to generate candidate matches, not confirmations. Rather than exhaustively searching vast biometric galleries, Fortify converts a photo into a mathematical template and returns only entries that score high enough to be treated as possible matches. That threshold could be set manually or adjusted dynamically in response to response-time requirements and system load.

When images are taken outside controlled conditions, even small differences—head tilt, lighting, shadow, cropping, focus, or expression—can alter the template and reshuffle the pool of candidates. Quicker responses also require smaller candidate pools. This is a significant trade-off of demanding real-time results.

When a poorly framed street photo causes the subject to be excluded by the system early, it is a mathematical certainty that any match will be a miss.

Mobile Fortify’s primary function is to expand the number of photos and biometric data that DHS collects, including fingerprints, by shifting its collection from ports of entry to routine ICE encounters occurring far from US borders. The data is stored in databases linked by a centralized platform known as the Automated Targeting System (ATS). CBP says the data are retained for up to 15 years but may persist longer if shared with other agencies beyond CBP’s control.

Among other biometric systems, ATS is linked to the Traveler Verification System (TVS), used by CBP for facial comparison at ports of entry, during pre-arrival vetting, and in other screenings tied to border crossings. Under CBP policy, photos and biometric data of US citizens who opt out of biometric identification are supposedly deleted from TVS in under a day.

Internal records show that data collected through Fortify may also be stored in the Seizure and Apprehension Workflow (SAW), which is described as a “biometric gallery of individuals for whom CBP maintains derogatory information.” Unlike TVS, SAW is used for intelligence purposes and lead generation. A “derogatory hit” does not indicate undocumented status, criminal conduct, or probable cause for arrest. US citizens are not explicitly excluded, and records are retained for up to 15 years.

ICE agents are instructed to photograph subjects for facial recognition before trying to match their fingerprints, which court records show is done in-office rather than on the street, even though fingerprints are a stronger biometric for confirming identity. The sequence prioritizes speed and ease of collection over positive identification. When fingerprints are taken, they are routed through ATS to the IDENT database and retained for a minimum of 75 years.

Records also indicate the existence of another derogatory watch list controlled by CBP and fed by Fortify, known as the Fortify the Border Hotlist. The list is mentioned in only a single publicly released document and was first revealed by 404 Media last year. The record does not describe the criteria for placement on the watch list nor any removal or appeals process. It is unclear whether US citizens are included.

DHS did not respond to questions about the criteria that governs the watch list, whether US citizens are added, or whether a redress process exists for individuals mistakenly included.

A letter released Tuesday by US senator Ed Markey warns that DHS officials have suggested building a database to catalog people who protest or observe immigration enforcement. It cites public statements and internal directives instructing agents to collect images and personal information on protesters and bystanders. Markey said in a statement on Wednesday that DHS has deployed an “arsenal of surveillance technologies” that it was using to monitor “both citizens and noncitizens alike,” calling it "the stuff of nightmares."

“There’s a cascading set of problems with this app and what ICE and CBP are doing,” says Trujillo. “Field facial-recognition scans in the interior are incredibly invasive. You’re taking a measurement of a person’s face and comparing it against millions of photos in a database. It gives a veneer of certainty when there isn’t certainty behind the scenes

SentinelOne
Related Product

SentinelOne Control

by SentinelOne$8.00/mo

Prevention and detection of attacks across all major vectors with fully automated, policy-driven response capabilities and real-time forensics.

Learn More
.”

Trujillo also believes that “there’s a straightforward argument that DHS and its components are exceeding their authority here.”

Fortify relies specifically on matching algorithms developed by the NEC Corporation of America, the US subsidiary of a Japanese multinational headquartered in Tokyo, as first reported by WIRED last month.

Testing by federal scientists at the National Institute of Standards and Technology, conducted with DHS and CBP, shows face-recognition accuracy drops sharply when images are taken outside controlled settings, including for top-performing NEC models. The tests distinguish between “high quality visa-like photos” taken in immigration offices and “wild” images captured in real-world conditions, such as immigration lanes or at registered traveler kiosks.

At ports of entry, CBP relies on tightly controlled visa photos: fixed cameras, cooperative subjects, neutral expressions, plain backgrounds, and uniform lighting. Images are rejected if a subject’s head falls outside a narrow size range. Even highly accurate systems, NIST says, struggle with poor framing or head tilt.

Street photos taken by cell phone lack those controls. Lighting varies, angles shift, and motion blur is likely common in the field, shaped as much by environment as the steadiness of the person holding the phone. High resolution alone does not correct for these constraints.

A WIRED review of recent face-recognition patents assigned to NEC shows the company’s technology is designed less to conclusively verify identity than to operate at scale under imperfect conditions. The patents describe systems that convert face images into biometric templates and compare them against stored records using similarity scores and adjustable thresholds, with the explicit goal of maintaining capacity when image quality varies.

The patents also acknowledge a core trade-off. NEC describes tuning match thresholds and system behavior to balance speed, scale, and accuracy, noting that lowering thresholds can reduce delays and failed transactions while increasing the risk of false positives, and that tightening them can have the opposite effect. Thresholds may be adjusted dynamically based on operational factors such as system load, frequency of use, or performance speed.

To support real-time use, the patents describe systems configured to stop searching after a short, fixed time window—on the order of seconds—if no match is found. In those cases, the system may still surface the highest-scoring candidate pair for human review, even though the score was insufficient for an automated match. Those limits reduce computing demands and enable rapid responses, but they also constrain how thoroughly large databases are searched, producing results that are suggestive rather than definitive.

NEC did not respond to questions about its licensing of facial recognition technology to US immigration agencies, including questions of how its systems are designed to perform in uncontrolled field conditions, what safeguards or usage constraints it provides to government customers, and whether it evaluates civil-liberties or human-rights implications prior to licensing its products.

Emily Peterson-Cassin, policy director of the Demand Progress Education Fund, a pro-privacy nonprofit, warned that unchecked facial recognition threatens free expression and civil liberties. “Privacy safeguards are essential to stopping wrongful targeting by unvetted tools such as Mobile Fortify,” she says, “and are the minimum protection needed to prevent this technology from becoming a choke hold on our most basic freedoms.”

In the days and weeks after the start of Trump’s second term, DHS officials began dismantling policies and oversight checks that had constrained the use of facial recognition, including those aimed at enforcing congressional mandated privacy protections. If DHS has an enterprise-wide policy today that governs when, how, and under what safeguards facial recognition can be used, it isn’t public.

Online archives show the last such directive, implemented in 2023, disappeared from the agency’s website three weeks after Trump’s inauguration. Among other constraints, Directive 026-11 stated that facial recognition should not be used as the sole basis for law or civil enforcement actions and that US citizens should have the right to opt out when collection isn’t for a law enforcement purpose.

“DHS has not publicly replaced its previous facial recognition directive, and it appears DHS has no policy or even restrictions on the use of facial-recognition technology,” says Jeramie Scott, senior counsel for the nonprofit Electronic Privacy Information Center and director of its surveillance oversight program.

The directive also prohibited “systemic, indiscriminate, or wide-scale monitoring, surveillance or tracking.” It said facial recognition could not be used to “profile, target, or discriminate against individuals for exercising their constitutional rights.” It forbade the use of tools that claim to analyze people’s faces to infer personal traits and characteristics (with a narrow exception for age). It also tied any use of facial recognition by ICE and CBP to a headquarters-level review and authorization process, to be carried out by DHS’s chief privacy and information officers, respectively.

Fortify was fast-tracked less than two months after Directive 026-11 disappeared, in May 2025. CBP and ICE privacy officers alone concluded that no new privacy assessment was required under federal law—an authority they did not previously possess. Records show that such determinations historically rested with the DHS senior director of privacy compliance, a headquarters official acting on behalf of the department’s chief privacy officer and independent of operational agencies.

A disclaimer in records first revealed by 404 Media documents the swap. CBP states that it “assumed responsibility for the review and adjudication” of privacy reviews on March 3, 2025, citing internal policy guidance issued by an office led by Roman Jankowski, who was appointed DHS’s chief privacy officer the day Trump was inaugurated.

Federal guidelines typically require a privacy assessment when an agency deploys a new technology that collects identifiable information about the public or materially changes how, where, or from whom that data is collected. They also flag “new uses of an existing IT system” that introduce “new privacy risks,” including changes that would open new avenues for data exposure.

Prior to joining the administration, Jankowski worked for the Heritage Foundation and its Oversight Project, where he was a contributor to the group’s Project 2025 blueprint for Trump’s second term. The document variously recommends merging ICE and CBP; weakening the department’s centralized oversight; and transferring civil rights and privacy review functions from DHS to the agencies it is meant to police.

“This cavalier approach to the use of facial recognition has real-world consequences to our privacy, civil liberties, and civil rights that are exacerbated by the undermining of what little oversight is in place,” Scott says. “The result, as we see with Mobile Fortify, is a failure to meaningfully scrutinize the technology.”

Senator Markey and colleagues this week introduced legislation aimed at prohibiting ICE and CBP from using certain facial-recognition and biometric surveillance tools, saying the agencies have built a sweeping surveillance apparatus that is being used far from the border to scan people without consent, accountability, or clear legal limits. The full text of the bill, short-titled the ICE Out of Our Faces Act, was unavailable at time of writing.

“Facial recognition technology sits at the center of a digital dragnet that has been created in our nation over the past year,” Markey said during a press conference on Wednesday. “It's dangerous, it's authoritarian, and it's unconstitutional.”

Originally published on February 5, 2026 by Wired.

Expert Analysis for Orange County Businesses

How this impacts SMBs in Southern California

Tech News Roundup: ICE and CBP’s Face-Recognition App Can’t Actually Verify Who People Are

The recent revelations about the limitations of the Mobile Fortify face-recognition app highlight significant concerns regarding privacy and the reliability of emerging technologies. For small and medium businesses (SMBs) in Orange County and Southern California, this serves as a cautionary tale about the deployment of tech solutions that may promise efficiency but lack accountability and accuracy. As federal agencies like ICE and CBP utilize such tools with minimal oversight, local businesses must be vigilant about how technology is employed in their operations, especially as they navigate increasingly complex regulatory environments.

For SMBs looking to enhance their operations without compromising on security or privacy, partnering with a reliable IT provider is essential. TNC’s managed IT services offer comprehensive support that includes evaluating technology solutions for their effectiveness and compliance. Additionally, our cybersecurity solutions can help businesses safeguard sensitive data against unauthorized access, ensuring that any technology adopted maintains stringent privacy standards. Furthermore, TNC’s BCDR services provide peace of mind by ensuring that your data is backed up securely and can be restored in case of emergencies. To learn more about how TNC can support your business in leveraging technology responsibly, contact us today.

Read the full article: Original Source Link

Frequently Asked Questions

What is the purpose of the Mobile Fortify app?

The app is intended to verify identities of individuals stopped by DHS but lacks reliable verification capabilities.

What privacy concerns are associated with Mobile Fortify?

The app's use has led to nonconsensual facial scans and a lack of transparency in DHS operations.

Content Quality

Last Reviewed:February 18, 2026
Fact-Checked:February 18, 2026
0
Word Count:2,720 words

Article Tags

Security
Security / National Security
Security / Privacy
Security / Security News
Politics / Policy
Mobile Fortify
ICE face recognition app
CBP technology privacy
facial recognition limitations
DHS identity verification
biometric data collection
privacy rights
immigration enforcement technology
face scanning app
surveillance technology concerns
D

About Dell Cameron, Maddy Varner

Content Author

Dell Cameron and Maddy Varner are investigative journalists specializing in privacy rights and technology's impact on civil liberties, with a focus on government surveillance practices.

Expertise: Investigative journalism, privacy rights, technology ethics, immigration enforcement, government surveillance

Related Articles

5 critical steps to achieve business resilience in cybersecurity
Security

5 critical steps to achieve business resilience in cybersecurity

What does it really take to keep your organization running when attackers strike? The answer is business resilience—being able to detect, contain, and recover fast enough that disruptions are minimized, customers stay confident, and operations keep moving. From the latest 2026 State of the SOC Report, which is based on more than 900,000 alerts observed between March and December 2025 from the Adlumin Managed Detection and Response (MDR) provided by the N-able SOC, we’ve seen firsthand where security strategies succeed—and where they fall short. Below, we break down five actionable ways to build true resilience for your IT environment, using real-world data, strategic guidance, and frameworks that leading IT teams put into practice today. 1. Stop trusting single-layer security If you’re depending on just endpoint or cloud controls, you’re missing nearly half the risk surface—and the numbers prove it. In 2025, 18% of all alerts at the N-able SOC came from network and perimeter (Unified Threat Management) exploits that bypassed endpoint visibility. Over 137,000 threats were detected where endpoint-only controls would have been blind. What we recommend: Embrace layered, defense-in-depth designs. That means combining identity, endpoint, network, cloud, and perimeter visibility—not just bolting on tools. Relying on a “magic bullet” solution leaves dangerous gaps. Looking for end-to-end coverage of your environment? Check out N-able Unified Security Solutions. 2. Transition from manual to automated response SOC teams can’t keep up with the flood of alerts—N-able handled 2 alerts per minute on average in 2025. That’s why automation and Security Orchestration, Automation and Response (SOAR) saw a 500% YoY surge—almost one in four responses are now orchestrated automatically. Pro tip for IT leaders: Streamline workflows, so triage and containment happen at machine speed, not human speed. Automate password resets, containment, and endpoint remediation, then focus your analysts on proactive threat hunting. 3. Modernize endpoint and identity management Attack patterns are shifting. Out of 909,155 total alerts identified in N-able’s 2026 SOC report, only about half touched the endpoint layer. Identity has become one of the fastest‑growing attack surfaces, and organizations need visibility into suspicious sign‑ins, privilege misuse, and anomalous authentication behavior before a breach unfolds. A flexible, unified endpoint management solution that helps you manage, control, and secure endpoints is table stakes in your tech stack. To address identity attacks, an Identity Threat Detection and Response (ITDR) solution helps close this gap by correlating identity events, detecting credential abuse, and stopping identity‑based attacks in progress. ITDR gives security teams a clearer picture of how users, systems, and privileges are being accessed so they can contain threats early, before lateral movement or escalation occurs. Actionable step: Integrate advanced multi-factor authentication, real-time patch management, and privileged access controls as foundational layers. Add continuous identity monitoring to detect unusual authentication patterns and catch malicious activity that endpoint‑only tools cannot see. Transform your endpoint management – Explore how N-able’s N-central delivers simpler, smarter IT and security management. 4. Build recovery readiness into your plan Resilience isn’t just stopping an attack—it’s restoring operations quickly and minimizing downstream damage. In an N-able case study, an MSP’s customer suffered a 1.5 terabyte ransomware attack on a Friday. Thanks to Cove’s reliable backups (validated via recovery testing), the entire environment was fully restored by Monday, getting the business back online in under 3 days. This rapid recovery dramatically limited downtime and business disruption. Our advice: Test backups regularly, ensure they’re immutable, and tie recovery procedures directly into your SOC playbooks. Business continuity hinges on the speed and certainty of your recovery. See how Cove Data Protection delivers data resiliency by recovering quickly and reliably after every disaster. 5. Prepare for the next attack surface: AI AI is transforming both defense and risk. By 2026, up to 90% of investigations could be automated by AI. But adversaries aren’t far behind—compromised AI orchestration or poisoning can create new attack vectors that bypass traditional controls. What you need to do now: Audit where AI and automation touch your environment and monitor their actions with the same rigor as human activity. Prepare to secure agent-to-agent communications and maintain oversight as AI-driven processes mature. Explore how N-able leverages AI to protect customer environments around the clock. Strengthen your business with resilience-first security Resilience isn’t a buzzword—it’s the only practical answer for IT leaders dealing with today’s complex, fast-moving threat landscape. By focusing on layered defense, automation, unified recovery, and AI-integrated controls, you position your organization for uptime and continued success. Ready to level up your approach? Get started with our Cyber Resilience Primer: What You Need to Know in 2026.

6 metrics IT leaders can’t afford to ignore for business resilience
Security

6 metrics IT leaders can’t afford to ignore for business resilience

If you’re in IT, you know: what we don’t measure puts business resilience at risk. In the face of rising threat volumes, scaling complexity, and board-level scrutiny, tracking the right operational metrics isn’t just about visibility—it’s the foundation for proactive risk management and business continuity. Compliance and insurance demands are also driving the scrutiny around measuring cybersecurity programs. Recent findings from the 2026 N-able State of the SOC Report are clear: the threat landscape keeps shifting, automation and integration are now must-haves, and organizations delivering true resilience measure what matters most. Below are the six metrics that we use to move the needle from firefighting to futureproofing. 1. Mean time to detect (MTTD): The speed of awareness Attackers are faster and stealthier than ever. In 2025 alone, N-able’s SOC processed more than 900,000 alerts, with attackers exploiting both endpoints and newly reemerging network perimeters. Our own data shows that rapid detection is non-negotiable: every extra minute a threat goes unseen increases the likelihood of a business-impacting event. If your MTTD is measured in hours, not minutes, you’re exposing your organization to avoidable risks. Automated threat detection, AI-driven analytics, and streamlined alert management significantly reduce dwell time. Key stat: The N-able SOC now averages 2 alerts per minute, an alert velocity that demands automated detection—not just human monitoring. 2. Mean time to respond (MTTR): From triage to containment It’s not enough to spot threats—you have to contain them fast. MTTR tracks how quickly your team can isolate and neutralize incidents. Integrated SOAR (Security Orchestration, Automation, and Response) workflows now drive a 500% year-over-year increase in orchestrated alert response actions, according to our latest SOC report. The difference? Teams leveraging automation have moved from after-the-fact remediation to business-saving containment in minutes rather than hours. 3. Time to recover: The business resilience reality check A single outage can mean hours or days of operational downtime. That’s why recovery time is a core resilience metric. It’s not just about restoring data; it’s about rebuilding trust and revenue streams. In 2025, we saw the top-performing organizations combine automated backup and disaster recovery solutions, rapid failover, and regular recovery testing to drive down time-to-recover. Cloud-native backups with built-in recovery processes are now the difference between near-instant resumption and prolonged business impact. Access the Cybersecurity Incident Response Plan template to help your team build a structured, comprehensive, and actionable approach to identifying, managing, and mitigating cyber incidents. 4. Endpoint patch compliance: Closing the doors Vulnerability exploits remain a constant threat, and unpatched endpoints often provide the easiest entry points. Maintaining a high percentage of fully patched endpoints helps reduce these paths of attack and strengthens your overall security posture. With centralized patch management, resilient teams can automate updates, track compliance, and remove the guesswork from keeping environments secure. This reduces risk surface area even as your operations grow. 5. Asset and identity coverage: Eliminate blind spots You can’t protect what you don’t see. With over 432,000 endpoint-layer detections and 14,000 identity threats recorded by the N-able SOC team between March and December 2025, the risk of shadow IT or credential theft from memory is real. Eliminating blind spots starts with full visibility across every asset in the environment. As devices, cloud workloads, and remote access points continue to expand, unmanaged or misconfigured assets can create opportunities for attackers to establish a foothold. Continuous discovery and consistent monitoring help ensure nothing operates outside the security team’s line of sight. Identity visibility is equally essential. With credential abuse now a leading attack vector, organizations need awareness of how accounts authenticate, when privileges change, and where anomalies appear across systems. Bringing asset and identity coverage together helps close the gaps attackers look for and strengthens an organization’s overall security posture. Your asset and identity coverage percentage tells you whether you’re operating with full visibility or exposing the business to unseen gaps. Resilient organizations unify asset discovery, endpoint management, and identity monitoring on a single pane of glass—empowering teams to stay ahead even as environments sprawl. Take a tour of N-central and see how we unify IT Ops and SecOps for stronger resilience. 6. Downtime avoided: Quantifying security’s business value Translating technical wins into business outcomes is how IT earns board trust. By correlating incident response and recovery metrics with downtime costs, you deliver a dollar-value impact: tangible proof that your efforts directly protect revenue. Integrated platforms, real-time dashboards, and automatic reporting transform security from a cost center into a business safeguard. Make metrics your roadmap The real message from the latest N-able SOC data? Single-layer approaches and isolated tools are dead ends. According to our recent State of the SOC report, 137,000+ network and perimeter threats bypassed endpoints, and nearly half of all alerts never touched a traditional endpoint. Business resilience is now about defense-in-depth, layered visibility, and automation. If you’re relying on what worked last year, you’re behind. We encourage you to start with these six metrics, identify your gaps, and leverage unified security solutions that support operational clarity and proactive resilience. Ready to up your security game? Learn more about N-able’s unified end-to-end cybersecurity and IT solutions.

5 Steps to break free from alert fatigue and build resilient security operations
Security

5 Steps to break free from alert fatigue and build resilient security operations

How many times has your SOC hit crisis mode at 2:00 AM, with the dashboard blaring red and analysts scrambling to separate real threats from useless noise? We’ve all been there, and if you’re still measuring success by the number of alerts closed, chances are you’re feeling the strain. The truth is, responding to everything is neither sustainable nor effective—and it puts resilience at risk. In this article, we’ll show you the five most important steps you can take to move from alert fatigue to business resilience, supported by hard data from the 2026 N-able State of the SOC Report. These are the practical habits security-driven IT leaders are adopting to future-proof their operations and protect what matters most. 1. Recognize the cost of noise: When “more alerts” means more risk Many SOCs still believe that more data equals better protection. But our 2026 State of the SOC report found that traditional alert volumes have hit a breaking point— our SOC team had to process an average of 2 alerts per minute last year. When everything is urgent, nothing is. Analysts get burned out, and critical threats can slip by undetected, leading to increased dwell times and real business impact. Key N-able SOC stat: 18% of threats in 2025 were only caught by network and perimeter layers—outside endpoint visibility. It’s clear: If you’re over-relying on endpoint or cloud signals, you’re missing threats and putting uptime and client trust at risk. 2. Prioritize outcomes over ticket volume Stop focusing on how many alerts are cleared. This may be a metric for a better understanding of where automation or headcount are necessary but prioritize outcomes. Instead, the right questions are: How quickly did you contain a threat? Did we disrupt business operations or keep recovery swift and effective? A practical, outcome-driven SOC measures: Dwell time: How long before a threat was neutralized? Mean Time to Contain: How quickly were you able to halt an attack? Business downtime avoided: How resilient were you when tested? Tie these metrics back to resilience. When you can tell the CEO or client you prevented X hours of downtime or stopped ransomware in minutes, you position yourself as more than a cost center—you’re a driver of business continuity. Hear how customers use N-able to boost efficiency, gain peace of mind, and ensure business resiliency. 3. Put AI and automation to work—or get left behind According to our SOC report, 90% of all investigations in 2026 could be automated by AI. In fact, only organizations that shifted to AI-centric security models kept up with the onslaught. Those stuck with purely manual playbooks fell behind. Here’s what works: AI-driven correlation to unify context across endpoints, networks, identities, and more. Automation to handle tasks like remediation, account disables, password resets, and notifications—repetitive work that machines do faster and with less error. Last year, our SOAR actions surged 500%, making up almost a quarter of all responses. That’s what resilience in the face of “volume crisis” looks like. Explore the benefits of integrating AI into your strategy and how it impacts your security team across crucial threat and detection stages. 4. Build defense-in-depth (and don’t rely on magic bullets) The “magic bullet” mindset, where a single security layer or tool is supposed to protect everything, doesn’t cut it. The 2026 N-able State of the SOC report underscores that business resilience depends on a defense-in-depth strategy: In 2025, half of all attacks bypassed endpoint controls entirely. 137,187 network and perimeter threats were invisible to endpoint-only deployments. The lesson: Layered security isn’t just “nice to have”—it’s the difference between stopping attacks and suffering a breach. Even with the right foundational layers in place, the real power only emerges when they operate as a unified system. Multi-layer correlation connects the signals coming from identity, endpoint, cloud, network, and perimeter controls, transforming isolated alerts into a clear, actionable picture of an unfolding attack. 5. Design playbooks that focus on business resilience Your playbooks shouldn’t just stop at technical containment—think bigger. The best teams design for resilience, from automated isolation and communication to verified recovery. For ransomware: Confirm the scope rapidly (AI correlates affected assets). Automate isolation of the subnet or systems involved. Communicate with stakeholders per your IR plan. Initiate backup restoration, leveraging recent, immutable recovery points. In our 2026 SOC report, organizations with unified, automated playbooks contained perimeter-initiated attacks in under 10 minutes—even during off-hours. That’s the bar you need to hit. The bottom line Volume and complexity aren’t going away, but SOC fatigue doesn’t have to be your story. By shifting to outcome-driven defense, embracing automation, layering controls, and focusing on measurable resilience, you move from reactive to proactive—protecting your clients, your brand, and your peace of mind. Are you ready to take the next step? Take a tour of Adlumin’s AI-powered XDR platform and expert-led MDR service.

Ready to Transform Your Business?

Discover how our expert IT solutions can help your business thrive.