A client demands at least 99.99% uptime from a service provider's hosted security services. Which of the following documents includes the information…

A Service Level Agreement (SLA) is a contract between a service provider and a

customer that defines the level of service expected from the provider. SLAs are output-

based in that their purpose is specifically to define what the customer will receive. They

typically include metrics for service availability (uptime), performance,

and responsibilities, along with remedies or penalties if the agreed-upon levels are not

met. The client's demand for "at least 99.99% uptime" is a classic example of a service

level objective that would be documented in an SLA.

· A. MOA (Memorandum of Agreement): An MOA typically outlines a cooperative

agreement or partnership where parties agree to a common line of action, not specific,

measurable service guarantees like uptime. It's less formal than an SLA.

· B. SOW (Statement of Work): A SOW details the specific tasks, deliverables,

timelines, and costs for a project. While it might reference an SLA, it doesn't

primarily define ongoing service levels like uptime guarantees.

· C. MOU (Memorandum of Understanding): An MOU is a document that describes a

bilateral or multilateral agreement between parties. It expresses a convergence of will

between the parties, indicating an intended common line of action, but is often less formal

and less binding than an SLA regarding service metrics.

1. NIST Special Publication 800-35, "Guide to Information Technology

Security Services":

o Section 5.2 "Service Level Agreements (SLAs)" discusses that SLAs define the terms

of service, including availability and performance metrics. (While this document doesn't

explicitly define SLA in the context of uptime guarantees with percentages, its

discussion on SLAs setting terms for service delivery is relevant).

o Note: A more direct definition linking SLA to uptime percentages is commonly

found in IT service management frameworks which are often reflected in vendor

documentation and academic materials.

2. NIST Special Publication 800-145, "The NIST Definition of Cloud Computing":

o While not directly defining SLA, it discusses service agreements in the context of

cloud service characteristics, where uptime is a critical component of availability,

typically governed by an SLA. (Page 2, Section "Essential Characteristics").

3. University of Washington, "Service Level Agreements (SLAs)":

o This university IT page defines an SLA as: "A Service Level Agreement (SLA) is a

contract between an IT service provider and a customer that specifies, in measurable

terms, what services the IT service provider will furnish." It often includes "Availability

(e.g. 99.9% uptime)."

o URL: https://itconnect.uw.edu/service-management/service-level-agreements-slas/

(Accessed May 30, 2025)

4. IETF RFC 5235, "SLA Parameters":

o This RFC, while specific to SIPPING, discusses various parameters that can be part

of an SLA, including availability metrics. Section 2 states, "A Service Level Agreement

(SLA) is a contract that exists between a customer and a service provider."

o URL: https://datatracker.ietf.org/doc/html/rfc5235 (Section 2, Paragraph 1)

5. Microsoft Azure, "Service Level Agreements summary":

o This vendor documentation provides numerous examples of SLAs that specify

uptime guarantees (e.g., "We guarantee at least 99.9% availability..."). This

demonstrates the practical application of SLAs for uptime commitments.

o URL: https://azure.microsoft.com/en-us/support/legal/sla/summary/ (Accessed May

30, 2025)