Next-Generation Secure Computing Base

From BetaArchive Wiki
Diagram of the NGSCB software architecture as presented during WinHEC 2003.

The Next-Generation Secure Computing Base (codenamed Palladium)[1] is a software architecture originally slated to be included in the Microsoft Windows "Longhorn" operating system. Development of the architecture began in 1997.[2][3]

The NGSCB was the result of years of research within Microsoft to create a secure computing solution that equaled the security of more closed systems while preserving the openness and flexibility of the Windows platform.[4] The NGSCB relied on new software components and specially designed hardware to create a new execution environment where more sensitive operations could be performed securely.[5] Microsoft's primary stated objective with the NGSCB was to "protect software from software."[4][6]


The idea of creating an architecture where software components can be loaded in a known and protected state predates the development of NGSCB.[7] A number of attempts were made in the 1960s and 1970s to produce secure computing systems,[8][9] with variations of the idea emerging in more recent decades.[10][11]

In 1999 the Trusted Computing Platform Alliance, a consortium of various technology companies, was formed in an effort to promote trust in the PC platform.[12] The TCPA would release several detailed specifications for a trusted computing platform with focus on features such as code validation and encryption based on integrity measurements, hardware based key storage, and attestation to remote entities. These features required a new hardware component designed by the TCPA called the Trusted Platform Module (referred to as a Security Support Component,[13] Secure Cryptographic Processor,[4] or Security Support Processor[4] in earlier Microsoft documentation). While most of these features would later serve as the foundation for Microsoft's NGSCB architecture, they were different in terms of implementation.[2] The TCPA was superseded by the Trusted Computing Group in 2003.[14]


Development of the NGSCB began in 1997 after Microsoft developer Peter Biddle conceived of new ways to protect content on personal computers.[5]

Microsoft later filed a number of patents related to elements of the NGSCB design.[15] Patents for a digital rights management operating system,[7] loading and identifying a digital rights management operating system,[16] key-based secure storage,[17] and certificate based access control[18] were filed on January 8, 1999. A method to authenticate an operating system based on its central processing unit was filed on March 10, 1999.[19] Patents related to the secure execution of code[20] and protection of code in memory[21] were filed on April 6, 1999.

During its Windows Hardware Engineering Conference of 2000, Microsoft had shown a presentation titled Privacy, Security, and Content in Windows Platforms which focused on the protection of end user privacy and intellectual property.[22] The presentation mentioned turning Windows into a "platform of trust" designed to protect the privacy of individual users. Microsoft would show a similar presentation during WinHEC 2001.[23]

The NGSCB was publicly unveiled under the name "Palladium" on June 24, 2002 in an article by Steven Levy of Newsweek that focused on its origin, design and features.[24][25][26] Levy stated that the technology would allow users to identify and authenticate themselves, encrypt data to protect it from unauthorized access, and allow users to enforce policies related to the use of their information. As examples of policies that could be enforced, Levy stated that users could send e-mail messages accessible only by the intended recipient, or create Microsoft Word documents that could only be read a week after they were created. To provide this functionality, the technology would require specially designed hardware components, including updated processors, chipsets, peripherals, and a Trusted Platform Module. In August 2002, Microsoft posted a recruitment advertisement seeking a group program manager to provide vision and industry leadership in the development of several Microsoft technologies, including its NGSCB architecture.[27]

In 2003, Microsoft publicly demonstrated the NGSCB for the first time at its Windows Hardware Engineering Conference[28][29][30] and released a developer preview of the technology later that year during its Professional Developers Conference.[31][32][33]

Diagram of NGSCB architecture revision shown during WinHEC 2004.

During WinHEC 2004, Microsoft announced that it would revise the technology in response to feedback from customers and independent software vendors who stated that they did not want to rewrite their existing programs in order to benefit from its functionality.[34][35] After the announcement, some reports stated that Microsoft would cease development of the technology.[36][37] Microsoft denied the claims and reaffirmed its commitment to delivering the technology.[38][39] Later that year, Microsoft's Steve Heil stated that the company would make additional changes to the technology based on feedback from the industry.[40]

In 2005, Microsoft's lack of continual updates on its progress with the technology had led some in the industry to speculate that it had been cancelled.[41] At the annual Microsoft Management Summit event, then Microsoft CEO Steve Ballmer said that the company was building on the foundation it had started with the NGSCB to create a new set of hypervisor technologies for its Windows operating system.[42] During WinHEC 2005, Microsoft announced that it had scaled back its plans for the technology in order to ship the post-reset Windows "Longhorn" operating system within a reasonable timeframe. Instead of providing an isolated software environment, the NGSCB would offer full operating system volume encryption with a feature known as Secure Startup (which would later be renamed as Bitlocker Drive Encryption).[43] Microsoft stated that it planned to deliver other aspects of its NGSCB architecture at a later date.[44]

In July 2008, Peter Biddle stated that negative perception was the main contributing factor responsible for the cancellation of the architecture.[45]


In Greek and Roman mythology, the term "palladium" refers to an object that the safety of a city or nation was believed to be dependent upon.[46]

On January 24, 2003, Microsoft announced that "Palladium" had been renamed as the "Next-Generation Secure Computing Base." According to NGSCB product manager Mario Juarez, the new name was chosen not only to reflect Microsoft's commitment to the technology in the upcoming decade, but also to avoid any legal conflict with an unnamed company that had already acquired the rights to the Palladium name. Juarez acknowledged that the previous name had been a source of criticism, but denied that the decision was made by Microsoft in an attempt to deflect criticism.[1]




Diagram of the Nexus design.

The Nexus, previously referred to as the "Nub"[2] or "Trusted Operating Root"[47][48] is the new kernel introduced by the NGSCB. The Nexus is responsible for the secure interaction between the specialized hardware components, and is also responsible for the isolation and management of Nexus Computing Agents.

Nexus Computing Agents

Nexus Computing Agents are user-mode application processes managed by the Nexus kernel.

Nexus Computing Agents are divided into three categories: "Application," "Component," and "Trusted Service Provider."[49]


Process isolation

Sealed storage

Sealed storage refers to the use of encryption to protect locally stored data. Sealed storage differs from traditional encryption schemes in that it allows data to be decrypted only under conditions specified at the time of its encryption.


Attestation refers to validation of a NGSCB machine configuration. Attestation allows users to attest to the state of a hardware or software configuration by sending its cryptographic information to a trusted third-party; the third-party can then determine whether it should trust the configuration.

Secure input

Secure output


Encrypted memory was once considered for the NGSCB, but the idea was later discarded as the only threat conceived of that would warrant its inclusion was the circumvention of digital rights management technology.[50][51]

Trusted Platform Module

The Trusted Platform Module is the hardware component that securely stores the cryptographic keys for the Nexus and Nexus Computing Agents, which makes the sealed storage and attestation features of the Nexus possible.

The Trusted Platform Module includes an asymmetric 2048-bit RSA key pair, referred to as the Endorsement Key (EK), which is unique to each particular module and is generated as part of its manufacturing process. The public key is accessible to applications or services that have established a trusted relationship with the owner, and is also used to provide the owner with Attestation Identity Keys (AIKs).

According to Microsoft, version 1.2 of the Trusted Platform Module is the first version compatible with its NGSCB architecture. Previous versions do not include the required functionality.[52]

In builds of Windows "Longhorn"

A successful attempt to configure the Next-Generation Secure Computing Base in Windows "Longhorn" build 4053.

In released pre-reset builds of Windows "Longhorn", NGSCB components reside in %SYSTEMDRIVE%\WINDOWS\NGSCB. The last build of Windows "Longhorn" known to include the NGSCB directory and subfolders is build 4066.[53]


The development of the Next-Generation Secure Computing Base ultimately led to the creation of Microsoft's Bitlocker drive encryption feature, which was one of the first mainstream device encryption features to support version 1.2 of the Trusted Platform Module, and the first device encryption feature to be integrated with the Windows operating system.[54] Certain design elements of the NGSCB would become part of Microsoft's virtualization technologies.[42][55] Microsoft's Windows 8 operating system, released in 2012, includes a feature called Measured Boot which allows a trusted server to verify the integrity of the Windows startup process.[56][57][58] Although it is not directly related to the NGSCB architecture, it serves a purpose comparable to the architecture's attestation feature in that they are both designed to validate a platform's configuration.[59]

In addition, features based on those originally intended for the NGSCB would later become available in alternative operating systems. In 2012, Giesecke & Devrient produced a parallel execution environment called MobiCore for the Android operating system designed to host secure user applications and protect confidential data.[60] In 2013, Apple released a new feature for its iOS operating system called Secure Enclave to protect a user's biometric information.[61]


  1. 1.0 1.1 Lemos, Robert. (January 24, 2003). "What's in a name? Not Palladium"
  2. 2.0 2.1 2.2 Biddle, Peter. (August 5, 2002). "Re: Dangers of TCPA/Palladium"
  3. Merritt, Rick. (July 15, 2002). "Microsoft scheme for PC security faces flak"
  4. 4.0 4.1 4.2 4.3 Aday, Michael. "Palladium"
  5. 5.0 5.1 Schoen, Seth. (July 5, 2002). "'Palladium' summary"
  6. Lee, Timothy. (November 30, 2012). "How 4 Microsoft engineers proved that the 'darknet' would defeat DRM"
  7. 7.0 7.1 Google Patents. Digital rights management operating system (U.S. Patent 6330670 B1)
  8. Google Patents. Secure and reliable bootstrap architecture (U.S. Patent 6185678)
  9. Anderson, James. (October 1972). "Computer Security Technology Planning Study"
  10. Google Patents. Method and apparatus for assessing integrity of computer system software (U.S. Patent 5421006)
  11. Kuhn, Markus. (April 30, 1997). "The TrustNo 1 Cryptoprocessor Concept"
  12. Trusted Computing Platform Alliance. "Home Page"
  13. Microsoft. "Microsoft Next-Generation Secure Computing Base - Technical FAQ"
  14. Trusted Computing Group. "TCG Timeline"
  15. Lampson, Butler. "Curriculum Vitae"
  16. Google Patents. Loading and identifying a digital rights management operating system (U.S. Patent 6327652 B1)
  17. Google Patents. Key-based secure storage (U.S. Patent 7194092 B1)
  18. Google Patents. Controlling access to content based on certificates and access predicates (U.S. Patent 6820063 B1)
  19. Google Patents. System and method for authenticating an operating system to a central processing unit (U.S. Patent 7174457 B1)
  20. Google Patents. Secure execution of program code (U.S. Patent 6651171 B1)
  21. Google Patents. Hierarchical trusted code for content protection in computers (U.S. Patent 6775779 B1)
  22. Microsoft. "Privacy, Security, and Content in Windows Platforms"
  23. Microsoft. "Privacy, Security, and Content Protection"
  24. Levy, Steven. (June 24, 2002). "The Big Secret"
  25. (June 24, 2002). "'Palladium': Microsoft's big plan for the PC"
  26. ExtremeTech. (June 24, 2002). "'Palladium': Microsoft Revisits Digital Rights Management"
  27. Lettice, John. (August 13, 2002). "MS recruits for Palladium microkernel and/or DRM platform"
  28. Bekker, Scott. (May 6, 2003). "'Palladium' on Display at WinHEC"
  29. Microsoft PressPass. "At WinHEC, Microsoft Discusses Details of Next-Generation Secure Computing Base"
  30. Evers, Joris. (May 7, 2003). "Microsoft turns to emulators for security demo"
  31. Rooney, Paula; Montalbano, Elizabeth. (October 1, 2003). "Microsoft to Hand Over Early Whidbey, Yukon Code At PDC"
  32. Evers, Joris. (October 30, 2003). "Developers get hands on Microsoft's NGSCB"
  33. Microsoft. "A Review of Microsoft Technology for 2003, Preview for 2004"
  34. Evers, Joris. (May 5, 2004). "WinHEC: Microsoft revisits NGSCB security plan"
  35. Sanders, Tom. (May 6, 2004) "Microsoft shakes up 'Longhorn' security"
  36. Bangeman, Eric. (May 5, 2004). "Microsoft kills Next-Generation Secure Computing Base"
  37. Rooney, Paula. (May 5, 2004). "Microsoft shelves NGSCB project as NX moves to center stage"
  38. eWeek. (May 5, 2004). "Microsoft: Palladium is still alive and kicking"
  39. Thurrott, Paul. (May 7, 2004). "WinHEC 2004 Show Report and Photo Gallery"
  40. Fried, Ina. (September 8, 2004). "Controversial Microsoft plan heads for 'Longhorn'"
  41. Ever, Joris. (February 24, 2005). "Silence Fuels Speculation on Microsoft Security Plan"
  42. 42.0 42.1 Microsoft. (April 20, 2005) "Steve Ballmer: Microsoft Management Summit"
  43. Sanders, Tom. (April 26, 2005). "'Longhorn' security gets its teeth kicked out"
  44. Microsoft. "Microsoft Shared Source Initiative Home Page"
  45. Biddle, Peter. (July 16, 2008). "Perception (or, Linus gets away with being honest again)"
  46. Greek Mythology Index. "PALLADIUM"
  47. Microsoft PressPass. "'Palladium': A Business Overview"
  48. Biddle, Peter. (September 19, 2002). "Re: Cryptogram: 'Palladium' only for DRM"
  49. Cram, Ellen. (October 2003). "Development Considerations for Nexus Computing Agents"
  50. Biddle, Peter. (February 22, 2008). "Attack isn't news, and there are mitigations"
  51. Biddle, Peter. (February 23, 2008). "Threat Model Irony"
  52. Microsoft. "Privacy-Enabling Enhancements in the Next-Generation Secure Computing Base"
  53. BetaArchive forums. (May 2, 2014). "Builds of 'Longhorn' with NGSCB?"
  54. Microsoft. "Windows BitLocker Drive Encryption Frequently Asked Questions"
  55. Clarke, Gavin. (May 19, 2005). "Microsoft running late in virtualization"
  56. Microsoft TechNet. "Windows 8 Boot Process - Security, UEFI, TPM"
  57. Microsoft TechNet. "Windows 8 Boot Security FAQ"
  58. Microsoft Software Developer Network (MSDN). "Measured Boot"
  59. Microsoft. "Secured Boot and Measured Boot: Hardening Early Boot Components against Malware"
  60. Giesecke & Devrient. (May 4, 2012). "G&D announces MobiCore® integrated security platform to support Samsung GALAXY S III in Europe"
  61. Apple. (September 10, 2013). "Apple Announces iPhone 5s—The Most Forward-Thinking Smartphone in the World"

External links