Questions and answers
Questions we're asked.
Start with the basics. The detailed answers below are written for security teams, procurement and counsel. If your question isn't here, ask us on a call.
The basics
What does Pennant do?
Why are drones a problem for places like power plants and water systems?
Is it legal to detect drones?
Do you shoot down or jam drones?
Who do you work with?
How much does it cost to get started?
For security teams, procurement and counsel
What actually happens when you detect something?
In short: The right people get an alert within minutes, your team follows its plan, and police are brought in when needed. Nothing is done to the drone.
The detection is matched against the rules in your post orders. If it crosses a threshold, the people you named are alerted on the channels you chose, within the minutes you set. Where the law and your post orders allow, a response goes to the control‑station location; the site adjusts what it can (emission control, an operational pause, screening). An incident package is built from the record, and if the event warrants it, it is handed to your law‑enforcement partner. Nothing is done to the aircraft.
Is the monitoring 24/7, and is it staffed?
In short: Yes, the system watches and alerts around the clock. People review alerts during agreed hours, and someone is always on call for serious events.
Detection and alerting run 24x7, automated, with on‑call escalation for threshold events at any hour. Analyst review runs in defined hours set in your contract. A staffed watch is added when committed sites cover its cost; we would rather tell you that than sell you a service level nobody is sitting behind.
Can you take a drone down, jam it or take it over?
In short: No. Only certain government agencies may do that. We spot and track drones and help you work with the agency that can act.
Not us. In the United States mitigation belongs to authorized agencies, and the DHS/DOJ rule for state and local agencies does not allow it to be contracted out as a managed service. What we do is everything on the lawful side of that line: detect, track, identify, respond on your side of the fence, and act as the liaison between your security operations and the agency that holds authority. Where the law gives your organization that authority, the gate opens for you and our playbooks and integration cover it.
What can Remote ID tell you about a drone?
In short: Most drones broadcast a public digital ID, a bit like a license plate, showing where the drone is and often where the pilot is standing.
A drone flying with standard Remote ID broadcasts its identity, position, altitude and velocity, and the position of its control station, usually where the pilot is standing. A drone fitted with a broadcast module sends its take‑off location instead (14 CFR 89.305 and 89.315). The broadcast is public by design, so receiving it is lawful. RF energy detection adds aircraft that do not broadcast, where your site's exposure says they matter. We never decode the control link between a drone and its pilot.
What happens if a drone is recovered on our site?
In short: We keep it safe, call the authorities first, and use what we learn to strengthen your site's protection.
It is preserved and documented, and the agency that holds authority is engaged first. Where the law allows, its data is extracted by a specialist partner under chain of custody. Then the incident becomes input: the launch point, approach, platform class, what the aircraft was doing, whether it was detected and how the response ran are recorded as measurements, your site is re‑scored on them, and the playbook is updated. That is the drone incident risk analysis, and it is how every incident makes your site's model sharper. Who may extract what, and when, is settled per engagement, because owners and their authority differ.
Do we have to buy your hardware?
In short: No. You can buy equipment from any qualifying maker, or ask us to buy and install it for you. Either way, you own it.
No. The assessment names the capability class a site needs, the evidence a sensor must produce, and the vendors that meet it. You buy from any of them, outright or with grant funds where you are eligible, or ask us to procure and install it. Either way you own it and we integrate it.
How is this different from a sensor vendor's assessment?
In short: Equipment sellers start with what they sell. We start with your site and tell you what is worth buying, and what isn't.
A hardware‑led assessment starts from what the vendor sells. Ours starts from the site: an exposure model built from its geometry, the owner's legal authority applied before anything is ranked, and capability classes ordered by risk removed per dollar, with the vendors that meet each class named and a line that says what not to buy. The assessment is priced on its own, and the list is the same whether you buy through us or from anyone else.
Is your methodology public?
In short: The method is our own, but every customer sees exactly how their score was worked out.
No. UVRAM, its calibration data and the engine are proprietary. Its provenance is public: it is built on ISO 31000, the physical‑security assessment lineage of CARVER and Sandia's vulnerability‑assessment methods, and cardinal risk scoring (Cox 2008; Hubbard & Seiersen 2016). Every customer receives the full workings behind their own number under agreement, so their auditor, regulator or underwriter can inspect them.
Can we license the software?
In short: Yes, for qualifying organizations. Just ask.
Yes, for qualifying organizations, on request. Scope, eligibility and terms are set per license. Ask on the scoping call or through the form.
Who owns the data?
In short: You do. Your records stay yours, even if you stop working with us.
You do. Raw export is a condition of every sensor we integrate, so the record is yours whether or not you stay with us. We process operator‑location data to the extent the law allows for the service you buy: a single‑owner service serves the owner; a multi‑owner network anonymizes operator positions; assessment data is retained for analysis under the agreement. Sharing beyond that happens on handoff to law enforcement or where a grant requires it.
What if nothing is detected in the thirty days?
In short: That is common, and you still get a full report on your site's weak spots and what to fix first.
That is the likeliest outcome at a fixed site, and the engagement is designed for it. The deliverable is the exposure model, how well your current controls hold up, and the ranked spend plan, none of which needs a detection. The activity rate is reported as a bounded interval with an upper confidence limit, never as zero, and the report says plainly that thirty days in one season is not a year.
How long until we are live?
In short: About ten weeks to the first full report, but the watch is live as soon as the sensors are installed.
About ten weeks from the scoping call to the first report, including the thirty‑day collection window. Monitoring and alerting run from the day the sensors are installed, so the watch is live before the report is.
What does a response exercise involve?
In short: A half‑day practice run with your team, so everyone knows exactly what to do when a drone shows up.
A half‑day with the people who will act: your security lead, the dispatcher or watch, and your law‑enforcement partner where they will join. We walk a detection through the playbook as written, time the calls, find where the handoff breaks, and rewrite it the same day. Exercises are an allowable cost under the FEMA Counter‑UAS Grant Program; whether yours qualifies is your state administrative agency's call.
Is this eligible under the FEMA Counter‑UAS Grant Program?
In short: Public agencies may be able to use federal grant money, applied for through their state. Here are the key dates and rules.
For public entities, through the state administrative agency. For FY2027, state administrative agencies apply to FEMA by 16 November 2026, FEMA expects to make awards on 10 December 2026, and states then have 30 days to submit local projects. A complete local package includes a vulnerability assessment; an Airspace Risk Assessment can supply it. Planning, training, exercises and detection equipment, including Remote ID receivers, are allowable, with no cost share. Licensing fees and recurring operating costs are not, so ask your state administrative agency how it will treat a monitoring service before you budget for one. Pre‑award costs are not allowed. Grant‑funded detection data must be shared with DHS as directed, which our record is built for. Eligibility is the state agency's determination, not ours; we provide a vendor‑neutral assessment your agency can include in its request, and your agency writes its own requirements.
Can a state or local agency take down a drone?
In short: Only police and corrections agencies that the federal government has certified and trained.
Only a certified law‑enforcement or correctional agency. Under the DHS/DOJ final rule published on 6 July 2026 (6 CFR Part 124), certified state, local, tribal and territorial agencies may detect and warn (Tier 1) and, with in‑person training at the FBI's National Counter‑UAS Training Center, mitigate (Tier 2). Mitigation events are reported to DOJ and DHS within 48 hours, and unauthorized mitigation carries civil penalties. Where your agency holds that authority, we plan for it, integrate it and hand off to it; we do not operate it.
Does this satisfy NERC CIP‑014?
In short: The power‑grid security standard doesn't mention drones. We give you a record of what actually flew, so you and your lawyers can decide.
CIP‑014‑4, approved by FERC on 10 September 2026, 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 your evaluation is your and your counsel's call. What we produce is a record of what actually flew, and post orders written in the standard's own vocabulary.
Will you prepare our FAA airspace‑restriction petition?
In short: No. The site and its lawyers file that, but our records provide the evidence it needs.
No. The FAA's fixed‑site restriction process is a proposed rule, not a final one, and when it is final the petition is filed by the facility and its counsel. What we produce is the evidence record the showing of necessity would rest on, and the airspace record that starts the day you start collecting.
Do you also serve drone operators?
In short: No. We only work for the owners of the sites being protected.
No. We serve the owners of fixed sites and never the operators transiting their airspace. Serving both would put us on both sides of the same airspace and would destroy the one claim that makes the assessment worth buying.
Buying this well
Eight questions to ask any airspace security provider. Including us.
The market sells hardware first and authority last. These questions put the order back, and our answers are on the record so you can hold us to them.
| Ask | Our answer |
|---|---|
| Is the assessment priced on its own, or bundled with hardware? | On its ownIt names the capability class and the vendors that meet it, and it says what not to buy. Buy through us or from anyone else; the list is the same. |
| Can my own reviewer inspect your method? | Under agreementThe full workings behind your number go to you and your reviewers: your auditor, your regulator or your underwriter. |
| Is what I may lawfully do applied before you rank options, or after? | BeforeThe authority gate comes before the ranking. Nothing reaches the list that this owner cannot lawfully act on. |
| Will you tell me what not to buy? | YesThe ranked list shows what each option would cost and what it would return, including the ones that earn nothing. |
| Who owns the detection data, and can I export it raw? | You doRaw export is a condition of every sensor we integrate. Sharing follows the service you buy and any grant condition you carry. |
| Is the watch staffed, or automated? | Both, statedDetection and alerting are automated around the clock; analyst hours are defined per contract; a staffed watch is added when committed sites cover it. |
| Do you mitigate, or arrange for someone to? | Not usWe do not operate mitigation and do not sell a managed mitigation service. We plan for it, integrate it, and hand off to whoever the law gives that authority. |
| What do I get if nothing flies for thirty days? | The same deliverableExposure, how well your controls hold up, the ranked spend plan and a rate reported as a bounded interval. The report is written to read well with zero. |
Pennant Airspace Security
Start with a 30‑minute call.
Tell us about your site, who is responsible for it and how it might be paid for. We'll explain what we would look at and what it would take.