Safety & Security

There are a number of security and safety features new to Windows Vista, most of which are not available in any prior Microsoft Windows operating system release. more...

Home
ATV Parts
Apparel & Merchandise
Automotive Tools
Aviation Parts
Boat Parts
Car & Truck Parts
Car Audio, Video
Manuals & Literature
Motorcycle Parts
Other Vehicle Parts
Personal Watercraft Parts
Racing Parts
Services & Installation
Snowmobile Parts
Vintage Car & Truck Parts
AC & Heating
Accessories
Air Intake & Fuel Delivery
Brakes
Charging & Starting Systems
Cooling System
Decals, Emblems, Detailing
Engines & Components
Exhaust
Exterior
Filters
Gaskets
Gauges
Glass
Ignition Systems
Interior
Lighting & Lamps
Other Parts
Radio & Speaker Systems
Safety & Security
Salvage Parts Cars
Suspension & Steering
Transmission & Drivetrain
Wheels, Tires, & Hub Caps
Wholesale Lots

Beginning in early 2002 with Microsoft's announcement of their Trustworthy Computing initiative, a great deal of work has gone into making Windows Vista a more secure operating system than its predecessors. Internally, Microsoft adopted a "Security Development Lifecycle" with the underlying ethos of, "Secure by design, secure by default, secure in deployment". New code for Windows Vista was developed with the SDL methodology, and all existing code was reviewed and refactored to improve security.

Some specific areas where Windows Vista introduces new security and safety mechanisms include User Account Control, parental controls, Network Access Protection, a built-in anti-malware tool, and new digital content protection mechanisms.

But new, non critical, vulnerabilities have already been found, some of which are still not fixed, according to security websites Secunia and SecurityFocus.

User Account Control

User Account Control is a new infrastructure that requires user consent before allowing any action that requires administrative privileges. With this feature, all users, including users with administrative privileges, run in a standard user mode by default, since most applications do not require higher privileges. When some action is attempted that needs administrative privileges, such as installing new software or changing system settings, Windows will prompt the user whether to allow the action or not. If the user chooses to allow, the process initiating the action is elevated to a higher privilege context to continue. While standard users need to enter a username and password of an administrative account to get a process elevated (Over-the-shoulder Credentials), an administrator can choose to be prompted just for consent or ask for credentials.

UAC asks for credentials in a Secure Desktop mode, where the entire screen is faded out and temporarily disabled, to present only the elevation UI. This is to prevent spoofing of the UI or the mouse by the application requesting elevation. If the application requesting elevation does not have focus before the switch to Secure Desktop occurs, then its taskbar icon blinks, and when focussed, the elevation UI is presented (however, it is not possible to prevent a malicious application from silently obtaining the focus).

Since the Secure Desktop allows only highest privilege System applications to run, no user mode application can present its dialog boxes on that desktop, so any prompt for elevation consent can be safely assumed to be genuine. Additionally, this can also help protect against shatter attacks, which intercept Windows inter-process messages to run malicious code or spoof the user interface, by preventing unauthorized processes from sending messages to high privilege processes. Any process that wants to send a message to a high privilege process must get itself elevated to the higher privilege context, via UAC.

Read more at Wikipedia.org