Jump to content

Next-Generation Secure Computing Base

From Wikipedia, the free encyclopedia
(Redirected from Palladium (MS))
NGSCB essentially partitions the operating system into two discrete modes. Untrusted Mode consists of traditional applications, Windows, and its components. Trusted Mode is the environment introduced by NGSCB and consists of a new software component called the Nexus that provides NGSCB applications—Nexus Computing Agents—with security-related features.

The Next-Generation Secure Computing Base (NGSCB; codenamed Palladium[1] and also known as Trusted Windows[2]) is a software architecture designed by Microsoft which claimed to provide users of the Windows operating system with better privacy, security, and system integrity.[3][4] NGSCB was the result of years of research and development within Microsoft to create a secure computing solution that equaled the security of closed platforms such as set-top boxes while simultaneously preserving the backward compatibility, flexibility, and openness of the Windows operating system.[5][6][7] Microsoft's primary stated objective with NGSCB was to "protect software from software."[5]

Part of the Trustworthy Computing initiative when unveiled in 2002, NGSCB was to be integrated with Windows Vista, then known as "Longhorn."[1] NGSCB relied on hardware designed by the Trusted Computing Group to produce a parallel operation environment hosted by a new hypervisor (referred to as a sort of kernel in documentation) called the "Nexus" that existed alongside Windows and provided new applications with features such as hardware-based process isolation, data encryption based on integrity measurements, authentication of a local or remote machine or software configuration, and encrypted paths for user authentication and graphics output.[3][8] NGSCB would facilitate the creation and distribution of digital rights management (DRM) policies pertaining the use of information.[9]

NGSCB was subject to much controversy during its development, with critics contending that it would impose restrictions on users, enforce vendor lock-in, and undermine fair use rights and open-source software. It was first demonstrated by Microsoft at WinHEC 2003[10] before undergoing a revision in 2004 that would enable earlier applications to benefit from its functionality.[11] Reports indicated in 2005 that Microsoft would change its plans with NGSCB so that it could ship Windows Vista by its self-imposed deadline year, 2006; instead, Microsoft would ship only part of the architecture, BitLocker, which can optionally use the Trusted Platform Module to validate the integrity of boot and system files prior to operating system startup.[12] Development of NGSCB spanned approximately a decade before its cancellation,[6][13] the lengthiest development period of a major feature intended for Windows Vista.

NGSCB differed from technologies Microsoft billed as "pillars of Windows Vista"—Windows Presentation Foundation, Windows Communication Foundation, and WinFS—during its development in that it was not built with the .NET Framework and did not focus on managed code software development.[8][14] NGSCB has yet to fully materialize; however, aspects of it are available in features such as BitLocker of Windows Vista, Measured Boot and UEFI of Windows 8,[15] Certificate Attestation of Windows 8.1,[16] Device Guard of Windows 10.[17] and Device Encryption in Windows 11 Home editions, with TPM 2.0 mandatory for installation.

History

[edit]

Early development

[edit]
Peter Biddle speaks at the ETech conference in 2007.

Development of NGSCB began in 1997 after Peter Biddle conceived of new ways to protect content on personal computers.[1][18][19][20] Biddle enlisted assistance from members from the Microsoft Research division and other core contributors eventually included Blair Dillaway, Brian LaMacchia, Bryan Willman, Butler Lampson, John DeTreville, John Manferdelli, Marcus Peinado, and Paul England.[21] Adam Barr, a former Microsoft employee who worked to secure the remote boot feature during development of Windows 2000 was approached by Biddle and colleagues during his tenure with an initiative tentatively known as "Trusted Windows," which aimed to protect DVD content from being copied. To this end, Lampson proposed the use of a hypervisor to execute a limited operating system dedicated to DVD playback alongside Windows 2000.[22] Patents for a DRM operating system were later filed in 1999 by England, DeTreville and Lampson;[23][24] Lampson noted that these patents were for NGSCB.[25] Biddle and colleagues realized by 1999 that NGSCB was more applicable to privacy and security than content protection, and the project was formally given the green-light by Microsoft in October, 2001.[1][19][20][26]

During WinHEC 1999, Biddle discussed intent to create a "trusted" architecture for Windows to leverage new hardware to promote confidence and security while preserving backward compatibility with previous software.[27] On October 11, 1999, the Trusted Computing Platform Alliance, a consortium of various technology companies including Compaq, Hewlett-Packard, IBM, Intel, and Microsoft was formed in an effort to promote personal computing confidence and security.[28] The TCPA released 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 machine authentication; these features required a new hardware component designed by the TCPA called the "Trusted Platform Module" (referred to as a "Security Support Component",[9] "Security CoProcessor",[5] or "Security Support Processor"[5] in early NGSCB documentation).

At WinHEC 2000, Microsoft released a technical presentation on the topics of protection of privacy, security, and intellectual property titled "Privacy, Security, and Content in Windows Platforms", which focused on turning Windows into a "platform of trust" for computer security, user content, and user privacy. Notable in the presentation is the contention that "there is no difference between privacy protection, computer security, and content protection"—"assurances of trust must be universally true".[2] Microsoft reiterated these claims at WinHEC 2001.[29] NGSCB intended to protect all forms of content, unlike traditional rights management schemes which focus only on the protection of audio tracks or movies instead of users they have the potential to protect which made it, in Biddle's words, "egalitarian".[2][30]

As "Palladium"

[edit]

Microsoft held its first design review for the NGSCB in April 2002, with approximately 37 companies under a non-disclosure agreement.[19] NGSCB was publicly unveiled under its codename "Palladium" in a June 2002 article by Steven Levy for Newsweek that focused on its design, feature set, and origin.[31][32] Levy briefly described potential features: access control, authentication, authorization, DRM, encryption, as well as protection from junk mail and malware, with example policies being email accessible only to an intended recipient and Microsoft Word documents readable for only a week after their creation;[1] Microsoft later release a guide clarifying these assertions as being hyperbolic; namely, that NGSCB would not intrinsically enforce content protection, or protect against junk mail or malware. Instead, it would provide a platform on which developers could build new solutions that did not exist by isolating applications and store secrets for them.[9] Microsoft was not sure whether to "expose the feature in the Control Panel or present it as a separate utility," but NGSCB would be an opt-in solution—disabled by default.[33]

Microsoft PressPass later interviewed John Manferdelli, who restated and expanded on many of the key points discussed in the article by Newsweek. Manferdelli described it as evolutionary platform for Windows in July, articulating how "'Palladium' will not require DRM, and DRM will not require 'Palladium'.[26] Microsoft sought a group program manager in August to assist in leading the development of several Microsoft technologies including NGSCB.[34] Paul Otellini announced Intel's support for NGSCB with a set of chipset, platform, and processor codenamed "LaGrande" at Intel Developer Forum 2002,[35][36] which would provide an NGSCB hardware foundation and preserve backward compatibility with previous software.[37]

As NGSCB

[edit]

NGSCB was known as "Palladium" until January 24, 2003 when Microsoft announced it had been renamed as "Next-Generation Secure Computing Base." Project manager Mario Juarez stated this name was chosen to avoid legal action from an unnamed company which had acquired the rights to the "Palladium" name, as well as to reflect Microsoft's commitment to NGSCB in the upcoming decade. Juarez acknowledged the previous name was controversial, but denied it was changed by Microsoft to dodge criticism.[38]

The Trusted Computing Platform Alliance was superseded by the Trusted Computing Group in April 2003.[39] A principal goal of the new consortium was to produce a Trusted Platform Module (TPM) specification compatible with NGSCB; the previous specification, TPM 1.1 did not meet its requirements.[19][40] TPM 1.2 was designed for compliance with NGSCB[41] and introduced many features for such platforms.[42] The first TPM 1.2 specification, Revision 62 was released in 2003.[43]

Biddle emphasized in June 2003 that hardware vendors and software developers were vital to NGSCB.[44] Microsoft publicly demonstrated NGSCB for the first time at WinHEC 2003,[10][45][46] where it protected data in memory from an attacker; prevented access to—and alerted the user of—an application that had been changed; and prevented a remote administration tool from capturing an instant messaging conversation.[47][48] Despite Microsoft's desire to demonstrate NGSCB on hardware,[49] software emulation was required for as few hardware components were available.[48] Biddle reiterated that NGSCB was a set of evolutionary enhancements to Windows, basing this assessment on preserved backward compatibility and employed concepts in use before its development, but said the capabilities and scenarios it would enable would be revolutionary.[50] Microsoft also revealed its multi-year roadmap for NGSCB,[51] with the next major development milestone scheduled for the Professional Developers Conference,[48][52] indicating that subsequent versions would ship concurrently with pre-release builds of Windows Vista; however, news reports suggested that NGSCB would not be integrated with Windows Vista when release, but it would instead be made available as separate software for the operating system.[53]

Microsoft also announced details related to adoption and deployment of NGSCB at WinHEC 2003, stating that it would create a new value proposition for customers without significantly increasing the cost of computers; NGSCB adoption during the year of its introductory release was not anticipated and immediate support for servers was not expected.[54][55] On the last day of the conference, Biddle said NGSCB needed to provide users with a way to differentiate between secured and unsecured windows—that a secure window should be "noticeably different" to help protect users from spoofing attacks;[53] Nvidia was the earliest to announce this feature.[56] WinHEC 2003 represented an important development milestone for NGSCB. Microsoft dedicated several hours to presentations and released many technical whitepapers,[57][58][59] and companies including Atmel,[60] Comodo Group,[61][62] Fujitsu,[61] and SafeNet[63][64] produced preliminary hardware for the demonstration. Microsoft also demonstrated NGSCB at several U.S. campuses in California and in New York in June 2003.[52][65]

Microsoft's roadmap for NGSCB as revealed during WinHEC 2003

NGSCB was among the topics discussed during Microsoft's PDC 2003 with a pre-beta software development kit, known as the Developer Preview, being distributed to attendees.[10] The Developer Preview was the first time that Microsoft made NGSCB code available to the developer community and was offered by the company as an educational opportunity for NGSCB software development.[66] With this release, Microsoft stated that it was primarily focused on supporting business and enterprise applications and scenarios with the first version of the NGSCB scheduled to ship with Windows Vista, adding that it intended to address consumers with a subsequent version of the technology, but did not provide an estimated time of delivery for this version.[8][66] At the conference, Jim Allchin said that Microsoft was continuing to work with hardware vendors so that they would be able to support the technology,[67] and Bill Gates expected a new generation of central processing units (CPUs) to offer full support.[68] Following PDC 2003, NGSCB was demonstrated again on prototype hardware during the annual RSA Security conference in November.[69]

Microsoft announced at WinHEC 2004 that it would revise NSCB in response to feedback from customers and independent software vendors who did not desire to rewrite their existing programs in order to benefit from its functionality;[11][70] the revision would also provide more direct support for Windows with protected environments for the operating system, its components, and applications, instead of it being an environment to itself and new applications.[71] The NGSCB secure input feature would also undergo a significant revision based on cost assessments, hardware requirements, and usability issues of the previous implementation.[72] There were subsequent reports that Microsoft would cease developing NGSCB;[73][74] Microsoft denied these reports and reaffirmed its commitment to delivery.[14][75] Additional reports published later that year suggested that Microsoft would make even additional changes based on feedback from the industry.[6][76]

Microsoft's absence of continual updates on NGSCB progress in 2005 had caused industry insiders to speculate that NGSCB had been cancelled.[77] At the Microsoft Management Summit event, Steve Ballmer said that the company would build on the security foundation it had started with the NGSCB to create a new set of virtualization technologies for Windows,[78] which were later Hyper-V. Reports during WinHEC 2005 indicated Microsoft scaled back its plans for NGSCB, so that it could to ship Windows Vista—which had already been beset by numerous delays and even a "development reset"—within a reasonable timeframe; instead of isolating components, NGSCB would offer "Secure Startup" ("BitLocker Drive Encryption") to encrypt disk volumes and validate both pre-boot firmware and operating system components.[12][79][80][81] Microsoft intended to deliver other aspects of NGSCB later.[3] Jim Allchin stated NGSCB would "marry hardware and software to gain better security", which was instrumental in the development of BitLocker.[81]

Architecture and technical details

[edit]

A complete Microsoft-based Trusted Computing-enabled system will consist not only of software components developed by Microsoft but also of hardware components developed by the Trusted Computing Group. The majority of features introduced by NGSCB are heavily reliant on specialized hardware and so will not operate on PCs predating 2004.

In current Trusted Computing specifications, there are two hardware components: the Trusted Platform Module (TPM), which will provide secure storage of cryptographic keys and a secure cryptographic co-processor, and a curtained memory feature in the CPU. In NGSCB, there are two software components, the Nexus, a security kernel that is part of the Operating System that provides a secure environment (Nexus mode) for trusted code to run in, and Nexus Computing Agents (NCAs), trusted modules which run in Nexus mode within NGSCB-enabled applications.

Secure storage and attestation

[edit]

At the time of manufacture, a cryptographic key is generated and stored within the TPM. This key is never transmitted to any other component, and the TPM is designed in such a way that it is extremely difficult to retrieve the stored key by reverse engineering or any other method, even to the owner. Applications can pass data encrypted with this key to be decrypted by the TPM, but the TPM will only do so under certain strict conditions. Specifically, decrypted data will only ever be passed to authenticated, trusted applications, and will only ever be stored in curtained memory, making it inaccessible to other applications and the Operating System. Although the TPM can only store a single cryptographic key securely, secure storage of arbitrary data is by extension possible by encrypting the data such that it may only be decrypted using the securely stored key.

The TPM is also able to produce a cryptographic signature based on its hidden key. This signature may be verified by the user or by any third party, and so can therefore be used to provide remote attestation that the computer is in a secure state.

Curtained memory

[edit]

NGSCB also relies on a curtained memory feature provided by the CPU. Data within curtained memory can only be accessed by the application to which it belongs, and not by any other application or the Operating System. The attestation features of the TPM can be used to confirm to a trusted application that it is genuinely running in curtained memory; it is therefore very difficult for anyone, including the owner, to trick a trusted application into running outside of curtained memory. This in turn makes reverse engineering of a trusted application extremely difficult.

Applications

[edit]

NGSCB-enabled applications are to be split into two distinct parts, the NCA, a trusted module with access to a limited Application Programming Interface (API), and an untrusted portion, which has access to the full Windows API. Any code which deals with NGSCB functions must be located within the NCA.

The reason for this split is that the Windows API has developed over many years and is as a result extremely complex and difficult to audit for security bugs. To maximize security, trusted code is required to use a smaller, carefully audited API. Where security is not paramount, the full API is available.

Uses and scenarios

[edit]
See also: Trusted Computing § Possible applications

NGSCB enables new categories of applications and scenarios. Examples of uses cited by Microsoft include decentralized access control policies; digital rights management services for consumers, content providers, and enterprises; protected instant messaging conversations and online transactions; and more secure forms of machine health compliance, network authentication, and remote access.[5] NGSCB-secured virtual private network access was one of the earliest scenarios envisaged by Microsoft.[82] NGSCB can also strengthen software update mechanisms such as those belonging to antivirus software or Windows Update.[83]

An early NGSCB privacy scenario conceived of by Microsoft is the "wine purchase scenario," where a user can safely conduct a transaction with an online merchant without divulging personally identifiable information during the transaction.[84] With the release of the NGSCB Developer Preview during PDC 2003, Microsoft emphasized the following enterprise applications and scenarios: document signing, secured data viewing, secured instant messaging, and secured plug-ins for emailing.[8]

"The concept of machine identity actually gives you the ability to do things like strengthen antivirus updates because you can start creating circumstances where you sort of create a little secure partition, or secure space within the PC, and that can let you do things like work around rootkits. [...] A lot of what is happening in the arms race of security today is an attempt to subvert an operating system so that the operating system is no longer behaving in the manner in which it was either designed or the user wants—without the user knowing—right? And in other cases, it's about creating a fake user which then does things on your behalf—which are not really on your behalf: spends your money, gives away your data, gives away personally identifiable information. So anything that lets you create a stronger, more immutable identity combination like: "this is the machine, this is the software, this is the operating system, this is the service, this is the user" is something that can benefit users because things that work on chiseling into those spaces are less effective."

— Peter Biddle.[83]

WinHEC 2004 scenarios

[edit]

During WinHEC 2004, Microsoft revealed two features based on its revision of NGSCB, Cornerstone and Code Integrity Rooting:[71]

  • Cornerstone would protect a user's login and authentication information by securely transmitting it to NGSCB-protected Windows components for validation, finalizing the user authentication process by releasing access to the SYSKEY if validation was successful. It was intended to protect data on laptops that had been lost or stolen to prevent hackers or thieves from accessing it even if they had performed a software-based attack or booted into an alternative operating system.[71]
  • Code Integrity Rooting would validate boot and system files prior to the startup of Microsoft Windows. If validation of these components failed, the SYSKEY would not be released.[71]

BitLocker is the combination of these features; "Cornerstone" was the codename of BitLocker,[85][86] and BitLocker validates pre-boot firmware and operating system components before boot, which protects SYSKEY from unauthorized access; an unsuccessful validation prohibits access to a protected system.[87][88]

Reception

[edit]
See also: Trusted Computing § Criticism

Reaction to NGSCB after its unveiling by Newsweek was largely negative. While its security features were praised,[89][90] critics contended that NGSCB could be used to impose restrictions on users;[90][91][92][93][94] lock-out competing software vendors;[91][95][94][96] and undermine fair use rights and open source software such as Linux.[94][97][98] Microsoft's characterization of NGSCB as a security technology was subject to criticism as its origin focused on DRM.[68][99] NGSCB's announcement occurred only a few years after Microsoft was accused of anticompetitive practices during the United States v. Microsoft Corporation antitrust case, a detail which called the company's intentions for the technology into question—NGSCB was regarded as an effort by the company to maintain its dominance in the personal computing industry.[100] The notion of a "Trusted Windows" architecture—one that implied Windows itself was untrustworthy—would also be a source of contention within the company itself.[101]

After NGSCB's unveiling, Microsoft drew frequent comparisons to Big Brother, an oppressive dictator of a totalitarian state in George Orwell's dystopian novel Nineteen Eighty-Four. The Electronic Privacy Information Center legislative counsel, Chris Hoofnagle, described Microsoft's characterization of the NGSCB as "Orwellian."[102] Big Brother Awards bestowed Microsoft with an award because of NGSCB.[84] Bill Gates addressed these comments at a homeland security conference by stating that NGSCB "can make our country more secure and prevent the nightmare vision of George Orwell at the same time."[103] Steven Levy—the author who unveiled the existence of the NGSCB—claimed in a 2004 front-page article for Newsweek that NGSCB could eventually lead to an "information infrastructure that encourages censorship, surveillance, and suppression of the creative impulse where anonymity is outlawed and every penny spent is accounted for."[104] However, Microsoft outlined a scenario enabled by NGSCB that allows a user to conduct a transaction without divulging personally identifiable information.[84]

Ross Anderson of Cambridge University was among the most vocal critics of NGSCB and of Trusted Computing. Anderson alleged that the technologies were designed to satisfy federal agency requirements; enable content providers and other third-parties to remotely monitor or delete data in users' machines; use certificate revocation lists to ensure that only content deemed "legitimate" could be copied; and use unique identifiers to revoke or validate files; he compared this to the attempts by the Soviet Union to "register and control all typewriters and fax machines."[94][105] Anderson also claimed that the TPM could control the execution of applications on a user's machine and, because of this, bestowed to it a derisive "Fritz Chip" name in reference to United States Senator Ernest "Fritz" Hollings, who had recently proposed DRM legislation such as the Consumer Broadband and Digital Television Promotion Act for consumer electronic devices. Anderson's report was referenced extensively in the news media and appeared in publications such as BBC News,[106] The New York Times,[107] and The Register.[108] David Safford of IBM Research stated that Anderson presented several technical errors within his report, namely that the proposed capabilities did not exist within any specification and that many were beyond the scope of trusted platform design.[109] Anderson later alleged that BitLocker was designed to facilitate DRM and to lock out competing software on an encrypted system,[110] and, in spite of his allegation that NGSCB was designed for federal agencies, advocated for Microsoft to add a backdoor to BitLocker.[111] Similar sentiments were expressed by Richard Stallman, founder of the GNU Project and Free Software Foundation,[112] who alleged that Trusted Computing technologies were designed to enforce DRM and to prevent users from running unlicensed software. In 2015, Stallman stated that "the TPM has proved a total failure" for DRM and that "there are reasons to think that it will not be feasible to use them for DRM."[112]

"We are not going to use Palladium to make our customers—our favorite people—angry at us."

Peter Biddle[113]

After the release of Anderson's report, Microsoft stated in an NGSCB FAQ that "enhancements to Windows under the NGSCB architecture have no mechanism for filtering content, nor do they provide a mechanism for proactively searching the Internet for 'illegal' content [...] Microsoft is firmly opposed to putting 'policing functions' into nexus-aware PCs and does not intend to do so" and that the idea was in direct opposition with the design goals set forth for NGSCB, which was "built on the premise that no policy will be imposed that is not approved by the user."[9] Concerns about the NGSCB TPM were also raised in that it would use what are essentially unique machine identifiers,[5] which drew comparisons to the Intel Pentium III processor serial number, a unique hardware identification number of the 1990s viewed as a risk to end-user privacy.[94][114][115] NGSCB, however, mandates that disclosure or use of the keys provided by the TPM be based solely on user discretion;[9][41] in contrast, Intel's Pentium III included a unique serial number that could potentially be revealed to any application.[116] NGSCB, also unlike Intel's Pentium III, would provide optional features to allow users to indirectly identify themselves to external requestors.[9]

In response to concerns that NGSCB would take control away from users for the sake of content providers, Bill Gates stated that the latter should "provide their content in easily accessible forms or else it ends up encouraging piracy."[117] Bryan Willman, Marcus Peinado, Paul England, and Peter Biddle—four NGSCB engineers—realized early during the development of NGSCB that DRM would ultimately fail in its efforts to prevent piracy.[101] In 2002, the group released a paper titled "The Darknet and the Future of Content Distribution" that outlined how content protection mechanisms are demonstrably futile.[118] The paper's premise circulated within Microsoft during the late 1990s and was a source of controversy within Microsoft; Biddle stated that the company almost terminated his employment as a result of the paper's release.[101] A 2003 report published by Harvard University researchers suggested that NGSCB and similar technologies could facilitate the secure distribution of copyrighted content across peer-to-peer networks.[119][120]

Not all assessments were negative. Paul Thurrott praised NGSCB, stating that it was "Microsoft's Trustworthy Computing initiative made real" and that it would "form the basis of next-generation computer systems."[121] Scott Bekker of Redmond Magazine stated that NGSCB was misunderstood because of its controversy and that it appeared to be a "promising, user-controlled defense against privacy intrusions and security violations."[89] In February 2004, In-Stat/MDR, publisher of the Microprocessor Report, bestowed NGSCB with its Best Technology award.[122] Malcom Crompton, Australian Privacy Commissioner, stated that "NGSCB has great privacy enhancing potential [...] Microsoft has recognised there is a privacy issue [...] we should all work with them, give them the benefit of the doubt and urge them to do the right thing."[123] When Microsoft announced at WinHEC 2004 that it would be revising NGSCB so that previous applications would not have to be rewritten, Martin Reynolds of Gartner praised the company for this decision as it would create a "more sophisticated" version of NGSCB that would simplify development.[124] David Wilson, writing for South China Morning Post, defended NGSCB by saying that "attacking the latest Microsoft monster is an international blood sport" and that "even if Microsoft had a new technology capable of ending Third World hunger and First World obesity, digital seers would still lambaste it because they view Bill Gates as a grey incarnation of Satan."[125] Microsoft noted that negative reaction to NGSCB gradually waned after events such as the USENIX Annual Technical Conference in 2003,[71] and several Fortune 500 companies also expressed interest in it.[71][126]

When reports announced in 2005 that Microsoft would scale back its plans and incorporate only BitLocker with Windows Vista, concerns pertaining digital rights management, erosion of user rights, and vendor lock-in remained.[12][80][127][128] In 2008, Biddle stated that negative perception was the most significant contributing factor responsible for the cessation of NGSCB's development.[129]

Vulnerability

[edit]

In an article in 2003, D. Boneh and D. Brumley indicated that projects like NGSCB may be vulnerable to timing attacks.[130]

See also

[edit]

References

[edit]
  1. ^ a b c d e Levy, Steven (June 24, 2002). "The Big Secret". Newsweek. Newsweek LLC. Retrieved January 30, 2015.
  2. ^ a b c Biddle, Peter; Peinado, Marcus; England, Paul (2000). "Privacy, Security, and Content in Windows Platforms". Microsoft. Archived from the original (PPT) on April 2, 2015. Retrieved January 30, 2015.
  3. ^ a b c Microsoft. "Shared Source Initiative Home Page". Microsoft. Retrieved January 30, 2015.
  4. ^ Carroll, Amy; Juarez, Mario; Polk, Julia; Leininger, Tony (2002). "Microsoft 'Palladium': A Business Overview" (PDF). Microsoft. Retrieved May 3, 2015.
  5. ^ a b c d e f Aday, Michael. "Palladium" (PDF). Microsoft. Retrieved January 30, 2015.
  6. ^ a b c Fried, Ina (September 8, 2004). "Controversial Microsoft plan heads for Longhorn". CNET. CBS Interactive. Retrieved January 30, 2015.
  7. ^ England, Paul; Lampson, Butler; Manferdelli, John; Peinado, Marcus; Willman, Bryan (July 2003). "A Trusted Open Platform" (PDF). IEEE Computer Society. Retrieved September 25, 2015.
  8. ^ a b c d Kaplan, Keith; Cram, Ellen (2003). "Next-Generation Secure Computing Base - Overview and Drilldown" (PPT). Microsoft. Retrieved January 30, 2015.
  9. ^ a b c d e f Microsoft (20 February 2014). "Next-Generation Secure Computing Base - Technical FAQ". TechNet. Retrieved February 16, 2015.
  10. ^ a b c "A Review of Microsoft Technology for 2003, Preview for 2004". News Center. Microsoft. December 15, 2003. Retrieved January 30, 2015.
  11. ^ a b Evers, Joris (May 5, 2004). "WinHEC: Microsoft revisits NGSCB security plan". Network World. IDG. Archived from the original on November 18, 2005. Retrieved January 30, 2015.
  12. ^ a b c Sanders, Tom (April 26, 2005). "Longhorn security gets its teeth kicked out". Incisive Media. Retrieved January 30, 2015.
  13. ^ Fried, Ina (April 25, 2005). "Microsoft: 'Trusted Windows' still coming, trust us". CNET. CBS Interactive. Retrieved August 18, 2015.
  14. ^ a b "Microsoft: Palladium is still alive and kicking". eWeek. QuinStreet. May 5, 2004. Retrieved January 30, 2015.
  15. ^ Microsoft. "Secured Boot and Measured Boot: Hardening Early Boot Components against Malware" (DOCX). MSDN. Retrieved January 30, 2015.
  16. ^ Microsoft (July 24, 2013). "What's Changed in Security Technologies in Windows 8.1". MSDN. Retrieved March 6, 2015.
  17. ^ Thomson, Iain (April 23, 2015). "Windows 10 Device Guard: Microsoft's effort to keep malware off PCs". The Register. Situation Publishing. Retrieved April 25, 2015.
  18. ^ Schoen, Seth (July 5, 2002). "Palladium summary". Archived from the original on August 2, 2002. Retrieved January 30, 2015.{{cite web}}: CS1 maint: unfit URL (link)
  19. ^ a b c d Merritt, Rick (July 15, 2002). "Microsoft scheme for PC security faces flak". EE Times. UBM plc. Retrieved January 30, 2015.
  20. ^ a b "Microsoft, allies gear to reshape copyright debate". Daily Times. Reuters. September 9, 2002. Archived from the original on March 4, 2016. Retrieved September 1, 2015.
  21. ^ LaMacchia, Brian. "An Overview of Palladium". Microsoft. Archived from the original (PPT) on June 23, 2020. Retrieved February 17, 2015.
  22. ^ Barr, Adam (July 9, 2002). "TCPA and Palladium: Sony Inside". Kuro5hin. Retrieved January 30, 2015.
  23. ^ US 6330670, England, Paul; DeTreville, John D. & Lampson, Butler W., "Digital rights management operating system", assigned to Microsoft Corporation 
  24. ^ US 6327652, England, Paul; DeTreville, John D. & Lampson, Butler W., "Loading and identifying a digital rights management operating system", assigned to Microsoft Corporation 
  25. ^ Lampson, Butler. "Cirriculum Vitae" (DOC). Microsoft. Retrieved January 30, 2015.
  26. ^ a b "Q&A: Microsoft Seeks Industry-Wide Collaboration for Palladium Initiative". News Center. Microsoft. July 1, 2002. Retrieved January 30, 2015.
  27. ^ Nash, Mike (2003). "Microsoft Directions In Security: Making It Real". Microsoft. Archived from the original (EXE) on August 8, 2003. Retrieved February 16, 2015.
  28. ^ Gorman, Ray (October 11, 1999). "Compaq, Hewlett Packard, IBM, Intel, and Microsoft Announce Open Alliance to Build Trust and Security into PCs for e-business". IBM. Archived from the original on November 17, 2014. Retrieved February 16, 2015.
  29. ^ Biddle, Peter; Peinado, Marcus; Flanagan, Dennis (2001). "Privacy, Security, and Content Protection". Microsoft. Archived from the original (PPT) on June 26, 2017. Retrieved January 30, 2015.
  30. ^ Biddle, Peter. "Re: Privacy-enabling uses for TCPA - MARC". MARC. Retrieved May 1, 2015.
  31. ^ Geek.com (June 24, 2002). "Palladium: Microsoft's big plan for the PC". Geek.com. Ziff Davis Media. Archived from the original on March 29, 2019. Retrieved January 30, 2015.
  32. ^ ExtremeTech (June 24, 2002). "Palladium: Microsoft Revisits Digital Rights Management". Ziff Davis Media. Retrieved January 30, 2015.
  33. ^ Rooney, Paula (June 25, 2002). "Channel Positive About Microsoft Palladium Security Project". The Channel Company. Retrieved January 30, 2015.
  34. ^ Lettice, John (August 13, 2002). "MS recruits for Palladium microkernel and/or DRM platform". The Register. Situation Publishing. Retrieved January 30, 2015.
  35. ^ "Paul Otellini Keynote -- IDF Fall 2002". Intel. September 9, 2002. Retrieved February 16, 2015.
  36. ^ Greene, Thomas (September 10, 2002). "Intel's new chip for security Renaissance". The Register. Situation Publishing. Retrieved February 16, 2015.
  37. ^ Girard, Luke; Jones-Ferron, Mike (2003). "LaGrande Technology & Safer Computing Overview" (PDF). Intel. Archived from the original (PDF) on December 17, 2003. Retrieved March 6, 2015.
  38. ^ Lemos, Robert (January 24, 2003). "What's in a name? Not Palladium". CNET. CBS Interactive. Archived from the original on August 10, 2011. Retrieved March 29, 2019.
  39. ^ Merritt, Rick (April 8, 2003). "New group aims to secure PCs, PDAs, cell phones". EETimes. UBM plc. Retrieved February 16, 2015.
  40. ^ Biddle, Peter (August 5, 2002). "Re: Dangers of TCPA/Palladium" (TXT). Retrieved February 16, 2015.
  41. ^ a b "Privacy-Enabling Enhancements in the Next-Generation Secure Computing Base". Microsoft. 2003. Archived from the original (DOC) on December 28, 2005. Retrieved February 21, 2015.
  42. ^ Heil, Stephen; Zeman, Pavel (2004). "TPM 1.2 Trusted Platform Module And Its Use In NGSCB". Microsoft. Archived from the original (PPT) on August 27, 2006. Retrieved February 21, 2015.
  43. ^ Trusted Computing Group. "Trusted Computing Group - TPM Main Specification". Retrieved February 21, 2015.
  44. ^ Fisher, Dennis (May 5, 2003). "Microsoft to Get More Control of the PC?". eWeek. QuinStreet. Retrieved January 30, 2015.
  45. ^ Lemos, Robert (May 6, 2003). "Microsoft shows off security prototype". CNET. CBS Interactive. Retrieved January 30, 2015.
  46. ^ Bekker, Scott (May 6, 2003). "Palladium on Display at WinHEC". Redmond Magazine. 1105 Media Inc. Retrieved January 30, 2015.
  47. ^ Hachman, Mark (May 7, 2003). "Microsoft Demos NGSCB Rights Scheme". ExtremeTech. Ziff Davis Media. Retrieved January 30, 2015.
  48. ^ a b c Evers, Joris (May 7, 2003). "Microsoft turns to emulators for security demo". Network World. IDG. Retrieved January 30, 2015.
  49. ^ Evers, Joris (March 26, 2003). "Microsoft plans Palladium demo in May". Computer World. IDG. Retrieved January 30, 2015.
  50. ^ Microsoft (May 7, 2003). "At WinHEC, Microsoft Discusses Details of Next-Generation Secure Computing Base". Microsoft. Retrieved January 30, 2015.
  51. ^ Foley, Jo Mary (April 8, 2003). "Microsoft To Do More Than Just Demo 'Palladium'". PC Magazine. Ziff Davis Media. Archived from the original on March 4, 2016. Retrieved January 30, 2015.
  52. ^ a b Krill, Paul (June 19, 2003). "Microsoft readies kit for security initiative". InfoWorld. IDG. Retrieved January 30, 2015.
  53. ^ a b Kanellos, Michael (May 8, 2003). "Microsoft: A separate look for security". CNET. CBS Interactive. Retrieved January 30, 2015.
  54. ^ Evers, Joris (May 8, 2003). "WinHEC: Microsoft expects slow adoption for NGSCB". InfoWorld. IDG. Retrieved January 30, 2015.
  55. ^ Evers, Joris. (May 9, 2003). "WinHEC: Palladium for servers a long way out". InfoWorld. IDG. Retrieved January 30, 2015.
  56. ^ Biddle, Peter; Kirk, David (2003). "Trusted Graphics and NGSCB". Microsoft. Archived from the original on August 8, 2003. Retrieved December 2, 2015.{{cite web}}: CS1 maint: unfit URL (link)
  57. ^ Microsoft (2003). "Trusted Platform Technologies". Windows Hardware Engineering Conference. Archived from the original on June 20, 2003. Retrieved January 30, 2015.
  58. ^ "Microsoft's Longhorn 3D UI - More Info Emerges". ExtremeTech. Ziff Davis Media. May 9, 2003. Retrieved January 30, 2015.
  59. ^ Bennett, Amy (May 2, 2003). "Microsoft to get technical on Longhorn and Palladium". ITWorld. IDG. Archived from the original on December 8, 2015. Retrieved January 30, 2015.
  60. ^ Business Wire (May 7, 2003). "Atmel and Microsoft Demonstrate New Secure USB Keyboard Prototype at WinHEC 2003" (Press release). Retrieved January 30, 2015. {{cite press release}}: |author= has generic name (help)
  61. ^ a b Linden, Marielle (May 6, 2003). "Fujitsu Components and Comodo Demonstrate the Future of Secure Input at WINHEC 2003". Fujitsu. Archived from the original on December 6, 2015. Retrieved January 30, 2015.
  62. ^ Comodo Group (2003). "SIDEN TC4000 Cost Optimized Security Solution (NGSCB Compatible)" (PDF). Retrieved November 22, 2014.
  63. ^ SafeNet (May 6, 2003). "SafeNet Supplies Encryption Technology to Microsoft for its Next-Generation Secure Computing Base Demonstration". Retrieved January 30, 2015.[permanent dead link]
  64. ^ "SafeNet Supplies Encryption Technology to Microsoft for its Next-Generation Secure Computing Base Demonstration; SafeNet to Demonstrate New Technology at the WinHEC 2003 Conference". BusinessWire. May 6, 2003. Retrieved December 6, 2015.
  65. ^ Evers, Joris (June 12, 2003). "Microsoft takes 'Palladium' on tour". InfoWorld. IDG. Retrieved January 30, 2015.
  66. ^ a b Evers, Joris (October 30, 2003). "Developers get hands on Microsoft's NGSCB". NetworkWorld. IDG. Retrieved January 30, 2015.
  67. ^ "Speech Transcript – Jim Allchin, Microsoft Professional Developers Conference 2003". News Center. Microsoft. October 27, 2003. Retrieved January 30, 2015.
  68. ^ a b Lettice, John (October 28, 2003). "NGSCB, aka Palladium, in next generation of CPU, says Gates". The Register. Situation Publishing. Retrieved January 30, 2015.
  69. ^ "Microsoft Details New Security Innovations at RSA Conference 2003, Europe". News Center. Microsoft. November 4, 2003. Retrieved January 30, 2015.
  70. ^ Sanders, Tom (May 6, 2004). "Microsoft shakes up Longhorn security". Incisive Media. Retrieved January 30, 2015.
  71. ^ a b c d e f Biddle, Peter (2004). "Next-Generation Secure Computing Base". Microsoft. Archived from the original (PPT) on August 27, 2006. Retrieved January 30, 2015.
  72. ^ Wooten, David (2004). "Securing the User Input Path on NGSCB Systems". Microsoft. Archived from the original (PPT) on May 9, 2006. Retrieved September 12, 2015.
  73. ^ Bangeman, Eric (May 5, 2004). "Microsoft kills Next-Generation Secure Computing Base". Ars Technica. Condé Nast. Retrieved January 30, 2015.
  74. ^ Rooney, Paula (May 5, 2004). "Microsoft shelves NGSCB project as NX moves to center stage". The Channel Company. Retrieved January 30, 2015.
  75. ^ Thurrott, Paul (May 7, 2004). "WinHEC 2004 Show Report and Photo Gallery". Supersite for Windows. Penton. Retrieved January 30, 2015.
  76. ^ Liang, Ping (August 19, 2004). "What to expect from Microsoft's NGSCB plan". Computerworld. IDG. Retrieved June 26, 2015.
  77. ^ Evers, Joris (February 24, 2005). "Silence Fuels Speculation on Microsoft Security Plan". PCWorld. IDG. Archived from the original on June 13, 2015. Retrieved January 30, 2015.
  78. ^ Microsoft (April 20, 2005). "Steve Ballmer: Microsoft Management Summit". Microsoft. Retrieved January 30, 2015.
  79. ^ Evers, Joris (April 25, 2005). "Microsoft delays bulk of next-generation security plan". Computerworld. IDG. Retrieved June 26, 2015.
  80. ^ a b Lemos, Robert (April 26, 2005). "Microsoft reveals hardware security plans, concerns remain". SecurityFocus. Symantec. Archived from the original on September 24, 2015. Retrieved January 30, 2015.
  81. ^ a b Foley Jo, Mary (April 15, 2005). "Microsoft Dusts Off 'Palladium' Security for Longhorn". PC Magazine. Ziff Davis. Archived from the original on June 13, 2015. Retrieved June 11, 2015.
  82. ^ Becker, Phil (June 26, 2002). "Interview with Palladium's Mario Juarez". Digital Identity World, LLC. Archived from the original on May 2, 2003. Retrieved March 14, 2015.
  83. ^ a b "Peter Biddle - BitLocker, Security in Windows Vista". Channel9. Microsoft. July 11, 2006. Retrieved March 13, 2015.
  84. ^ a b c Cannon, JC (2003). "Trustworthy Computing in Action: Privacy at Microsoft". Microsoft. Archived from the original (PPT) on June 14, 2015. Retrieved March 14, 2015.
  85. ^ Thurrott, Paul (September 9, 2005). "Pre-PDC Exclusive: Windows Vista Product Editions". Supersite for Windows. Penton. Archived from the original on April 2, 2015. Retrieved March 14, 2015.
  86. ^ Ourghanlian, Bernard (2007). "Plongée en aux profondes" (PPTX). Microsoft TechDays. Microsoft. Retrieved September 4, 2015.
  87. ^ Microsoft (April 22, 2005). "Secure Startup - Full Volume Encryption: Technical Overview" (DOC). Retrieved March 14, 2015.
  88. ^ Microsoft (April 21, 2005). "Secure Startup - Full Volume Encryption: Executive Overview" (DOC). Retrieved June 9, 2015.
  89. ^ a b Bekker, Scott (July 7, 2003). "Palladium: Don't Fear the Nexus". Redmond Magazine. 1105 Media Inc. Retrieved June 10, 2015.
  90. ^ a b Schneier, Bruce (August 15, 2002). "Palladium and the TCPA". Retrieved July 26, 2015.
  91. ^ a b Stephens, Mark (June 27, 2002). "I Told You So: Alas, a Couple of Bob's Dire Predictions Have Come True". Public Broadcasting Service. Retrieved June 11, 2015.
  92. ^ Forno, Richard (June 24, 2002). "MS to micro-manage your computer". The Register. Situation Publishing. Retrieved June 11, 2015.
  93. ^ Markoff, John (June 30, 2003). "A Safer System for Home PC's Feels Like Jail to Some Critics". The New York Times. Retrieved July 10, 2015.
  94. ^ a b c d e Anderson, Ross (2003). "'Trusted Computing' Frequently Asked Questions". Cambridge University. Retrieved June 11, 2015.
  95. ^ Fisher, Ken (April 15, 2003). "Cryptographers question Microsoft's Palladium". ArsTechnica. Condé Nast. Retrieved July 10, 2015.
  96. ^ "Germans fear Microsoft's 'trusted' Palladium technology". TVTechnology. Retrieved June 10, 2015.[permanent dead link]
  97. ^ Greene, Thomas (June 25, 2002). "MS to eradicate GPL, hence Linux". The Register. Situation Publishing. Retrieved June 11, 2015.
  98. ^ McMillan, Robert (January 15, 2003). "Microsoft's Power Play". Linux Magazine. IT Business Edge. Archived from the original on June 12, 2008. Retrieved June 11, 2015.{{cite web}}: CS1 maint: unfit URL (link)
  99. ^ Lettice, John (June 24, 2002). "MS DRM OS, retagged 'secure OS' to ship with Longhorn?". The Register. Situation Publishing. Retrieved June 11, 2015.
  100. ^ Lettice, John (October 30, 2003). "Longhorn as the next Microsoft desktop domination play". The Register. Situation Publishing. Retrieved June 11, 2015.
  101. ^ a b c Lee, Timothy (November 30, 2012). "How 4 Microsoft engineers proved that the 'darknet' would defeat DRM". ArsTechnica. Condé Nast. Retrieved June 10, 2015.
  102. ^ Morrissey, Brian (June 28, 2002). "Is Microsoft's Palladium a Trojan Horse?". IT Business Edge. QuinStreet. Archived from the original on April 20, 2015. Retrieved June 10, 2015.
  103. ^ McCullagh, Declan (June 26, 2003). "Gates v Orwell: Security needn't mean a Big Brother state". CNET. CBS Interactive. Retrieved June 10, 2015.
  104. ^ Levy, Steven (2004). "A Net of Control". Newsweek. Newsweek LLC. Archived from the original on January 13, 2004. Retrieved June 10, 2015.
  105. ^ Mills, Elinor; McCullagh, Declan (June 25, 2008). "Whatever happened to Microsoft's DRM plan?". CNET. CBS Interactive. Retrieved June 10, 2015.
  106. ^ BBC News (June 27, 2002). "Microsoft's bid for secure computing". Retrieved June 11, 2015.
  107. ^ Varian, Hal (July 4, 2002). "New Chips Can Keep a Tight Rein on Consumers". The New York Times. Retrieved June 11, 2015.
  108. ^ Lettice, John (June 28, 2002). "MS Palladium protects IT vendors, not you – paper". The Register. Situation Publishing. Retrieved June 11, 2015.
  109. ^ Safford, David (2002). "Clarifying Misinformation on TCPA" (PDF). IBM Research. IBM. Retrieved July 19, 2015.
  110. ^ Great Britain: Parliament: House of Commons: Home Affairs Committee (2006). Terrorism Detention Powers: Fourth Report of Session 2005-06. The Stationery Office. p. 28. ISBN 978-0-215-02953-9. I think what you have to watch out for here is that from later this year the encryption landscape is going to change with the release of Microsoft [Windows] Vista, the next generation of [the] Windows operating system, which will support the use of a chip called a TPM which manufacturers are putting on PC motherboards. [...] This is being done for a number of commercial reasons: firstly, to do digital rights management on downloaded music and films and, secondly, by the software vendors so they can lock the customers in tightly and charge more for their products. [...]
  111. ^ Stone-Lee, Ollie (February 16, 2006). "UK holds Microsoft security talks". BBC News. BBC. Retrieved July 11, 2015.
  112. ^ a b Stallman, Richard. "Can You Trust Your Computer?". Free Software Foundation. Retrieved June 11, 2015.
  113. ^ Lemos, Robert (November 7, 2002). "MS Palladium: A must or a menace?". ZDNet. CBS Interactive. Retrieved July 12, 2015.
  114. ^ Cullen, Drew (June 25, 2002). "Why Intel loves Palladium". The Register. Situation Publishing. Retrieved July 26, 2015.
  115. ^ Loney, Matt (June 27, 2002). "Who trusts Microsoft's Palladium? Not me". ZDNet. CBS Interactive. Retrieved June 11, 2015.
  116. ^ Glass, Brett (May 17, 1999). "Intel PIII: Is Big Brother Inside?". ZDNet. CBS Interactive. Retrieved August 24, 2015.
  117. ^ Sydney Morning Herald (May 12, 2003). "Palladium won't stifle users, says Gates". Associated Press. Retrieved July 10, 2015.
  118. ^ Biddle, Peter; England, Paul; Peinado, Marcus; Willman, Bryan (2003). "The Darknet and the Future of Content Distribution" (PDF). ACM Digital Rights Management Workshop. Microsoft. doi:10.1007/10941270_23. Archived from the original (PDF) on July 17, 2012. Retrieved July 19, 2015.
  119. ^ Schechter, Stuart; Greenstadt, Rachel; Smith, Michael (May 16, 2003). "Trusted Computing, Peer-To-Peer Distribution, and the Economics of Pirated Entertainment" (PDF). Harvard University. Retrieved June 10, 2015.
  120. ^ Fisher, Dennis (May 5, 2003). "Microsoft Security Plan Has Gaps, Study Says". eWeek. QuinStreet. Retrieved June 11, 2015.
  121. ^ Thurrott, Paul (October 20, 2002). "Microsoft Palladium". Windows IT Pro. Penton. Retrieved June 10, 2015.
  122. ^ Glaskowsky, Peter; Fanciullo, Kimberly. "Microprocessor Report Announces Winners for the Fifth Annual Analysts' Choice Awards". In-Stat/MDR. Reed Business Information. Archived from the original on March 17, 2004. Retrieved June 10, 2015.
  123. ^ Bajkowski, Julian (November 24, 2003). "Privacy commissioner slams music enforcers, cautions on DRM". Computerworld. IDG. Archived from the original on January 25, 2018. Retrieved July 12, 2015.
  124. ^ Naraine, Ryan (May 12, 2004). "Gartner Hails Microsoft's 'Palladium' Modification". IT Business Edge. QuinStreet. Archived from the original on January 23, 2018. Retrieved July 12, 2015.
  125. ^ Wilson, David (September 30, 2003). "Palladium pesticide triggers poison pens". South China Morning Post. SCMP Group. Retrieved July 12, 2015.
  126. ^ Brintzenhofe, Keith (2003). "Ecosystem and Opportunities with NGSCB". Microsoft. Archived from the original (EXE) on August 8, 2003. Retrieved July 12, 2015.
  127. ^ Schneier, Bruce (May 2, 2006). "Microsoft's BitLocker". Retrieved July 12, 2015. EDITED TO ADD (5/3): BitLocker is not a DRM system. However, it is straightforward to turn it into a DRM system. Simply give programs the ability to require that files be stored only on BitLocker-enabled drives, and then only be transferrable to other BitLocker-enabled drives. How easy this would be to implement, and how hard it would be to subvert, depends on the details of the system.
  128. ^ Spooner, John (May 30, 2006). "Can Microsoft's BitLocker Save Us from Ourselves?". eWeek. QuinStreet. Retrieved July 12, 2015.
  129. ^ Biddle, Peter. (July 16, 2008). "Perception (or, Linus gets away with being honest again)"
  130. ^ "Boneh Publications: Remote timing attacks are practical". Retrieved 2014-09-22.
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Next-Generation_Secure_Computing_Base&oldid=1248202990"