Supply Chain • Blue List • Federal Procurement
Security Drone Procurement and NDAA Checks (Updated for 2027)
Last updated:
Review FAR 40.202 against the actual federal procurement or operation and covered-entity status. FCC equipment authorization and FAA operating authority answer different questions. Record the model, exact supplier, program, applicable exceptions and review date.
An “NDAA-compliant security drone” is not one universal certificate or approved-product list. A defensible purchase starts by identifying the customer and contract requirement, then checking the current DCMA Blue List or relevant Green UAS status, the FAR clause and SAM list when federal work is involved, and the exact aircraft, controller, payload, software, connectivity and data chain.
Five checks before buying an NDAA-compliant security drone
- Identify the controlling requirement: contract, solicitation, agency policy, funding condition or private-client standard.
- Check current status: verify the exact platform on the current DCMA Blue List or applicable AUVSI Green UAS list rather than relying on a vendor badge.
- Search covered entities when required: federal contractors should follow FAR 52.240-1 and check the FASC-maintained list published through SAM.
- Verify the complete configuration: aircraft, controller, camera, radio, software, cloud, network services and supplied components.
- Save dated evidence: archive the list result, supplier documents, bill of materials, contract decision and approver before purchase and before performance.
Check the DCMA Blue List • Review FAR 52.240-1 • Search SAM.gov
NDAA-compliant security drones at a glance
Read the contract first
The solicitation, FAR clause, agency policy and customer specification determine the actual procurement requirement.
Verify the exact configuration
A brand name is not enough. Check the aircraft, controller, camera, radio, software, cloud, connectivity and supplied components.
Blue List management moved
The Blue UAS Cleared List transferred from DIU to DCMA in December 2025. Use the current DCMA source rather than an old downloaded list.
Procurement is not flight approval
An accepted platform still requires Part 107 compliance, trained pilots, Remote ID, airspace authorization, privacy controls and safe procedures.
Critical rule: never rely on the words “NDAA-compliant” alone
A vendor statement may address one statute, one model or one point in time. It may not establish Blue List status, Green UAS certification, compliance with a federal contract clause, absence from a FASC-covered list or acceptance by a particular agency.
Require evidence identifying the exact model, configuration, software, components, certification or list status, applicable legal framework and date of verification. Recheck that evidence before the bid and again before contract performance.
This page provides general educational information, not legal advice, procurement approval, cybersecurity certification or a determination that a particular platform is acceptable.
What “NDAA-compliant” means—and what it does not
| Statement | What it may mean | What it does not prove |
|---|---|---|
| “NDAA-compliant” | The vendor asserts that the product meets one or more federal supply-chain restrictions. | Which statute, contract clause, components or configuration were evaluated. |
| “Made in the USA” | Some manufacturing or assembly occurs in the United States. | That every restricted component, software service or data connection is acceptable. |
| “American company” | The seller or manufacturer is incorporated or headquartered in the United States. | The origin of controllers, cameras, radios, software, cloud services or ownership interests. |
| “Blue UAS” | The exact platform or component appears in the current defense Blue List ecosystem. | That every configuration, payload, modification or non-defense contract automatically accepts it. |
| “Green UAS” | The platform completed an AUVSI Green UAS assessment pathway. | Automatic federal-agency acceptance or final Blue List inclusion. |
| “Secure drone” | The vendor may offer cybersecurity or data-protection features. | Compliance with a particular statute, standard, customer or mission environment. |
| “Offline capable” | Some functions may operate without an external cloud connection. | That no telemetry, update, support or account service communicates externally. |
The main procurement frameworks
FY2020 NDAA Section 848
Applies defense restrictions to covered UAS, companies, components, software, connectivity and data-storage arrangements linked to covered foreign countries or entities.
American Security Drone Act
Implemented through FAR Part 40 and the contract clause at FAR 52.240-1 for prohibited systems manufactured or assembled by FASC-covered foreign entities.
DCMA Blue List
A defense ecosystem of vetted UAS platforms and components. Management transferred from DIU to DCMA in December 2025.
AUVSI Green UAS
An industry assessment program covering specified product, supply-chain, corporate-cyber and remote-connectivity frameworks.
Agency and customer requirements
A solicitation may impose approved-product lists, domestic-content, cybersecurity, data-location, component or reporting terms beyond a general NDAA statement.
Private-client standards
Critical-infrastructure and enterprise clients may adopt Blue, Green or similar requirements even when no federal procurement statute directly controls the purchase.
Current procurement status — July 2026
| Development | Current position | Security-company action |
|---|---|---|
| Blue List management | Management formally transferred from the Defense Innovation Unit to the Defense Contract Management Agency on December 3, 2025. | Use the current DCMA Blue List source and archive the verification date. |
| Federal contractor prohibition | FAR 52.240-1 prohibits delivery of covered systems and, from December 22, 2025, prohibited operation during contract performance and use of federal funds for their procurement or operation, subject to stated exemptions, exceptions or waivers. | Review the clause and search the current SAM list before proposing or using a UAS. |
| Subcontract flowdown | The FAR clause requires its substance to be inserted into subcontracts and other contractual instruments, including commercial products and commercial services. | Apply the same verification process to pilots, vendors and service subcontractors. |
| Green UAS pathways | AUVSI offers Green UAS Cleared and Green UAS Certified pathways. AUVSI states that Green certification is recognized as a pathway toward Blue UAS Cleared status. | Confirm the exact certification level, platform and current status. |
| FAA operating rules | Supply-chain acceptance does not replace Part 107, Remote ID, airspace or operational-waiver requirements. | Run procurement and flight compliance as separate workstreams. |
Do not use an old spreadsheet as the current approved list
Platform status, model configurations, recognized assessors and covered-entity lists can change. Verify current official or program sources for every bid and purchase.
DCMA Blue List versus AUVSI Green UAS
| Area | Blue List | Green UAS |
|---|---|---|
| Program owner | Defense Contract Management Agency. | Association for Uncrewed Vehicle Systems International. |
| Primary role | Defense trusted catalog and procurement ecosystem for vetted UAS and components. | Industry certification and assessment pathway for secure UAS platforms. |
| Government status | Managed within the U.S. defense procurement environment. | Industry-led rather than a federal acquisition regulation or government list. |
| Current pathways | Blue List processes and DCMA-managed resources. | Green UAS Cleared and Green UAS Certified. |
| Core assessment areas | Security, performance, supply-chain and applicable defense requirements. | Green UAS Cleared focuses on product and device security plus supply-chain risk management. Green UAS Certified adds corporate cyber hygiene and remote operations and connectivity. |
| Relationship | Final Blue List status must be confirmed through the current defense list. | AUVSI states its pathway aligns with and can support progression toward Blue UAS status. |
| Private-security use | Useful where defense or strict government acceptance is required. | Useful for commercial and critical-infrastructure assurance and vendor due diligence. |
| What neither proves | Neither list or certification replaces review of the solicitation, FAR clause, SAM list, exact aircraft configuration, FAA authority, state law or customer-specific cybersecurity requirements. | |
Procurement rule
Use Blue or Green status as strong supporting evidence—not as a substitute for contract review and exact-model verification.
American Security Drone Act and FAR Part 40
FAR Subpart 40.2 implements federal procurement and operation prohibitions involving UAS manufactured or assembled by American Security Drone Act-covered foreign entities.
| FAR requirement | Plain-language meaning | Contractor control |
|---|---|---|
| Delivery prohibition | A contractor may not deliver a FASC-prohibited UAS under a covered contract. | Verify the system before proposal, purchase and delivery. |
| Operation prohibition | From December 22, 2025, a contractor may not operate a FASC-prohibited UAS while performing the contract unless an applicable determination is expressly included. | Check every company-owned, rented, client-owned and subcontractor-operated system. |
| Federal-funds prohibition | From December 22, 2025, federal funds may not be used to procure or operate a prohibited system unless an exemption, exception or waiver applies. | Trace the funding and confirm the contracting officer’s position. |
| SAM search | Contractors must search SAM for the FASC-maintained covered-foreign-entity list before proposing or using a system in performance. | Save the search record, date, entity name and system reviewed. |
| Subcontract flowdown | The substance of the clause must flow to subcontracts and other contractual instruments, including commercial products and services. | Add the clause and verification duty to pilot, vendor and service agreements. |
| Exemptions, exceptions and waivers | Limited statutory routes may apply when the agency makes the required determination and the contract expressly states it. | Do not assume an exception; obtain the written contractual determination. |
| Current authority period | The current FAR text states that the applicable authorities expire December 22, 2028. | Monitor legislation and FAR changes before relying on that date. |
SAM and FASC covered-entity verification
Identify every relevant entity
- Aircraft manufacturer.
- Assembler and brand owner.
- Parent company and affiliates.
- Controller and ground-system supplier.
- Cloud or remote-operations provider.
- Subcontracted operator.
Document the result
- Date and time searched.
- Exact legal entity searched.
- Alternative and former names.
- System and configuration reviewed.
- Search result or reference.
- Person completing verification.
Repeat the check
- Before aircraft assignment.
- Before contract extension or option.
- After ownership or brand changes.
- After adding a new subcontractor.
- After material software changes.
- When the contracting officer requests it.
Stop when the answer is unclear
- Do not interpret similar names casually.
- Do not rely only on the reseller.
- Request manufacturer evidence.
- Refer uncertainty to contract compliance.
- Obtain contracting-officer direction.
- Do not operate pending resolution.
Who needs which procurement standard?
| Security work | Likely requirement | Recommended action |
|---|---|---|
| Direct federal contract | FAR review required | Review FAR 52.240-1, SAM, agency instructions and the solicitation. |
| Federal subcontract | Flowdown may apply | Review the prime contract and every flowed-down UAS clause. |
| Department of Defense work | Defense restrictions | Verify Section 848, Blue List, contract and agency requirements. |
| Federally funded project | Funding review | Identify the source of funds and written recipient or agency terms. |
| State or local government contract | Jurisdiction-specific | Check state procurement law, grant conditions and contract specifications. |
| Critical-infrastructure client | Customer standard | Expect supply-chain, cyber, data-location and remote-access requirements. |
| Private commercial site | May have no statutory NDAA requirement. | Still assess cybersecurity, privacy, lifecycle and future contract needs. |
| School, hospital or public-safety client | Policy and funding check | Review grants, state rules, data sensitivity and local procurement policy. |
| Internal company demonstration | Usually a commercial procurement decision. | Do not imply that demonstration acceptance proves federal eligibility. |
Why the exact configuration matters
Procurement status can attach to a specific platform, component set or approved configuration rather than every product sold under a manufacturer’s name.
| Configuration change | Possible impact | Required control |
|---|---|---|
| Different camera or gimbal | The payload supplier or component origin may differ from the assessed platform. | Verify the exact payload and part number. |
| Replacement flight controller | A repair may introduce an unverified critical component. | Use approved parts and preserve repair traceability. |
| Third-party radio or modem | The command link or network supplier may change the supply-chain position. | Review radios, cellular modules and service providers. |
| Alternative ground-control application | Software origin, support access and data transfer may change. | Approve the exact software, version and hosting arrangement. |
| Cloud-service migration | Data location, administrators, subcontractors or remote access may change. | Repeat cyber, contract and supply-chain review. |
| Firmware update | Connectivity, telemetry, update servers or security behavior may be altered. | Use controlled update and regression testing. |
| Dock integration | The dock may add cameras, controllers, routers, servers and remote vendor access. | Assess the complete docked-drone system, not only the aircraft. |
| Brand or company acquisition | Ownership, control, support and covered-entity status may change. | Repeat entity and contract review. |
Approved platform does not mean unlimited modification
Replacing a critical component or connecting an unreviewed service can move the delivered system outside the evidence on which its acceptance was based.
Supply-chain review matrix
| System area | Evidence to request | Procurement risk |
|---|---|---|
| Aircraft manufacture and assembly | Manufacturing and final-assembly locations, legal manufacturer and model identifiers. | Marketing brand obscures the true manufacturer or assembler. |
| Flight controller | Manufacturer, part number, origin and approved configuration. | Restricted or undocumented critical component. |
| Radios and data-transmission devices | Radio, modem, cellular and command-link supplier details. | Unreviewed communication hardware or network dependency. |
| Cameras and gimbals | Payload manufacturer, model, sensor and component origin. | Aircraft qualifies but the selected payload does not. |
| Ground-control system | Controller manufacturer, operating system and application details. | Unapproved software or foreign-administered service. |
| Operating software | Developer, version, update process, repositories and remote-support arrangements. | Software origin or control is not transparent. |
| Network connectivity | Carriers, gateways, vendor tunnels, remote support and external endpoints. | Data or control travels through an unacceptable service. |
| Data storage | Hosting region, provider, administrators, backups and subcontractors. | Data stored in or administered from a restricted environment. |
| Batteries and charging | Supplier, traceability, safety documentation and replacements. | Counterfeit or untraceable parts undermine system assurance. |
| Repair parts | Approved-parts list, serial tracking and repair-provider controls. | Field repairs introduce nonapproved components. |
| Corporate ownership | Parent companies, subsidiaries, affiliates and material ownership changes. | Covered-entity or foreign-control issue is hidden behind a reseller. |
| Subcontracted services | Operators, cloud vendors, assessors, maintenance and technical-support entities. | Contractor verifies the aircraft but not the supporting service chain. |
Cybersecurity and data due diligence
Account and administrator control
- Individual accounts.
- Multi-factor authentication.
- Role-based access.
- Privileged-user review.
- Vendor access restrictions.
Command and data links
- Encryption.
- Authentication.
- Key management.
- External endpoints.
- Lost-link behavior.
Storage and transfer
- Hosting location.
- Data ownership.
- Retention and deletion.
- Backup locations.
- Export and audit logs.
Software lifecycle
- Patch process.
- Update servers.
- Change notices.
- Rollback capability.
- End-of-support policy.
Security assurance
- Disclosure program.
- Security testing.
- Incident notices.
- Remediation targets.
- Customer communications.
Offline and continuity controls
- Offline operation.
- Backup control method.
- Cloud-outage behavior.
- Local evidence export.
- Contract-exit plan.
Seven-stage compliant procurement workflow
Define the Mission
Identify the site, security purpose, payload, range, flight model, network and evidence needs.
Identify the Authority
Determine the customer, funding, prime contract, FAR clauses, agency rules and required lists.
Build the Shortlist
Use current Blue, Green or contract-approved sources where applicable, without treating them as the final decision.
Verify the System
Review the exact aircraft, payload, controller, software, cloud, connectivity and component configuration.
Verify the Entities
Complete SAM, ownership, supplier, subcontractor and covered-entity checks.
Approve and Test
Complete security, operational, data, acceptance and contract review before deployment.
Monitor and Reverify
Control updates, repairs, ownership changes, list status, renewals and new contract requirements.
Vendor evidence checklist
| Evidence | What it should identify | Weak response |
|---|---|---|
| Compliance statement | Applicable statute, section, model, configuration, date and responsible legal entity. | “All our drones are NDAA-compliant.” |
| Blue List evidence | Current DCMA entry for the exact platform or component. | Old DIU screenshot without current verification. |
| Green UAS evidence | Exact certification pathway, platform, assessed frameworks and current status. | General AUVSI membership badge. |
| Bill of materials or component declaration | Critical components, manufacturers, origin and approved substitutions. | Refusal to identify component suppliers. |
| Ownership disclosure | Parent, subsidiaries, affiliates and relevant foreign ownership or control. | Only the reseller’s name is provided. |
| Software declaration | Developer, hosting, update servers, external connections and remote-support access. | “The app is secure” without architecture information. |
| Data-flow diagram | Where telemetry, video, credentials, logs and backups travel and are stored. | No answer about cloud destinations. |
| Security documentation | Encryption, access, vulnerability handling, audit logs and incident notification. | Marketing brochure with no technical evidence. |
| Lifecycle statement | Support period, patches, parts, end of life and replacement process. | No guaranteed support or notice period. |
| Change-notification commitment | Notice of component, ownership, hosting, software or certification changes. | Vendor may substitute parts without notice. |
| Contract warranty | Accurate representations, remedies, cooperation and continuing notification duties. | Verbal assurance excluded from the purchase agreement. |
Contract and subcontract controls
| Contract control | Purpose | Required evidence |
|---|---|---|
| Exact system schedule | Prevents substitution of a different platform or configuration. | Manufacturer, model, payload, controller, software and serials. |
| Applicable-standard clause | Defines which law, list, certification or customer requirement must be met. | Specific references rather than “NDAA-compliant.” |
| FAR flowdown | Applies federal restrictions to relevant subcontractors and services. | Clause included in pilot, vendor and service agreements. |
| No unauthorized substitution | Stops unreviewed components or aircraft entering the contract. | Written approval requirement. |
| Continuing representation | Requires notice when compliance facts change. | Ownership, list, supplier and component-change notice. |
| Audit and records | Allows verification of claims and system traceability. | Access to relevant certifications, parts and supplier records. |
| Cybersecurity duties | Protects flight, customer and security information. | Access controls, incident notice and data-location terms. |
| Remediation and replacement | Addresses loss of eligibility or incorrect representation. | Replacement, refund, suspension and cooperation provisions. |
| End-of-contract data return | Prevents vendor lock-in or uncontrolled retained data. | Export, deletion and certification of deletion. |
| Contracting-officer direction | Creates a route for uncertain federal requirements. | Written determination rather than informal assumptions. |
Delivery and acceptance testing
Identity and configuration
- Correct manufacturer and model.
- Aircraft and component serial numbers.
- Approved payload and controller.
- Software and firmware versions.
- Remote ID status and registration data.
Supply-chain documentation
- Compliance statement.
- List or certification evidence.
- Critical-component declaration.
- Ownership information.
- SAM verification record where required.
Cybersecurity acceptance
- Default passwords changed.
- Multi-factor authentication enabled.
- External connections reviewed.
- Logs and exports tested.
- Vendor support access controlled.
Operational acceptance
- Aircraft and payload function tested.
- Control links verified.
- Lost-link behavior tested.
- Evidence export confirmed.
- Approved configuration locked.
Acceptance record
Create one signed acceptance pack linking the delivered serial numbers and configuration to the procurement evidence, cybersecurity settings, operating documentation and contract requirement.
Configuration and change control
| Change | Review needed | Operating status |
|---|---|---|
| Firmware or software update | Connections, functionality, security, data flow and approval impact. | Test before release |
| Replacement critical component | Part number, supplier, origin and approved-platform status. | Hold pending verification |
| New payload | Manufacturer, component restrictions, cybersecurity and mission approval. | Separate approval |
| New cloud or network service | Hosting, administrators, data location, remote access and contract terms. | No connection until approved |
| Vendor ownership change | SAM status, covered entities, list eligibility and contract representations. | Immediate recheck |
| Platform removed from a list | Reason, customer direction, existing-contract treatment and replacement plan. | Suspend affected assignment |
| New federal or government contract | Solicitation, funding, clauses, agency rules and customer-approved products. | Requalify the fleet |
Drone-in-a-Box and remote-operations procurement
A docked-drone system contains more procurement and cybersecurity elements than the aircraft alone. The complete system must be reviewed.
| System element | Procurement question | Required control |
|---|---|---|
| Aircraft and payload | Does the exact aircraft and sensor configuration meet the contract requirement? | Match serials and part numbers to approved evidence. |
| Dock controller | Who manufactures the controller and operating hardware? | Include dock electronics in the component review. |
| Routers and modems | Which devices, carriers and network services provide connectivity? | Approve the communication chain and external endpoints. |
| Cloud mission platform | Where is the platform hosted, and who administers it? | Document hosting, subcontractors and customer controls. |
| Remote vendor access | Can the vendor view data, change routes or control equipment? | Use time-limited, logged and approved access. |
| Automatic updates | Can the platform change without customer approval? | Disable or control automatic production updates. |
| Video and telemetry storage | Where are source data, backups and logs stored? | Align data location and retention with the contract. |
| Operational approval | Does procurement acceptance authorize remote or BVLOS operation? | No—complete the separate FAA authorization pathway. |
Continue with the Drone-in-a-Box Perimeter Security guide.
Managing an existing or nonqualifying fleet
| Option | When it may fit | Control required |
|---|---|---|
| Private-commercial fleet only | The aircraft remains lawful and acceptable for clearly separated private work. | Prevent assignment to restricted government or funded contracts. |
| Separate compliant sub-fleet | The company serves both ordinary commercial and higher-assurance customers. | Use distinct asset tags, software, storage and dispatch rules. |
| Phased replacement | Current contracts allow transition while future requirements are known. | Create dates, budgets, training and disposal controls. |
| Vendor-supported reconfiguration | An approved component or software change can create an acceptable configuration. | Obtain written evidence and repeat acceptance testing. |
| Contract waiver or exception | An agency formally determines that a statutory route applies. | Require the written determination in the contract. |
| Retirement or disposal | The platform cannot meet future customer or security requirements. | Erase data, remove credentials and document disposal. |
Segregation must be operational, not just a spreadsheet label
Dispatch systems, asset tags, pilot instructions and contract controls must prevent an ineligible aircraft from being selected for restricted work.
Procurement red flags
| Red flag | Why it matters | Required response |
|---|---|---|
| “NDAA-compliant” with no cited framework | The claim cannot be matched to the contract requirement. | Request the exact statute, clause, list or certification. |
| Old DIU Blue UAS screenshot | Blue List management and status may have changed. | Verify through the current DCMA source. |
| Green logo used as proof of Blue status | Green assessment and final Blue List inclusion are related but not identical. | Verify both statuses independently where Blue is required. |
| No component information | Critical hardware may fall outside the vendor’s broad claim. | Require component and configuration evidence. |
| Reseller cannot identify the manufacturer | Ownership and covered-entity checks cannot be completed. | Stop the purchase until the legal supply chain is known. |
| Mandatory foreign cloud account | Connectivity and data-administration requirements may be affected. | Complete detailed contract and security review. |
| Vendor can substitute parts without notice | The delivered configuration may differ from the reviewed configuration. | Add change notification and approval terms. |
| No export of native footage or logs | Evidence, audits and incident response may be impaired. | Require open export and retention controls. |
| Unsupported promise of “future approval” | Certification or listing is not guaranteed. | Base the purchase on current status or contractual remedies. |
| Procurement team ignores FAA operation | A secure platform may still be unusable for the planned flight model. | Complete operational and procurement reviews together. |
Frequently asked questions
Is NDAA compliance required for every private-security drone operation?
No. A purely private contract may not impose a federal procurement restriction. The customer, funding source, state, contract or company policy may still require a particular supply-chain or cybersecurity standard.
Is NDAA-compliant an FAA approval?
No. It concerns procurement, supply-chain or security requirements. It does not replace Part 107, Remote ID, airspace authorization, BVLOS approval or other flight requirements.
Who manages the Blue UAS Cleared List now?
Management transferred from the Defense Innovation Unit to the Defense Contract Management Agency in December 2025. Verify current platforms through the DCMA Blue List source.
Is Green UAS the same as Blue UAS?
No. Green UAS is an AUVSI assessment and certification program. AUVSI states that its pathway aligns with and can support progression toward Blue UAS status, but current Blue List status must be confirmed separately.
What is the difference between Green UAS Cleared and Green UAS Certified?
AUVSI describes Green UAS Cleared as focusing on product and device security plus supply-chain risk management. Green UAS Certified adds corporate cyber hygiene and remote operations and connectivity.
Does made in the USA prove NDAA compliance?
No. Critical components, software, controllers, data links, ownership and cloud services may come from other sources. Verify the complete system and applicable requirement.
Does a Blue-listed aircraft automatically meet every federal contract?
No. Review the solicitation, FAR clauses, SAM list, agency instructions, exact configuration, payload and customer cybersecurity requirements.
What must a federal contractor check in SAM?
FAR 52.240-1 requires contractors to search SAM for the FASC-maintained list of American Security Drone Act-covered foreign entities before proposing or using a UAS in contract performance.
Does the FAR drone prohibition apply to subcontractors?
The clause requires its substance to be inserted into subcontracts and other contractual instruments, including those involving commercial products and commercial services.
Can a client-owned drone be used on a federal security contract?
Ownership alone does not resolve the issue. The contractor must determine whether operation of that exact system is permitted under the contract, FAR clause and any agency determination.
Can a compliant drone be modified with another camera?
Possibly, but the change may affect the approved configuration or supply-chain evidence. Review the exact payload and obtain approval before use.
Should a Drone-in-a-Box system use a Blue or Green platform?
That depends on the contract. Regardless of aircraft status, assess the dock controller, modem, network, cloud platform, data storage, remote access and software-update chain.
Official and program sources
- Defense Contract Management Agency: Current Blue List
- DCMA: Blue List Transition and Expansion
- Defense Innovation Unit: Formal Blue UAS List Transfer to DCMA
- Acquisition.gov: FAR Part 40 — Information Security and Supply Chain Security
- Acquisition.gov: FAR 40.202 — UAS Procurement and Operation Prohibition
- Acquisition.gov: FAR 52.240-1 — American Security Drone Act Contract Clause
- SAM.gov: Federal Acquisition Supply Chain Security Information
- 10 U.S.C. § 4871, U.S. Government Publishing Office
- AUVSI: Green UAS Program and Certification Pathways
- AUVSI: Green UAS Cleared Platforms
- NIST: Cybersecurity Framework
- FAA: Certificated Remote Pilots and Commercial Operators
- FAA: Remote Identification of Drones
Lists, covered entities, contract clauses, certifications and platform configurations can change. Preserve a dated verification record and obtain direction from the contracting authority when the requirement is uncertain.



