In RDP, which virtual channels carry clipboard, drive, printer and audio redirection, and which of them move data out of a session?
answer
- one connection, many named streams
- redirection is a channel, not a port
- printers ride the drive channel
- encrypted does not mean permitted
basics
~20 sA virtual channel is a named data stream inside the one RDP connection. The clipboard uses CLIPRDR and drives use RDPDR, which also carries printers; audio output uses RDPSND. Clipboard and drives move data both ways.
solid answer
~40 sRDP multiplexes display and input with named **virtual channels** inside a single connection; the core protocol treats their contents as opaque. The clipboard is `CLIPRDR` (MS-RDPECLIP) and moves text, images and, through file-contents requests, files, in both directions. Drives are `RDPDR` (MS-RDPEFS), which gives the session host access to the client's file system; printers (MS-RDPEPC) are an extension that rides the same `RDPDR` channel. Audio output (MS-RDPEA) uses `RDPSND` and sends session sound to the client; USB pass-through (MS-RDPEUSB) uses a dynamic channel. The clipboard and file system specifications say channel traffic is protected by the core protocol, so encryption in transit does not decide what may be redirected. That is a host policy, and the default on a session host maps client drives automatically.
go deeper
Know that a virtual channel is a named stream inside the one connection, and that clipboard and drive redirection can move data between the user's machine and the session.
Map each redirection to its channel and specification, including printers riding the drive channel, and name the host settings that limit the clipboard and drives.
Turn the list into review evidence: per channel, the direction that carries data out, the setting that limits it, and what that setting costs the users who rely on it.
Decide which populations keep which channels and accept that every kept channel is a residual exposure to document, not a closed risk.
## What a virtual channel is An RDP connection is one transport stream between a client and a session host. Beside the display and input traffic it carries **virtual channels**: independent, named data streams. MS-RDPBCGR describes static virtual channel data as application-specific and opaque to RDP, split into chunks, with each channel acting as its own stream. A feature such as the clipboard is therefore a client-side component and a server-side component talking over a channel, with RDP only routing the bytes. That design is why redirection is a data-protection topic. Every channel is a path between the session host and the machine the user is sitting at, and each one carries a different kind of content. ## The channels behind each redirection | Redirection | Specification | Channel | What moves | |---|---|---|---| | Clipboard | MS-RDPECLIP | `CLIPRDR` (static) | Clipboard formats both ways, and files through file-contents requests and responses | | Drives | MS-RDPEFS | `RDPDR` (static) | Access from the server to the client's file system | | Printers | MS-RDPEPC | `RDPDR`, as an extension of the drive protocol | Print jobs from the session to a printer the client announces | | Serial, parallel, smart card | MS-RDPEFS device types | `RDPDR` | Device access announced by the client | | Audio output | MS-RDPEA | `RDPSND` (static), or a dynamic channel | Session sound to the client | | USB devices | MS-RDPEUSB | Dynamic channel named `URBDRC` | A client-side USB device presented to the session | Three points are easy to get wrong: - **Printers are not a separate channel.** MS-RDPEPC states that it relies on the file system protocol for transport and only operates once that protocol is initialised. A reviewer who disables only "drives" in their head has not necessarily dealt with printers. - **`RDPDR` is a family, not a drive.** Its device announcement structure names file system, printer, serial, parallel and smart card types. - **A channel name is not a policy name.** The Group Policy settings an administrator uses have their own names, covered below. ## Which ones move data out Data leaves a session through any channel that carries content from the host to the client, and enters through any that carries content the other way. - **Clipboard.** Anything copied inside the session can be pasted on the user's machine, and anything copied locally can be pasted in. Without a restricting setting, arbitrary content flows both ways when clipboard redirection is enabled. - **Drives.** The server gets access to the client's file system, so files can be read from and written to the user's disks from inside the session. Microsoft's policy page says a session host maps client drives automatically on connection by default. - **Printers.** Print output is produced in the session and delivered to a printer on the client side. - **USB.** A device plugged into the client is presented to the session, which differs from file copying because the session talks to the device rather than to files. - **Audio output.** Sound moves from the session to the client. It carries what is heard, not files. ## What the protocol does and does not protect The clipboard and file system specifications each state that they have no security considerations of their own, because all static virtual channel traffic is secured by the core protocol. That statement is about the channel in transit. It does not say that a redirection is safe to allow. Whether a channel exists in a session at all is an authorization decision made on the host. ## What an administrator controls Microsoft's policy CSP page for Remote Desktop Services names the settings used most: 1. `DoNotAllowDriveRedirection`: when enabled, client drive redirection is not allowed and clipboard file copy is not allowed either. When disabled, both are always allowed (clipboard file copy only if clipboard redirection is allowed). 2. `LimitClientToServerClipboardRedirection`: limits what can be pasted into the session, from nothing up to plain text, images, Rich Text Format and HTML. 3. `LimitServerToClientClipboardRedirection`: the same graded limit for what leaves the session. If either clipboard setting is not configured, users can copy arbitrary content in that direction as long as clipboard redirection is enabled. Where a clipboard setting appears in both Computer and User Configuration, the stricter restriction applies. ## Common mistakes - Assuming that because the session is encrypted, redirected content is protected from leaving. - Treating printing as unrelated to drive redirection. - Treating audio as the same risk class as drives or the clipboard. - Believing redirection is opt-in on the host: the policy page describes drive mapping as automatic by default. - Forgetting that a restriction on the host, not a request from the client, is what makes a channel unavailable. In a review, list each channel, state which direction carries data out, and record the host setting that limits it. That produces evidence an auditor can check, rather than a statement that "RDP is encrypted".
- The clipboard and file system specifications say they have no security considerations. Does that make redirection safe to leave on?No. The statement means the channel adds no protection of its own because the core protocol secures all static virtual channel traffic in transit. It says nothing about whether content should be allowed to cross. Whether the clipboard or a drive is available in a session is a host policy decision, so the review has to record the setting that limits each channel.
- Why does a team that disables drive redirection also lose pasted files, even with the clipboard left on?Microsoft's policy page for DoNotAllowDriveRedirection says that when it is enabled, clipboard file copy redirection is not allowed either. Plain text can still move if the clipboard stays on. A team that wants a group to keep some file movement has to give it a sanctioned path inside the environment rather than relying on redirection.
- Says each redirection uses its own network port
- Believes an encrypted RDP session cannot leak redirected data
- Treats printer redirection as independent of the drive channel
- Assumes drive redirection only lets the client read the host's disks
- Assumes drive mapping is off by default on a session host