Managed drone detection and response for critical infrastructure sites.
This document describes the services Pennant Airspace Security offers, what each includes, the service levels behind them, how data and evidence are handled, what a customer must provide, and where the services stop. It is written to be forwarded.
1Overview
Pennant makes airspace risk to a fixed site a measured, auditable number, and then runs the watch that keeps it current. The company specifies the capability a site needs and the vendors that meet it, procures and installs where the customer asks, integrates the sensors the customer owns, turns each detection into a lawful response and a defensible record, and prices what to buy next by the risk it removes.
Three constraints define the offer. Vendor‑neutral: outputs name capability classes and, within each class, the vendors that meet it on published criteria; the assessment is priced on its own and says what not to buy, and any fee on procurement or installation is disclosed in the agreement. Proprietary method, open to the customer: the assessment methodology (UVRAM, the UAS Vulnerability and Risk Assessment Method), its calibration data and the engine are proprietary; each customer and its reviewers receive the full workings behind the customer's own number under agreement, and the software is available under license to qualifying organizations. Inside the law, on the owner's side of the fence: Pennant detects, tracks, identifies, responds on the site and hands off; it does not operate mitigation, which stays with whoever the law gives it to; it acts as the liaison between the customer's security operations and the agencies that hold authority; and it serves site owners, never the operators overflying them.
2Who the services are for
Fixed sites whose loss is felt beyond the fence: transmission stations and generation, process facilities, airports and ports, data centers, water and wastewater, correctional and public‑safety sites, and clusters of these within one radio horizon. The risk belongs to the site; the engagement belongs to the owner.
| Owner | Funding | Authority | Procurement |
|---|---|---|---|
| Private owner‑operator | Capital, operating and compliance budgets | Detect, track, identify; respond on the site; hand off. No mitigation. | Direct. Hardware is the owner's; Pennant specifies, the owner buys. |
| Public agency (state, local, tribal, territorial) | FEMA Counter‑UAS Grant Program through the state administrative agency; no cost share | Any owner may detect, track and identify; under the DHS/DOJ rule, certified law‑enforcement and correctional agencies may also detect and warn (Tier 1) and, with FBI training, mitigate (Tier 2) | Federal grant rules; the vendor contract must enable data sharing with DHS |
| Mixed or joint | Often both an authority's grant path and a tenant's budget | Split between the owner and the agency that polices the site; the gate is drawn per party | Whichever party buys the sensors owns them; the record is shared by agreement |
3Services
3.1 Airspace Risk Assessment
Purpose. A defensible number for the site's aerial exposure, a ranked list of the capabilities that reduce it ordered by risk reduced per dollar, and the reports the decision needs.
Method. The assessment combines an exposure model computed from elevation data before any visit, a thirty‑day passive Remote ID collection on site with a matched off‑site control, a field walk and a structured discovery instrument. It scores the site against a declared design‑basis threat, applies the owner's lawful authority before anything is ranked, and ranks capability classes by risk reduced per dollar, delivered in the report profiles below. The full workings behind the customer's number are disclosed to the customer under agreement.
Deliverables. The exposure model; the measured airspace baseline with its stated interval; per‑objective scores; the ranked treatment frontier including options that survive the gate but earn nothing; and three report profiles from the same scored model: a regulator‑facing evidence record, an underwriter‑facing summary, and an internal finance case. Every number traces to its input, its collection method and the methodology version that scored it.
What the customer provides. A named point of contact; site access under the customer's onboarding rules (badging, safety training, escort, typically four to eight weeks at a utility, started at signature); answers to the discovery instrument; power and mounting for two receiver nodes and a location for the control node; the customer's own authority posture and any standing agreements with law enforcement.
Timeline. About ten weeks from scoping call to readout, including the thirty‑day window. A mid‑window interim readout is offered so the substantive conversation happens before the calendar closes.
The likeliest outcome at a fixed site over thirty days is few or no detections. The deliverable does not depend on detections; the activity rate is reported as a bounded interval with an upper confidence limit, never as zero; and the report states that thirty days in one season is not a year.
3.2 Managed Detection & Response
Detect. Remote ID reception on every site, on sensors the customer owns. Energy detection or radar are added only where the assessment shows the non‑cooperative case changes the answer. Every detection carries its provenance: time, position or bearing, signal level, and the sensor that saw it.
Respond. Alerts by rule to the people the customer names, on the channels the customer uses, within the minutes the post orders set. Dispatch to the control‑station location where the law and the post orders allow. Adjustment of the site, not the aircraft: emission control on the customer's own assets, operational pauses, screening, movement of people and vehicles. Lawful handoff to the agency that holds authority, with the record it needs to act.
Drone incident risk analysis. For events that cross a threshold: the incident package (timeline, detections, response, handoff) and coordination with the customer's security operations and law‑enforcement partner. Where an aircraft is recovered, it is preserved and documented, the agency that holds authority is engaged first, and, where the law allows, its data is extracted by a specialist partner under chain of custody. The incident then becomes measured input: launch point and approach, platform class, the aircraft's apparent objective, detection performance and the response timeline are recorded as measurements, the site is re‑scored on them, and the playbooks are updated. This is how every incident makes the site's model sharper. Pennant does not determine admissibility, does not attribute beyond what the data supports, and does nothing to an aircraft; the record is built so that whoever must rely on it can trace every entry. Authority to extract, and the sequence with law enforcement, are settled per engagement in the playbooks, because owners and their authority differ.
Report. A monthly airspace report (activity, rates with stated intervals, what changed, what it means for the number); an incident package for every event that crosses a threshold; an evidence record the customer owns; re‑scoring when the law, the site or the threat changes.
| Service level | As offered |
|---|---|
| Detection and alerting | 24x7, automated. Rules set in the playbooks; alerts to named people on chosen channels within [__] minutes of a threshold event; on‑call escalation at any hour. |
| Analyst review and escalation | Defined hours per contract [__ to __, __ days]; escalation paths for events outside them. A staffed watch is added when committed sites cover its cost, and the customer is told when that happens rather than sold it in advance. |
| Reporting | Monthly airspace report within [__] business days of month end; incident package within [__] hours of a threshold event; re‑scoring on a change of law, site or threat. |
| Availability of the alerting service | Target [__]% monthly, excluding sensor outages on the customer's equipment and planned maintenance notified [__] days ahead. |
| Hardware | Customer‑owned. Pennant specifies the capability class and the evidence it must produce; the customer buys, or the grant does; Pennant procures and installs on request. No inventory, no lock‑in. |
Pennant does not operate mitigation (jamming, protocol takeover, kinetic or signal interception) and does not offer a managed mitigation service; in the United States these are reserved to authorized agencies. Where the law gives the customer or its agency that authority, Pennant plans for it, integrates it into the playbooks and hands off to it. Nothing in this service acts on an aircraft.
3.3 Reporting & Compliance
One scored model renders into the languages the decision travels in. Board and finance: what the exposure is, what it would cost to reduce it, what the next dollar buys. Regulator‑facing evidence record: the inputs, methods and versions behind every number, usable in the customer's own compliance evaluations. Underwriter‑facing summary: the score, its basis and its stated boundary (a prioritization on a 0 to 1 scale, not an annualized loss expectancy). Grant overlay, on the evidence record: for public owners, the record is exportable and structured to satisfy the grant's data‑sharing condition.
On NERC CIP‑014‑4: approved by FERC on 10 September 2026, it requires an evaluation of the potential threats and vulnerabilities of a physical attack on each identified station, and a physical security plan with provisions to evaluate evolving physical threats. The standard names no aerial threat. Whether an aerial threat belongs in a given utility's evaluation is the utility's and its counsel's call; Pennant produces the record of what actually flew and post orders written in the standard's own vocabulary.
On the FAA's proposed fixed‑site restriction process (proposed 14 CFR Part 74): not a final rule. When final, the petition is filed by the facility and its counsel; Pennant produces the evidence record and does not prepare or file regulatory submissions.
3.4 Planning & Exercises
Incident playbooks. Written from the scored model: what is watched, who is called, on which channel, within how many minutes, what the site may and may not do, and how the handoff to law enforcement works. Called post orders where the customer runs a guard force. Reviewed annually and on any change of law or site.
Integration workflows. How the watch sits inside the customer's security operations: alert routing, dispatch, the video management or physical security platform, and the escalation path to the agencies that hold authority.
Response exercises. A half‑day with the people who will act (the customer's security lead, the dispatcher or watch, and the law‑enforcement partner where they will join): a detection is walked through the post orders as written, the calls are timed, the points where the handoff breaks are found, and the orders are rewritten the same day.
Grant‑support assessment for public owners: a vendor‑neutral vulnerability assessment of the sites in the agency's jurisdiction, in a form the agency can include in its subaward request. The agency writes its own requirements and specifications. Eligibility is the state administrative agency's determination; Pennant does not draft, decide or file the application.
4Hardware and integrations
Pennant integrates detection hardware the customer already owns or buys on Pennant's specification. Sensor classes: Remote ID receivers; RF energy detection; radar; EO/IR cameras; acoustic sensors. A sensor is integrated when it provides raw per‑detection export by API or file without a live subscription; written customer ownership of the data with retention and deletion terms; calibration and test records for the evidence chain; no decoding of control‑link content; and, where the buyer is public, US manufacture and a Section 889 statement. Detections are delivered as events with provenance to the customer's alert channels, to its video management or physical security platform where an API exists, to its security operations tooling, to its law‑enforcement partner on handoff, and to DHS where a grant requires it.
Vendor performance claims enter the model as upper bounds, not values, and any result computed from one says so.
5Data, evidence and privacy
- Ownership. The detection record and the assessment outputs belong to the customer. Pennant retains de‑identified, aggregated, non‑attributable data for calibration under the data‑rights clause of the agreement.
- Operator location. Retained and used to the extent the law allows for the service tier: a single‑owner service serves the owner; a multi‑owner network anonymizes operator positions; assessment data is retained for analysis under the agreement. Remote ID is a public broadcast; Pennant does not decode control‑link content.
- Sharing. On lawful handoff to law enforcement; to DHS where the customer's funding requires; otherwise only by the customer's instruction.
- Sensitive findings. Site‑specific vulnerability findings may be critical infrastructure information; they are held under the customer's handling rules, are not used in marketing, and any reference or case study requires the customer's written consent.
- Retention. [__] months for the raw record and [__] years for reports unless the agreement says otherwise; deletion on request at contract end, with a certificate.
6Onboarding
| Step | When | What happens |
|---|---|---|
| Scoping call | Week 0 | Site class, who holds authority, funding path, which report profile the decision needs. |
| Agreement and access | Weeks 0–2 | Agreement with data rights; insurance certificates; the customer's contractor onboarding started (typically four to eight weeks at a utility, in parallel). |
| Exposure model and discovery | Weeks 1–3 | Elevation data, reverse line of sight, approach sectors; discovery instrument answered remotely; placements computed. |
| Site visit and placement | Weeks 3–4 | Field walk; nodes installed at the site and at the matched control; post orders drafted. |
| Collection window | Weeks 4–8 | Thirty days of passive reception. Monitoring and alerting run from day one. |
| Report and readout | Weeks 9–10 | Scoring, the frontier, three report profiles, readout with the people who will spend the money; monitoring continues. |
7Boundaries
- Pennant does not operate mitigation and offers no managed mitigation service; where the customer or its agency holds that authority, Pennant plans, integrates and hands off.
- Facility‑side only: no services to drone operators.
- Capability classes with named qualifying vendors; procurement and installation on request, with any fee disclosed in the agreement.
- No regulatory filings on the customer's behalf; the evidence record is produced, the customer's counsel files.
- The risk score is a prioritization, not a calibrated annual probability or an annualized loss expectancy.
- Illustrative figures in public material are synthetic and labeled; nothing on Pennant's public pages is a customer's site data.
8Commercial structure
| Service | Basis | Figure |
|---|---|---|
| Airspace Risk Assessment | Project fee per site, including the thirty‑day collection window and the three report profiles | [$__] |
| Managed Detection & Response | Recurring, per site per month, on customer‑owned sensors; shared‑coverage pricing for genuine clusters | [$__ / site / month] |
| Reporting & Compliance | Included in monitoring; additional profiles or re‑scoring outside a change event at a project fee | [included / $__] |
| Planning & Exercises | Post orders included in the assessment; exercises at a day rate; grant‑support assessment at a project fee | [$__ / day · $__] |
| Hardware | Bought by the customer from any qualifying vendor, or procured by Pennant on the customer's instruction | [pass‑through / disclosed fee] |
| Installation and integration | Sensor installation, alert routing, VMS or security‑operations integration, playbook build | [$__ per site] |
The assessment is priced on its own and is not discounted to win the monitoring or the hardware. Every agreement carries the data‑rights clause, the customer's ownership of the record, the disclosure of any procurement or installation fee, and the boundaries in section 7.
9Glossary
- C‑UAS
- Counter‑unmanned aircraft systems: the field. Pennant's services cover detection, tracking, identification, defender‑side response and reporting, not mitigation.
- Remote ID
- The broadcast most drones are required to transmit, identifying the aircraft and its control station. A public broadcast; receiving it is lawful for anyone.
- MDR
- Managed detection and response. In cybersecurity, a service that watches a customer's telemetry and acts on it. Here, the same shape applied to airspace, with response limited to what the owner may lawfully do.
- Post orders
- The standing instructions for the watch: what is watched, who is called, what is logged, what may and may not be done. The term is borrowed from contracted guard forces.
- UVRAM
- The UAS Vulnerability and Risk Assessment Method: Pennant's proprietary, versioned assessment methodology. The workings behind a customer's number are disclosed to that customer under agreement.
- The gate
- The step in the method where the owner's lawful authority is applied before options are ranked.
- Treatment frontier
- The ranked list of capability classes ordered by risk reduced per dollar, with the knee marking where the next dollar stops buying much.
- SLTT · SAA · NOFO
- State, local, tribal and territorial government; state administrative agency (the grant applicant for FEMA preparedness grants); notice of funding opportunity.
- CIP‑014‑4
- The NERC physical‑security reliability standard for identified transmission stations, substations and control centers, approved by FERC on 10 September 2026, effective 1 October 2028.
10Sources
- FEMA, Counter‑Unmanned Aircraft Systems Grant Program, Notice of Funding Opportunity, FY2027 (October 2026).
- DHS and DOJ, Counter‑UAS Authority for State, Local, Tribal and Territorial Law Enforcement and Correctional Agencies, final rule, Federal Register, 6 July 2026 (6 CFR Part 124).
- FERC, Order Approving Reliability Standard CIP‑014‑4, Federal Register, 15 September 2026 (91 FR 58430, Docket RD26‑9‑000); NERC, Reliability Standard CIP‑014‑4.
- FAA, Designation: Restrict the Operation of Unmanned Aircraft in Close Proximity to a Fixed Site Facility, notice of proposed rulemaking, 6 May 2026 (Docket FAA‑2026‑4558).
- FAA, DOJ, DHS and FCC, Advisory on the Application of Federal Laws to the Acquisition and Use of Technology to Detect and Mitigate Unmanned Aircraft Systems, August 2020.