Terminology

• Business Service - A business service is a collection of IT resources with defined relationships to one another that can be viewed in a topology.
• Business Service Owner - A user who defines the business service, the statement of applicability, and exceptions. 
• Compliance Architect - A user who authors the policies using the controls library.
• Control - A control is a reusable, shareable function or test that can be used in a policy to create a rule.
• Dashboard - The Dashboard provides a comprehensive overview of ITOC results in an environment.
• Exception - An exception is defined in the statement of applicability for a specific resource (within the business service) that is not required to comply with a specific requirement in the policy. 
• IT Resource - The ITOC application's representation of an IT resource in the customer's environment.
• ITOC Administrator - The seeded itocadmin user. The ITOC administrator is responsible for setting up and customizing ITOC. The ITOC administrator creates users and assigns roles to users.
• Maintenance Window – A definition of a block of time within which jobs are allowed to run and which types of jobs can run in the window.
• Measurement SLO (MSLO) - The timeframe in which a business service needs to be measured against a particular policy. This value is set in the SoA. 
• Platform Engineer - A user who creates the controls.
• Policy- A policy is a system representation of a government or corporate regulatory policy. Policies have a set of requirements and requirements can have one or many rules.
• Remediation SLO (RSLO) - The time frame in which a non-compliant IT resource needs to be remediated against a particular requirement.  
• Results - Results represent a resource's compliance with policy requirements.
• Requirement - Requirements are defined in a policy and contain rules. You can set a requirement severity to high, medium, or low.
• Rule - A rule is defined in a policy. It ties together a requirement and a control. A rule defines scope, parameters, and other values to evaluate compliance with the requirement.
• Scope - Scope allows the system to determine to which IT resources a rule must apply, and a rule defines the scope. A control has applicable scope. The author can use the same control in multiple rules with different scope and parameter values.
• Service Level Objective (SLO) - See Measurement SLO or Remediation SLO. 
• Statement of Applicability (SoA) - The SoA ties a business service to a policy and defines the SLOs, maintenance windows, and exceptions. Scan compliance and remediation jobs are manually run within the maintenance windows.
• VP of Operations - A user who is primarily interested in overall compliance status, viewed from the dashboard.