The only publication dedicated to OSS Volume 1, Issue 7 - November 2004 |
|
“Telecom General’s” Warning (cont'd) For example, large Internet players like AOL are already moving beyond basic user name-password security measures and offering multi-factor authentication processes such as RSA secure ID, where users must supply a password and a constantly changing secure token ID number. GSM-based mobile operators are also moving toward secure SIM-based authentication to utilize their existing secure infrastructure. In the “extended” network world, service providers will want to allow enterprise customers to roam onto networks they don't own, and yet maintain a direct link to insure things like single sign-on applications remain secure. For instance, when a user signs onto the network, the server sitting on the “home” provider's network can check to ensure that the device has the latest firewall settings and software patches before allowing the user to long onto the enterprise network. In such a case, the client software would communicate with an endpoint that validates the user's settings before launching the VPN. If the user isn't up-to-date, the system would prompt the user to update her software before permitting her to log on. Assuring Quality for Cash Once quality is monitored, service providers must insure that they deliver quality and usage information back to the enterprise, to show the customer they've been billed accurately and their SLAs are met. A related concept is to provide the customer with control over connection rules that determine which network to use based on the service in question or the quality required for that service. Keeping Control
© 2004, All information contained herein is the sole property of Pipeline Publishing, LLC. Pipeline Publishing LLC reserves all rights and privileges regarding the use of this information. Any unauthorized use, such as copying, modifying, or reprinting, will be prosecuted under the fullest extent under the governing law. |