Study guide
3.2 Border Control Function (BCF) & Security Edge
NENA Emergency Number Professional ENP
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the NENA ENP Exam
2 Chapter 1: 9-1-1 Evolution & Legacy Network Architecture
1.1 Evolution of 9-1-1 & Central Office Tandem Architecture 1.2 Legacy Location Infrastructure: MSAG, ANI, ALI & ESN/ESZ 1.3 Legacy Network Signaling: CAMA, SS7 & Selective Routing 1.4 Network Design: Originating Service Providers, Local Loops & Transport Facilities 1.5 Signaling, Transport Protocols & Transmission Systems 1.6 Types and Features of 9-1-1 Systems: Basic, Enhanced & NG9-1-1
3 Chapter 2: Modern Location Technologies & MLTS
2.1 Wireless 9-1-1: Phase I, Phase II & Location Accuracy 2.2 Device-Based Location, Supplemental Data & RapidSOS 2.3 MLTS Compliance: Kari's Law & RAY BAUM'S Act
4 Chapter 3: NG911 i3 Core Network & Security
3.1 NG911 Architecture: The ESInet & Core Services 3.2 Border Control Function (BCF) & Security Edge 3.3 SIP Signaling in NG911 (RFC 3261) & Emergency Call Flow
5 Chapter 4: NG911 Location Services & Call Routing
4.1 Location Information Server (LIS) & PIDF-LO 4.2 Emergency Call Routing Function (ECRF) & LoST 4.3 Location Validation Function (LVF) & Legacy Gateways 4.4 NG9-1-1 PSAPs, EIDO, Additional Data & Transitional Elements
6 Chapter 5: Public Safety Radio, Broadband & FirstNet
5.1 Land Mobile Radio (LMR) Architecture & P25 Standards 5.2 Conventional vs. Trunked Radio Systems & Frequency Bands 5.3 Public Safety Broadband, FirstNet & Mission-Critical Services
7 Chapter 6: Call Processing, Accessibility & Protocol Systems
6.1 Call Answering Standards & Answering Point Workflows 6.2 Accessibility: TTY/TDD, Text-to-911 & Real-Time Text (RTT) 6.3 Emergency Protocol Systems & Medical Direction 6.4 PSAP Types & 9-1-1 Call Handling Equipment
8 Chapter 7: Computer Aided Dispatch & Information Systems
7.1 Computer Aided Dispatch (CAD) System Architecture 7.2 CAD Interfaces: Mobile Data, RMS & External Telematics 7.3 Logging Recorders & Synchronized Master Clocks 7.4 Non-Voice Communications & Information Networks 7.5 NENA Standards & Other Documents
9 Chapter 8: GIS for Next Generation 9-1-1
8.1 NG911 GIS Data Layers: Road Centerlines & Address Points 8.2 Boundary Polygons: PSAP, Law, Fire & EMS Jurisdictions 8.3 GIS Data Quality, Topology & Provisioning Workflows 8.4 9-1-1 Databases: Service Orders, ALI & Routing Records, Number Portability & Database Management
10 Chapter 9: Cybersecurity & CJIS Compliance
9.1 PSAP Cybersecurity Frameworks: NENA NG-SEC & NIST CSF 9.2 CJIS Security Policy: Access Control, MFA & Encryption 9.3 TDoS, Ransomware & Cyber Incident Response Planning
11 Chapter 10: Telecommunications Policy, Funding & Civil Rights
10.1 Regulatory Governance: FCC Authority & Part 9 Orders 10.2 9-1-1 Surcharges, Fee Diversion & Federal Grant Programs 10.3 Civil Rights & Language Access: Title VI & ADA Title II 10.4 Telecommunications Service Priority, Public Utility Commissions & the Canadian Framework 10.5 Special Legislative Areas: Alarms, Mass Notification, Pipelines & Other 9-1-1 Laws
12 Chapter 11: PSAP Governance, Strategy & Facility Design
11.1 PSAP Governance Models: Standalone, Co-Located & Consolidated 11.2 Strategic Planning & Performance Management 11.3 PSAP Facility Architecture, Physical Security & Ergonomics 11.4 Management Decision Making & Short-Range, Long-Range & Strategic Planning
13 Chapter 12: Power Redundancy, COOP & Disaster Recovery
12.1 Electrical Power Redundancy: UPS Systems & Generator Sets 12.2 Continuity of Operations Planning (COOP) & Alternate Facilities 12.3 Disaster Recovery, Redundant Connectivity & Evacuation 12.4 Emergency Management: Disaster Types & the Four Phases
14 Chapter 13: Emergency Incident Management & NIMS/ICS
13.1 National Incident Management System (NIMS) & ICS Architecture 13.2 Emergency Operations Centers (EOC) & Incident Command Interfaces 13.3 Mutual Aid & Interagency Interoperability: MACS & MABAS
15 Chapter 14: Procurement, Contracts & Financial Management
14.1 Capital Budgeting, Operational Expense & Financial Auditing 14.2 Public Procurement: RFPs, RFQs & Bid Evaluations 14.3 Vendor Contracting: MSAs, SLAs & Life-Cycle Management
16 Chapter 15: Staffing Models, Scheduling & Wellness
15.1 PSAP Staffing Models: Erlang C & NENA Staffing Calculator 15.2 Shift Scheduling Models, Overtime & Fatigue Mitigation 15.3 Telecommunicator Wellness: CISM, Peer Support & PTSD
17 Chapter 16: Training, CTO Coaching & Quality Assurance
16.1 Adult Learning & Communications Training Officer (CTO) Models 16.2 Quality Assurance & Continuous Quality Improvement (APCO/NENA ANS 1.107) 16.3 Continuing Education, Certifications & Professional Pathways 16.4 Performance Management, Employee Feedback & Customer Service
18 Chapter 17: Employee Relations, Labor Standards & Legal Protections
17.1 Fair Labor Standards Act (FLSA) & Dispatcher Overtime Rules 17.2 EEO, Title VII, FMLA & ADA in the PSAP Workplace 17.3 Progressive Discipline, Just Cause & Union Negotiations 17.4 Employee Relations, Employment Rights & Labor-Management Relations 17.5 Employment Laws: ADEA, Pregnancy Protections, Uniform Guidelines, OSH Act & Canadian Law 17.6 Compensation Laws: Equal Pay Act, COBRA, Social Security Act & Affordable Care Act
19 Chapter 18: Records Governance, Liability & Public Relations
18.1 Public Records, FOIA & Recording Retention Schedules 18.2 Legal Liability, Tort Claims Acts & Immunity Doctrines 18.3 Public Relations, Media Inquiries & Community Outreach
20 Chapter 19: Recruiting, Hiring, Compensation & Retention
19.1 Recruiting: Workforce Needs, Outreach & Sourcing 19.2 Hiring Procedures: Testing, Interview Panels, Agency Tours & Background Checks 19.3 Compensation & Benefits: Job Analysis, Pay Structures & Medical Benefits 19.4 Employee Retention & Succession Planning
3.2 Border Control Function (BCF) & Security Edge
Key Takeaways Explain This Topic AI
The Border Control Function (BCF) is the mandatory NENA i3 security perimeter gateway deployed at all ingress and egress boundaries of the ESInet and PSAP internal networks.
The BCF integrates Session Border Controller (SBC) capabilities with Next-Generation Firewalls (NGFW) and Intrusion Prevention Systems (IPS), performing deep packet inspection, SIP normalization, topology hiding, and dynamic pinholing for negotiated RTP media.
Topology hiding obscures internal network infrastructure (IP addresses, hostnames, server signatures) in SIP headers (Via, Record-Route, Contact, Call-ID) to protect internal public safety networks from reconnaissance.
Telephony Denial of Service (TDoS) and volumetric DDoS attacks are mitigated at the BCF through algorithmic rate limiting, anomaly detection, STIR/SHAKEN validation, and mutual TLS (mTLS) authentication using Public Safety PKI certificates.
Transitional gateways—including Legacy Network Gateways (LNG), Legacy PSAP Gateways (LPG), and Legacy Selective Router Gateways (LSRG)—must interface through the BCF to ensure strict security isolation and protocol standardization.
Last updated: September 2026
3.2 Border Control Function (BCF) & Security Edge
Quick Answer: The Border Control Function (BCF) is the standardized security gateway defined in NENA-STA-010 that sits at every perimeter boundary of the Emergency Services IP Network (ESInet) and the Public Safety Answering Point (PSAP). Combining Session Border Controller (SBC) capabilities with Next-Generation Firewalls (NGFW) and Intrusion Prevention Systems (IPS), the BCF protects public safety infrastructure from cyberattacks, normalizes non-standard SIP signaling, obscures internal network topology, dynamically controls media pinholes, and mitigates Distributed Denial of Service (DDoS) and Telephony Denial of Service (TDoS) attacks.
Architecture and Role of the Border Control Function
As emergency communications transitioned from closed TDM circuits to open IP networks, PSAPs became vulnerable to the entire spectrum of IP-based threats—including malware, unauthorized penetration, volumetric flooding, and protocol exploitation. To protect life-safety systems, NENA-STA-010 mandates the deployment of a Border Control Function (BCF) at every ingress and egress boundary of the ESInet, between the ESInet and external Originating Service Providers (OSPs), and at the perimeter separating the ESInet from local PSAP LAN networks. BORDER CONTROL FUNCTION (BCF)
- +-----------------------------+
- [ External Networks ] ---------> | [1] Next-Gen Firewall/IPS |
- (Wireline, Wireless, (Untrusted)| - Packet Filtering / Rate |
- 3rd-Party Providers) Ingress | - SYN Flood / DDoS Def |
- | |
- | [2] Session Border Ctr (SBC)| ---------> [ Trusted Internal ]
- | - Topology Hiding | Egress - ESRP / NGCS Core
- | - SIP Normalization | - PSAP CHE Consoles
- | - Dynamic RTP Pinholing | - CAD & Recorders
- +-----------------------------+
Rather than representing a single hardware box, the BCF is an architectural functional entity. In carrier-grade public safety implementations, the BCF is composed of tightly coupled, high-availability clusters comprising:
Next-Generation Firewalls (NGFW) with Intrusion Detection/Prevention (IDS/IPS): Inspects network traffic from Layer 3 through Layer 7, enforcing access control lists (ACLs), protocol conformance, and stateful flow tracking.
Session Border Controller (SBC): An application-layer gateway tailored specifically for real-time SIP signaling and RTP/SRTP media stream governance.
Session Border Controller (SBC) Capabilities in Public Safety
The SBC component of the BCF provides specialized real-time communications security and interoperability that traditional data firewalls cannot perform:
1. Topology Hiding
In native SIP communications, message headers contain extensive forensic metadata regarding internal networks. The Via , Record-Route , Contact , and Call-ID headers reveal internal IP subnets, server domain names, interface designations, and vendor software builds. Threat actors exploit this data during the reconnaissance phase of an attack.
The BCF SBC executes topology hiding by stripping all internal routing information from outbound SIP messages. It replaces internal IP addresses and hostnames with its own external-facing public/routable address before transmitting the message across the boundary. To external entities, the BCF appears as the sole endpoint terminating all calls.
2. Protocol Normalization and Header Sanitization
Although SIP is defined by IETF RFC 3261, telecommunications carriers and PBX vendors implement SIP extensions, optional headers, and syntax variations differently. These discrepancies can cause call handling equipment (CHE) to reject calls or crash. The BCF parses incoming SIP messages, repairs malformed headers, strips unsupported non-standard parameters, and standardizes the signaling to comply strictly with the NENA i3 profile.
3. Dynamic Media Pinhole Management
A critical vulnerability of legacy VoIP firewalls was leaving massive ranges of UDP ports permanently open to accommodate incoming RTP media. The BCF eliminates this vulnerability through dynamic pinholing :
During call setup, the SBC performs deep packet inspection of the Session Description Protocol (SDP) payload embedded within the SIP INVITE and 200 OK messages.
It extracts the exact IP addresses and UDP port pairs negotiated by the endpoints for that specific session.
The BCF opens a narrow "pinhole" in the firewall strictly for those negotiated IP/port combinations.
As soon as a SIP BYE or error response terminates the session, the BCF immediately closes the pinhole , blocking unauthorized packets from penetrating dormant ports.
4. NAT Traversal and Media Bridging
Public safety networks predominantly operate on private IPv4 address spaces (RFC 1918) or dedicated IPv6 ranges, while originating carriers may use public IPs or Carrier-Grade NAT (CGNAT). The BCF bridges these disjoint network realms, rewriting SDP connection addresses and proxying RTP media streams between external carrier interfaces and internal PSAP networks.
Denial of Service (DoS) & Distributed Denial of Service (DDoS) Mitigation
Emergency networks represent prime targets for malicious actors seeking to disrupt critical civil infrastructure. Attacks are classified into volumetric infrastructure floods and application-layer resource exhaustion attacks:
Attack Type Target Layer Attack Mechanism BCF Countermeasure
SYN Flood Transport (Layer 4) Inundates servers with TCP SYN packets, exhausting transmission control block (TCB) memory SYN Cookies, aggressive TCP connection aging, hardware stateful tracking
UDP Reflection / Amplification Network / Transport (Layers 3 & 4) Spoofed UDP packets targeting open DNS/NTP/SNMP reflectors directed at PSAP IPs Upstream BGP Blackholing, hardware rate-limiting, dropping unsolicited UDP packets
SIP INVITE Flood Application (Layer 7) Bombards SBC with thousands of bogus SIP INVITEs to exhaust CPU and call-state tables Algorithmic SIP transaction rate limiting, source IP reputation, digest challenge verification
Malformed SIP Exploit Application (Layer 7) Transmits deliberately oversized or malformed headers to cause buffer overflows in CHE Strict RFC 3261 parsing, regex sanitization, immediate packet dropping and source isolation
Telephony Denial of Service (TDoS) Countermeasures
A Telephony Denial of Service (TDoS) attack is an organized assault designed to saturate inbound 9-1-1 telephone circuits, automated call distribution (ACD) queues, and dispatcher workstations, rendering call-takers incapable of answering real emergency calls.
TDoS attacks manifest in two primary forms:
High-Volume Automated Robocalling: Computer-generated automated scripts place hundreds of simultaneous calls per minute from spoofed originating numbers, hanging up immediately upon answer or playing prerecorded audio.
Distributed Social / Coordinated Harassment: Organized groups manually flood lines, tying up call-takers with bogus inquiries or abusive statements.
BCF Technical Countermeasures against TDoS
Cryptographic Signature Verification (STIR/SHAKEN): When originating carriers sign calls under the FCC's STIR/SHAKEN caller ID authentication framework, the BCF can inspect the SIP Identity header carrying a cryptographic PASSporT token. If the call fails authentication (e.g., an untrusted Attestation Level C or missing signature on a high-volume burst), the BCF flags the session metadata, routing it to specialized scrutiny queues. Attestation results support flagging and analysis only: FCC call-blocking rules protect calls to 9-1-1, so a missing or low attestation is never a reason to reject an emergency call.
Algorithmic Rate Limiting: The BCF monitors call setup velocities per originating trunk, carrier, or source IP. If call requests from a specific originating gateway exceed historical baseline thresholds (e.g., more than 5 calls per second from an unrecognized source), the BCF throttles the excess traffic.
Adaptive Behavioral Profiling: Machine-learning heuristics track anomalous patterns—such as rapid sequential calls resulting in immediate zero-second hang-ups. The BCF isolates the associated sessions without impacting normal call flow.
Interactive Verification (Automated Guard): Some TDoS mitigation designs contemplate diverting clearly identified attack traffic to an automated challenge before it reaches a call-taker. Crucial Rule: Any such technique must be narrowly limited to confirmed malicious traffic under documented policy and must never be applied to legitimate emergency callers.
Mutual TLS (mTLS) & Public Safety PKI Authentication
Within a true NENA i3 ESInet, every network element must prove its identity before establishing a signaling or data connection. The BCF enforces Mutual Transport Layer Security (mTLS - RFC 8446) at the transport layer. +-----------------------+ +------------------------+
- | Ingress BCF Gateway | | ESRP / Core Function |
- | (Presents PCA Cert) | === [ 1. Exchange Certs ] =>| (Presents PCA Cert) |
- | | <= [ 2. Validate Trust ] == | |
- +-----------------------+ +------------------------+
- | |
- +========= [ 3. Establish Encrypted TLS Tunnel ] ======+
- +========= [ 4. Transmit Authenticated SIP ] ==========+
PSAP Credentialing Agency (PCA): NENA i3 defines a public safety Public Key Infrastructure (PKI) for NG9-1-1 whose root of trust is the PCA. Agencies and service providers use X.509 credentials that chain to the PCA, directly or through authorized intermediate certificate authorities.
Bilateral Identity Verification: When an originating gateway connects to a BCF, both sides present their digital certificates. The BCF verifies that the client certificate is chains to the PCA root, has not expired, and does not appear on the Certificate Revocation List (CRL) or Online Certificate Status Protocol (OCSP) cache.
Rogue Endpoint Isolation: Any endpoint failing mTLS authentication is immediately blocked at the perimeter. The BCF logs the security incident and generates an automated alert to the PSAP Cybersecurity Incident Response Team.
Demilitarized Zone (DMZ) Segmentation in NG911
Defense-in-depth requires strict structural network segmentation. A PSAP network must never be deployed as a flat, single-tier subnet. Security best practice, reflected in NENA's NG-SEC guidance, favors a multi-tiered Demilitarized Zone (DMZ) architecture: +-----------------------------------------------------------------------------+
- | UNTRUSTED EXTERNAL ZONE (Originating Service Providers, Commercial Carriers)|
- +-----------------------------------------------------------------------------+
- |
- [ Outer BCF / External Perimeter Firewall ]
- |
- +-----------------------------------------------------------------------------+
- | PERIMETER DMZ (Ingress SBCs, Public DNS, Reverse Proxies, Clearinghouses) |
- +-----------------------------------------------------------------------------+
- |
- [ Inner BCF / Core Security Inspection ]
- |
- +-----------------------------------------------------------------------------+
- | CORE ESInet / NGCS ZONE (ESRP, PRF, ECRF/LVF, LIS, Spatial Interface) |
- +-----------------------------------------------------------------------------+
- |
- [ PSAP Perimeter Firewall / Internal BCF ]
- |
- +-----------------------------------------------------------------------------+
- | SECURE PSAP LAN (Call-Taking Consoles, CAD Workstations, Logging Recorders) |
- +-----------------------------------------------------------------------------+
External Perimeter DMZ: Hosts the outer interfaces of the BCF, carrier demarcation equipment, and public-facing ingress points. It prevents external packets from directly addressing internal servers.
Core ESInet / NGCS Zone: Houses the centralized routing functions (ESRP, PRF), spatial databases (ECRF/LVF), and policy engines. Only authenticated BCF nodes can communicate with this tier.
Secure PSAP LAN Enclave: The most sensitive operational zone, housing Call Handling Equipment (CHE) positions, Computer Aided Dispatch (CAD) clients, and evidentiary logging recorders. Access is governed by micro-segmentation, preventing any direct connection from external networks.
Interfacing Transitional Gateways Through the BCF
During the multi-year transition from legacy 9-1-1 to full NG911, public safety networks must interoperate with legacy TDM networks and non-i3 PSAPs. Three standardized gateways interface directly through the BCF:
Legacy Network Gateway (LNG): Positioned at the ingress of the ESInet. It receives legacy analog, CAMA MF, or SS7/ISUP trunks from wireline Central Offices and wireless Mobile Switching Centers (MSCs), queries the legacy ALI database, and converts the call into an RFC 3261 SIP INVITE with an encapsulated PIDF-LO location object. The LNG hands the newly generated SIP call off to the BCF for perimeter inspection.
Legacy PSAP Gateway (LPG): Positioned at the egress of the ESInet facing a legacy PSAP that cannot process native SIP. The LPG receives SIP i3 calls from the ESInet (via the BCF), converts the SIP signaling into legacy CAMA or ISDN PRI signaling, and translates PIDF-LO location into legacy tabular ANI/ALI records for legacy call-taker consoles.
Legacy Selective Router Gateway (LSRG): Facilitates bi-directional inter-tandem routing between an ESInet and a legacy E9-1-1 selective router, allowing call transfer between NG911 PSAPs and legacy PSAPs.