"Distributed Computing Environment / Remote Procedure Calls", is the remote procedure call system developed for the Distributed Computing Environment (DCE). This system allows programmers to write distributed software as if it were all working on the same computer, without having to worry about the underlying network code.
DCERPC inspection module is responsible for processing the data portion of the packet and performing inspection related tasks such as applying translations to IP addresses and ports contained in the packet when applicable, opening secondary channel etc., with the help of other modules
Since FWSM version 4.1 the inspectione engine has been redesigned and enhanched by RCI (Remote Create Instance) calls over RPC and the processing of RPC messaging.
Microsoft is no longer just using EPM (End Point Mapper)
As Microsoft switched from using pure RPC to use DCOM (ORPC) calls, those non-epm calls will be used more and more. Windows RPC/DCOM services use the RPC Endpoint Mapper to accept initial communications on port 135 and then dynamically transition to ports for the service.
"The OXID Resolver resides at different endpoints (ports) depending on the transport being used. The OXID Resolver optimally resides at the same endpoints as the DCE RPC Endpoint Mapper (EPM). To accommodate systems where DCOM will coexist with existing DCE RPC installations (i.e., where an EPM and presumably a complete DCE RPC runtime already exists), the DCOM implementation on that system will register its interfaces with the DCE EPM and all DCOM implementations must be able to fall back if they make DCOM -specific calls on the DCE EPM endpoint which fail."
Starting with Windows 2000, the ISystemActivator COM interface is used instead of the IRemoteActivation RPC interface.
The IOXIDResolver RPC interface (formerly known as IObjectExporter) is remotely used to reach the local object resolver (OR). The Object Resolver component is in charge to:
return protocol sequences, string bindings and machine id for an object server, given its OXID (ResolveOXID() and ResolveOXID2() (only supported by DCOM version 5.2 and above))
respond to ping requests (SimplePing() and ComplexPing() functions)
respond to ServerAlive() and ServerAlive2() functions requests
NON-EMP support for ASA/FWSM
only the RCI (Remote Create Instance) non-EPM message supported
only 1 WMI message is supported
RemoteCreateInstance (Opnum 4)
Any other message type from IRemoteSCMActivator (eg. RemoteGetClassObject) will not be passed
IOXIDResolver (Opnum 5) that is remotely used to reach the local object resolver and is part of the OXID resolver interface. This Opnum is not supported by us. Essentially, this is a RPC call from WMI (WMI uses DCOM to handle remote calls) to a non-epm subsystem that is DCOM based. Packets with opnum 5 don't need inspection support unless there is NAT involved, as there is no need for opening pinholes.
Opnum 3 & 4, EPM.
Opnum=5, this does not contain port numbers and FWSM does not inspect this. If there is a NAT involved, FWSM does not inspect.
CSCsk97762 - ENH: Allow DCERPC inspect to open pin-holes for WMI queries. non epm map
CSCto43960 - FWSM: DCERPC inspection of packet with multiple segments fail
In addition to the North American Threat Response data center, Threat Response is available in the EU and APIs Threat Response available outside of the United States?JC regions.
Learn more about Threat Response here.
Threat Response is FREE for customers of a growing list of Cisco Security products such as AMP for Endpoints, Umbrella, Firepower NGFW/NGIPS, Threat Grid Portal, and Email Security (SMA). Having any of these products is enough to get free access, though t...
Threat Response leverages an integrated security architecture that automates integrations across select Cisco Security products. It can help you accelerate key security operations functions: detection, investigation, and remediation.
Learn more about Thre...
We have a wired authentication issue and I can't find a solution. The problem is this: we use user or computer certificates issued by Windows domain CA for authentication and it works fine. The certificates are enrolled automatically thr...