IM Engineer Study Notes
← Back to list
Security & Privacy
#DRM#디지털저작권관리#포렌식워터마킹#멀티DRM#EME
Last updated · 2026-09-29

DRM (Digital Rights Management)

1. Overview

Definition: DRM is a copyright-protection technology and management framework that encrypts digital content and issues and controls usage rights (licenses) separately from the content, so that the content is consumed only on authorized users, devices, and environments under defined conditions (playback, copy, print, validity period, and so on).

Unlike physical media, digital content shows no quality difference between an original and its copies and can be distributed without limit over networks. This property lowers distribution cost but also becomes a structural risk that threatens the revenue base of creators and rights holders. Because valuable information assets such as music, video, e-books, software, and corporate documents can practically never be recovered once leaked, the focus of control has shifted from "tracing leaks after the fact" to "enforcing rights at the moment of consumption."

Traditional access control governs only up to the moment a file is accessed inside a system boundary and can no longer control the file once it leaves that boundary. DRM, by contrast, binds encryption and policy to the content itself and verifies rights at each moment of consumption regardless of the distribution path. In other words, DRM pursues persistent usage control in which "policy travels with the content wherever it goes," and in this respect it is conceptually linked to Information Rights Management (IRM/E-DRM) and to recent zero-trust data protection.

That said, DRM is not a panacea. Overly restricting the convenience of legitimate users invites user resistance and market shrinkage, while loosening control weakens protection. Therefore an engineer must design not only encryption strength but also user experience, interoperability, fair use under copyright law, and the playback ecosystem (browsers, OSes, chipsets) together.

1.1 Background and Necessity

First, it must respond to the intrinsic digital risks of lossless copying and ultra-low-cost redistribution. Copy protection in the CD/DVD era was media-level, but streaming/download environments require fine-grained control at the level of the content file and the session. For example, a global OTT provider is required by studios, as a contractual condition, to apply hardware-based protection (hardware DRM) in order to deliver 4K UHD content.

Second, as the distribution model shifts from "sale (ownership)" to "subscription/rental (usage rights)," the need to control rights finely by time, count, and device has grown. As with e-book lending, 48-hour movie rentals, and seat-based software licenses, the object of trade has become not the content itself but a "usage right under defined conditions."

Third, demand has grown for preventing leaks of trade secrets, design drawings, and personal-data documents inside enterprises. E-DRM (document security), which assigns view/edit/print/screen-capture/validity-period policies to internal documents, combines with DLP and privacy protection to form one axis of data-centric security.

2. Core Components and Operating Principles of DRM

A DRM system is divided into a packaging layer that encrypts and distributes content, a license layer that verifies rights and issues decryption keys, and a client layer that enforces policy on the actual consumption device. The core design principle is the separation of content from keys and rights. The content is encrypted with a strong symmetric key so that it may be distributed widely, while that symmetric key (the content key) is delivered over a separate secure channel only at the authorized moment of consumption.

flowchart LR
    subgraph PROD["Content production and packaging"]
        C["Original content"] --> PK["Packager (encryption)"]
        PK --> EC["Encrypted content"]
        PK -. content key .-> KM["Key management server (KMS)"]
    end
    subgraph DIST["Distribution infrastructure"]
        EC --> CDN["CDN, store, streaming server"]
    end
    subgraph CONS["Consumption device"]
        CDN --> CL["DRM client, player"]
        CL -->|"rights, device auth request"| LS["License server"]
        LS -. policy lookup .-> RM["Rights and policy store"]
        LS -. key request .-> KM
        LS -->|"license (encrypted content key + rights)"| CL
        CL --> OUT["Decrypt and play (policy enforced)"]
    end

2.1 Content Encryption and Packaging

In the packaging stage, content is encrypted with a symmetric algorithm such as AES-128/256 (CTR or CBC mode). A symmetric key is used because large media must be decrypted in real time, which makes public-key computation unsuitable on performance grounds. Public-key (asymmetric) cryptography is used only in a limited way, to securely deliver and protect the content key itself.

In streaming, content is split into many segments and keys may be rotated per segment or on a periodic basis. This way, even if a specific key is exposed, the damage is confined to that interval. Using MPEG-CENC (Common Encryption, ISO/IEC 23001-7), the common encryption standard for MPEG-DASH/HLS environments, a single piece of encrypted content can be shared across multiple DRMs (Widevine, PlayReady, FairPlay), greatly reducing storage and transmission costs.

2.2 Licenses and Rights Expression

A license is a secure data structure that holds an "encrypted content key + usage rights (policy)." Languages for expressing rights include the REL of MPEG-21 (ISO/IEC 21000) and the open standard ODRL (Open Digital Rights Language), which describe permitted actions (permission), prohibitions (prohibition), duties (duty), and constraints (period, count, resolution, region, and so on). Because a license is bound to a specific device and user, even copying the file to another device cannot decrypt it without that device's license.

2.3 Client-Side Policy Enforcement and Trusted Execution

The final line of defense in DRM is the consumption device. So that the decrypted plaintext is not stolen in memory, on screen, or at the output stage, the client uses white-box cryptography, a Trusted Execution Environment (TEE), a secure video path, and output protection (HDCP). For example, Widevine distinguishes security levels from software-protection level L3 up to L1, where keys and decryption are handled inside a TEE, and studios often require L1 for high definition (HD/UHD).

Component Role Representative technology/standard
Packager Content encryption and segmentation AES-128/256, MPEG-CENC
Key management (KMS) Content-key generation, storage, delivery HSM, KMS
License server Rights verification, license issuance ODRL, MPEG-21 REL
DRM client (CDM) Decryption, policy enforcement TEE, white-box cryptography
Output protection Playback path, screen protection HDCP, secure path

3. License Acquisition and Consumption Process

The flow from a legitimate user requesting encrypted content to playing it is as follows. The key point is that the content-download path and the license (key) acquisition path are separate, and device/rights verification occurs just before playback.

sequenceDiagram
    participant U as User, player
    participant CDN as Content server (CDN)
    participant LS as License server
    participant KM as Key management (KMS)
    U->>CDN: 1. Request encrypted content
    CDN-->>U: 2. Encrypted content, manifest (PSSH)
    U->>LS: 3. License request (device cert, content ID)
    LS->>LS: 4. Verify user rights, subscription, region
    LS->>KM: 5. Look up content key
    KM-->>LS: 6. Return content key
    LS-->>U: 7. License (content key encrypted with device key + policy)
    U->>U: 8. Decrypt in TEE and play with policy enforced

3.1 Step-by-Step Detail

In the device authentication of step 3, the client presents a certificate and device key that prove its trustworthiness. Jailbroken/rooted devices, devices whose integrity is compromised, and revoked clients are filtered out at this stage. This process is the starting point of the chain of trust that prevents a forged client from obtaining keys.

The content key inside the license issued in step 7 is re-encrypted with "that device's public key (or device-unique key)." Therefore, even if the license is intercepted, the content key cannot be extracted without that device's private key. When a license is stored on the device for offline playback, constraints such as validity period and playback count are stored together, so it is automatically invalidated upon expiry.

The decryption in step 8 is carried out, where possible, inside a TEE or secure hardware, so that the plaintext content key is not exposed to the operating system or application layer. The played video is delivered to the display through an HDCP-protected output path, making analog-hole capture through capture cards and the like difficult.

4. DRM Technology Types and Comparison

DRM is divided into several branches by protection target and method. If encryption-based access control blocks "before decryption," watermarking/forensic marking is a complementary means that traces and deters "post-decryption leakage."

4.1 Encryption-Based DRM vs. Watermarking

Encryption-based DRM is a preventive control that fundamentally blocks unauthorized playback in advance. However, it is powerless against content that a legitimate user records off the screen or reacquires through the analog hole. What fills this gap is forensic watermarking, which embeds a unique identifier invisible to the human eye into the content per user/session. When an illegally distributed copy is found, the watermark can be extracted to trace the leak path, so deterrence is maximized when prior blocking (DRM) and after-the-fact tracing (watermarking) are combined.

Category Encryption-based DRM Forensic watermarking
Control timing Prior (before playback) After the fact (leak tracing)
Purpose Block unauthorized access/copy Identify and deter the leaker
Analog hole Vulnerable Can respond
User awareness Present (login, device limit) None (invisible embedding)

The difference arises because the two technologies have different threat models. DRM focuses on blocking "unauthorized consumption," but has limits against the insider threat of an authorized user betraying trust. Watermarking, by contrast, cannot block consumption itself, but enables accountability tracing on leakage, deterring insiders and account sharing. Therefore, in practice both technologies are applied together to premium content (live sports, newly released films).

4.2 Multi-DRM and Interoperability

Because the device ecosystem is fragmented, a single DRM cannot support all terminals. Chrome/Android use Google Widevine, Edge/Windows/Xbox use Microsoft PlayReady, and Safari/Apple devices use Apple FairPlay Streaming. For this reason, content providers adopt a multi-DRM strategy that maps all three DRM licenses to one CENC-encrypted piece of content.

In the browser, the W3C EME (Encrypted Media Extensions) standard connects a JavaScript player with each DRM's CDM (Content Decryption Module). Thanks to EME, protected content can be played with just the HTML5 <video> element without a separate plugin, largely resolving the interoperability problems of the old Flash/Silverlight-based DRM. In practice, global OTTs such as Netflix and Disney+ combine CENC + EME + multi-DRM + session watermarking to cover hundreds of millions of heterogeneous terminals with a single content asset.

4.3 Representative Application Cases

In e-books, Amazon Kindle binds purchased books to an account and device with its own DRM, and library lending services set a period constraint in the license so that access automatically expires when the loan period passes. In enterprise document security (E-DRM), domestic and overseas solutions assign view/edit/print/validity-period/screen-watermark policies to Office and PDF documents, expiring a departed employee's account access to documents or exposing the user's information together on screen capture to deter leaks. In games/software, online authentication (for example, checking with a license server at launch) is combined with code obfuscation and integrity checks; excessive always-on authentication has caused inconvenience for legitimate users and drawn a market backlash in some cases, showing that the balance of control strength matters.

5. Deep Dive: Standardization Trends and Extension to Content Authenticity in the AI Era

The DRM ecosystem keeps evolving around issues of interoperability and trust. First is the convergence of streaming standards. MPEG-CENC defines two schemes, cenc (CTR) and cbcs (CBC-pattern); when FairPlay required cbcs, content initially had to be double-packaged, but recently convergence toward cbcs and adoption of CMAF (Common Media Application Format) has established a direction that supports multiple DRMs and platforms with a single content/format.

Second is the strengthening of hardware trust foundations. UHD/4K premium content effectively requires hardware DRM (Widevine L1, PlayReady SL3000) and HDCP 2.2/2.3 output protection. This reflects studios' threat perception that integrity is hard to assure with software alone, and an end-to-end chain of trust combined with chipset, TEE, and secure boot has become the key.

Third, interest is expanding beyond copyright protection to content authenticity and provenance. As generative AI causes a surge of forged/altered content, provenance-metadata signing such as C2PA/Content Credentials and watermarking of AI-generated works are being discussed. This reflects a new requirement of "verifying the trustworthiness and origin of content," beyond the classic DRM goal of "blocking unauthorized consumption," and shows a convergence of DRM, digital signatures, watermarking, and PKI. However, because the standards and effectiveness in this area are still being established, adoption should prioritize interoperability and verifiability over assertions about any specific technology.

6. Considerations and Implications

First is the balance between protection strength and user experience. Excessive device limits and always-on authentication drive away legitimate users and encourage the use of circumvention tools. Risk-based design is needed that applies software DRM and hardware DRM differentially according to content value and threat level, and that states legitimate conveniences such as offline playback and device transfer explicitly as policy.

Second is interoperability and standards compliance. Because vendor lock-in worsens terminal scalability and cost, a strategy of building multi-DRM around open standards such as CENC/EME/CMAF and packaging the content asset only once in a DRM-neutral way is advantageous in terms of total cost of ownership (TCO).

Third is consistency with law and institutions. One must examine conflicts with fair use and private copying under copyright law, prohibitions on circumventing access controls, consumer protection, and privacy protection (minimal collection and purpose limitation when embedding user-identifying information in watermarks). When controlling personal-data documents with E-DRM, access-right revocation, validity periods, and disposal policies should be designed together to link with the personal-data lifecycle.

Fourth is combining prior blocking with after-the-fact tracing, and operational governance. Because encryption DRM alone cannot stop the analog hole or insider threats, it should run alongside forensic watermarking, DLP, and anomaly detection, with an operational framework that includes key management (KMS/HSM), client revocation, logging/audit, and incident-response procedures.

Fifth is future readiness. It is advisable to prepare, from a mid-to-long-term perspective, a roadmap for transition to post-quantum cryptography (PQC) to protect keys in the quantum-computing era, the use of TEE/confidential computing, and integration with content-authenticity proof (C2PA).

References

In one line: DRM is a copyright-protection framework that encrypts content and separates and binds rights (licenses) to enforce policy at each moment of consumption; it combines CENC/EME-based multi-DRM with forensic watermarking while balancing user experience, interoperability, and legal/institutional requirements.