How do I detect the method of IPC in the pipe monitor?

In case of pipe monitoring on Windows, can we know that the actually examined process what kind of IPC method it is using? (Pipe, sockets or shared memory etc.)

Sorry, if it is a trivial question!

Based on the screenshot below, there is a file being sent from the process. I would like to know which type of IPC the process was using in this case.

![0_1736967033591_3d57a8db-494f-4fba-a2c6-5477ef6b0e91-image.png](Uploading 0%)

The screenshot failed to upload; could you try again, please?

Regarding the IPC method, well, the Pipe Monitor shows communications over named and anonymous pipes. To see if a particular read or write is issued over an anonymous or named pipe (and the name of the pipe), you have to follow the log up all the way to the pipe open operation for this particular file ID; there you'll see the file name and the role (client or server).

@vladimir

Thanks for your quick response!

49f4cbea-94d2-4ab4-b64d-0f56e3eb0e4d-image.png

So in this snapshot I went to the file ID. This should be an anonymous pipe.

while in the below snapshot, we can now the file in the first case (and the file serves as a client) As far as I undesrtand.

ff38d254-f645-413e-b086-d102173800ed-image.png

Are those little icons on the snapshot indicates the type of connection besides it is a pipe? (Socket, shared memory, message queue)

Are those little icons on the snapshot indicates the type of connection besides it is a pipe? (Socket, shared memory, message queue)

Pipe Monitor shows named and anonymous pipes only.

Anonymous pipe opens will be marked as (unnamed). If you run a Win32 code to create anonymous pipes such as:

	HANDLE hReadPipe;
	HANDLE hWritePipe;
	dword_t actualSize;
	char data[] = "abcdefghi";
	char buffer[1024];

	::CreatePipe(&hReadPipe, &hWritePipe, NULL, 0);

	::WriteFile(hWritePipe, data, sizeof(data), &actualSize, NULL);
	::ReadFile(hReadPipe, buffer, sizeof(buffer), &actualSize, NULL);

	::CloseHandle(hReadPipe);
	::CloseHandle(hWritePipe);

You should see something like:
86d9aea6-baa1-418e-a3c5-6f7b0e6800e3-image.png