Windows Vista provides a range of enhancements to the Windows security model. The Windows security model includes many technologies, features, and tools.
This high-level overview of the new security features in Windows Vista is a good place to start learning about Windows Vista Security:
User Account Control
Under User Account Control in Windows Vista, by default, all interactive processes run as standard user by default, even if they are launched by a member of the Administrators group. Developers should understand how UAC works and how it can impact their applications.
Internet Explorer Protected Mode
On Windows Vista, Microsoft Internet Explorer® 7 (IE7) runs in what is referred to as Protected Mode, which helps protect users from attack by running with greatly restricted privileges.
Protected Mode in IE relies on three security features introduced in Windows Vista: User Account Control, Mandatory Integrity Control (MIC), and User Interface Privilege Isolation (UIPI).
UAC is discussed in the preceding section.
MIC assigns integrity levels to users and securable objects, allowing an additional security distinction beyond privilege level.
UIPI comes into effect for a user who is a member of the Administrators group that may be running applications with least privilege (sometimes referred to as a process with a filtered token), and also for processes running with full administrative privileges on the same desktop. UIPI prevents lower privilege processes from accessing higher privilege processes.
Cryptography Next Generation API
Cryptographic Next Generation (CNG) provides a set of APIs that can be used to perform basic cryptographic operations, cryptographic key storage and retrieval operations, and configuration of cryptographic providers. It also enables custom cryptography algorithms to be plugged into CNG via a simple extensibility mechanism. It is the long-term replacement for the CryptoAPI and is supported in Windows Vista and later releases of the Windows operating system.
Resources: |
|---|
Cryptography API: Next Generation (CNG) Any application can use Transactional NTFS (TxF) to preserve the integrity of data on disks caused by unexpected error conditions, isolate changes from others while the changes are being made, and help resolve concurrent file-system user scenarios. |
Parental Controls for Windows Vista
Parental Controls is a consumer-targeted feature that provides functionality to monitor and limit exposure of selected computer users to online dangers and inappropriate content. The Parental Controls API provides access to policy and restrictions settings, and logging functionality.
Windows Filtering Platform API
The Windows Filtering Platform API enables developers to write code that interacts with the filtering that takes place at several layers in the networking stack and throughout the operating system. It also integrates with and provides support for firewall features—such as authenticated communication and dynamic firewall configuration—based upon applications' use of sockets API (an application-based policy).
Network Address Protection API
The Network Address Protection platform provides an integrated way of detecting the state of a network client attempting to connect to a network and restricting the access of that network client until the policy requirements for connecting to the network have been met. It is an extensible platform, providing an infrastructure and an API set for adding components that verify and amend a computer's health and that enforce existing policy systems.
Certificate Enrollment API
The new Certificate Enrollment API enables developers to create client applications that can be used to request and install certificates. This new COM API replaces the ones previously provided in Xenroll.dll, which has been deprecated and is no longer included in Windows Vista.
BitLocker Drive Encryption Provider
Windows Vista and Windows Server 2008 offer a provider interface in Windows Mgmt Instrumentation (WMI) for managing and configuring BitLocker™ Drive Encryption (BDE). It can be used by developers writing scripts, user interface components, or other administrative tools for BitLocker Drive Encryption.
Trusted Platform Module Provider
The Windows Vista Trusted Platform Module (TPM) Services architecture allows a rich, competitive environment to grow on top of TPM 1.2 technologies by providing robust infrastructure for accessing hardware-based security.
Winlogon Re-architecture and Credential Providers
Previous versions of Windows allowed developers to add a custom authentication DLL (called a Graphical Identification and Authentication DLL, or GINA) that would interface with authorization hardware. Fingerprint scanners, authentication key cards, and other authorization hardware that required a custom logon could use GINA DLLs to work with Windows.
The logon architecture for Windows Vista has changed significantly. For reliability reasons, plug-ins have been moved out of the Winlogon process space as much as possible (in the past, a poorly coded GINA DLL, for example, could crash the machine this way). In addition, the logon experience has been standardized.
Credential providers now fill the GINA roll on Windows Vista. Credential providers are designed to work with the new logon architecture and to work with multi-factor authentication (for instance, a smart card and a fingerprint scan).
GINA applications need to be re-authored to use Credential Provider APIs.