|
Internet Information Server |
|||||||||||||||||||||
START | AD | DNS | FRAMES | W2000 | ISDN | SERVICES | PPP | VLANS | LDAP TECH | TCP/IP | VPN | WSH | NETMAN | OSI | SWITCH | DDNS | NANO | HI TECH | |
||||||||||||||||||||||
Web links
William Mohawk P.O. Box 1612 Santa Monica, CA 90406 (310) 585 - 2634 |
Microsoft
Internet Information Server (IIS) is built into the Microsoft Windows NT
Server operating system. It was designed to deliver security for corporate
intranets and the Internet. Additionally, IIS provides implementation of
Secure Sockets Layer 3.0 (SSL) for secure communication and authentication
with X.509 certificates, RSA Public Key Cipher, and a broad array of
additional security features.
The security architecture of Windows NT Server is used across all system components, with authentication tied to controlled access to all system resources. IIS integrates into the Windows NT security model and operating system services such as the file system and directory. Because IIS uses the Windows NT Server user database, administrators do not need to create separate user accounts on every Web server, and intranet users need only to log on to their network once. IIS automatically uses the same file and group permissions as the existing file, print, and application servers. Some Web servers install their own security implementations on top of the operating system, creating additional overhead and potential security exposure due to lack of integration and synchronization. Windows NT Server is secure by design. Files and system objects can only be accessed with the proper permissions. User and group accounts are managed by a globally unique identification. When accounts are deleted, all access permissions and group memberships are deleted. So even if a new account is created using a previous user name, none of the permissions are inherited. Permissions to control access files and directories can be set graphically, because IIS uses the same Windows NT Server Access Control Lists (ACLs) as all other Windows services, such as file sharing or Microsoft SQL ServerTM permissions. Permissions for the Web server are not separate from other file services, so the same files can be securely accessed over other protocols, such as FTP, CIFS/SMB, or NFS without duplicating administration.Administrators do not need to maintain multiple sets of user databases, and all of the services for literally hundreds of intranet servers can be managed from a single graphical tool. IIS produces standard Web server access logs to analyze usage. Integration with Windows NT Server also means IIS can take advantage of system auditing for more secure monitoring of resource use. For example, failed attempts to access a secure file can be recorded in the Windows NT Event Log, and audited with the same tools used for managing existing servers.
|
Web Links
|