National Information Assurance Partnership
Common Criteria Evaluation and Validation Scheme
Validation Report
for
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
Report Number: CCEVS-VR-10635-2015
Dated: August 27, 2015
Version: 1.0
National Institute of Standards and Technology National Security Agency
Information Technology Laboratory Information Assurance Directorate
100 Bureau Drive 9800 Savage Road STE 6940
Gaithersburg, MD 20899 Fort George G. Meade, MD 20755-6940
®
TM
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
ii
ACKNOWLEDGEMENTS
Validation Team
Paul Bicknell
Luke Florer
Stelios Melachrinoudis
Common Criteria Testing Laboratory
Kevin Micciche
Kevin Steiner
Gregory Beaver
Gary Grainger
Leidos (formerly SAIC, Inc.)
Columbia, MD
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
iii
Table of Contents
1 Executive Summary.............................................................................................................1
2 Identification........................................................................................................................3
2.1 Threats.........................................................................................................................3
2.2 Organizational Security Policies.................................................................................4
3 Architectural Information ....................................................................................................5
4 Assumptions.........................................................................................................................6
4.1 Clarification of Scope .................................................................................................6
5 Security Policy.....................................................................................................................7
5.1 Security Audit...........................................................Error! Bookmark not defined.
5.2 Cryptographic Support................................................................................................7
5.3 User Data Protection...................................................................................................7
5.4 Identification and Authentication ...............................................................................7
5.5 Security Management .................................................................................................7
5.6 Protection of the TSF..................................................................................................7
5.7 Session Locking..........................................................................................................8
5.8 Trusted Path/Channels ................................................................................................8
6 Documentation.....................................................................................................................9
7 Independent Testing...........................................................................................................10
8 Evaluated Configuration ....................................................................................................11
9 Results of the Evaluation ...................................................................................................12
10 Validator Comments/Recommendations ...........................................................................13
11 Annexes 14
12 Security Target...................................................................................................................15
13 Abbreviations and Acronyms ............................................................................................16
14 Bibliography ......................................................................................................................17
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
1
List of Tables
Table 1: Evaluation Details............................................................................................................. 2
Table 2: ST and TOE Identification................................................................................................ 3
Table 3: TOE Security Assurance Requirements ......................................................................... 12
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
1
1 Executive Summary
This report is intended to assist the end-user of this product and any security certification agent for that
end-user to determine the suitability of this Information Technology (IT) product in their environment.
End-users should review the Security Target (ST), (which is where specific security claims are made) as
well as this Validation Report (VR) (which describes how those security claims were evaluated, tested,
and any restrictions that may be imposed upon the evaluated configuration) to help in that determination.
Prospective users should carefully read the Assumptions and Clarification of Scope in Section 4 and the
Validator Comments in Section 10, where any restrictions on the evaluated configuration are highlighted.
This report documents the National Information Assurance Partnership (NIAP) assessment of the
evaluation of Microsoft Windows 8.1 and Microsoft Windows Phone 8.1. It presents the evaluation
results, their justifications, and the conformance results. This VR is not an endorsement of the Target of
Evaluation (TOE) by any agency of the U.S. Government and no warranty of the TOE is either expressed
or implied. This VR applies only to the specific version and configuration of the product as evaluated and
as documented in the ST.
The evaluation of Microsoft Windows 8.1 and Microsoft Windows Phone 8.1 was performed by Leidos
(formerly Science Applications International Corporation (SAIC)) Common Criteria Testing Laboratory
(CCTL) in Columbia, Maryland, in the United States and was completed in August 2015. The evaluation
was conducted in accordance with the requirements of the Common Criteria and Common Methodology
for IT Security Evaluation (CEM), version 3.1, revision 4 and the assurance activities specified in the
Protection Profile for Mobility Device Fundamentals, version 1.1. The evaluation was consistent with
NIAP Common Criteria Evaluation and Validation Scheme (CCEVS) policies and practices as described
on their web site (www.niap-ccevs.org).
The Leidos evaluation team determined that Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
is conformant to the claimed Protection Profile (PP) and, when installed, configured and operated as
specified in the evaluated guidance documentation, satisfied all of the security functional requirements
stated in the ST. The information in this VR is largely derived from the publically available Assurance
Activities Report (AAR) and the associated proprietary test report produced by the Leidos evaluation
team.
The TOE is a hardware and software solution that consists of Microsoft Windows 8.1 and Microsoft
Windows Phone 8.1 Operating Systems, running on the following devices:
 Microsoft Surface 3, Windows 8.1 Pro, 64-bit, Intel Atom Z8700, Marvell 8897 Wi-Fi a/b/g/n
adapter, Bluetooth 4.0, Bluetooth LE, Intel TPM 2.0
 Microsoft Lumia 635, Windows Phone 8.1, Qualcomm Snapdragon 400, GSM, HSPA, LTE,
Qualcomm WCN3620 Wi-Fi b/g/n adapter, Qualcomm TPM 2.0
 Microsoft Lumia 830, Windows Phone 8.1, Qualcomm Snapdragon 400, GSM, HSPA, LTE,
Qualcomm WCN3620 Wi-Fi b/g/n adapter, Qualcomm TPM 2.0
The validation team monitored the activities of the evaluation team, examined evaluation evidence,
provided guidance on technical issues and evaluation processes, and reviewed the evaluation results
produced by the evaluation team. The validation team found that the evaluation results showed that all
assurance activities specified in the claimed PP had been completed successfully and that the product
satisfied all of the security functional and assurance requirements as stated in the ST. Therefore the
validation team concludes that the testing laboratory’s findings are accurate, the conclusions justified, and
the conformance results are correct. The conclusions of the testing laboratory in the evaluation technical
report are consistent with the evidence produced.
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
2
Table 1: Evaluation Details
Item Identifier
Evaluated Product Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
Sponsor & Developer Michael Grimm
Microsoft Corporation
CCTL Leidos
Common Criteria Testing Laboratory
6841 Benjamin Franklin Drive
Columbia, MD 21046
Completion Date August 2015
CC Common Criteria for Information Technology Security Evaluation,
Version 3.1, Revision 4, September 2012
Interpretations There were no applicable interpretations used for this evaluation.
CEM Common Methodology for Information Technology Security
Evaluation: Version 3.1, Revision 4, September 2012
PP Protection Profile for Mobility Device Fundamentals, Version 1.1
Evaluation Class None
Disclaimer The information contained in this Validation Report is not an
endorsement of the Microsoft Windows 8.1 and Microsoft Windows
Phone 8.1 by any agency of the U.S. Government and no warranty of
Windows 8.1 and Windows Phone 8.1 is either expressed or implied.
Evaluation Personnel Kevin Micciche
Kevin Steiner
Gregory Beaver
Gary Grainger
Validation Personnel Paul Bicknell
Luke Florer
Stelios Melachrinoudis
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
3
2 Identification
The CCEVS is a joint National Security Agency (NSA) and National Institute of Standards and
Technology (NIST) effort to establish commercial facilities to perform trusted product evaluations. Under
this program, security evaluations are conducted by commercial testing laboratories called Common
Criteria Testing Laboratories (CCTLs) in accordance with National Voluntary Laboratory Assessment
Program (NVLAP) accreditation.
The NIAP Validation Body assigns validators to monitor the CCTLs to ensure quality and consistency
across evaluations. Developers of information technology products desiring a security evaluation contract
with a CCTL and pay a fee for their product’s evaluation. Upon successful completion of the evaluation,
the product is added to NIAP’s Product Compliant List (PCL).
The following table identifies the evaluated Security Target and TOE.
Table 2: ST and TOE Identification
Name Description
ST Title Microsoft Windows 8.1 and Microsoft Windows Phone 8.1 Security Target
ST Version 1.0
Publication Date August 27, 2015
Vendor and ST Author Microsoft
TOE Reference Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
TOE Hardware Models Microsoft Surface 3 (Windows 8.1 Pro)
Microsoft Lumia 635 (Windows Phone 8.1)
Microsoft Lumia 830 (Windows Phone 8.1)
TOE Software Version Microsoft Windows 8.1 (Pro) and Microsoft Windows Phone 8.1 (GDR2)
Keywords Mobility Device
2.1 Threats
The ST identifies the following threats that the TOE and its operational environment are intended to
counter:
 An attacker is positioned on a wireless communications channel or elsewhere on the network
infrastructure. Attackers may monitor and gain access to data exchanged between the Mobile
Device and other endpoints.
 An attacker is positioned on a wireless communications channel or elsewhere on the network
infrastructure. Attackers may initiate communications with the Mobile Device or alter
communications between the Mobile Device and other endpoints in order to compromise the
Mobile Device. These attacks include malicious software update of any applications or system
software on the device. These attacks also include malicious web pages or email attachments
which are usually delivered to devices over the network.
 The loss or theft of the Mobile Device may give rise to loss of confidentiality of user data
including credentials. These physical access threats may involve attacks which attempt to access
the device through external hardware ports, through its user interface, and also through direct and
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
4
possibly destructive access to its storage media. The goal of such attacks is to access data from a
lost or stolen device which is not expected to return to its user.
 Applications loaded onto the Mobile Device may include malicious or exploitable code. This
code could be included intentionally by its developer or unknowingly by the developer, perhaps
as part of a software library. Malicious apps may attempt to exfiltrate data to which they have
access. They may also conduct attacks against the platform‘s system software which will provide
them with additional privileges and the ability to conduct further malicious activities. Malicious
applications may be able to control the device's sensors (GPS, camera, microphone) to gather
intelligence about the user's surroundings even when those activities do not involve data resident
or transmitted from the device. Flawed applications may give an attacker access to perform
network-based or physical attacks that otherwise would have been prevented.
 Persistent access to a device by an attacker implies that the device has lost integrity and cannot
regain it. The device has likely lost this integrity due to some other threat vector, yet the
continued access by an attacker constitutes an on-going threat in itself. In this case the device and
its data may be controlled by an adversary at least as well as by its legitimate owner.
2.2 Organizational Security Policies
There are no Organizational Security Policies for the Mobile Device protection profile.
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
5
3 Architectural Information
The TOE is a hardware and software solution that consists of Microsoft Windows 8.1 and Microsoft
Windows Phone 8.1 Operating Systems, running on the following devices:
 Microsoft Surface 3, Windows 8.1 Pro, 64-bit, Intel Atom Z8700, Marvell 8897 Wi-Fi a/b/g/n
adapter, Bluetooth 4.0, Bluetooth LE, Intel TPM 2.0
 Microsoft Lumia 635, Windows Phone 8.1, Qualcomm Snapdragon 400, GSM, HSPA, LTE,
Qualcomm WCN3620 Wi-Fi b/g/n adapter, Qualcomm TPM 2.0
 Microsoft Lumia 830, Windows Phone 8.1, Qualcomm Snapdragon 400, GSM, HSPA, LTE,
Qualcomm WCN3620 Wi-Fi b/g/n adapter, Qualcomm TPM 2.0
Windows 8.1 and Windows Phone 8.1 are preemptive multitasking, multiprocessor, and multi-user
operating systems. In general, operating systems provide users with a convenient interface to manage
underlying hardware. They control the allocation and manage computing resources such as processors,
memory, and Input/Output (I/O) devices. Windows 8.1 and Windows Phone 8.1, collectively referred to
as Windows, expands these basic operating system capabilities to controlling the allocation and managing
higher level IT resources such as security principals (user or machine accounts), files, printing objects,
services, window station, desktops, cryptographic keys, network ports traffic, directory objects, and web
content. Multi-user operating systems such as Windows keep track of which user is using which resource,
grant resource requests, account for resource usage, and mediate conflicting requests from different
programs and users.
The TOE includes the following variants of Windows and Windows Phone:
 Windows 8.1 Pro
 Windows Phone 8.1 GDR2
Windows Phone 8.1 is based on the same core operating system as Windows 8.1 and provides a
simplified user interface that makes Windows Phone a communications hub for voice, text, and web
access.
The TOE includes both physical and logical boundaries. Its operational environment is that of a
networked environment with IEEE 802.11 (Wi-Fi), mobile broadband networks (3G/4G and LTE) and
Bluetooth networks.
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
6
4 Assumptions
The ST identifies the following assumptions about the use of the product:
 It is assumed that the TOE‘s security functions are configured correctly in a manner to ensure that
the TOE security policies will be enforced on all applicable network traffic flowing among the
attached networks.
 It is assumed that the mobile user will immediately notify the administrator if the Mobile Device
is lost or stolen.
 It is assumed that the mobile user exercises precautions to reduce the risk of loss or theft of the
Mobile Device.
4.1 Clarification of Scope
All evaluations (and all products) have limitations, as well as potential misconceptions that need
clarification. This text covers some of the more important limitations and clarifications of this evaluation.
Note that:
1. As with any evaluation, this evaluation only shows that the evaluated configuration meets the
security claims made, with a certain level of assurance (the assurance activities specified in the
claimed PPs and performed by the evaluation team).
2. This evaluation covers only the specific device models and software version identified in this
document, and not any earlier or later versions released or in process.
3. The evaluation of security functionality of the product was limited to the functionality specified
in the claimed PPs. Any additional security related functional capabilities of the product were
not covered by this evaluation. Any additional non-security related functional capabilities of the
product, even those described in the ST, were not covered by this evaluation.
4. This evaluation did not specifically search for, nor attempt to exploit, vulnerabilities that were not
“obvious” or vulnerabilities to objectives not claimed in the ST. The CEM defines an “obvious”
vulnerability as one that is easily exploited with a minimum of understanding of the TOE,
technical sophistication and resources.
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
7
5 Security Policy
The TOE enforces the following security policies as described in the ST.
5.1 Cryptographic Support
Windows provides FIPS 140-2 validated cryptographic functions that support encryption/decryption,
cryptographic signatures, cryptographic hashing, cryptographic key agreement, and random number
generation. The TOE additionally provides support for public keys, credential management and certificate
validation functions and provides support for the National Security Agency’s Suite B cryptographic
algorithms. Windows also provides extensive auditing support of cryptographic operations, the ability to
replace cryptographic functions and random number generators with alternative implementations, and a
key isolation service designed to limit the potential exposure of secret and private keys. In addition to
using cryptography for its own security functions, Windows offers access to the cryptographic support
functions for user-mode and kernel-mode programs. Public key certificates generated and used by
Windows to authenticate users and machines as well as protect both user and system data in transit.
 Software-based disk encryption: Windows implements BitLocker to provide encrypted data
storage for fixed and removable volumes and protects the disk volume’s encryption key with one
or more intermediate keys and authorization factor
 IPsec: Windows implements IPsec to provide protected, authenticated, confidential, and tamper-
proof networking between two peer computers.
5.2 User Data Protection
In the context of this evaluation Windows protects user data at rest and provides secure storage of
X.509v3 certificates.
5.3 Identification and Authentication
In the context of this evaluation, Windows provides the ability to use, store, and protect X.509 certificates
that are used for IPsec and authenticates the user to their mobile device.
5.4 Security Management
Windows includes several functions to manage security policies. Policy management is controlled
through a combination of access control, membership in administrator groups, and privileges.
5.5 Protection of the TSF
Windows provides a number of features to ensure the protection of TOE security functions. Windows
protects against unauthorized data disclosure and modification by using a suite of Internet standard
protocols including IPsec, IKE, and ISAKMP. Windows ensures process isolation security for all
processes through private virtual address spaces, execution context, and security context. The Windows
data structures defining process address space, execution context, memory protection, and security
context are stored in protected kernel-mode memory. Windows includes self-testing features that ensure
the integrity of executable program images and its cryptographic functions. Finally, Windows provides a
trusted update mechanism to update Windows binaries itself.
Like TSF processes, user processes also are provided a private address space and process context, and
therefore are protected from each other. Additionally, the TSF has the ability to protect memory pages
using Data Execution Prevention (DEP) which marks memory pages in a process as non-executable
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
8
unless the location explicitly contains executable code. When the processor is asked to execute
instructions from a page marked as data, the processor will raise an exception for the OS to handle.
The Windows kernel, user-mode applications, and all Windows Store Applications implement Address
Space Layout Randomization (ASLR) in order to load executable code at unpredictable base addresses.
The base address is generated using a pseudo-random number generator that is seeded by high quality
entropy sources when available which provides at least 8 random bits for memory mapping.
5.6 Session Locking
Windows provides the ability for a user to lock their session either immediately or after a defined interval.
Windows constantly monitors the mouse, keyboard, and touch display for activity and locks the computer
after a set period of inactivity. Windows allows an authorized administrator to configure the system to
display a logon banner before the logon dialog.
5.7 Trusted Path/Channels
Windows uses the IPsec suite of protocols to provide a Virtual Private Network Connection (VPN)
between itself, acting as a VPN client, and a VPN gateway in addition to providing protected
communications for HTTPS and TLS.
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
9
6 Documentation
Microsoft offers a number of guidance documents along with a CC-specific supplemental document
describing the installation process for the TOE as well as guidance for subsequent use and administration
of the applicable security features.
The guidance documentation examined during the course of the evaluation and delivered with the TOE is
as follows:
 Microsoft Windows 8.1 and Microsoft Windows Phone 8.1 Common Criteria Supplemental
Admin Guidance, Version 1.0, May 7, 2015
The above document is considered to be part of the evaluated TOE. Any additional customer
documentation delivered with the TOE or made available through electronic downloads should not be
relied upon for using the TOE in its evaluated configuration.
The Security Target used is:
 Microsoft Windows 8.1 and Microsoft Windows Phone 8.1 Security Target, Version 1.0, August
21, 2015
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
10
7 Independent Testing
This section describes the testing efforts of the evaluation team. It is derived from information contained
in the following proprietary documents:
 Microsoft Windows Surface 3 Common Criteria Test Report and Procedures for Mobility Device
PP, Version 1.1, August 27, 2015
 Microsoft Windows Lumia 635 and Lumia 830 Common Criteria Test Report and Procedures for
Mobility Device PP, Version 1.0, July 17, 2015
A non-proprietary version of the tests performed and samples of the evidence that was generated is
summarized in the following document:
 Microsoft Windows Common Criteria Evaluation Microsoft Windows 8.1 and Microsoft
Windows Phone 8.1 Assurance Activities Report, Version 1.0, August 25, 2015
The purpose of the testing activity was to confirm the TOE behaves in accordance with the TOE security
functional requirements as specified in the ST for a product claiming conformance to MDFPP v1.1.
The evaluation team devised a Test Plan based on the Testing Assurance Activities specified in MDFPP.
The Test Plan described how each test activity was to be instantiated within the TOE test environment.
The evaluation team executed the tests specified in the Test Plan and documented the results in the team
test report listed above.
Independent testing took place at the CCTL location in Columbia, Maryland.
The evaluators received the TOE in the form that normal customers would receive it, installed and
configured the TOE in accordance with the provided guidance, and exercised the Team Test Plan on
equipment configured in the testing laboratory.
Given the complete set of test results from the test procedures exercised by the evaluators, the testing
requirements for MDFPP v1.1 were fulfilled.
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
11
8 Evaluated Configuration
The evaluated version of the TOE is:
TOE Software Identification: The following Windows Operating Systems (OS):
 Microsoft Windows 8.1 Pro Edition (64-bit version) on Microsoft Surface 3
 Microsoft Windows Phone 8.1 GDR2 on Microsoft Lumia 635 and Microsoft Lumia 830
The following security updates must be applied to the above Windows 8.1 products:
 All critical updates as of April 30, 2015
The following security updates must be applied to the above Windows Phone 8.1 products:
 All critical updates as of April 30, 2015
TOE Hardware Identification: The following hardware platforms and components are included in the
evaluation:
 Microsoft Surface 3, Windows 8.1 Pro, 64-bit, Intel Atom Z8700, Marvell 8897 Wi-Fi a/b/g/n
adapter, Bluetooth 4.0, Bluetooth LE, Intel TPM 2.0
 Microsoft Lumia 635, Windows Phone 8.1, Qualcomm Snapdragon 400, GSM, HSPA, LTE,
Qualcomm WCN3620 Wi-Fi b/g/n adapter, Qualcomm TPM 2.0
 Microsoft Lumia 830, Windows Phone 8.1, Qualcomm Snapdragon 400, GSM, HSPA, LTE,
Qualcomm WCN3620 Wi-Fi b/g/n adapter, Qualcomm TPM 2.0
The TOE must be deployed as described in section 4 of this document and be configured in accordance
with the Microsoft Windows 8.1 and Microsoft Windows Phone 8.1 Common Criteria Supplemental
Admin Guidance, Version 1.0, May 7, 2015.
Per Policy Letter #22, user installation of vendor-delivered bug fixes and security patches is encouraged
between completion of the evaluation and the Assurance Maintenance Date; with such updates properly
installed, the product is still considered by NIAP to be in its evaluated configuration.
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
12
9 Results of the Evaluation
The evaluation was conducted based upon the assurance activities specified in Protection Profile for
Mobility Device Fundamentals Version 1.1, in conjunction with version 3.1, revision 4 of the CC and the
CEM. A verdict for an assurance component is determined by the resulting verdicts assigned to the
corresponding evaluator action elements.
The validation team’s assessment of the evidence provided by the evaluation team is that it demonstrates
that the evaluation team performed the assurance activities in the claimed PPs, and correctly verified that
the product meets the claims in the ST.
The details of the evaluation are recorded in the Evaluation Technical Report (ETR), which is controlled
by the Leidos CCTL. The security assurance requirements are listed in the following table.
Table 3: TOE Security Assurance Requirements
Assurance Component ID Assurance Component Name
ADV_FSP.1 Basic functional specification
AGD_OPE.1 Operational user guidance
AGD_PRE.1 Preparative procedures
ALC_CMC.1 Labeling of the TOE
ALC_CMS.1 TOE CM coverage
ALC_TSU_EXT.1 Timely Security Updates
ATE_IND.1 Independent testing – conformance
AVA_VAN.1 Vulnerability survey
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
13
10 Validator Comments/Recommendations
The functionality evaluated is scoped exclusively to the security functional requirements specified in the
Security Target, and only the functionality implemented by the SFR’s within the Security Target was
evaluated. All other functionality provided by the Microsoft Surface 3 with Windows 8.1 Pro, Microsoft
Lumia 635 with Windows Phone 8.1, and Microsoft Lumia 830 with Windows Phone 8.1, to include
software that was not part of the evaluated configuration, needs to be assessed separately and no further
conclusions can be drawn about their effectiveness.
To be in the evaluated configuration, the Lumia devices must be enrolled in MDM; when not enrolled in
MDM, the devices do not support data at rest encryption, nor do they support configuration of a
maximum number of unsuccessful authentication attempts.
In order to remotely lock the Surface 3 device, remote administrators are required to set the timeout
period to the smallest possible value.
The applications that may be loaded and used in an evaluated configuration are limited to applications
from the Windows Apps Store. The MDFPP has requirements it places on TOE system services that
applications can leverage and this evaluation used only apps from the Windows App Store to comply with
those requirements. The ability or inability to “side-load” unapproved applications onto the devices,
bringing it out of the evaluated configuration, was not tested; likewise, the capabilities and limits of such
an application were not considered in this evaluation.
Microsoft is using Trusted Platform Modules (TPMs) for products under this evaluation. The
cryptography in TPMs is not currently CAVP-validated. NIAP recognizes and temporarily accepts this
limitation.
This product uses a key with strength 112 bits to protect all keys used for data encryption, thus limiting
the strength of data encryption to 112 bits.
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
14
11 Annexes
Not applicable.
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
15
12 Security Target
Name Description
ST Title Microsoft Windows 8.1 and Microsoft Windows Phone 8.1 Security Target
ST Version 1.0
Publication Date August 21, 2015
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
16
13 Abbreviations and Acronyms
AAA Authentication, Authorization and Accounting
AAR Assurance Activities Report
CAVP Cryptographic Algorithm Validation Program
CC Common Criteria
CCEVS Common Criteria Evaluation and Validation Scheme
CCTL CC Testing Laboratory
CEM Common Methodology for IT Security Evaluation
CLI Command Line Interface
EP Extended Package
ESP Encapsulating Security Payload
ETR Evaluation Technical Report
FIPS Federal Information Processing Standard
IKE Internet Key Exchange
IOS Inter-network Operating System
IPsec Internet Protocol security
IT Information Technology
LAN Local Area Network
NIAP National Information Assurance Partnership
NIM Network Interface Module
NIST National Institute of Standards and Technology
NSA National Security Agency
NTP Network Time Protocol
NVLAP National Voluntary Laboratory Assessment Program
OS Operating System
PCL Product Compliant List
PP Protection Profile
RADIUS Remote Authentication Dial In User Service
RFC Request For Comment
SA Security Association
SAR Security Assurance Requirement
SFP Small Form-factor Pluggable
SFR Security Functional Requirement
SNMP Simple Network Management Protocol
SSHv2 Secure Shell version 2
SSL Secure Sockets Layer
ST Security Target
TACACS+ Terminal Access Controller Access-Control System Plus
TLS Transport Layer Security
TOE Target of Evaluation
TSF TOE Security Functions
TSS TOE Summary Specification
USB Universal Serial Bus
VPN Virtual Private Network
VR Validation Report
WAN Wide Area Network
VALIDATION REPORT
Microsoft Windows 8.1 and Microsoft Windows Phone 8.1
17
14 Bibliography
The Validation Team used the following documents to produce this Validation Report:
[1] Common Criteria for Information Technology Security Evaluation Part 1: Introduction, Version
3.1, Revision 4, September 2012.
[2] Common Criteria for Information Technology Security Evaluation Part 2: Security Functional
Requirements, Version 3.1 Revision 4, September 2012.
[3] Common Criteria for Information Technology Security Evaluation Part 3: Security Assurance
Components, Version 3.1 Revision 4, September 2012.
[4] Common Methodology for Information Technology Security Evaluation, Evaluation
Methodology, Version 3.1, Revision 4, September 2012.
[5] Microsoft Windows 8.1 and Microsoft Windows Phone 8.1 Security Target, Version 1.0,
August 21, 2015
[6] Common Criteria Evaluation and Validation Scheme - Guidance to CCEVS Approved
Common Criteria Testing Laboratories, Version 2.0, 8 Sep 2008.
[7] Evaluation Technical Report for Microsoft Windows 8.1 and Microsoft Windows Phone 8.1,
Version 1.0, August 21, 2015
[8] Microsoft Windows 8.1 and Microsoft Windows Phone 8.1 Common Criteria Supplemental
Admin Guidance, Version 1.0, May 7, 2015