DOCSLIB.ORG

Windows 2003/XP Security Target

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Windows 2003/XP Security Target Microsoft Windows Server 2003, XP Professional and XP Embedded Security Target Version 3.0 November 19, 2007 Prepared For: Microsoft Corporation Corporate Headquarters One Microsoft Way Redmond, WA 98052-6399 Prepared By: Science Applications International Corporation Common Criteria Testing Laboratory 7125 Gateway Drive Columbia, MD 21046-2554 Version 3.0, 11/19/07 © Microsoft Corporation, 2008 ii All Rights Reserved. Version 3.0, 11/19/07 This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. This work is licensed under the Creative Commons Attribution-NoDerivs- NonCommercial License (which allows redistribution of the work). To view a copy of this license, visit http://creativecommons.org/licenses/by-nd-nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Visual Basic, Visual Studio, Windows, the Windows logo, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. © Microsoft Corporation, 2008 iii All Rights Reserved. Version 3.0, 11/19/07 Table of Contents 1. SECURITY TARGET INTRODUCTION......................................................................................... 1 1.1 SECURITY TARGET, TOE, AND CC IDENTIFICATION ................................................................ 1 1.2 CC CONFORMANCE CLAIMS .................................................................................................... 4 1.3 STRENGTH OF ENVIRONMENT .................................................................................................. 4 1.4 CONVENTIONS, TERMINOLOGY, ACRONYMS............................................................................ 4 1.4.1 Conventions ............................................................................................................................ 4 1.4.2 Terminology............................................................................................................................ 5 1.4.3 Acronyms ................................................................................................................................5 1.5 SECURITY TARGET OVERVIEW AND ORGANIZATION ............................................................... 5 2. TOE DESCRIPTION........................................................................................................................... 7 2.1 PRODUCT TYPES ...................................................................................................................... 7 2.2 PRODUCT DESCRIPTION ........................................................................................................... 8 2.3 PRODUCT FEATURES ................................................................................................................ 9 2.3.1 Windows 2003/XP Administration and Management Features............................................ 10 2.3.2 Windows 2003/XP Network Security Features..................................................................... 13 2.3.3 Windows 2003/XP Scalability Features................................................................................ 15 2.3.4 New Windows 2003/XP TOE Features................................................................................. 17 2.4 SECURITY ENVIRONMENT AND TOE BOUNDARY................................................................... 19 2.4.1 Logical Boundaries............................................................................................................... 19 2.4.2 Physical Boundaries............................................................................................................. 21 2.5 TOE SECURITY SERVICES...................................................................................................... 21 3. SECURITY ENVIRONMENT.......................................................................................................... 24 3.1 THREATS TO SECURITY .......................................................................................................... 24 3.2 ORGANIZATIONAL SECURITY POLICIES.................................................................................. 25 3.3 SECURE USAGE ASSUMPTIONS............................................................................................... 25 3.3.1 Connectivity Assumptions..................................................................................................... 26 3.3.2 Personnel Assumptions......................................................................................................... 26 3.3.3 Physical Assumptions ........................................................................................................... 26 4. SECURITY OBJECTIVES ............................................................................................................... 28 4.1 TOE IT SECURITY OBJECTIVES.............................................................................................. 28 4.2 NON-IT SECURITY OBJECTIVES FOR THE ENVIRONMENT....................................................... 29 5. IT SECURITY REQUIREMENTS................................................................................................... 30 5.1 TOE SECURITY FUNCTIONAL REQUIREMENTS....................................................................... 30 5.1.1 Audit (FAU) Requirements ................................................................................................... 37 5.1.2 Cryptographic Support (FCS) .............................................................................................. 41 5.1.3 User Data Protection (FDP) Requirements ......................................................................... 45 5.1.4 Identification and Authentication (FIA)................................................................................ 55 5.1.5 Management Requirements (FMT)....................................................................................... 57 5.1.6 Protection of the TOE Security Functions (FPT) ................................................................. 65 5.1.7 Resource Utilization (FRU).................................................................................................. 68 5.1.8 TOE Access (FTA)................................................................................................................ 68 5.1.9 Trusted Path/Channels ......................................................................................................... 69 5.2 TOE SECURITY ASSURANCE REQUIREMENTS ........................................................................ 69 5.2.1 Configuration Management (ACM)...................................................................................... 70 5.2.2 Delivery and Operation (ADO) ............................................................................................ 73 5.2.3 Development (ADV).............................................................................................................. 74 5.2.4 Guidance Documents (AGD)................................................................................................ 78 5.2.5 Life Cycle Support (ALC) ..................................................................................................... 80 © Microsoft Corporation, 2008 iv All Rights Reserved. Version 3.0, 11/19/07 5.2.6 Security Testing (ATE).......................................................................................................... 82 5.2.7 Vulnerability Assessment (AVA) ........................................................................................... 84 5.3 SECURITY REQUIREMENTS FOR THE IT ENVIRONMENT.......................................................... 87 6. TOE SUMMARY SPECIFICATION............................................................................................... 88 6.1 TOE SECURITY FUNCTIONS ................................................................................................... 88 6.1.1 Audit Function .....................................................................................................................
Load more

Recommended publications
  • Cygwin User's Guide
    Cygwin User’s Guide Cygwin User’s Guide ii Copyright © Cygwin authors Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .4 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . .7 1.7 What’s new and what changed in Cygwin . .7 1.7.1 What’s new and what changed in 3.2 .
    [Show full text]
  • Microsoft Windows Common Criteria Evaluation Security Target
    Microsoft Common Criteria Security Target Microsoft Windows Common Criteria Evaluation Microsoft Windows 10 version 1809 (October 2018 Update) Microsoft Windows Server 2019 (October 2018 Update) Security Target Document Information Version Number 0.05 Updated On June 18, 2019 Microsoft © 2019 Page 1 of 126 Microsoft Common Criteria Security Target Version History Version Date Summary of changes 0.01 June 27, 2018 Initial draft 0.02 December 21, 2018 Updates from security target evaluation 0.03 February 21, 2019 Updates from evaluation 0.04 May 6, 2019 Updates from GPOS PP v4.2.1 0.05 June 18, 2019 Public version Microsoft © 2019 Page 2 of 126 Microsoft Common Criteria Security Target This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. This work is licensed under the Creative Commons Attribution-NoDerivs- NonCommercial License (which allows redistribution of the work). To view a copy of this license, visit http://creativecommons.org/licenses/by-nd-nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.
    [Show full text]
  • Windows System Error Codes and What They Mean
    Windows system error codes and what they mean This information was gathered from: https://msdn.microsoft.com/en-us/library/windows/desktop/ ms681382(v=vs.85).aspx You can find additional error codes and messages in the above website. Code Description: 0 The operation completed successfully. 1 Incorrect function. 2 The system cannot find the file specified. 3 The system cannot find the path specified. 4 The system cannot open the file. 5 Access is denied. 6 The handle is invalid. 7 The storage control blocks were destroyed. 8 Not enough storage is available to process this command. 9 The storage control block address is invalid. 10 The environment is incorrect. 11 An attempt was made to load a program with an incorrect format. 12 The access code is invalid. 13 The data is invalid. 14 Not enough storage is available to complete this operation. 15 The system cannot find the drive specified. 16 The directory cannot be removed. 17 The system cannot move the file to a different disk drive. 18 There are no more files. 19 The media is write protected. 20 The system cannot find the device specified. 21 The device is not ready. 22 The device does not recognize the command. 23 Data error (cyclic redundancy check). 24 The program issued a command but the command length is incorrect. 25 The drive cannot locate a specific area or track on the disk. 26 The specified disk or diskette cannot be accessed. 27 The drive cannot find the sector requested. 28 The printer is out of paper.
    [Show full text]
  • DRBL-Winroll: the Free Configuration Program for Microsoft Windows
    DRBL-Winroll: The Free configuration program for Microsoft Windows Ceasar Sun, Steven Shiau, Thomas Tsai http://drbl-winroll.org , http://drbl.org , http://clonezilla.org/ RMLL (LSM) 2015 Q3, 2015 1 Outline Introduction to DRBL-Winroll – Develop Team – Common Issues for Windows Replication – Feature/Framework Cases of Usages – Basic Installation and usage – How to do centralize management – Advanced usage Limitation/Development/Contribution Q&A 2 Outline Introduction to DRBL-Winroll – Develop Team – Common Issues for Windows Replication – Feature/Framework Cases of Usages – Basic Installation and usage – How to do centralize management – Advanced usage Limitation/Development/Contribution Q&A 3 About us • From Taiwan, working for the NPO NCHC (National Center for High- Performance Computing) • Developers of free/open-source software: – DRBL, Clonezilla – DRBL-Winroll, Tux2live – Partclone, Tuxboot, Cloudboot – ... more Taiwan image source: wikipedia.org 4 Developers/Contributor • Steven Shiau • Ceasar Sun • Thomas Tsai • Jazz Wang • Jean René Mérou Sánchez • K. L. Huang • Jean-Francois Nifenecker • Louie Chen • Nagappan Alagappan • … 5 Replication Issue 6 Copy & Paste ? • Data v.s Configurations – For small scale replication , it's easy. • Deployment is one thing, but configuration is another – Not only copy-and-paste 7 Configuration with Massive Scale • Not possible by hand , automatical configuration is better I©m Robot #1 Hello, I©m Robot #2 Hello, I©m Robot #3 Hello, I©m Robot #.. 8 Mass Deployment • What is “mass deployment”
    [Show full text]
  • Clustered Data ONTAP® 8.3 File Access Management Guide for NFS
    Updated for 8.3.1 Clustered Data ONTAP® 8.3 File Access Management Guide for NFS NetApp, Inc. Telephone: +1 (408) 822-6000 Part number: 215-10105_A0 495 East Java Drive Fax: +1 (408) 822-4501 June 2015 Sunnyvale, CA 94089 Support telephone: +1 (888) 463-8277 U.S. Web: www.netapp.com Feedback: [email protected] Table of Contents | 3 Contents Considerations before configuring file access .......................................... 10 File protocols that Data ONTAP supports ................................................................. 10 How Data ONTAP controls access to files ................................................................ 10 Authentication-based restrictions .................................................................. 10 File-based restrictions ................................................................................... 11 LIF configuration requirements for file access management .................................... 11 How namespaces and volume junctions affect file access on SVMs with FlexVol volumes ................................................................................................................ 11 What namespaces in SVMs with FlexVol volumes are ................................. 11 Volume junction usage rules ......................................................................... 12 How volume junctions are used in SMB and NFS namespaces .................... 12 What the typical NAS namespace architectures are ...................................... 12 Creating and managing data volumes
    [Show full text]
  • Clustered Data ONTAP 8.3 NFS File Access Reference Guide
    Clustered Data ONTAP® 8.3 NFS File Access Reference Guide February 2016 | 215-10877_A0 [email protected] Updated for 8.3.2 Table of Contents | 3 Contents Deciding whether to use this guide ............................................................. 8 Considerations before configuring file access ............................................ 9 File protocols that Data ONTAP supports ................................................................... 9 How Data ONTAP controls access to files .................................................................. 9 Authentication-based restrictions .................................................................... 9 File-based restrictions ................................................................................... 10 LIF configuration requirements for file access management .................................... 10 How namespaces and volume junctions affect file access on SVMs with FlexVol volumes ................................................................................................................ 10 What namespaces in SVMs with FlexVol volumes are ................................. 10 Volume junction usage rules ......................................................................... 11 How volume junctions are used in SMB and NFS namespaces .................... 11 What the typical NAS namespace architectures are ...................................... 11 Creating and managing data volumes in NAS namespaces ...................................... 14 Creating data volumes
    [Show full text]
  • More Than You Ever Wanted to Know About NT Login Authentication
    A Perspective On Practical Security 2000 More Than You Ever Wanted to Know about NT Login Authentication SystemExperts Corporation Philip C. Cox & Paul B. Hill Abstract Inside The login process is the user's entry-point to the computing • Under the covers for a local NT login environment, the best or perhaps only chance for real • NT & LAN Manager compatibility authentication. No authorization decision has any meaning absent authentication. Taking the rapid adoption of NT as a given, any • Password encryption within the Security Accounts Manager organization must understand exactly how NT login authentication (SAM) database works if it is to determine whether or not NT login can meet the organization's needs. Otherwise, the choices are faith and luck. • User Authentication Process This white paper describes an Interactive NT login and lays the • Use of the LsaLogonUser API groundwork for understanding the Network login. This information is current as of NT 4.0 Service Pack 5. • The groundwork for understanding network login. NT Login Authentication SystemExperts Corporation There are no less than 5 types of “logons” in Windows NT, but only three are commonly used: Interactive, Network, and Service. Boston New York Washington D.C Tampa San Francisco Los Angeles Sacramento 1. Interactive logons are for users logging onto the console and for processes that require “interactive” access. Interactive NT Toll free (USA only): +1 888 749 9800 user authentication itself takes several forms: From outside USA: +1 978 440 9388 - Login with a locally defined user account — no network access is required; the account is authenticated by the machine you are logging into and only by that machine www.systemexperts.com [email protected] Copyright 1997-2001 SystemExperts Corporation.
    [Show full text]
  • Windows Server 2003 Security Guide
    Microsoft Solutions for Security and Compliance Windows Server 2003 Security Guide April 26, 2006 © 2006 Microsoft Corporation. This work is licensed under the Creative Commons Attribution-Non Commercial License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc/2.5/ or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA. Table of Contents iii Contents Chapter 1: Introduction to the Windows Server 2003 Security Guide ............. 1 Overview....................................................................................................1 Executive Summary .....................................................................................1 Who Should Read This Guide.........................................................................2 Scope of this Guide......................................................................................2 Chapter Summaries .....................................................................................3 Chapter 1: Introduction to the Windows Server 2003 Security Guide .............4 Chapter 2: Windows Server 2003 Hardening Mechanisms ............................4 Chapter 3: The Domain Policy..................................................................4 Chapter 4: The Member Server Baseline Policy ...........................................4 Chapter 5: The Domain Controller Baseline Policy .......................................5 Chapter 6: The Infrastructure Server Role .................................................5
    [Show full text]
  • Online Microsoft Image Mastering Api V2 for Xp 32 Bit Rtf for Amazon
    Site Navigation Deutsch Enter Search Microsoft image only. Note that UA FireWire products are incompatible with Big mastering api v2 for xp Sur. (Auto-Tune Realtime Advanced) Resolved crash that could 32 bit occur in some macOS applications. UAD v9.14.0 is compatible 16 First Avenue with Windows and earlier macOS versions. Using UAD Plug-Ins Haskell, NJ 07420 USA with Pro Tools on Windows. needs to be downloaded from your 973-248-8080 Microsoft Store account. This may happen if you're trying. (Ocean Fax: 973-248-8012 Way Studios) Improved high-frequency response at sample rates [email protected] of 88.2 kHz and 96 kHz. On-premises and Oracle Cloud options [email protected] simplify digital transformations. (Moog Multimode Filter XL) Settings are now correctly preserved when using ARM in LUNA. Oracle IT infrastructure simplifies organization's digital transformation by enabling IT teams to deploy optimized solutions in customer data centers and easy-to-manage appliances in remote offices and edge environments. Solutions with full-stack integration and optimizations allow customers to run Oracle Databases up to 10X faster with Oracle Exadata's Smart Scan query offload, as highlighted in the NTT DoCoMo video. Important: macOS High Sierra, Mojave, and Catalina require manual steps to enable UAD software. For details, see this article. Specific Windows operating system settings are necessary for optimum performance when using UAD devices. For details, please review the. After Pro Tools finishes loading, QUIT Pro Tools. The UAD plug-ins are now ready for use the next time Pro Tools is opened.
    [Show full text]
  • Windows XP Technical Overview
    Operating System Windows XP Technical Overview Microsoft Corporation Published: May 2001 Abstract This paper provides a technical overview of what’s new in the Microsoft® Windows® XP operating system. It shows how new technologies and features make it easier to get work done, share information, manage your desktop, stay productive while traveling with a mobile computer, obtain help and support, and perform many other computing tasks. Because this paper is an overview, it does not address any area in detail but provides a broad look at the many new technologies and features in Windows XP. This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.
    [Show full text]
  • A Survey of Access Control Policies
    A Survey of Access Control Policies Amanda Crowell University of Maryland [email protected] ABSTRACT nisms to the standard checks. Modern operating systems each have different implementa- tions of access controls and use different policies for deter- The Common Weakness Enumeration (CWE) describes sev- mining the access that subjects may have on objects. This eral mistakes that application developers have made in re- paper reviews the three main types of access control policies: gard to access control. Often, developers do not give the discretionary, mandatory, and role-based. It then describes application objects the appropriate rights to begin with (i.e. how Windows and various Unix systems implement their they specify more rights than are necessary) and do not chosen access control policies. Finally, it discusses some modify rights throughout the application's lifetime. Since common mistakes that application programmers make when spawned processes typically take on the rights of the spawn- enforcing access control in their applications and gives some ing process, rights might be passed on to the spawned pro- general guidance to reduce the occurrence of mistakes. cess that were unintentional. In response to these mistakes, some researchers have developed guidelines for using access 1. INTRODUCTION controls appropriately. These include: (a) understanding Modern operating systems use different mechanisms for pro- what information is available to the system and how it can viding access control. These mechanisms are designed to be used to make decisions, (b) determining exactly which meet security policies that vary in the way access decisions rights are absolutely necessary and only allow those and are made.
    [Show full text]
  • Database Installation Guide
    Oracle® Database Database Installation Guide 19c for Microsoft Windows E96293-06 June 2020 Oracle Database Database Installation Guide, 19c for Microsoft Windows E96293-06 Copyright © 1996, 2020, Oracle and/or its affiliates. Primary Authors: Sunil Surabhi, Tanaya Bhattacharjee Contributing Authors: Prakash Jashnani, Mark Bauer, Bharathi Jayathirtha Contributors: Barb Glover, Eric Belden, Sudip Datta, David Friedman, Alex Keh, Peter LaQuerre, Rich Long, Matt McKerley, Sham Rao Pavan, Hanlin Qian, Sujatha Tolstoy, Sergiusz Wolicki, Sue Mavris, Mohammed Shahnawaz Quadri, Vishal Saxena, Krishna Itikarlapall, , Santanu Datta, Christian Shay, Aneesh Khanderwal, Michael Coulter, Robert Achacoso, Malai Stalin, David Price, Ramesh Chakravarthula This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S.
    [Show full text]