OCI-P stands for Open Client Interface - Provisioning. In Cisco BroadWorks, it is the provisioning path used to submit configuration changes and administrative updates. That makes it part of the system’s control plane, not just a background utility.
Security teams care about OCI-P because any XML-driven provisioning channel can become a high-value attack surface. If it accepts untrusted input, weaknesses such as unsafe XML parsing or XXE can let an attacker reach local files, internal resources, or sensitive configuration data. In attacks, this often appears as malformed provisioning requests sent to an exposed interface. In defenses, operators should limit network access, require authentication, and harden the XML parser by disabling external entities and DTD processing. Treat OCI-P like an administrative endpoint: only trusted systems should be able to reach it, and any automation that uses it should be tightly controlled and monitored.