What to look for in a service-level agreement

15.03.2006
Many IT administrators are not comfortable handing over control of the most critical security components of their infrastructure. But in recent years, security outsourcing has become a popular and viable means of lowering the cost of perimeter security management. More and more companies are outsourcing parts of their security infrastructure, including firewalls, intrusion detection systems and VPNs, to managed security service providers (MSSPs).

Anyone thinking about outsourcing such a mission-critical aspect of their network should understand in detail the potential implications to their IT security infrastructure as well to as their company. One of the biggest differences among providers of security services is the service level agreement (SLA). In this five-part series of articles, we will dive deep into the various aspects of the SLA and attempt to explain in details what the SLA should contain and why each of the items is necessary. In general, a MSSP SLA should cover the following areas: Service Summary or Description The service summary section usually appears in the introductory section of the SLA. It should always state the name of the provider and the name of the customer.

This summary will enumerate the obligations you, the customer, have in order to satisfy the SLA. For example, you may be asked to provide up-to-date contacts, network topologies, and customer escalation paths. This section will usually list the support level (e.g., Gold or Platinum) you have purchased. The support level determines how fast the service provider will respond to your service requests, how many service requests you're allowed per week or month, how often you will be notified during emergencies, and most importantly, what your general service availability guarantee is.

Hardware

Service providers host security services in a variety of ways. Some will install dedicated hardware at your site. Some will provide you with dedicated hardware, but it sits in the provider's own NOC. And others will provide the security service through virtual domains that share, with other customers, the same physical hardware located (again) at the service provider's site.

Regardless of the method used, the service provider should state clearly in the SLA how the service is to be provided. Once you're sure of the hardware in use, you will be able to ask intelligent questions about hardware specification, performance, throughput, size, upgrades, and so forth. Software Most service providers use products from name-brand companies such as Check Point, ISS, Cisco, and others. Other service providers will use open source software such as Snort for IDS.