The Copy and Improve Dilemma: A Case Study of How Microsoft Hijacked the Kerberos Standard

Microsoft embedded the proprietary Privilege Attribute Certificate in RFC 4120 Kerberos tickets, converting an open IETF standard into Active Directory lock-in fined 497.2 million euros in 2004.

The Copy and Improve Dilemma: How Microsoft Rendered the Kerberos Standard Obsolete and What Independent Inventors Can Do to Protect Their Designs

Executive Summary

Microsoft’s adoption of Kerberos version 5, the open authentication protocol codified in RFC 4120, and its subsequent augmentation with proprietary extensions embedded in the Privilege Attribute Certificate structure represents the most fully documented case study of how an incumbent can absorb an open standard, enrich it with undisclosed proprietary data, and produce a de facto lock-in that no competing system can break without first reverse-engineering or licensing the incumbent’s specification. This report examines that operation in technical and legal detail, draws on the European Commission’s March 2004 decision fining Microsoft 497.2 million euros for abuse of dominant position, and connects the Kerberos case to the broader legal tools available to independent inventors who need to prevent their protocols, designs, and technical standards from being optimized into oblivion by larger market participants.

The central finding is this: an open protocol becomes a proprietary moat not at the moment of adoption but at the moment the adopter embeds proprietary data in the protocol’s extension fields and then requires all participants in the network to parse that proprietary data to function. In the Kerberos case, Microsoft accomplished this through the Privilege Attribute Certificate, a binary blob inserted into the AuthorizationData field of every Kerberos service ticket issued by a Windows domain controller. Because Active Directory domain membership requires PAC validation, every non-Windows system that wants to authenticate in a Windows domain must implement Microsoft’s proprietary PAC specification, not just the IETF standard.

For independent inventors, the lesson is specific and actionable. A design that enters an open standard without patent protection, without a trade secret layer on the implementation, and without a FRAND licensing commitment recorded in a standard-setting organization’s intellectual property rights policy is a design that a well-resourced incumbent can adopt, extend, and effectively own. The legal tools that exist to prevent this outcome include continuation patent applications under 35 U.S.C. § 120, standard essential patent declarations under SSO intellectual property rights policies, defensive publication under 37 C.F.R. § 1.139, trade secret protection under the Defend Trade Secrets Act of 2016, 18 U.S.C. § 1836, and, in the most serious cases, a Sherman Act § 2 antitrust claim against the incumbent for monopoly maintenance through the abuse of a standard.

Detailed Findings

What Is Kerberos and How Did It Enter the Enterprise Network?

Kerberos version 5 is a network authentication protocol developed at the Massachusetts Institute of Technology in the late 1980s under Project Athena. The IETF first standardized it in RFC 1510 in 1993. RFC 4120, published in July 2005, superseded RFC 1510 and remains the current authoritative specification for the Kerberos Network Authentication Service. RFC 4120 specifies a ticket-granting system in which a Key Distribution Center issues encrypted tickets to authenticated users, and services validate those tickets without contacting the KDC for every request. The protocol was designed for interoperability: any system implementing RFC 4120 can authenticate to any other compliant system, regardless of operating system or vendor.

Microsoft adopted Kerberos v5 as the primary authentication protocol for Windows 2000 and Active Directory, replacing the proprietary NTLM protocol that had governed Windows network authentication through the 1990s. At the time, the adoption of an open IETF standard appeared to represent a step toward interoperability. The Microsoft documentation made clear that Windows Server was implementing the open Kerberos standard. What that documentation did not initially disclose was the scope and nature of the proprietary extensions Microsoft had embedded inside the standard’s extension fields.

How Did Microsoft Extend Kerberos With the Privilege Attribute Certificate?

RFC 4120 defines an AuthorizationData field in the Kerberos ticket structure. The specification reserves this field for authorization data that implementations may attach to tickets. Microsoft used this field to embed the Privilege Attribute Certificate, a proprietary binary data structure documented internally as [MS-PAC]. The PAC carries Windows-specific security information that the base RFC 4120 protocol does not define: Security Identifier values identifying the user and every security group the user belongs to, user account profile information, logon and password metadata, and cryptographic signatures used by the domain controller and the target service to verify PAC integrity.

The consequence of this design is that a service running on a Windows domain will, by default, reject any Kerberos ticket that does not contain a valid PAC. If a Linux server running MIT Kerberos issues a ticket to a user, that ticket will be a fully compliant RFC 4120 ticket, but it will contain no PAC. A Windows service receiving that ticket will either fail authentication entirely or produce authorization errors because the service cannot resolve the user’s group memberships and access rights without the PAC-embedded SIDs. Conversely, when a Windows client authenticates to a non-Windows service, the client presents a ticket containing the PAC. If the non-Windows service does not implement PAC parsing, it cannot extract the authorization data, and authentication either fails or degrades to a lesser security model. The PAC made true interoperability impossible without implementing Microsoft’s specification.

Microsoft published the [MS-PAC] specification publicly only after the European Commission compelled disclosure of interoperability information as a condition of its March 2004 antitrust decision. Prior to that disclosure, developers who needed to build systems interoperable with Active Directory had to reverse-engineer the PAC structure from network traffic, as the Samba project team did beginning in the early 1990s when Andrew Tridgell used a packet-sniffing approach to reconstruct Microsoft’s undocumented SMB and authentication protocols.

What Does Antitrust Law Say About Proprietary Extensions to Open Standards?

The United States Court of Appeals for the District of Columbia Circuit, in United States v. Microsoft Corp., 253 F.3d 34 (D.C. Cir. 2001), affirmed that Microsoft had maintained a monopoly in the market for Intel-compatible personal computer operating systems in violation of § 2 of the Sherman Act, 15 U.S.C. § 2. The court held that the relevant question under § 2 is whether the defendant willfully acquired or maintained monopoly power through anticompetitive conduct, as distinguished from growth or development as a consequence of a superior product, business acumen, or historical accident. The D.C. Circuit did not reach the Kerberos protocol extensions directly, because the antitrust proceedings focused on the browser and operating system market, but the legal standard it articulated applies with equal force to authentication protocols.

The European Commission’s March 24, 2004 decision, finding that Microsoft had abused its dominant position under Article 82 of the Treaty Establishing the European Community (now Article 102 of the Treaty on the Functioning of the European Union), addressed the interoperability problem directly. The Commission found that Microsoft had refused to supply indispensable interoperability information, specifically the technical specifications for protocols used in communications between workgroup servers and between workgroup servers and personal computers. The Commission ordered Microsoft to supply those specifications on reasonable and non-discriminatory terms. The initial fine was 497.2 million euros. When Microsoft failed to comply adequately with the interoperability remedy, the Commission imposed an additional fine of 899 million euros in 2008. The cumulative enforcement cost exceeded 1.3 billion euros before additional administrative proceedings concluded.

The legal basis for the European decision maps directly onto what happened with Kerberos. An incumbent that controls an essential input to a market, in this case the authentication infrastructure that Windows domain networks require, and that withholds the technical specifications necessary for competitors to interoperate, abuses the dominant position. In the United States, a similar theory could be advanced under § 2 of the Sherman Act, provided the plaintiff can establish a relevant product market, the defendant’s monopoly power in that market, and a willful course of anticompetitive conduct that maintained or extended that power. The ’embrace, extend, extinguish’ strategy, if accompanied by the withholding of specifications and the creation of artificial network effects, can satisfy each of those elements.

How Did the Samba Project Illuminate the Technical and Legal Problem?

The Samba project, founded in 1992 by Andrew Tridgell at the Australian National University, offers the clearest empirical record of what it costs to achieve interoperability with an incumbent that uses proprietary protocol extensions. Tridgell reverse-engineered Microsoft’s SMB file-sharing protocol by intercepting and analyzing raw network packets. He had no access to the protocol specifications, because Microsoft did not publish them. The Samba team extended this approach to the broader Active Directory protocol suite, including the Kerberos extensions, over the course of more than a decade. The Samba 4.0 Active Directory-compatible domain controller, released in December 2012, was built with the assistance of the official protocol documentation that Microsoft was compelled to publish following the European Commission’s 2004 decision. Without that compelled disclosure, Samba’s Active Directory implementation would have required an estimated additional decade of reverse-engineering work. That is the concrete cost, measured in developer-years, of withholding interoperability specifications in a standards-based market.

What Legal Tools Can Independent Inventors Use to Protect Their Designs?

The Kerberos case teaches that the window between an inventor’s disclosure of a design and an incumbent’s absorption of that design is narrow, and the legal tools that close that window must be deployed before or contemporaneously with any public disclosure. Six tools, used in combination, provide the most complete protection.

First, file utility patent applications before any publication or public disclosure. Under 35 U.S.C. § 102, a public disclosure that precedes a patent application by more than twelve months bars the application in the United States and immediately bars it in most foreign jurisdictions. The patent application should claim not only the core protocol or design but also the anticipated extension fields and variant implementations that an incumbent might use to create a proprietary layer above the standard. Claims that reach the data structures, the encoding formats, and the validation mechanisms are more durable than claims limited to the abstract authentication sequence.

Second, file continuation applications under 35 U.S.C. § 120 as the incumbent’s implementation becomes visible. A continuation application claims the benefit of the original filing date but can present new claims drafted to cover the specific design choices the incumbent has made. The Supreme Court’s decision in Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 535 U.S. 722 (2002), places limits on claim scope after prosecution history amendment, but a well-structured patent family with multiple continuations and continuation-in-part applications can cover the original design and its extensions with overlapping claim sets that are difficult to design around completely. This is the specific mechanism that prevents the ‘optimize into oblivion’ outcome: the inventor’s claims evolve in parallel with the incumbent’s product.

Third, if the invention participates in or becomes a technical standard, declare standard essential patents to the relevant standard-setting organization and commit to FRAND licensing. Standard-setting organizations including the IETF, the IEEE, and ISO each maintain intellectual property rights policies that require participants to disclose patents they believe are essential to a proposed standard and to commit to license those patents on fair, reasonable, and non-discriminatory terms. A FRAND commitment does not prevent the inventor from enforcing the patent; it requires the inventor to offer licenses on reasonable terms and prohibits royalty stacking and discriminatory pricing. Courts have held that an SEP holder that makes a FRAND commitment without intending to comply may violate § 2 of the Sherman Act. The inverse proposition also holds: an implementer that incorporates a patented element into a standard without obtaining a license is an infringer under 35 U.S.C. § 271.

Fourth, use defensive publication under the USPTO’s Defensive Publication Program, 37 C.F.R. § 1.139, to create prior art covering design variants the inventor does not wish to patent. A defensive publication becomes prior art under 35 U.S.C. § 102(a)(1) immediately upon publication. If an incumbent attempts to patent a design-around that the original inventor has already published defensively, the patent application will fail for lack of novelty. This tool is particularly useful for protocol extensions and data structures that are too numerous or too narrow to patent individually but that represent the space an incumbent might exploit to create a proprietary layer.

Fifth, protect implementation details not disclosed in published patents as trade secrets under the Defend Trade Secrets Act of 2016, 18 U.S.C. § 1836. The DTSA provides a federal civil cause of action for trade secret misappropriation, with ex parte seizure available in exceptional cases and exemplary damages of up to twice the compensatory award. An inventor who patents the protocol specification but keeps the optimized implementation, the key derivation parameters, or the performance tuning details secret retains a competitive advantage that survives even after a competitor obtains a license to the patent.

Sixth, for inventions with distinctive visual or structural design elements, layer design patent protection under 35 U.S.C. § 171 with trade dress protection under § 43(a) of the Lanham Act, 15 U.S.C. § 1125(a). A design patent issued under § 171 provides fifteen years of protection for the ornamental features of a product design. Once the design patent expires or during the period before it issues, trade dress protection attaches to any distinctive, non-functional design element that has acquired secondary meaning in the market. Unlike the seventeen-to-twenty year term of a utility patent, trade dress protection is indefinite as long as the mark remains in use and continues to identify the source of the product.

What Happens When Antitrust Remedies Are the Last Resort?

When patent and trade secret tools have been exhausted or were never deployed, the independent inventor may face an incumbent that has already captured the market through a proprietary extension strategy. At that point, the available remedies narrow to antitrust enforcement and compelled interoperability. The European Microsoft case demonstrates that antitrust relief is achievable but slow. The Commission’s 2004 decision came nearly seven years after the initial complaints about Microsoft’s server protocol practices were filed in 1998. The compliance process consumed another decade. The Kerberos ecosystem’s architecture was largely cemented before the compelled disclosure materially changed the competitive picture.

Under § 2 of the Sherman Act, a plaintiff must establish: a relevant market, monopoly power in that market, and willful maintenance of that power through anticompetitive conduct. The D.C. Circuit’s 2001 Microsoft decision provides the controlling standard in federal courts. A company that embraces an open standard, extends it with proprietary data embedded in specification-reserved extension fields, withholds the specification from competitors, and builds its dominant market position on the resulting interoperability gap presents facts that can satisfy all three elements. The difficulty is establishing that the interoperability information is an ‘essential facility’ that the dominant firm is obligated to share, a doctrine that the D.C. Circuit treats cautiously. Courts are reluctant to impose compulsory licensing or information-sharing obligations under antitrust law when the dominant firm can articulate a plausible business justification for withholding the information, even if that justification is thin.

Open Questions

Several legal and technical questions remain unresolved as of 2026 and will shape the practical utility of the protection strategies described in this report.

First: does the Federal Circuit’s evolving treatment of patent eligibility under 35 U.S.C. § 101, as applied to protocol specifications and data structures, leave authentication protocol inventions vulnerable to invalidity challenges? Post-Alice Corp. v. CLS Bank International, 573 U.S. 208 (2014), software and protocol claims face heightened scrutiny under the two-step abstract idea analysis. A protocol that encodes authorization data in a Kerberos ticket’s AuthorizationData field may be characterized as an abstract idea implemented on a computer. The boundaries of patent eligibility for this class of invention remain contested in the Federal Circuit.

Second: does the open-source release of a protocol implementation under a permissive license constitute a dedication to the public that extinguishes subsequent patent rights in the released code? The Federal Circuit addressed the relationship between open-source licensing and patent rights in Jacobsen v. Katzer, 535 F.3d 1373 (Fed. Cir. 2008), holding that copyright license conditions in open-source licenses are enforceable conditions, not mere covenants. The intersection of open-source licensing, patent dedication, and FRAND commitments in protocol standards remains analytically contested.

Third: as artificial intelligence systems increasingly generate protocol specifications and design documents, how do the inventorship requirements of 35 U.S.C. § 100(f) and the human authorship requirements of copyright law apply to machine-generated protocol designs? An inventor whose AI system generates the PAC-equivalent for a new authentication standard may find the resulting specification unpatentable and uncopyrightable, leaving only trade secret and first-mover commercial strategies to prevent adoption and extension by a well-resourced competitor.

Fourth: will the European Union’s proposed Interoperability Act, which as of 2025 remained in legislative development, impose broader mandatory interoperability obligations on dominant platforms than the Article 102 TFEU enforcement standard currently requires? If enacted, the Interoperability Act could shift the default presumption in favor of protocol disclosure rather than requiring a competitor to prove abuse of dominance through a multi-year administrative proceeding.

Source List

1. RFC 4120, The Kerberos Network Authentication Service (V5), IETF, July 2005. Controlling technical specification for the open Kerberos protocol; defines the AuthorizationData extension field that Microsoft used for the PAC.

2. [MS-PAC]: Privilege Attribute Certificate Data Structure, Microsoft Open Specifications, multiple revisions. Technical specification for Microsoft’s proprietary PAC structure embedded in Windows Kerberos tickets; the primary exhibit in the interoperability analysis.

3. United States v. Microsoft Corp., 253 F.3d 34 (D.C. Cir. 2001). Controlling D.C. Circuit precedent on monopoly maintenance under § 2 of the Sherman Act; introduced the ’embrace, extend, extinguish’ terminology into the legal record through Steven McGeady’s trial testimony.

4. European Commission Decision of March 24, 2004, Case COMP/C-3/37.792 Microsoft. Foundational enforcement decision on Article 82 EC (now Article 102 TFEU) and compelled interoperability disclosure; directly produced the Microsoft Open Specifications.

5. Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 535 U.S. 722 (2002). Supreme Court decision on prosecution history estoppel; governs the scope of continuation application claims in the context of design-around strategies.

6. Alice Corp. v. CLS Bank International, 573 U.S. 208 (2014). Controlling Supreme Court decision on patent eligibility under 35 U.S.C. § 101 for software and protocol inventions; shapes the vulnerability of authentication protocol patents.

7. Defend Trade Secrets Act of 2016, 18 U.S.C. § 1836 et seq. Federal statutory framework for trade secret protection; provides the civil cause of action and remedies available to inventors protecting implementation details.

8. Jacobsen v. Katzer, 535 F.3d 1373 (Fed. Cir. 2008). Federal Circuit decision on the enforceability of open-source license conditions; relevant to the intersection of open-source protocol releases and patent rights.

9. Samba Project History and Active Directory Implementation Documentation, samba.org, various dates 1992-2026. Primary record of the reverse-engineering effort required to achieve Active Directory interoperability without access to Microsoft’s specifications.

10. European Commission Press Release IP-08-318, February 27, 2008. Documents the 899 million euro additional fine for non-compliance with the 2004 interoperability remedy; demonstrates the length and cost of compelled disclosure proceedings.

Bibliography

RFC Editor. RFC 4120: The Kerberos Network Authentication Service (V5). C. Neuman, T. Yu, S. Hartman, K. Raeburn. IETF. July 2005. https://www.rfc-editor.org/info/rfc4120.

Microsoft Corporation. [MS-PAC]: Privilege Attribute Certificate Data Structure. Microsoft Open Specifications. https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-pac/c38cc307-f3e6-4ed4-8c81-dc550d96223c.

Microsoft Corporation. [MS-KILE]: Kerberos Protocol Extensions. Microsoft Open Specifications. https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-kile/.

United States v. Microsoft Corp., 253 F.3d 34, 346 U.S.App.D.C. 330 (D.C. Cir. 2001). https://law.justia.com/cases/federal/appellate-courts/F3/253/34/576095/.

European Commission. Decision of 24 March 2004. Case COMP/C-3/37.792 Microsoft. EUR-Lex. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62004TJ0201.

European Commission. Press Release IP-08-318. Antitrust: Commission imposes 899 million euro penalty on Microsoft for non-compliance with March 2004 Decision. February 27, 2008. https://europa.eu/rapid/press-release_IP-08-318_en.htm.

Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 535 U.S. 722 (2002). United States Supreme Court.

Alice Corp. v. CLS Bank International, 573 U.S. 208 (2014). United States Supreme Court.

Jacobsen v. Katzer, 535 F.3d 1373 (Fed. Cir. 2008). United States Court of Appeals for the Federal Circuit.

Defend Trade Secrets Act of 2016. Pub. L. 114-153. 18 U.S.C. § 1836 et seq.

Electronic Frontier Foundation. ‘Samba versus SMB: Adversarial Interoperability is Judo for Network Effects.’ July 2019. https://www.eff.org/deeplinks/2019/07/samba-versus-smb-adversarial-interoperability-judo-network-effects.

Samba Project. ‘Samba 4.0: Opening Windows to a Wider World.’ December 11, 2012. https://www.samba.org/samba/news/releases/4.0.0.html.

Interested in analysis about the intersection of tech, policy and the law? Check out my Substack channel. https://theinnovationattorney.substack.com/