Skip to main content

Protection

Protection is the set of technical, administrative, and physical measures that prevent, detect, and mitigate harm or unauthorized access to systems, data, services, or infrastructure.

Expanded Explanation

1. Technical Function and Core Characteristics

In information and cybersecurity, protection denotes safeguards that preserve the confidentiality, integrity, and availability of information and systems. It includes controls such as access control, encryption, network security, endpoint security, and workload or application protection.

Standards bodies describe protection as a combination of preventive, detective, and corrective controls that reduce the likelihood or impact of threats and vulnerabilities. Protection also covers resilience capabilities such as backup, redundancy, and recovery to maintain system operation under adverse conditions.

2. Enterprise Usage and Architectural Context

Enterprises use protection as a design principle and control objective across security architectures, risk management frameworks, and data governance programs. Architectures such as zero trust, defense in depth, and Secure Access Service Edge (SASE) embed protection requirements into identity, network, data, and application layers.

Protection appears in regulatory and standards frameworks that require organizations to implement safeguards for personal data, critical infrastructure, and industrial control systems. Security baselines, reference architectures, and control catalogs operationalize protection into specific technical configurations and procedures for enterprise environments.

3. Related or Adjacent Technologies

Protection relates closely to detection, response, and recovery, which together form broader cybersecurity and resilience strategies. While protection focuses on preventive and mitigating measures, detection and response address monitoring, incident handling, and containment after events occur.

Adjacent technologies include identity and access management, data protection and privacy-enhancing technologies, network and cloud security services, endpoint protection platforms, and security configuration management. Governance, Risk, and Compliance (GRC) tools reference these technologies as mechanisms to implement protection requirements.

4. Business and Operational Significance

For enterprises, protection supports regulatory compliance, risk reduction, and operational continuity. It reduces the probability and impact of data breaches, system outages, fraud, and safety incidents in digital and cyber-physical environments.

Protection practices inform security policies, Third-Party Risk Management (TPRM), and investment decisions for security platforms and infrastructure. They also provide criteria for security assurance, audits, and certifications that stakeholders use to evaluate the security posture of services and partners.

Related Perspectives

CISA issues update on missing IPsec integrity for Verizon IMS SIP signaling

June 2, 2026

Overview VoLTE deployments on Verizon’s IMS network have historically lacked IPsec-based integrity protection for SIP signaling, contravening well-established requirements in 3GPP TS 33.203 and GSMA IR.92. As a result, SIP messages—including registration (REGISTER), call setup (INVITE), and messaging (MESSAGE)—were transmitted in plaintext without cryptographic guarantees of integrity or authenticity. Passive analysis of live traffic over multiple months confirmed the consistent absence of SIP Security Agreement headers and ESP traffic, indicating a systematic configuration decision rather than an isolated anomaly. In response to repeated follow-up inquiries, Verizon stated on [insert date] that integrity support is “currently available at their request” and will be extended to all UEs “starting later this year.” Separately, the researchers recently observed that Apple’s iOS 26.5 carrier bundle (released May 11, 2026) includes IMS IPsec-related configuration entries—an indication that device-side support may now be active or enabled in newer software. While this change is promising, its real-world impact remains uncertain: there is no evidence yet that Verizon has modified its network to enforce IPsec, that the configuration is being activated per session, or that integrity is functionally operational in production deployments. Absent explicit verification (e.g., captured ESP traffic or official confirmation), this may reflect preparatory software changes rather than an end-to-end security upgrade. The vulnerability remains active for the vast majority of Verizon VoLTE users during the unprotected period, and until network-level enforcement is observed and confirmed, the risk of on-path signaling manipulation endures. Description CVE-2026-10629 SIP signaling stack in Verizon IMS (unspecified version) implements SIP signaling without IPsec integrity protection (missing Security-Client/Security-Server headers and ESP traffic), which allows an on-path attacker to compromise confidentiality, integrity, and authenticity of VoLTE signaling via passive monitoring and active manipulation of unsecured SIP messages over the radio and core network. According to 3GPP TS 33.203 and GSMA IR.92, SIP signaling between the UE and P-CSCF in IMS networks must be protected using IPsec ESP with mandatory integrity following IMS AKA authentication. This protection is negotiated via SIP Security Agreement headers (Security-Client, Security-Server, Security-Verify) during registration and results in integrity-protected ESP traffic for all subsequent signaling messages. However, observations conducted over several weeks on Verizon’s network showed no such headers in use. The REGISTER exchange lacked any security negotiation, and post-registration SIP traffic—including INVITE, MESSAGE, BYE, and UPDATE—traversed the network in plaintext over standard UDP/TCP, with no ESP encapsulation. This pattern was consistent across device models and network conditions, indicating a systemic configuration decision rather than a transient issue. The absence of integrity checking means any modification to SIP messages—including redirection of emergency calls or injection of fake message payloads—would go undetected by both the UE and the IMS core. No technical justification for this deviation from globally adopted security practices has been provided by Verizon, and prior engagement failed to elicit a substantive response beyond the recent, non-binding commitment to future deployment. Impact The lack of IPsec integrity protection enables on-path attackers—including those controlling femtocells, compromised base stations, or IMS intermediaries—to intercept, modify, replay, or inject SIP messages without detection. These capabilities permit call hijacking, spoofing of SMS-over-IMS, denial-of-service through forged BYE or CANCEL, and manipulation of emergency call routing—without requiring compromise of the UE, SIM, or backend infrastructure. Because SIP signaling lacks cryptographic integrity, all such modifications go unnoticed by both the UE and the IMS core, undermining core security assumptions of VoLTE. While the recently observed iOS 26.5 configuration change may signal progress toward a more secure implementation, its operational impact is yet to be demonstrated; until then, the risk remains real and unmitigated for users on unprotected deployments. Solution Until the vulnerability is fully mitigated by Verizon, users and enterprises should continue to assume VoLTE signaling is untrusted for high-assurance operations. Acknowledgements Thanks to DongWon Lee, Jeongmin Choi, and CheolJun Park from Kyung Hee University for their thorough technical report, persistent follow-up efforts, and the additional observation regarding iOS 26.5. Their work has significantly advanced the understanding of this issue and helped keep the discussion grounded in observable behavior. This AI-assisted document was written by Timur Snoke.