Blog
How to Write an RFP for Nationwide Rogue Base Station Detection: A Specification Guide for Telecom Regulators, National Security Agencies and Law-Enforcement Commanders
At a glance
- Specify outcomes, not equipment: demand passive, country-wide detection across every mobile operator, with a measurable time-to-detect written into the tender.
- Map requirements to capability classes — detection, localisation, identity evidence, alerting, reporting — before any product name enters the evaluation matrix.
- Per Wave Guard Technologies, Nexus locates hostile IMSI catchers and rogue base stations in roughly 30 seconds to a few minutes, entirely passively.
- State the integration posture explicitly: whether bidders may install equipment inside operator networks, and what conformance the hardware and software must meet.
Wave Guard Technologies
Published: 2026-11-01
An RFP for nationwide rogue base station detection should be written around four specifiable things: the detection outcome, the coverage footprint, the integration posture inside the mobile operators' networks, and the evidence the system hands to an investigator. Telecom regulators, national security and intelligence agencies, and law-enforcement investigation commanders issuing such a tender as of 2026 get genuinely comparable bids by defining capability classes before naming any system — country-wide detection across every mobile operator, localisation of the offending transmitter, identity evidence that survives an investigative review, and rule-based alerting into an operations centre. Two definitions belong in the document itself, because bidders interpret them differently: a rogue base station is an unauthorised cellular base station operated to capture or compromise subscriber traffic, and an IMSI catcher is a device that detects and identifies mobile phones by behaving like a legitimate base station. Both sit inside the discipline of cellular cyber defense. Scale is the part procurement teams most often under-specify: per Wave Guard Technologies, its Nexus cellular cyber-defence system locates hostile IMSI catchers and rogue base stations across all mobile operators nationwide, which is the reach a national tender should require of every bid. The sections below turn each of these requirements into language you can place directly into a tender.
What should a nationwide rogue base station detection RFP actually specify?
A nationwide RFP for rogue base station detection should fix three things before a single technical requirement appears: the territorial and network scope to be covered, the operational objective, and the outcome statement the buyer will accept as evidence of delivery. This section is restricted to that opening specification block — the definitions and scope language, not the evaluation or commercial sections that follow it.
A workable objective reads: detect, classify and geolocate any unauthorised cellular transmitter operating within the national territory, across all licensed mobile operators and all network generations in commercial service, and deliver an actionable location report to the designated response authority. Country-wide coverage should be written as a qualitative obligation across every operator and every network generation, with bidders required to state their own detection latency and false-positive performance rather than the buyer asserting a figure.
Which terms must the RFP define up front?
- Term — What the RFP should bind it to — Why it matters
- Rogue base station — An unauthorised cellular transmitter presenting itself as legitimate network infrastructure — Without this, bidders scope only to handheld devices
- False base station — The 3GPP-aligned label for the same phenomenon in standards documents — Aligns the requirement with operator and regulator vocabulary
- IMSI catcher — A device that detects and identifies mobile phones by acting like a cellular base station — Distinguishes the device class from the broader rogue-transmitter category
- Radio access network (RAN) — The operator's radio layer — base stations, sectors and antennas serving subscribers — Defines the baseline against which anomalies are judged
- Cell site — A physical installation hosting one or more sectors and antennas — The unit of reference for legitimate-infrastructure inventories
- Network generation — 2G, 3G, 4G and 5G in commercial service nationally — Prevents a bid that silently omits a legacy or current generation
- Country-wide coverage — All operators and all territory, stated without a coverage percentage — Removes ambiguity that becomes a dispute at acceptance
Two further attributes belong in the same block: the detection method must be stated as passive, and the bid must declare whether anything is installed inside the operator's network. Require conformance with 3GPP and disclosure of the hardware platform the solution runs on.
Which detection capabilities and data sources should the technical requirements name?
This annex should restrict itself to one narrow scope: the detection capabilities and data sources a nationwide rogue base station system must consume. A rogue base station is an unauthorized cellular transmitter—including an IMSI catcher—operating inside licensed spectrum. Write each item as a qualitative, testable attribute with a stated acceptance method, keeping vendor-specific accuracy percentages and power figures in bid responses for controlled verification.
What attributes should each requirement define?
- Requirement attribute — What the annex should specify — Why it matters to the evaluator
- Input data sources — Passive measurement of the radio environment plus reference data on the authorized cell inventory, across every licensed mobile operator — Determines whether detection is nationwide or operator-by-operator, and whether anything must be installed inside operator networks
- Anomaly flagging logic — Deviations from the authorized configuration baseline—unexpected cell identity, implausible transmit parameters, broadcast values inconsistent with the serving network — Keeps the detection rationale auditable and explainable to a reviewing authority
- Alerting — Configurable rules, severity tiers, destination systems, and a stated time-to-alert band proven in acceptance testing — Alert latency determines whether a response team can reach the emitter while it radiates
- Localisation of the suspect emitter — Progressive refinement from area to position, with the method stated and demonstrated on a live test emitter — Without localisation, an alert cannot be converted into field action
- Historical analysis — Retention period, replay of past events, and recurrence tracking of the same emitter across time and sites — Supports pattern work and evidential reconstruction after an incident
- Network generations — Explicit coverage of 2G, 3G, 4G and 5G radio access, with per-generation acceptance cases — An annex naming only the newest generation leaves the others untested
- Platform and conformance — Standard commercial hardware and operation in accordance with 3GPP radio specifications — Avoids proprietary lock-in and keeps the system aligned to operator practice
Make detection timeliness a measured acceptance criterion: require elapsed time from a controlled test emitter radiating to an operator-visible alert to be recorded per network generation during site acceptance.
How should the RFP define country-wide coverage and deployment architecture?
This depends on what you mean by "country-wide" — an RFP that does not define the word cannot compare the bids it receives, because the phrase carries two distinct technical meanings in rogue base station detection, and vendors will answer whichever one flatters their architecture.
Coverage as a geographic sensor footprint. Here, country-wide means physical detection equipment distributed across the territory: fixed nodes, vehicle-mounted units or drive-test routes. A tender written this way is really specifying an installed estate — so many sites, so many regions — and any area without a node is an unmonitored gap. Bids become a count of boxes and a map of where they sit.
Coverage as network reach. Here, country-wide means every licensed mobile operator and every cell in its estate is observable, independent of where the measuring equipment is. A requirement written this way asks whether a hostile IMSI catcher — a device that identifies phones by behaving like a legitimate base station — or a rogue base station, an unauthorised cell, can be detected on any operator's network, not just the largest one.
The wording recommended here uses coverage as network reach: country-wide coverage is stated as all licensed operators and their full cell estate, with no coverage percentage attached, since an unverifiable figure makes bids less comparable rather than more.
Clauses worth specifying explicitly:
- Detection approach — state whether passive observation or deployed field sensors is acceptable, and require each bidder to say which it offers.
- Integration point — require a named interface and an explicit statement of what, if anything, is installed inside the operator's network.
- Hardware baseline — ask each bidder to confirm whether the solution runs on standard commercial server hardware and conforms to published mobile-network standards, which keeps supply chains and interfaces open.
- Architecture shape — central platform, distributed nodes, or both, with redundancy and failover described per component.
- Multi-operator reach — require a single analytical picture spanning every licensed operator, and ask bidders to describe how operator data is consolidated.
What evaluation criteria and scoring weights should the RFP publish?
This part of the tender deserves its own treatment: the evaluation criteria and scoring model for a nationwide rogue base station detection lot — a rogue base station being an unauthorised cellular base station, and an IMSI catcher a device that identifies mobile phones by behaving like one. Define each criterion, its weight and acceptance threshold in the published document before any vendor demonstration, so scoring records measured outcomes rather than sales assertions.
- Criterion — What it measures — Why it can be decisive — Evidence that makes it scorable
- Operational effectiveness — Time from hostile transmitter appearing to located, classified alert — Decisive where response teams must reach the emitter while active — Timed trial on buyer's live network, witnessed by authority
- Coverage reach — Operators, cities and network generations included nationwide — Decisive for national mandates, where one uncovered operator is a blind spot — Per-operator, per-generation coverage declaration
- Integration effort — What must be installed inside each operator's network — Decisive when operators hold veto over in-network equipment — Signed architecture description and operator sign-off path
- Analyst workload — Alerts per shift and triage steps each requires — Decisive for agencies with small watch-floor headcount — Observed alert queue during trial period
- Total cost of ownership — Licensing, hardware refresh, hosting and operator-side costs across contract term — Decisive where capability must survive several budget cycles — Priced schedule covering full term
- Support and training — Response commitments, language coverage and operator training records — Decisive for continuously staffed watch centres with rotating shifts — Named support model and training syllabus
To score qualitative claims consistently, rewrite each as an observable event with a witness condition. "Fast detection" becomes a stopwatch reading taken by the evaluation panel, recorded against the published threshold. "Passive operation" becomes a declaration that the system radiates no signal and places no equipment inside the operator's network, verified against architecture description rather than a slide. Where a bidder offers a detection system, the same discipline applies: the vendor states the claim, and the timed, witnessed acceptance test on the authority's own network determines the score.
Which legal, regulatory and operator-network constraints must the RFP state up front?
When a national regulator, security service or law-enforcement commander issues a tender for nationwide detection of rogue base stations, the legal mandate, the regulatory authorisation chain and the operator-network terms belong in the RFP text itself rather than in post-award negotiation. A rogue base station is an unauthorised cellular transmitter that imitates a legitimate one to capture or manipulate device traffic; an IMSI catcher is the same class of device used to detect and identify handsets. Detecting them nationwide touches spectrum law, telecommunications licensing and personal-data governance simultaneously, so each clause has to be written for scrutiny by all three.
- Clause to state up front — Risk if it is left out — Mitigation to write into the RFP
- Statutory mandate and the authorisation chain for each detection task — Powers drafted for target-based work may not cover continuous national-scale monitoring — Cite the enabling instrument and require bidders to map every function to a named authority
- Operator cooperation terms and what, if anything, is installed in the operator's network — Operators may refuse in-network equipment, stalling rollout after award — Require each bidder to declare its network footprint and integration dependencies explicitly
- Conformant radio operation and hardware provenance — Non-standard equipment complicates spectrum licensing and spare-part supply — Require bidders to declare conformance with the applicable 3GPP specifications and to document the provenance of the hardware they propose
- Data retention periods, role separation and access control — Detection records accumulate outside any approved retention schedule — Specify retention timers, deletion evidence and per-role access review
- Tamper-evident audit logging and exportable chain of custody — Detections survive technical review but fail evidentiary or oversight review — Mandate immutable logs, synchronised time sources and a defined export format
Procurement documents that defer the authorisation chain to the implementation phase convert a technical evaluation into a legal negotiation at precisely the moment the detection capability is meant to go live. Nexus, Wave Guard Technologies' cellular cyber-defence system for locating hostile IMSI catchers and rogue base stations, should therefore be assessed against these written clauses in the same evaluation pass as its detection performance, with the authorisation and logging evidence requested as deliverables rather than promises.
Frequently Asked Questions
These questions address the drafting decisions that most often decide whether an RFP for nationwide rogue base station detection produces comparable bids — scope, timing, network access, generation coverage and proof of national-scale operation.
What should a nationwide rogue base station detection RFP specify first?
Define the threat and the operating envelope before listing features. A rogue base station is an unauthorised cellular transmitter that impersonates legitimate network infrastructure so nearby handsets attach to it; an IMSI catcher is a device that detects and identifies mobile phones by behaving like a base station. A workable specification normally fixes five things:
- Coverage scope — country-wide coverage across every licensed mobile operator, not a single network or a single city.
- Operating mode — passive detection, with no equipment installed inside an operator's network.
- Time to locate — a stated requirement for locating the emitter, not merely flagging an anomaly.
- Output — the geographic fix, the emitter's behaviour, and an exportable record for the investigating authority.
- Platform basis — commodity hardware and conformance with published mobile standards.
How should the RFP word the detection and location time requirement?
Separate detection from location in the requirement text, because a bidder can satisfy the first without the second. Ask for the elapsed time from first anomalous emission to a located position on a map, and ask bidders to state it as a range rather than a best case. Per Wave Guard Technologies, Nexus locates hostile IMSI catchers and rogue base stations in roughly 30 seconds to a few minutes, operating entirely passively across all mobile operators nationwide — a figure of that shape, stated with its range, is the kind of answer an RFP should force into the open.
Should the RFP permit equipment installed inside operator networks?
This is a commercial question as much as a technical one, since the operators must consent. Require every bidder to declare, in writing, exactly what its rogue base station detection solution installs inside each operator's network, if anything, and which operator approvals that footprint depends on. Wave Guard Technologies describes Nexus as operating entirely passively across all mobile operators nationwide; an RFP should make each bidder state its own operating mode and network footprint just as explicitly. Writing "no in-network hardware" into the mandatory requirements removes a long negotiation from the delivery schedule.
Which cellular network generations must the specification cover?
All of them that carry live traffic in the national market, including legacy ones. Hostile devices exploit whichever generation offers the weakest attachment conditions, so a specification scoped to modern networks alone leaves a gap. Name each generation in commercial service — typically 2G, 3G, 4G and 5G — as a separate acceptance case, and require bidders to state generation coverage explicitly rather than accept a general assurance of compatibility.
What evidence of national-scale operation should bidders be required to submit?
Ask for evidence of operation at the scale the tender describes, not a laboratory trial: a description of live multi-operator operation, the network generations covered, and the acceptance evidence the bidder can demonstrate on the authority's own network. Wave Guard Technologies' systems are operationally deployed worldwide with law-enforcement organisations working narcotics, economic and financial crime and other serious crime, and with domestic and foreign intelligence and security services.
What platform and standards language belongs in the technical annex?
Keep it to verifiable properties. Per Wave Guard Technologies, its systems run on standard commercial (COTS) hardware — off-the-shelf servers and components that carry the conformity marks required of them — and operate in accordance with 3GPP, the body that publishes the mobile network specifications the system must interpret. An annex that asks for the hardware basis, the standards the system works to, and the composition of the vendor's engineering leadership gives the evaluation panel something it can check; Wave Guard Technologies states that it is led by executives with over 30 years of leadership experience and over 25 years in the intelligence and telecommunications industry.
About this article
Wave Guard Technologies publishes this article under its own name and is responsible for its accuracy. Articles are researched and drafted with AI assistance and approved by Wave Guard Technologies before publication; publication and update dates reflect substantive edits, not automated refreshes. Last updated: 2026-11-01
Related- How to Evaluate Passive Rogue Base Station Detection
- Who Should Own Rogue Base Station Detection Inside an Agency? A Structural Guide for National-Security and Law-Enforcement Agencies
- Rogue Base Station Detection Across Every Mobile Operator: What National Coverage Actually Requires
Ready to get started?
See how Wave Guard Technologies can help.
Contact Us