About MSPAlliance.org
#MSPAlliance.org brings MSPAlliance standards and public reference material into a clear, searchable format for cloud and managed service providers, their customers, and the professionals who support them.
MSPAlliance is a vendor-neutral global industry association and certification body for cloud and managed service providers. Its work advances integrity, professional standards, education, compliance, and trusted service delivery across the managed services profession.
The first complete reference presented here is the Unified Certification Standard, MSPAlliance's compliance framework purpose-built for cloud and managed service providers.
Visit MSPAlliance.comUnified Certification Standard for Cloud and Managed Service Providers® Version 4 (UCS)
Domains, Objectives and Requirements
This web edition reproduces the complete substantive text of the official 23-page UCS Version 4 framework and restructures it for navigation and search.
Overview
#The following UCS (Unified Certification Standard) Domains, Objectives and underlying Requirements will be used by the independent auditor to perform the necessary verification procedures to issue a report on the MSP/Cloud organization seeking certification. In addition to being used by the independent auditor, these requirements can be used by the MSP to anticipate specific documentation and verification requirements that will likely arise during the examination process. In the context of the UCS requirement text an organization is the Company seeking certification. The organization is referred to as Organization Seeking Certification or (OSC)
This version of the UCS became effective on July 1, 2026.
UCS Domains
#The UCS is organized into five Domains: Expertise, Trust, Security, Resilience, and Transparency. Together, these Domains group ten Objectives into a unified framework for evaluating how an MSP or cloud service provider governs its operations, protects organizational and customer information and identities, sustains service delivery, demonstrates accountability, and communicates material practices and performance. Each Domain contains defined Objectives and Requirements that the Organization must satisfy to obtain certification. Certification under the UCS demonstrates that the Organization has implemented and can evidence the operational, security, resilience, and transparency practices established by the standard.
Service Providers using an MSP
#While originally designed for MSPs and Cloud service providers, the UCS can also be extended to the Customers of a certified Organization in a shared responsibility matrix. This matrix ensures that the majority of services provided by the customer rely heavily on either an MSP, MSSP, or Cloud service provider to manage their IT infrastructure. By leveraging a suite of SaaS or Cloud-hosted tools, these service providers offer comprehensive solutions that cater to the specific needs of their clients. The UCS framework helps these certified organizations maintain high standards in service delivery, trust, and reliability, thereby creating a harmonious relationship between the service providers and their customers. This shared responsibility approach allows customers to benefit from cutting-edge technology and expert management without the burden of maintaining the infrastructure themselves. As a result, customers can focus on their core business activities while ensuring that their IT systems are robust, secure, and resilient. The UCS certification demonstrates the organization's commitment to excellence and adherence to rigorous industry standards. This ensures that both the service providers and their customers are aligned in their goals and expectations, fostering a collaborative environment that promotes innovation and continuous improvement. The UCS Domains of Expertise, Trust, Security, Resilience, and Transparency collectively contribute to this dynamic partnership, ultimately driving growth and success for all parties involved.
The five UCS domains
UCS domain EXP
Expertise
#The Expertise domain evaluates the OSC’s ability to define, manage, and sustain the services within its scope. It addresses strategic planning, software and configuration management, controlled changes, patching, centralized operations, operational review, recovery testing, contractual foundations, financial sustainability, and customer and employee retention. An OSC demonstrating proficiency in this domain understands its customers’ business and technical requirements, maintains the operational information needed to manage services consistently, and aligns resources and controls with the services it has committed to deliver. Expertise begins with disciplined planning and service definition. Strategic plans and priorities are established and communicated to management, so the OSC can align resources, control scope, and manage sustainable service delivery. Software-related legal and financial risks are addressed through defined management processes and an inventory of in-scope SaaS vendors. Before managed or monitored objects are placed under service, relevant configuration information is documented according to the applicable service level. Customer configuration changes are evaluated, approved, implemented, and recorded through controlled processes that preserve an accurate current-state record. Operational capability is further demonstrated through standardized patch and change management, centralized monitoring, and periodic review of tickets, operational events, and access rights. Recovery testing is conducted and results are retained to confirm that backup data can be restored when needed. Signed customer agreements define the service relationship, while financial reporting and retention records provide evidence that the OSC can sustain operations, maintain service continuity, and support its contractual commitments. Together, these controls demonstrate that the OSC has the governance, technical processes, operational oversight, and business foundations necessary to deliver the services within its certified scope consistently.
Requirements in this domain
| ID | Title | Description |
|---|---|---|
| 01.02 | Strategic Planning | Strategic plans and priorities have been developed and communicated to the management of the company. |
| 01.04 | Software Management | Process for managing and determining legal and financial risk of software audits or third-party intellectual property claims. Inventory of in scope SaaS vendors is maintained. |
| 04.01 | Configuration Documentation | Configuration data for objects managed or monitored is documented based on level of service before management of the object. |
| 04.04 | Customer Change Tracking | Modifications to Customer object configurations are documented to ensure changes are evaluated and approved by the Customer before implementation. Configuration data is updated following implementation to reflect the current Customer configuration. |
| 04.06 | Patch Management | Vendor-supplied software and hardware patches are applied to managed objects and environments following standardized procedures. Non-critical patches are evaluated for issues before release and applied during planned or accepted maintenance windows. Critical patches are applied as soon as possible. |
| 04.07 | SaaS Special Requirement: Application Development Procedures | Application Changes to information systems follow a formal process that requires the requesting, logging, approval, testing, and acceptance of changes before being implemented into production. |
| 05.01 | Centralized Operations Center | MSOC/NOC/SOC is used to provide effective and secure monitoring and management of Organization and Customer managed environments. |
| 05.05 | Operations Monitoring | Organization management performs a periodic internal review of tickets and operational events. |
| 06.07 | Continuous Review of Access Rights | Access to information systems, as well as the underlying customer systems and data, is continually reviewed by the Organization’s upper management to ensure that resource access is appropriately restricted to authorized personnel. |
| 07.03 | Data Recovery Testing | Backup data restoration and recovery testing procedures are conducted periodically, with the results of tests being logged and monitored by the Organization. |
| 09.01 | Signed Contracts and Agreements | Signed Master Service Level Agreements (MSA) are in place between the Organization and Customers. |
| 10.01 | Operational Sustainability | Financial reports demonstrate profitability of a minimum of 6 of the previous 12 months, or sufficient access to funds necessary to keep the Organization operational for a 12-month period of time. |
| 10.06 | Customer and Employee Retention Tracking | The Organization maintains records to track the retention of customers (both voluntary and involuntary) and employees (both voluntary and involuntary) to ensure business continuity. |
UCS domain TRU
Trust
#The Trust domain evaluates how the OSC demonstrates reliability, accountability, and continuity in its relationships with customers. It addresses internal audit, service transition planning, capacity management, problem logging and resolution, secure remote access, environmental and colocation safeguards, customer reporting, sustainable service margins, customer commitments, and insurance coverage. Together, these practices provide customers with evidence that services are monitored, issues are addressed, responsibilities are documented, and the OSC is positioned to support dependable long-term service delivery. Trust begins with independent review and operational discipline. Internal audits are conducted at planned intervals to determine whether internal systems meet defined control criteria. Documented transition procedures and signed agreements support the safe transfer of IT management when a customer changes providers. Capacity for managed objects and environments is monitored and planned, while problem management processes ensure nonstandard operational events are recorded, categorized, correlated, investigated, resolved, and reported to appropriate Organization and customer management. Secure and dependable service delivery is further supported through controlled remote access, environmental safeguards, and restricted access to colocation hardware. Remote connections to Organization and customer information systems are restricted through approved secure access methods and are monitored, logged, and reviewed. Environmental and maintenance controls are implemented and tested for applicable operations centers and data centers, and physical access to customer colocation equipment is limited to designated customer personnel and authorized Organization personnel. The OSC also makes contractual reporting metrics available to customers and maintains evidence that managed service and cloud offerings operate with sustainable gross margins. Customer commitment measures provide insight into the continuity of customer relationships, while applicable errors and omissions, professional liability, cybersecurity, and other insurance coverage help mitigate business disruption. Collectively, these controls demonstrate that the OSC can monitor service performance, communicate material results, manage operational and financial risks, and sustain reliable customer commitments.
Requirements in this domain
| ID | Title | Description |
|---|---|---|
| 02.04 | Internal Audit | Conduct internal audits at planned intervals to provide information on whether internal systems are meeting control criteria. |
| 02.08 | Service Transition Continuity | Documented policy containing procedures for effectuating the safe transfer of IT management to another provider. Uses signed agreements with specific provisions for addressing transition services. |
| 04.05 | Capacity Planning | Monitors the capacity of managed objects and environments. Manages and proactively plans capacity requirements internally or with the Customer. |
| 05.02 | Support and Problem Logging | A problem management system (help desk / ticketing system) has been implemented to ensure that operational events that are not part of the Organization’s standard operations are recorded, analyzed and resolved in a timely manner. |
| 05.03 | Categorization and Correlation | Problem/incident documentation is categorized to allow for event correlation and the elimination of false positives. |
| 05.04 | Support and Problem Resolution | Problems and/or incidents identified in the Customer’s environment are properly resolved and documented. Resolution is reported to both Organization and Customer management. |
| 06.08 | Restricted Secure Remote Access | Remote access to information systems is protected by restricting access using a VPN or Zero Trust Network Access (ZTNA) configuration. Remote access is monitored, logged, and reviewed following a Remote Access Policy. |
| 08.05 | Data Center Environmental Controls | Environmental safeguards in NOC(s) and/or data center(s) to protect from disruptive events. |
| 08.06 | Data Center Maintenance | Environmental and maintenance services are performed and tested regularly following a standardized and documented process. |
| 08.07 | Data Center Colocation | Physical access to collocation hardware maintained in facilities is restricted to individuals designated by the Customer and authorized Organization personnel. |
| 09.03 | Report Availability | Reporting metrics are available to Customers following signed contracts. |
| 10.03 | Sustainable Profit Margin on Services | Demonstrates that a sustainable gross profit margin is realized on managed service/cloud offerings. |
| 10.04 | Customer Commitments | The Organization shows that most of its customers and revenue come from relationships that last at least a year or longer. |
| 10.05 | Insurance | Maintains errors and omissions, professional liability, cyber security and any other applicable insurance policies necessary to mitigate against business disruption. |
UCS domain RES
Resilience
#The Resilience domain evaluates the OSC’s ability to prepare for, withstand, respond to, and recover from operational and security disruptions. It combines governance and risk management, incident response, employee readiness, personnel screening and confidentiality obligations, secure development practices, logical and physical access revocation, segregation of duties, data backup and recovery, and business continuity planning. Together, these controls help protect critical services, systems, data, and operational responsibilities when personnel, technology, facilities, or external events disrupt normal operations. Resilience begins with a formal management structure, executive oversight, and a risk management strategy that identifies, analyzes, communicates, and treats operational risks. Documented incident response policies address data breaches, ransomware, and cyberattacks. Employee orientation, continuing education, and security awareness training reinforce ethical, confidentiality, privacy, security, and acceptable-use expectations. Background checks and signed confidentiality and privacy acknowledgments further reduce personnel-related risk. Operational resilience is further supported through application version tracking, segregation of duties between development and production promotion, functional separation of system access, and timely revocation of logical and physical access when personnel depart. Documented and monitored backup schedules protect Organization and Customer data, while tested business continuity plans support recovery and continued service delivery. Collectively, these controls enable the OSC to manage disruption risk, preserve accountability, protect data and systems, and maintain recoverable operations.
Requirements in this domain
| ID | Title | Description |
|---|---|---|
| 01.01 | Organizational Structure | Formal management structure with executive steering committee/board of directors responsible for management and supervision. |
| 01.03 | Risk Management | A risk management strategy is established by the organization. Risks are logged and communicated to management to ensure adequate and timely analysis. A risk treatment strategy is in place and followed. |
| 02.02 | Incident Response Policies and Procedures | Incident Response policy documented; addresses data breaches, ransomware payments, and cyber-attacks. |
| 02.06 | Training and Orientation | Orientation/training and continuing education programs for ethical, integrity, confidentiality, privacy, security, and acceptable use standards. |
| 02.07 | Security Awareness Training | Employees receive essential cybersecurity and information security training. |
| 03.01 | Employee Background Checks | Background checks conducted on personnel following policies and procedures. |
| 03.02 | Employee Confidentiality and Privacy Acceptance | Employees sign and attest to understanding and adherence to confidentiality and privacy policies. |
| 04.08 | SaaS Special Requirement: Version Tracking and Code Maintenance | The Organization has a process for tracking application versions. |
| 04.09 | SaaS Special Requirement: Development Segregation of Duties | Segregation of duties exists between the development and promotion of application changes to the production environment. |
| 06.04 | Revocation of Access | Logical access to information systems and Customer systems/data revoked for terminated and departing employees. |
| 06.06 | Segregation of Access | Access to information systems separated by functional area to ensure segregation of duties. |
| 07.01 | Customer Data Backup and Replication | Customer data backup schedules documented and followed; backups monitored and errors handled; data encrypted. |
| 07.02 | Organization Data Backup and Replication | Organization data backups completed and monitored; errors handled; data encrypted. |
| 07.04 | Disaster and Business Continuity Planning | Business continuity plans documented and tested periodically to ensure data integrity. |
| 08.04 | Revocation of Physical Access | Upon termination, employee access to facilities is revoked. |
UCS domain TRA
Transparency
#The Transparency domain evaluates whether the OSC documents, maintains, and communicates information that customers and stakeholders need to understand service responsibilities, data handling, external provider involvement, service levels, billing, and financial concentration risk. It addresses policy governance and employee acceptance, disclosure of data geolocation and external service provider access, service-level categorization, accurate invoicing, and management of significant customer revenue concentration. Together, these practices support informed customer decisions, consistent service administration, and accountability for material operational and financial information. Transparency begins with documented policies and procedures that govern daily operations. These documents are reviewed and updated at least annually, with changes approved and implemented through established processes. Employees attest to their understanding of and adherence to applicable policies and procedures, providing evidence that operational expectations are communicated and acknowledged. The OSC also maintains processes to identify and disclose the geolocation of managed data, including data managed by external service providers, and to communicate external provider access to Customer information systems and data. Service levels are categorized within organizational systems, and invoices are generated in accordance with signed customer agreements. Customer revenue concentration is monitored against defined thresholds to reduce dependency on significant customers. Collectively, these controls provide customers and stakeholders with clear, supportable information about data location, third-party involvement, service commitments, billing, and material financial exposure.
Requirements in this domain
| ID | Title | Description |
|---|---|---|
| 02.01 | Documentation of Policies and Procedures | Policies and procedures formally documented to guide daily operations. The sequence of employee onboarding and org layout will contribute to the ability for the MSP to withstand any disruptions |
| 02.03 | Periodic Review and Approval | Policies and procedures reviewed and updated annually for approval and implementation. The sequence of employee onboarding and org layout will contribute to the ability for the MSP to withstand any disruptions |
| 02.05 | Employee Acceptance | Employees sign and attest to understanding and adherence to policies and procedures. The sequence of employee onboarding and org layout will contribute to the ability for the MSP to withstand any disruptions |
| 03.04 | Organization Data Geolocation Disclosure | Policies and procedures are implemented to govern the identification and disclosure of the geolocation of managed data. |
| 03.05 | External Service Provider Geolocation Disclosure | Policies and procedures are implemented to govern the identification and geolocation disclosure of external service provider managed data. |
| 03.07 | External Service Provider Access Disclosure | Policies and procedures have been implemented to govern the communication and disclosure of external service provider access to Customer information systems and data. |
| 04.02 | Service Level Categorization | Service levels are adequately categorized and identified within Organizational systems. |
| 09.02 | Accuracy of Service Invoices | Organization invoices are generated following signed Master Service Level Agreement contracts. |
| 10.02 | Significant Customer Risk | The Organization demonstrates sufficient managed services revenue distribution so that the largest Customer does not represent more than 20% of total managed services revenue and the five largest Customers do not represent more than 50% of total managed services revenue. |
UCS domain SEC
Security
#Security is a cornerstone of UCS operations. External service providers, including providers of cloud, SaaS, managed services, and AI-enabled services, are carefully evaluated, approved, and governed by designated personnel before use and throughout the service lifecycle. Confidential or private internal or customer data is encrypted, and where encryption is unavailable, other security practices safeguard the data. This rigorous approach helps ensure that sensitive information, identities, and systems are protected from unauthorized access and potential threats. Access by external providers to organizational and customer systems is strictly controlled, monitored, and documented. This access is limited to necessary occasions and follows documented policies and procedures. Changes to internal configurations are also documented, ensuring that they are requested, reviewed, and approved through a consistent process. A formal identity and access management framework governs authentication, authorization, and identity lifecycle activities across organizational and customer systems. Access is provisioned, verified, monitored, and revoked according to defined roles and business requirements, with automated and risk-based controls supporting identity assurance, accountability, and least-privilege access. Access control policies further restrict system access to authorized personnel using unique IDs and securely stored passwords. Administrator IDs for critical systems are limited to approved personnel, ensuring that privileged access to sensitive information is tightly controlled. Networks are secured through a suite of threat management tools. Email and environments are scanned for attacks and malware, while EDR and related monitoring technologies protect network-connected devices and traffic. The wireless network is segregated from the guest wireless network. Physical security at work locations includes periodic reviews of access rights, visitor logging, and restricted access to sensitive areas such as operations centers, data centers, and server rooms. Visitors are required to sign in upon entry, and physical access to sensitive areas is limited to authorized personnel. The Security domain demonstrates the OSC's commitment to protecting organizational and customer information, identities, systems, applications, AI-enabled services, and operating environments through coordinated access control, identity governance, encryption, network and endpoint security, system logging, security testing, data and device management, and physical security measures. Together, these controls reduce unauthorized access and misuse, strengthen accountability, support least-privilege access, and provide a secure and reliable foundation for service delivery.
Requirements in this domain
| ID | Title | Description |
|---|---|---|
| 01.05 | External Service Provider Governance | External service providers (contractors, third parties, vendors), including providers of cloud, SaaS, managed services, and AI-enabled services utilized by the Organization, are evaluated, approved, and periodically reviewed by designated personnel prior to use and throughout the service lifecycle. |
| 03.03 | Data Classification, Data Protection and Encryption | Internal or Customer data classified as confidential or private is encrypted following applicable industry best practices or regulations. Where encryption is not available, inherent information security practices are in place to protect internal and customer data. |
| 03.06 | External Service Provider Access Control | External service providers only monitor or gain access to Organizations and Customers' information systems only when needed. This access is monitored, logged, and reviewed according to documented policies and procedures. |
| 04.03 | Internal Change Tracking | Modifications to internal object configurations are documented to ensure changes are requested, reviewed, and approved following a consistent process. |
| 06.01 | Controlled Access to Applications and Environments | Access to Organization and Customer systems and configuration data is restricted to authorized personnel following a documented Access Control Policy. All critical service delivery and internal applications have centralized access control mechanisms implemented. |
| 06.02 | Super-User and Administrator Access Security | Administrator IDs to information systems (network and in-scope critical systems) are restricted to a limited number of approved personnel. |
| 06.03 | Unique Users and Passwords | Users authenticate to Organizational information systems and the underlying Customer data using unique user account IDs and passwords. |
| 06.05 | Strong Passwords | User authentication password mechanisms are implemented and require minimum standards for password length, complexity, expiration, reuse, and account lockout for failed attempts. Organization passwords are stored in a secure password repository. |
| 06.09 | Network and Endpoint Security Management and Monitoring | Local and wide area networks are secured through the use of managed firewalls and other devices and software. Where applicable, MDR/EDR/XDR controls and security information and event management (SIEM) systems are utilized to monitor and secure the Organization’s network. |
| 06.10 | Email Security | The Organization has implemented applications and/or systems to scan and protect email and environments from email attacks and malware/viruses. |
| 06.11 | Network and Endpoint Protection | Organization has implemented an EDR (Endpoint Detection and Response) system on the network’s connected devices and traffic (web and email) to scan and protect its environment. |
| 06.12 | Wireless Network Security | The Organization's wireless network is segregated from its guest wireless network. |
| 06.13 | Network Security Review | Network security reviews (including security assessments, scans, penetration tests, etc.) of the Organization’s network are conducted periodically. |
| 06.14 | System Logging | The Organization has a formal process for tracking, retaining and reviewing audit logs. |
| 06.15 | Identity and Access Management Framework | The Organization establishes and maintains an Identity and Access Management (IAM) framework to govern authentication, authorization, and identity lifecycle activities across Organizational and Customer systems, ensuring that access is appropriately provisioned, verified, monitored, and revoked in alignment with defined roles and business requirements. The IAM framework operates in conjunction with access control, authentication, and external service provider management processes, incorporating automated, monitored, and risk-based controls to enforce identity assurance, accountability, and least-privilege access across all environments. |
| 07.05 | Internal Data Destruction | Objects containing internal data are handled and destroyed following end-of-life policies. |
| 07.06 | Customer Data Destruction | If data destruction services are delivered to Customers, objects containing Customer data are handled and destroyed following end-of-life policies. |
| 07.07 | Asset and Device Management | Assets and devices are maintained in a centralized inventory list. A device management policy and supporting security measures shall be adopted to manage the risks of all devices and assets. The Organization is using an active discovery tool when managing customer assets. |
| 08.01 | Organizational Physical Security | Physical security controls are implemented by the Organization with respect to all work locations. Access rights of personnel are reviewed and approved by Organization upper management on a periodic basis. |
| 08.02 | Logging of Visitors | Visitor logs are maintained at each facility by the Organization. Visitors are required to sign the log upon entering the building. |
| 08.03 | Sensitive Area Security | Physical access to the sensitive areas (including operations centers, data centers, and server rooms) is restricted to authorized personnel. |
The ten UCS objectives
UCS objective 01
Governance
#UCS Objective Summary and Purpose: The goal of the Governance Objective is to provide assurance to the Customer that the Organization has established a corporate structure designed to maximize efficiency, minimize risk, provide sufficient oversight and accountability with regard to the services delivered. This objective also addresses external service provider management protocols of the Organization.
Organizational Structure
The Organization has a formal management structure, with an executive steering committee/board of directors responsible for the management and supervision of the company.
Strategic Planning
Strategic plans and priorities have been developed and communicated to the management of the company.
Risk Management
A risk management strategy is established by the organization. Risks are logged and communicated to management to ensure adequate and timely analysis. A risk treatment strategy is in place and followed.
Software Management
For infrastructure, platform, or software as a service being delivered, the Organization has a process for managing and determining their legal and financial risk of software audits or third-party intellectual property claims. An inventory of in scope SaaS vendors is maintained by the organization.
External Service Provider Governance
External service providers (contractors, third parties, vendors), including providers of cloud, SaaS, managed services, and AI-enabled services utilized by the Organization, are evaluated, approved, and periodically reviewed by designated personnel prior to use and throughout the service lifecycle.
UCS objective 02
Policies and Procedures
#UCS Objective Summary and Purpose: The goal of the Policies and Procedures Objective is to ensure the Organization has documented the necessary policies and procedures in order to maintain effective service delivery levels, as well as to minimize deviation from those established policies and procedures.
Documentation of Policies and Procedures
Policies and procedures have been formally documented to guide the daily operations of the Organization.
Incident Response Policies and Procedures
An Incident Response policy has been formally documented. Policies and procedures to address data breaches, ransomware payments, and cyber-attacks impacting the daily operations of the Organization are established and tested, and if applicable, it’s Customers.
Periodic Review and Approval
Policies and procedures are reviewed and updated at least annually to ensure any modifications are approved and implemented.
Internal Audit
The Organization shall conduct internal audits at planned intervals to provide information on whether their internal systems are meeting their control criteria.
Employee Acceptance
Employees are required to sign and attest to their understanding and adherence to Organizational policies and procedures.
Training and Orientation
New employee orientation/training and continuing education programs for existing employees are implemented to address the ethical, integrity, confidentiality, privacy, security, and acceptable use standards developed by the Organization.
Security Awareness Training
Organization employees receive essential cybersecurity and information security training.
Service Transition Continuity
The Organization has a documented policy containing procedures for effectuating the safe transfer of IT management to another provider. The Organization uses signed agreements which contain specific provisions for addressing transition services in situations where the client is changing providers.
UCS objective 03
Confidentiality, Privacy and Service Transparency
#UCS Objective Summary and Purpose: The goal of the Confidentiality and Privacy Objective is to ensure the Organization has sufficient policies and procedures related to the protection and disclosure of Customer data, specifically protocols safeguarding confidentiality, privacy, geolocation of managed data (including external service provider managed data) and identification of applications utilized to deliver services.
Employee Background Checks
Background checks are conducted on personnel following Organization policies and procedures.
Employee Confidentiality and Privacy Acceptance
Employees are required to sign and attest to their understanding and adherence to Organizational confidentiality and privacy policies.
Data Classification, Data Protection and Encryption
Internal or Customer data classified as confidential or private is encrypted following applicable industry best practices or regulations. Where encryption is not available, inherent information security practices are in place to protect internal and customer data.
Organization Data Geolocation Disclosure
Policies and procedures are implemented to govern the identification and disclosure of the geolocation of managed data.
External Service Provider Geolocation Disclosure
Policies and procedures are implemented to govern the identification and geolocation disclosure of external service provider managed data.
External Service Provider Access Control
External service providers only monitor or gain access to Organizations and Customers' information systems only when needed. This access is monitored, logged, and reviewed according to documented policies and procedures.
External Service Provider Access Disclosure
Policies and procedures have been implemented to govern the communication and disclosure of external service provider access to Customer information systems and data.
UCS objective 04
Change Management
#UCS Objective Summary and Purpose: The goal of the Change Management Objective is to ensure the Organization has formalized change management policies and procedures that may include, if applicable, the modification of Organization and Customer configurations, capacity planning and patch management. Customer change management policies are documented based on the level of services delivered to the Customer by the Organization.
Configuration Documentation
Configuration data for objects managed or monitored is documented based on level of service before management of the object.
Service Level Categorization
Service levels are adequately categorized and identified within Organizational systems.
Internal Change Tracking
Modifications to internal object configurations are documented to ensure changes are requested, reviewed, and approved following a consistent process.
Customer Change Tracking
Modifications to Customer object configurations are documented to ensure changes are evaluated and approved by the Customer before implementation. Configuration data is updated following implementation to reflect the current Customer configuration.
Capacity Planning
The Organization monitors the capacity of managed objects and environments. If applicable, the Organization manages and proactively plans (both internally or with the Customer) and prioritizes capacity requirements.
Patch Management
Vendor-supplied software and hardware patches are applied to managed objects and environments following standardized procedures. on-critical patches are evaluated for issues before release and applied during planned or accepted maintenance windows. Critical patches are applied as soon as possible to both Customer and internal environments.
UCS objective 05
Service Operations Management
#UCS Objective Summary and Purpose: The goal of the Service Operations Management Objective deals with how the Organization identifies and responds to IT (Information Technology) related events that could impact services delivered to the Customer. In this UCS objective, the examination covers the Organization’s Network Operations Center (“NOC”), Trouble Ticketing systems and Service Desk operations specifically related to event management policies and procedures.
Centralized Operations Center
A Managed service/Network/Secure Operation Center (MSOC/NOC/SOC) is used to provide effective and secure monitoring and management of Organization and Customer managed environments.
Support and Problem Logging
A problem management system (help desk / ticketing system) has been implemented to ensure that operational events that are not part of the Organization’s standard operations are recorded, analyzed and resolved in a timely manner.
Categorization and Correlation
Problem/incident documentation is categorized to allow for event correlation and the elimination of false positives.
Support and Problem Resolution
Problems and/or incidents identified in the Customer’s environment are properly resolved and such resolution is documented and reported to both Organization and Customer management.
Operations Monitoring
Organization management performs a periodic internal review of tickets and operational events.
UCS objective 06
Information Security
#UCS Objective Summary and Purpose: The goal of the Information Security Objective is to ensure the Organization has implemented the governance and technical controls necessary to protect identities, access, managed data, networks, systems, and environments that could affect the security of both the Organization and the Customer. This includes identity and access management, identity lifecycle administration, authentication, authorization, privileged access, remote access, segregation of duties, wireless and network security, endpoint protection, security assessments, system logging, and monitoring of access to Customer systems.
Controlled Access to Applications and Environments
Access to Organization and Customer systems and configuration data is restricted to authorized personnel following a documented Access Control Policy. All critical service delivery and internal applications have centralized access control mechanisms implemented.
Super-User and Administrator Access Security
Administrator IDs to information systems (network and in-scope critical systems) are restricted to a limited number of approved personnel.
Unique Users and Passwords
Users authenticate to Organizational information systems and the underlying Customer data using unique user account IDs and passwords.
Revocation of Access
Logical access to the Organization’s information systems (Organization LAN (Local Area Network) and web portals) and Customer systems and data is revoked and reviewed for terminated and departing employees.
Strong Passwords
User authentication password mechanisms are implemented and require minimum standards for password length, complexity, expiration, reuse, and account lockout for failed attempts. Organization passwords are stored in a secure password repository.
Segregation of Access
Access to information systems (including Customer systems and data) is separated by functional area to ensure segregation of duties.
Continuous Review of Access Rights
Access to information systems, as well as the underlying customer systems and data, is continually reviewed by the Organization’s upper management to ensure that resource access is appropriately restricted to authorized personnel.
Restricted Secure Remote Access
Remote access to the Organization and Customer information systems is protected by restricting access to the Remote Access Tool using a VPN or Zero Trust Network Access (ZTNA) configuration. Remote access is monitored, logged, and reviewed by Organization management following a Remote Access Policy.
Network and Endpoint Security Management and Monitoring
Local and wide area networks are secured through the use of managed firewalls and other devices and software. Where applicable, MDR/EDR/XDR controls and security information and event management (SIEM) systems are utilized to monitor and secure the Organization’s network.
Email Security
The Organization has implemented applications and/or systems to scan and protect email and environments from email attacks and malware/viruses.
Network and Endpoint Protection
Organization has implemented an EDR (Endpoint Detection and Response) system on the network’s connected devices and traffic (web and email) to scan and protect its environment.
Wireless Network Security
The Organization's wireless network is segregated from its guest wireless network.
Network Security Review
Network security reviews (including security assessments, scans, penetration tests, etc.) of the Organization’s network are conducted periodically.
System Logging
The Organization has a formal process for tracking, retaining and reviewing audit logs.
Identity and Access Management Framework
The Organization establishes and maintains an Identity and Access Management (IAM) framework to govern authentication, authorization, and identity lifecycle activities across Organizational and Customer systems, ensuring that access is appropriately provisioned, verified, monitored, and revoked in alignment with defined roles and business requirements. The IAM framework operates in conjunction with access control, authentication, and external service provider management processes, incorporating automated, monitored, and risk-based controls to enforce identity assurance, accountability, and least-privilege access across all environments.
UCS objective 07
Data and Device Management
#UCS Objective Summary and Purpose: The goal of the Data Management Objective is to confirm the Organization has sufficient policies and procedures to ensure the integrity and availability of managed Customer and Organization internal data in the event of natural disasters, cyber-attacks (i.e., ransomware), and user error or malfeasance. This includes the implementation of data backup as well as encryption, security, retention, and restoration of managed Customer and Organization internal data.
Customer Data Backup and Replication
Where applicable, Customer data backup schedules are documented and followed following contractual service agreements, with backups being monitored, with any errors being handled following operations management policies and procedures. Customer backup and/or replicated data is encrypted following contractual requirements.
Organization Data Backup and Replication
Organization data backups are being completed and monitored following backup schedules, with any errors being handled following operations management policies and procedures. Backup and/or replicated data is encrypted following Organization policies and procedures.
Data Recovery Testing
Backup data restoration and recovery testing procedures are conducted periodically, with the results of tests being logged and monitored by the Organization.
Disaster and Business Continuity Planning
Business continuity plans are documented and tested periodically to ensure the integrity of Organization and, if applicable, Customer data.
Internal Data Destruction
Objects containing internal data are handled and destroyed following end-of-life policies.
Customer Data Destruction
If data destruction services are delivered to Customers, objects containing Customer data are handled and destroyed following end-of-life policies.
Asset and Device Management
Assets and devices are maintained in a centralized inventory list. A device management policy and supporting security measures shall be adopted to manage the risks of all devices and assets. The Organization is using an active discovery tool when managing customer assets.
UCS objective 08
Physical Security
#UCS Objective Summary and Purpose: The goal of the Physical Security Objective is to ensure the Organization has documented policies and procedures governing physical access and environmental security of the Organizational assets. The Organization must demonstrate sufficient physical security controls at each facility, including controls such as physical access administration, card key, CCTV, on-site security, visitor/guest logs and other effective security and environmental controls.
Organizational Physical Security
Physical security controls are implemented by the Organization with respect to all work locations. Access rights of personnel are reviewed and approved by Organization upper management on a periodic basis.
Logging of Visitors
Visitor logs are maintained at each facility by the Organization. Visitors are required to sign the log upon entering the building.
Sensitive Area Security
Physical access to the sensitive areas (including operations centers, data centers, and server rooms) is restricted to authorized personnel.
Revocation of Physical Access
Upon termination, employee access to the Organization’s facilities is revoked.
Data Center Environmental Controls
The Organization has environmental safeguards in its NOC(s) and/or data center(s) to protect from disruptive events.
Data Center Maintenance
Environmental and maintenance services are performed and tested regularly following a standardized and documented process.
Data Center Colocation
Physical access to collocation hardware maintained in the Organization’s facilities is restricted to individuals designated by the Customer and authorized Organization personnel.
UCS objective 09
Billing and Reporting
#UCS Objective Summary and Purpose: The goal of the Billing & Reporting Objective is to ensure the Organization is accurately monitoring service delivery, reporting, and invoicing for Customers following SLAs (service level agreements) signed by both parties.
Signed Contracts and Agreements
Signed Master Service Level Agreements (MSA) are in place between the Organization and Customers.
Accuracy of Service Invoices
Organization invoices are generated following signed Master Service Level Agreement contracts.
Report Availability
Reporting metrics are available to Customers following signed contracts.
UCS objective 10
Corporate Health
#UCS Objective Summary and Purpose: The goal of the Corporate Health Objective is to ensure sufficient corporate and financial health on the part of the Organization so that all of its Customers are adequately protected. Technical proficiency is only part of the Organization’s value to the Customer. The Organization must be on firm financial footing, as well as risk averse in a variety of areas unique to managed services and cloud in order to effectively deliver its services to the Customer.
Operational Sustainability
Financial reports demonstrate profitability of a minimum of 6 of the previous 12 months, or sufficient access to funds necessary to keep the Organization operational for a 12-month period of time
Significant Customer Risk
The Organization demonstrates sufficient managed services revenue distribution so that the largest Customer does not represent more than 20% of total managed services revenue and the five largest Customers do not represent more than 50% of total managed services revenue.
Sustainable Profit Margin on Services
The Organization demonstrates that a sustainable gross profit margin is realized on its managed service/cloud offerings.
Customer Commitments
The Organization shows that most of its customers and revenue come from relationships that last at least a year or longer.
Insurance
The Organization maintains errors and omissions, professional liability, cyber security and any other applicable insurance policies necessary to mitigate against Organization business disruption.
Customer and Employee Retention Tracking
The Organization maintains records to track the retention of customers (both voluntary and involuntary) and employees (both voluntary and voluntary) to ensure business continuity.
Special requirements and definitions
Special Requirements
#The following special requirements contain controls that are commonly associated with specific service lines and Customer industries. As such, these special requirements can be added to the Cyber Verify reports.
SaaS (Software as a Service) Special Requirements
SaaS Special Requirement: Application Development Procedures
Application Changes to information systems follow a formal process that requires the requesting, logging, approval, testing, and acceptance of changes before being implemented into production.
SaaS Special Requirement: Version Tracking and Code Maintenance
The Organization has a process for tracking application versions.
SaaS Special Requirement: Development Segregation of Duties
Segregation of duties exists between the development and promotion of application changes to the production environment.
Helpful Definitions
#- Customer
- A Customer refers to the clients of a company who receive professional services as defined in a service level agreement or comparable ongoing service-level document. Customers are the end-users who benefit from the services provided by the organization.
- Vendor
- A Vendor is a company or individual that provides a product or performs a service for another company. Vendors can include consultants, banking service providers, software maintenance vendors, and auditors. They often have access to customers or other sensitive data and have a contractual commitment to the company.
- External Service Provider (ESP)
- An External Service Provider (ESP) is any Vendor or third party that provides a service for your company. This service could take many forms, such as an application, Infrastructure as a Service (IaaS), Software as a Service (SaaS), Hardware as a Service (HaaS), data destruction services, data centers/colocation services, etc. Continuous access refers to any access that is constant or permanent within an application or service.