Abstract: A request to resolve an IP address is received by a Domain Name Server (DNS). A record, such as an MX record, relating to the request is obtained that comprises a unique label (e.g. record=customer-com.mail.messaging.com) that is used in determining how to resolve the request. The unique label portion of the record (e.g. customer-com) is used to identify information relating to the request such as a version of software/service to use to handle the request, a region used to handle the request, and the like. The same record may be used to direct a request to a different version and/or different region. For example, without changing the record, a request at one time may access a first version/region and a request at a different time access a different version/region.

Abstract: Aspects of the subject matter described herein relate to authentication for a distributed secure content management system. In aspects, a request to access a resource available through the Internet is routed to a security component. The security component is one of a plurality of security components distributed throughout the Internet and responsible for authenticating entities associated with an enterprise. The security component determines an authentication protocol to use with the entity and then authenticates the entity. If the entity is authenticated, the entity is allowed to use a forward proxy.

Abstract: A request to resolve an IP address is received by a Domain Name Server (DNS). A record, such as an MX record, relating to the request is obtained that comprises a unique label (e.g. record=customer-com.mail.messaging.com) that is used in determining how to resolve the request. The unique label portion of the record (e.g. customer-com) is used to identify information relating to the request such as a version of software/service to use to handle the request, a region used to handle the request, and the like. The same record may be used to direct a request to a different version and/or different region. For example, without changing the record, a request at one time may access a first version/region and a request at a different time access a different version/region.

Abstract: Aspects of the subject matter described herein relate to authentication for a distributed secure content management system. In aspects, a request to access a resource available through the Internet is routed to a security component. The security component is one of a plurality of security components distributed throughout the Internet and responsible for authenticating entities associated with an enterprise. The security component determines an authentication protocol to use with the entity and then authenticates the entity. If the entity is authenticated, the entity is allowed to use a forward proxy.

Abstract: Secure content management is enabled as a cloud-based service through which security protection and policy enforcement may be implemented for both on-premise network users and roaming users. The global SCM service integrates the security functionalities—such as anti-virus, spyware and phishing protection, firewall, intrusion detection, centralized management, and the like—that are typically provided by enterprise network SCM appliance hardware or servers into a cloud-based service that users reach via Internet-based points-of-presence (“POPs”). The POPs are configured with forward proxy servers, and in some implementations, caching and network acceleration components, and coupled to hubs which provide configuration management and identity management services such as active directory services.