OAM (Operations, Administration, and Maintenance)

Operations, Administration, and Maintenance covers the management functions that keep a network running: configuration, fault detection and resolution, performance monitoring, software upgrades, and security operations. OAM interfaces are highly sensitive and historically a frequent attack vector; they should be on dedicated management networks with strong authentication and monitoring.

Categories: Security ControlsThreats and AttacksProtocols and Standards

OAM in context

Security controls in telecom span signaling firewalls (SS7/Diameter/GTP screening at the network edge), transport encryption (IPsec, TLS, PRINS), identity and access on OSS/BSS, and monitoring at both the packet and log level. Controls are audited against GSMA FS.11/FS.19/FS.20/FS.36 and, in Europe, NIS2 sectoral rules.

Telecom threats range from opportunistic SMS phishing and SIM swap to nation-state grade location tracking and lawful-interception abuse. The common thread is that most attacks exploit the inherited trust model of legacy signaling. SS7 and Diameter were designed for a closed operator community that no longer exists.

To place OAM in the wider telecom-security picture, review SCADA, Cipher Downgrade Attack, Management Plane, SNMP, CLI Spoofing and HI2.

Related terms

Equipment

OSS, OAM and element managers (EMS, NMS)

Articles in the P1 mobile network security guide

Related topic hubs

More from the TelcoSec Glossary

Browse the full TelcoSec Glossary, the Ultimate Guide to Mobile Network Security, or the P1 Arsenal of telecom-security tools.