Dahua Technology and the NDAA: what the law actually says
This page is a compliance-migration resource, not a standard product comparison. Dahua Technology is on the FCC Covered List and is named in NDAA Section 889. Tec-Tel doesn’t install Dahua and doesn’t recommend it for any customer. This page exists because buyers searching for Dahua alternatives are often mid-migration and need accurate information about the regulation, the scope of affected equipment, and which compliant alternatives they can actually buy.
NDAA Section 889 is part of the National Defense Authorization Act for Fiscal Year 2019 (Public Law 115-232). The statute prohibits federal executive agencies from procuring, obtaining, or using equipment, systems, or services that use “covered telecommunications equipment or services.” Dahua Technology is named in Section 889 by statute, alongside Huawei, ZTE, Hytera, and Hikvision.
Section 889 has two operative parts that matter here:
Part A prohibits federal agencies from directly buying or using covered equipment. This is the straightforward prohibition - a federal agency can’t cut a purchase order for Dahua cameras.
Part B has a wider reach. It prohibits federal agencies from contracting with any company that itself uses covered equipment. This is what catches contractors and subcontractors who thought the prohibition only applied to direct government procurement. If you hold a federal contract or subcontract and Dahua cameras are on your premises - even in facilities unrelated to the federal work - Part B may apply.
The FCC Covered List identifies communications equipment and services that pose an unacceptable risk to US national security under the Secure and Trusted Communications Networks Act of 2019. Dahua Technology appears on this list. Federal agencies cannot purchase equipment on the Covered List using FCC Universal Service funds. The list is publicly available at https://www.fcc.gov/supplychain/coveredlist.
The Lorex connection is a common source of confusion. Lorex is sold as a consumer and small business camera brand in retail channels including major electronics stores. The parent company structure connects Lorex to Dahua Technology’s hardware and firmware. Lorex cameras use Dahua chip architecture, Dahua firmware, and Dahua’s app infrastructure. For Section 889 purposes, subsidiaries and affiliates of named entities are covered. If you have Lorex cameras in a federal-touching facility, your compliance posture is the same as if they were labeled Dahua.
Who this applies to:
- Federal executive agencies: directly prohibited from procuring or using Dahua or Dahua-affiliated equipment.
- Federal contractors and subcontractors: prohibited under Part B from using covered equipment in contract performance; some agencies extend this to all company facilities.
- Recipients of federal grants: check your grant terms; infrastructure and security grants increasingly require NDAA compliance.
- Private companies with no federal exposure: the legal prohibition doesn’t currently apply. The decision to migrate is a risk management call, not a legal requirement.
What Tec-Tel’s position is: We don’t install Dahua or any Dahua-affiliated brand. We work across manufacturing, logistics, healthcare, and other industries with federal contract exposure. Installing covered equipment creates procurement risk for our customers and downstream liability for us. We removed Dahua from our install portfolio and we’ve been helping customers migrate off it ever since.
The compliance migration: what it involves
If you’re a federal agency, contractor, or grant recipient with Dahua or Lorex cameras, this is a remediation project with a compliance clock, not a product comparison.
Here’s how the migration typically works:
- Inventory your camera fleet. Identify every Dahua-branded and Dahua-affiliated unit by model, serial number, location, and network connection. Don’t assume Lorex or other labels are safe - check the underlying hardware. A full inventory is the starting point for any compliance documentation.
- Map your federal exposure. Which sites, networks, or systems are in scope for your federal contracts or grant awards? Cameras at those locations take priority. Cameras at non-federal-facing facilities may follow in a second phase.
- Audit your VMS compatibility. Dahua cameras typically run in a Dahua NVR environment or through a compatible VMS. When you replace the cameras, you may also need to update NVR units or VMS configurations. Axis, Hanwha, Avigilon, and Bosch all support the major open VMS platforms (Genetec, Milestone, Avigilon Unity, Eagle Eye Networks).
- Select compliant replacements. The four vendors Tec-Tel installs as Dahua replacements are covered in detail below. The right choice depends on your budget, the existing VMS, and the facility’s security requirements.
- Document the removal. Your contracting officer or grant administrator will want records showing covered equipment has been physically removed and compliant equipment has replaced it. Serial numbers, removal photos, and disposal records are standard.
Compliant alternatives Tec-Tel installs
All four primary partners below have published NDAA Section 889 compliance statements and are headquartered outside the People’s Republic of China.
Axis Communications
Headquarters: Sweden (Lund). NDAA Section 889 compliant per Axis’s published compliance statement.
Axis cameras are the quality benchmark in commercial IP cameras. The product line covers fixed domes, multi-sensor panoramic cameras, PTZ cameras, and edge AI cameras. ARTPEC processors enable on-camera analytics that don’t require cloud routing. Axis cameras integrate with every major VMS - Genetec, Milestone, Avigilon Unity, Eagle Eye Networks, and others - through published ONVIF and proprietary APIs.
For Dahua customers migrating to a higher-quality system, Axis is the clear premium choice. Axis has a published security advisory program, a consistent firmware update cadence, and hardware built for 10 to 15-year commercial lifespans. If your compliance migration is also an opportunity to upgrade your overall camera quality and cybersecurity posture, Axis is where that conversation starts.
Axis hardware costs more per unit than Dahua did. That’s real. But camera longevity, firmware reliability, and absence of compliance risk are part of the total cost when you’re buying cameras for a 10-year deployment.
Hanwha Vision
Headquarters: South Korea. NDAA compliant per Hanwha Vision’s published compliance statement.
Hanwha Vision (formerly Samsung Techwin) occupies the value-performance position among compliant camera vendors. Wisenet cameras deliver comparable resolution and feature sets to Axis at 15 to 25% lower per-camera hardware cost. ONVIF compatibility is strong. Genetec, Milestone, and Avigilon Unity all support Hanwha as a primary camera partner.
For Dahua customers with large fleets where budget is a real constraint, Hanwha is the most common replacement path. The price gap between Dahua and Hanwha is smaller than the gap between Dahua and Axis, which matters when you’re replacing 200 cameras. The compliance documentation is clean - Hanwha’s supply chain is South Korean, not PRC-controlled.
Hanwha’s AI capabilities have also grown significantly. Wisenet AI cameras include on-board analytics for motion detection, object classification, and basic intrusion detection. For deeper AI - workplace safety, forklift proximity, PPE compliance - Tec-Tel layers purpose-built workplace-safety analytics on top of the Hanwha cameras.
Avigilon (Motorola Solutions)
Headquarters: United States (Chicago, via Motorola Solutions). NDAA compliant per Avigilon’s published documentation.
Avigilon Unity cameras include on-camera AI with Appearance Search, which makes forensic video review significantly faster than standard motion-based search. For customers who are migrating compliance requirements and want to upgrade AI capabilities simultaneously, Avigilon is worth evaluating. The tradeoff is that Avigilon’s best AI features require Avigilon’s Unity VMS. If you’re running Genetec or Milestone and want to stay on it, Avigilon cameras are compliant but you won’t get the full AI feature set.
Avigilon is a US-headquartered company, which matters for federal customers who want domestic supply chain documentation alongside NDAA compliance.
Bosch Security
Headquarters: Germany. NDAA compliant per Bosch Security’s published documentation.
Bosch cameras are built for high-security and critical infrastructure environments. Signed firmware, secure boot, strong encryption, and compatibility with all major VMS platforms are the core features. Bosch is the default recommendation when the customer’s primary requirement is camera-level cybersecurity posture - not just NDAA compliance status, but the actual firmware and communication security architecture of the device itself.
Higher price point than Hanwha, comparable to Axis premium lines. The customer profile is usually government, defense contractors, hospitals, or financial services - environments where cybersecurity documentation is as important as the lens.
Compliant alternatives at a glance
| Vendor | HQ | NDAA compliant | On-prem option | Primary use case |
|---|---|---|---|---|
| Hanwha Vision | South Korea | Yes | Yes | Value rip-and-replace, large Dahua fleet migration |
| Axis Communications | Sweden | Yes | Yes | Premium quality, firmware security, high-security facilities |
| Avigilon (Motorola Solutions) | United States | Yes | Yes | AI upgrade + compliance migration, Motorola ecosystem |
| Bosch Security | Germany | Yes | Yes | Critical infrastructure, cybersecurity-priority deployments |
Side-by-side: What changes in the migration
| Dimension | Dahua (pre-migration) | Axis | Hanwha | Avigilon | Bosch |
|---|---|---|---|---|---|
| NDAA Section 889 | Covered - prohibited | Compliant | Compliant | Compliant | Compliant |
| FCC Covered List | Yes | Not listed | Not listed | Not listed | Not listed |
| HQ supply chain | China | Sweden | South Korea | United States | Germany |
| Published security advisories | Inconsistent | Yes, regular | Yes | Yes | Yes |
| VMS compatibility | Dahua-native, partial ONVIF | Broad | Broad | Unity preferred | Broad |
| Federal contract use | Prohibited | Permitted | Permitted | Permitted | Permitted |
Pricing reality
Dahua cameras are priced significantly below the compliant alternatives. That’s partly why they spread so widely in the market. Compliant replacements cost more per unit. The gap is real and the migration budget needs to reflect it.
In the quotes we benchmark:
- Hanwha Vision typically runs 1.3x to 2x the Dahua hardware cost per camera at comparable resolution. This is the smallest premium in the compliant market.
- Axis runs 2x to 3.5x the Dahua cost at comparable resolution. The premium covers firmware quality, cybersecurity posture, advisory track record, and a longer hardware lifespan.
- Bosch and Avigilon land in a similar tier to Axis, with Avigilon higher when AI feature tiers are included.
For a 50-camera single-site migration to Hanwha Vision, hardware cost alone typically runs $12,000 to $30,000 depending on camera type and resolution. Add installation labor, cabling if needed, VMS reconfiguration, and migration documentation: $20,000 to $50,000 total project cost. Site-specific and quoted after the free consultation.
The price of non-compliance - a federal contract suspended, a grant clawed back, or a security audit that flags covered equipment - typically exceeds the cost of the migration.
Who should migrate when
Migrate immediately if you: hold a federal contract or subcontract, receive federal grant funding that covers security infrastructure, or have already received a compliance flag from your contracting officer or security officer.
Migrate on your next camera refresh if you: have no current federal exposure but want to preempt insurance underwriters and enterprise procurement requirements that are increasingly asking about covered equipment.
Get legal advice before acting if you: aren’t sure whether your specific contracts or funding sources trigger Section 889 Part B obligations. The law has nuances that depend on your specific contract vehicles.
Tec-Tel will not install Dahua or Lorex for any customer. Our install portfolio is built around compliant vendors, and we’d rather pass on a project than create NDAA liability downstream.
Get a free consultation
If you have Dahua or Lorex cameras and want to understand your compliance posture, book a free consultation. The Tec-Tel team can walk through your camera inventory, map your federal contract exposure, and give you a written migration plan with options at different price points.
Book directly: . You’ll leave knowing which cameras need to come out, what replaces them, and what the project will cost.
Tec-Tel. Morganville, NJ. 855-577-0400.