Professional Documents
Culture Documents
ISA Server 2006 Standard Edition & Enterprise Edition Common Criteria Evaluation
ISA Server 2006 Standard Edition & Enterprise Edition Common Criteria Evaluation
Internet Security
and Acceleration
Server
Author:
Microsoft Corp.
Version:
1.6
Last Saved:
2008-11-12
File Name:
MS_ISA2006_ADD_1.6.docx
Abstract
This document is the Guidance Documentation Addendum of ISA Server 2006 Standard Edition
and Enterprise Edition.
Keywords
CC, ISA, Common Criteria, Firewall, Guidance Documentation Addendum
Page 2/44
Page 3/44
Table of Contents
Page
Page 4/44
7.3
Installing a remedy ................................................................................................... 40
7.4
Authentication of a Fix .............................................................................................. 41
8 REFERENCES AND GLOSSARY .................................................................................. 42
8.1
References............................................................................................................... 42
8.2
Acronyms ................................................................................................................. 43
8.3
Glossary ................................................................................................................... 43
Page 5/44
List of Tables
Page
List of Figures
Page
Page 6/44
1.1 Scope
This document extends the ISA Server 2006 manual [MSISA] and provides required
information for the ISA Server 2006 common criteria evaluation.
The evaluated Guidance Documentation ([MSISA] and this document) is valid for ISA
Server 2006 Standard Edition and ISA Server 2006 Enterprise Edition. Its software version is
for both evaluated configurations 5.0.5720.100.
ISA Server 2006 references both configurations ISA Server 2006 Standard Edition and ISA Server 2006
Enterprise Edition.
Page 7/44
Relevant chapters
SF3 - Audit
[MSISA] Monitoring > Monitoring: How To > Configure Logging > Configure
logging to an MSDE database
[MSISA] Monitoring > Monitoring: How To > Configure Logging > Filter the
log viewer data
[MSISA] Monitoring > Monitoring: How To > Configure Logging > S pecify
fields to log
Page 8/44
Relevant chapters
Overview
Manual
Warnings
Each chapter identifies and describes the warnings, the assumptions and the security
parameters related to that SF when necessary. The identification and description are
made in a complete and consistent way.
Examples for chapters that contain additional hints:
Important (
[MSISA] Firewall Policy > Firewall Policy: How To > Configure Authentication >
Configure authentication method for a Web listener
Caution (
[MSISA] Administration > Administration: How To > Back Up and Restore >
Import a configuration (Note: This is not a security function according the
Security Target but gives an example for a caution.)
Warning (
Microsoft Windows Server 2003, Standard Edition (English) Service Pack 1 (SP1)
including MS05-042 (KB899587), MS05-039 (KB899588), MS05-027 (KB896422), and
update KB907865. Also, ensure that no additional software products have been
installed on this computer.
150 MB of available hard disk space. This is exclusive of hard disk space you want to
use for caching.
One network adapter that is compatible with the computer's operating system, for
communication with the Internal network.
An additional network adapter for each network connected to the ISA Server computer.
One local hard disk partition that is formatted with the NTFS file system.
Please also check Section 3.5 Requirements for the Operational Environment.
Page 9/44
ISA Server Management. The console through which the administrator manages the
enterprise.
Advanced Logging. Note that the Advanced Logging component can only be installed
on a computer running ISA Server services.
To install the evaluated version, the administrator must install ISA Server and ISA Server
Management (file \ISAAutorun.exe). The following pictures show the step-by-step installation
process for ISA Server 2006 Standard Edition.
Startup screen
License Agreement
Installation options
Page 10/44
Service warning
After installation, apply the registry settings shown in Figure 1.1. These settings enforce 128 bit
encryption for Forms-based authentication. Without applying the registry keys a 56 bit SSL
connection for Forms-based authentication might be established (e.g. when a client is used
which does not support 128 bit encryption). This means that even when in the HTTPS listener
Page 11/44
128 bit encryption is enforced for the data transfer user credentials will be sent over a weak
encrypted connection.
Figure 1.1 Disable weak algorithms
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\DES 56/56]
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC2 40/128]
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 40/128]
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 56/128]
"Enabled"=dword:00000000
Microsoft Windows Server 2003, Standard Edition (English) Service Pack 1 (SP1)
including MS05-042 (KB899587), MS05-039 (KB899588), MS05-027 (KB896422), and
update KB907865. Also, ensure that no additional software products have been
installed on this computer.
150 MB of available hard disk space. This is exclusive of hard disk space you want to
use for caching.
One network adapter that is compatible with the computer's operating system, for
communication with the Internal network.
An additional network adapter for each network connected to the ISA Server computer.
One local hard disk partition that is formatted with the NTFS file system.
Page 12/44
Please also check Section 3.5 Requirements for the Operational Environment.
ISA Server Management. The console through which the administrator manages the
enterprise.
Configuration Storage server. The repository of the enterprise layout and the
configuration for each server in the enterprise. This repository is an instance of Active
Directory Application Mode (ADAM). Each ISA Server computer has a local copy of
its configuration that is a replica of the servers configuration, which is located on the
Configuration Storage server.
ISA Server services. This is the computer that runs the firewall. The computer running
ISA Server services is connected to a Configuration Storage server, which stores the
configuration information.
To install the evaluated version, the administrator must install ISA Server Management and the
Configuration Storage server (file \ISAAutorun.exe) on the same machine. The following
pictures show the step-by-step installation process for ISA Server 2006 Enterprise Edition.
Startup screen
License Agreement
Page 13/44
Installation options
Installation note
Page 14/44
Service warning
After installation, apply the registry settings shown in Figure 1.2. These settings enforce 128 bit
encryption for Forms-based authentication. Without applying the registry keys a 56 bit SSL
connection for Forms-based authentication might be established (e.g. when a client is used
which does not support 128 bit encryption). This means that even when in the HTTPS listener
128 bit encryption is enforced for the data transfer user credentials will be sent over a weak
encrypted connection.
Page 15/44
Page 16/44
2 Security Functions
This chapter identifies all the security functions available to the administrator. The security
functions are derived from the ISA Server 2006 security functions described in the ISA Server
2006 Security Target (ST).
For administration, ISA Server 2006 includes graphical taskpads and wizards. These simplify
navigation and configuration for common tasks. These features are embedded in the Microsoft
Management Console and do not belong to the TOE. They are provided by the environment.
The underlying operating system is the certified Windows Server 2003, Standard Edition
(English) SP1 including MS05-042 (KB899587), MS05-039 (KB899588), MS05-027
(KB896422), and update KB907865. (The same installation has been used for Windows
Server 2003 Common Criteria EAL 4+ evaluation; Validation Report Number CCEVS-VR-050131, [WINST] and [WINVR], and referenced as Windows Server 2003 in this document.)
Warnings
The administrator must ensure that ISA Server 2006 is installed and used with
Windows Server 2003. More details can be found in the Security Target of ISA Server
2006 Standard Edition/Enterprise Edition [ST].
The administrator has to observe the Security Bulletins, to ensure that all possible
countermeasures are used.
The administrator should only use programs that are required to administer and
operate the firewall. The administrator should not install additional software which may
compromise the security of the TOE or the underlying operating system.
Page 17/44
in the local user database or a remote authentication server using Remote Authentication DialIn User Service (RADIUS).
Important
When trying to connect to a Web site via HTTP (not HTTPS) that is published using ISA Server
2006, you receive an error message (see Figure 2.1), when all the following conditions are
true:
The Web listener has any one of the following authentication methods enabled:
o Basic authentication
o Radius authentication
o Forms-Based authentication
The Web listener is configured to listen for HTTP traffic.
The Require all users to authenticate check box is selected for the Web listener or the
Web publishing rules apply to a user set other than the default All users user set.
You connect to the published Web site by using HTTP instead of by using HTTPS.
Figure 2.1 Error messages
If the ISA Server Web listener has Basic authentication enabled, you receive the following error
message:
Error Code: 403 Forbidden.
The page must be viewed over a secure channel (Secure Sockets Layer (SSL)). Contact the server
administrator. (12211)
If the ISA Server Web listener has RADIUS authentication or Microsoft Outlook Web Access
Forms-Based authentication (Cookie-auth) enabled, you receive the following error message:
Error Code: 500 Internal Server Error.
An internal error occurred. (1359)
When you use HTTP-to-HTTP bridging, ISA Server 2006 does not enable traffic on the
external HTTP port if the Web listener is configured to request one or more of the following
kinds of credentials:
Basic authentication
Radius authentication
Forms-based authentication
This behavior occurs because these kinds of credentials should be encrypted. These
credentials should not be sent in plaintext over HTTP.
ISA Server 2006 prevents you from entering credentials in plaintext. When you try to do this,
you receive an error message2.
For ISA Server 2004 versions that are earlier than ISA Server 2004 SP2, you are prompted to enter credentials in
plaintext. This behavior may cause the credentials to be transmitted over the network in plaintext if you have not
Page 18/44
Warnings
MS06-018 requires blocking following ports to the local host at the firewall:
- All unsolicited inbound traffic on ports greater than 1024
- Any other specifically configured RPC port
These ports can be used to initiate a connection with the Microsoft Distributed
Transaction Coordinator. Blocking them at the firewall (to local host) will protect the
operating system to exploit this vulnerability. Also, make sure that you block any other
specifically configured RPC port on the local host. While RPC can use UDP ports 135,
137, 138, 445, and TCP ports 135, 139, 445, and 593, the Microsoft Distributed
Transaction Coordinator service is not vulnerable over those ports.
implemented some other form of network security, such as an external Secure Sockets Layer (SSL) accelerator or
an encrypted tunnel. ISA Server 2006 does not provide these forms of security.
Page 19/44
Add the DWORD Value: DisableIPSourceRouting. Set the value to 2. This value
disables IP source routing processing. By default, this key does not exist.
Warning
It should be assured that there is always enough free disk space. Choosing the right
resource and the right parameters for logging is mandatory. Creating logs that are too
large or creating too many files can lead to problems. Nevertheless, it is possible to
create an alert, which will move or delete old or unneeded log files.
Page 20/44
Page 21/44
3 Operating Environment
The security environment of the evaluated configurations of ISA Server 2006 is described in
the ISA Server 2006 Standard Edition/Enterprise Edition Security Target [ST] and identifies the
threats to be countered by ISA Server 2006, the organizational security policies, and the usage
assumptions as they relate to ISA Server 2006. The administrator should ensure that the
environment meets the organizational policies and assumptions. They are restated here from
the Security Target.
To use the TOE in the evaluated configuration, the underlying environment must be the
certified Windows Server 2003 operating system (see chapter 3.5).
3.1 Assumptions
Table 3.1 lists the TOE Secure Usage Assumptions for the IT environment and intended
usage.
Table 3.1 Assumptions for the IT environment and intended usage
#
Assumption name
Description
A.DIRECT
A.GENPUR
3
4
A.NOEVIL
A.ENV
A.PHYSEC
6
7
A.SECINST
A.SINGEN
A.WEBI&A
A.SSL
Page 22/44
Policy name
Description
P.AUDACC
Persons must be accountable for the actions that they conduct. Therefore,
audit records must contain sufficient information to prevent an attacker to
escape detection.
Functional requirement
Title
Identification & Authentication
FIA_ATD.1
FIA_UID.2
FIA_UAU.2
FCS_COP.1
Cryptographic operation
Information Flow Control
FMT_MSA.1 (1)
FMT_MSA.1 (2)
FMT_MSA.1 (3)
FPT_STM.1
FAU_SAR.2
10
FAU_STG.1
11
FMT_SMF.1
12
FMT_SMR.1
Security roles
Page 23/44
5
6
Objective Name
Objective Description
OE.DIRECT
OE.GENPUR
OE.NOEVIL
OE.ENV
OE.PHYSEC
OE.SECINST
OE.SINGEN
OE.WEBI&A
OE.SSL
The required user identities (used for user authentication) and required SSL
certificates for server authentication (HTTPS encryption) should be stored
using a confidential path. That means that created certificates and user
passwords should not be available to unauthorized persons (OE.DIRECT
ensures that unauthorized persons cannot get these information by
accessing the TOE).
Information should not flow among the internal and external networks unless
it passes through the TOE. Thereby the TOE administrator has to guarantee
an adequate integration of the TOE into the environment.
The Radius Server should verify provided user credentials and return if a
valid account exists or not.
Data (user credentials and return values) between TOE and the Radius
Server should be transferred in the TOE secured environment, which means
that the Radius Server should be placed on the internal network for Web
Identification & Authentication.
All web publishing rules which support Form-based authentication should be
configured by the administrator so that strong encryption for SSL is enforced
(at least 128bit encryption).
Page 24/44
describing how to complete a specific task to "bug" articles documenting known issues with
Microsoft products.
When you scan your computer for available updates, through the Windows Update Web site,
the Windows Update Web site displays a number along with the title of the update, for
example, "Update for Windows Media Player 9 Series (KB837272)." This KB number is
included in the security bulletin to help identify the corresponding KB article in the Microsoft
Knowledge Base.
Because the computer on which ISA Server 2006 is running is often the primary interface to
the External network, we recommend to secure this computer. The Security Best Practices
[MSISAHARD]3 document ISA Server 2004 Security Hardening Guide, available on the ISA
Server Web site, containing details how to secure the ISA Server 2004 Enterprise Edition
computer, is applicable to ISA Server 2006 (SE and EE), and is updated periodically with new
information.
Additional information can be found on
http://www.microsoft.com/technet/isa/2006/security_guide.mspx
Warning
The administrator should check http://www.microsoft.com/security/ regularly for the latest
Windows Server 2003 hotfixes.
Page 25/44
4 Security-Relevant Events
This subsection describes all types of security-relevant events and what administrator action (if
any) to take to maintain security. Security-relevant events that may occur during operation of
ISA Server 2006 must be adequately defined to allow administrator intervention to maintain
secure operation. Security-relevant events are defined as events that signify a security related
change in the system or environment. These changes can be grouped as routine or abnormal.
The routine events are already addressed in subsection Security Functions.
Table 4.1 Security-relevant events
Security function
Web Identification and
Authentication
Security-relevant event
Configure Forms-based
authentication.
The user has a missing permission to
access the Internet.
A user is leaving the company, so his
or her rights have to be withdrawn.
Relevant chapters
see Chapter 6.1
[MSISA] Firewall Policy > Firewall
Policy: How To > Configure Web
Publishing Rules > Configure a
listener for a Web publishing rule
[MSISA] Monitoring >
Monitoring: How To > Configure
Logging > To configure logging to
an MSDE database
Information Flow
Control
Audit
Page 26/44
5 TOE Integrity
This chapter describes how the administrator can verify that the evaluated version of the TOE
is used.
The corresponding hash files are available from the Microsoft corporate Web site, as well as a
batch file that runs the tool and a Readme file that explains the usage for users that do not
have access to this document. The hash file contains SHA-1 values for each of the relevant
files that must be verified and is downloadable using a secured channel from the ISA Server
common criteria Web page:
https://go.microsoft.com/fwlink/?linkid=49507
The FCIV is a command-prompt utility that computes and verifies cryptographic hash values of
files (MD5 and SHA-1 cryptographic hash values are possible). The tool is run by the supplied
batch file. To run the batch file the user opens a Command Prompt window and changes to the
folder into which the validation files were downloaded. The user then types the following (the
exact file name depends what CD-ROM or file the user wants to verify):
integritycheck.cmd X:
Where x: is the local CD-ROM drive that contains the ISA Server 2006 CD-ROM.
Figure 5.1 shows a successful verification of the TOE. Figure 5.2 shows an error message
because of the missing FCIV tool.
Important
The hash value of the FCIV tool is published on the ISA Server common criteria web page and
should be verified by the customer using a 3rd party tool of his choice. The complete process is
described on the web site and in the guidance addendum (the following is a shortened quote
from the ISA Server common criteria web page which also states the correct hash values
required for the verification process):
Please perform the following steps in order to ensure the integrity of your downloads from this
website:
1.
Download the FCIV tool from http://support.microsoft.com/default.aspx?scid=kb;enus;841290. The sha-1 value of this download is
Page 27/44
99fb35d97a5ee0df703f0cdd02f2d787d6741f65 (hex)
and shall be verified before executing the download. This can be done using any
tool capable of calculating SHA-1 values.
2.
Download the "Integrity Check ISA 2006" and "CC Guidance Documentation
Addendum" to the directory where FCIV has been extracted.
3.
Open a command prompt and change to directory where FCIV has been extracted.
4.
5.
6.
Follow the CC Guidance Addendum for further Installation and Configuration of the
TOE.
Figure 5.1 Example of Integrity check I (successful)
Page 28/44
Page 29/44
Page 30/44
Page 31/44
6 Annotations
6.1 Authentication methods
This chapter describes how ISA Server manages authentication. It provides information about
authentication and delegation methods supported by the TOE, and how the authentication
process is handled.
Page 32/44
Delegation of authentication to Web servers that are behind the TOE, such as servers
running SharePoint Portal Server 2003.
Note
The first two components are configured on the Web listener that receives client requests.
The third is configured on the publishing rule. This means that you can use the same listener
for different rules, and have different types of delegation.
Step 1, receipt of client credentials: The client sends a request to connect to the corporate
Outlook Web Access server in the Internal network. The client provides the credentials in an
HTML form (Frontend authentication).
Steps 2 and 3, sending credentials: The TOE sends the credentials to the authentication
provider, such as a domain controller for Integrated Windows authentication, or a RADIUS
server, and receives acknowledgment from the authentication provider that the user is
authenticated (Gateway authentication).
Step 4, authentication delegation: The TOE forwards the client's request to the Outlook Web
Access server, and authenticates itself to the Outlook Web Access server using the client's
credentials. The Outlook Web Access server will revalidate those credentials, typically using
the same authentication provider (Backend authentication).
Note
The Web server must be configured to use the authentication scheme that matches the
delegation method used by the TOE.
Step 5, server response: The Outlook Web Access server sends a response to the client,
which is intercepted by the TOE.
Page 33/44
Step 6, forwarding the response: The TOE forwards the response to the client.
Note
If you do not limit access to authenticated users, as in the case when a rule allowing access
is applied to all users, the TOE will not validate the user's credentials. The TOE will use the
user's credentials to authenticate to the Web server according to the configured delegation
method.
We recommend that you apply each publishing rule to all authenticated users or a specific
user set, rather than selecting Require all users to authenticate on the Web listener, which
requires any user connecting through the listener to authenticate.
No authentication
Forms-based authentication
6.1.3.1 No Authentication
You can select to require no authentication. If you do so, you will not be able to configure a
delegation method on rules that use this Web listener.
Password form. The user enters a user name and password on the form. This is the type of
credentials needed for Integrated and RADIUS credential validation.
Notes
Page 34/44
You should ensure that your Web application is designed to resist session riding attacks
(also known as cross-site-posting, cross-site-request-forgery, or luring attacks) before
publishing it using the TOE. This is particularly important for Web servers published through
the TOE, because clients must use the same trust level for all of the Web sites they access
through the publishing ISA Server firewall.
6.1.4.2 Integrated
The TOE checks if the user is a member of the local user database.
Page 35/44
Page 36/44
An event triggers the Firewall service to shut down. When you configure alert definitions,
you decide which events will cause the Firewall service to shut down. Essentially, you
configure when ISA Server enters lockdown mode.
The Firewall service is manually shut down. If you become aware of malicious attacks, you
can shut down the Firewall service, while configuring the ISA Server computer and the
network to handle the attacks.
Page 37/44
Allow remote management of the firewall using MMC (RPC through port 3847).
Outgoing traffic from the Local Host network to all networks is allowed. If an outgoing
connection is established, that connection can be used to respond to incoming traffic. For
example, a DNS query can receive a DNS response, on the same connection.
No incoming traffic is allowed, unless a system policy rule (listed previously) that
specifically allows the traffic is enabled. The one exception is DHCP traffic, which is
allowed by default system policy rules. The UDP Send protocol on port 68 is allowed from
all networks to the Local Host network. The corresponding UDP Receive protocol on port
67 is allowed.
VPN remote access clients cannot access ISA Server. Similarly, access is denied to
remote site networks in site-to-site VPN scenarios.
Any changes to the network configuration while in lockdown mode are applied only after
the Firewall service restarts and ISA Server exits lockdown mode. For example, if you
physically move a network segment and reconfigure ISA Server to match the physical
changes, the new topology is in effect only after ISA Server exits lockdown mode.
For ISA Server Enterprise Edition, if the Configuration Storage server is installed on the
computer running ISA Server services, a system policy rule, named Allow access from trusted
servers to the local Configuration Storage server, is enabled. This system policy rule allows
the use of Microsoft CIFS (TCP), Microsoft CIFS (UDP), and MS Firewall Storage protocols
from all array members to the Local Host. This rule is applied even in lockdown mode. Traffic
using those protocols is allowed, even in lockdown mode.
Page 38/44
Affected product information (product name, product version, service packs for the
product, security patches for the product, vulnerability information)
Data submitted via this page is encrypted using the Secure Sockets Layer protocol.
2. Alternatively, an email address, secure@microsoft.com can also be used. Mail to this
address can be encrypted using PGP5.
3. The customer can contact Microsoft Services for additional
(http://www.microsoft.com/services/microsoftservices/default.mspx ).
support
Regardless of the method used to initially contact the MSRC or Microsoft Services,
subsequent communications typically take place via email, using the secure@microsoft.com
email address. When requested, MSRC can also conduct these communications via telephone
or other methods.
Page 39/44
7.2 How to get informed about Security Flaws and Flaw Remediation
A security update that is issued by the MSRC is always accompanied with a bulletin. The
bulletin contains the information that Microsoft makes available for the customers so that they
can take a decision whether to install the fix and on what systems. Every bulletin comes with a
rating to reflect its criticality (four levels). A KB is also provided but it is mostly a pointer to the
bulletin article.
The public page with Microsoft bulletins is located at
http://www.microsoft.com/security/bulletins/default.mspx
The original finder of the problem is kept in the picture throughout the process, if he chooses.
MSRC manages the communication with the reporter throughout the process.
Security updates typically can be installed on the current service pack and the previous one.
However, this is only a general rule. If the previous service pack is more than two years old,
the patch may be limited to only the current service pack. Conversely, if several service packs
have been released in short order, the patch may install on additional ones. The security patch
will be included automatically in the next service pack. Service packs, and patches, are
generally available for the previously released service pack. The security bulletin will always
provide specific information on the service pack requirements for the patch.
All
security
bulletins
for
Microsoft
products
are
available
at
http://www.microsoft.com/technet/security/current.aspx , and newly released bulletins are
highlighted on http://www.microsoft.com/security , http://www.microsoft.com/technet/security ,
and http://www.microsoft.com/isaserver Web sites.
In addition, Microsoft offers a free service through which customers can receive a technical or
non-technical bulletin synopsis by email. Customers can sign up for mailer at
https://www.microsoft.com/technet/security/bulletin/notify.mspx. Microsoft digitally signs the
technical
synopsis,
and
the
PGP
key
located
at
http://www.microsoft.com/technet/security/MSRC.asc can be used to validate the signature.
Microsoft security bulletins always discuss the risk the vulnerability poses, the software it
affects, and the steps customers can take to eliminate it including, in the case of patches,
specific locations for obtaining them. In addition, security bulletins also frequently include a
public thank-you to the Finder, subject to the qualification criteria discussed at
http://www.microsoft.comtechnet/security/bulletin/policy.mspx .
Microsoft strongly encourages customers to sign up for the security bulletins.
So the steps to be always informed of security flaws and how to install them are:
1. Signing up for security bulletins (registering for receiving bulletins by email)
2. Checking for security bulletins (if not registered)
3. Deciding, whether to download and install a remedy
4. Downloading the fix, authentication of the fix
5. Installing the fix/remedy (follow bulletin description, see above)
Page 40/44
Page 41/44
Page 42/44
8.1 References
General Common Criteria Documents
[CC]
ISA Server 2006 Administrator Guidance and Publicly Available Evaluation Developer Documents
[MSISA]
Microsoft Internet Security and Acceleration Server 2006 Help, Microsoft Corp.,
Version 2006 Standard Edition / Enterprise Edition
This help file is installed during ISA Server 2006 setup (isa.chm, stored on CDROM).
[MSISAHARD]
Security Hardening Guide - Microsoft Internet Security and Acceleration Server 2004,
Microsoft Corp., Version 2006, downloadable from
http://go.microsoft.com/fwlink/?LinkID=24507
[ST]
ISA Server 2006 SE/EE Common Criteria Evaluation - Security Target, Version 1.1,
2007-06-05, Microsoft Corp.
[WINST]
[WINVR]
Page 43/44
8.2 Acronyms
CC
Common Criteria
EAL
FCIV
PP
Protection Profile
SF
Security Function
SFP
SSL
ST
Security Target
TOE
Target of Evaluation
8.3 Glossary
application filters
authentication
Basic authentication
feature pack
identification
ISA Server
Page 44/44
Microsoft
Management Console
NTLM
A packet filter log file contains records of packets that were dropped or
allowed.
port number
publishing rules
server publishing
service pack
Web publishing