This page outlines the process for integrating your Service Desk platform with Cymmetri. This integration will streamline workflows, enhance communication, and improve overall service management.
Before beginning the integration, ensure you have:
Administrative access to both the Service Desk and Cymmetri.
API keys or authentication tokens for both platforms.
Backup of existing configurations, if necessary.
Login to Your Service Desk
Access your Service Desk portal and log in with your admin credentials.
Access API Settings
Navigate to Settings > API.
Enable API access if it is not already enabled.
Generate an API key if you do not have one.
Record API Endpoint
Note the API endpoint URL (e.g., https://your-servicedesk.com/api/v1/).
Login to Cymmetri
Go to your Cymmetri dashboard and log in as an administrator.
Access Integration Settings
Navigate to Identity Hub > Applications.
Click on Add New Application.
Select Service Desk
Choose your specific Service Desk platform from the list of available integrations. Cymmetri has ready connectors for ServiceNow, Atlassian (Jira), Fresh Service, etc.
Enter API Details
API URL: Enter the API endpoint noted from your Service Desk.
API Key: Paste the API key generated in your Service Desk.
Test Connection
Click on Test Connection to ensure Cymmetri can successfully communicate with your Service Desk.
If successful, proceed to the next step. If not, double-check your API settings.
Field Mapping using Policy Map
Map relevant fields between your Service Desk and Cymmetri. Common fields to consider include:
Ticket ID
Status
Priority
Assignee
Comments
Configure Sync Settings
Decide on the synchronization direction (one-way or two-way).
Set the sync frequency (e.g., real-time, hourly, daily).
To integrate a service desk with Cymmetri for handling requests such as user provisioning for applications like CRM, the process involves leveraging Cymmetri’s Identity Governance and Administration (IGA) platform capabilities to manage the lifecycle of requests while synchronizing the ticketing and provisioning process. Here’s a brief description of how to manage this integration:
The integration between Cymmetri and service desks like Zoho Desk or ServiceNow typically uses APIs or webhooks to enable communication between the two systems. The integration can be broken down into the following steps:
• A user submits a request for access to an application, like CRM, via the service desk portal.
• This request triggers an API call or webhook from the service desk to Cymmetri, initiating the workflow in Cymmetri for provisioning.
• Cymmetri receives the request and starts the approval workflow, following its defined governance policies.
• Multiple layers of approval can be enforced, such as managerial, application owner, or compliance approval, based on pre-defined rules.
• Once the request is approved, Cymmetri will provision the user access to the requested application (in this case, CRM).
• Once the provisioning is successful, Cymmetri sends an API response or webhook back to the service desk, indicating that the provisioning process is complete.
• The service desk system then automatically updates the ticket status to “Closed.”
Governance is crucial in ensuring the proper approval, auditing, and compliance are maintained throughout the request and provisioning lifecycle. Here’s how governance can be managed:
• Define governance rules and policies for access requests originating from the service desk.
• Set up role-based access controls (RBAC) to ensure that users can only request access to applications they are entitled to.
• Configure workflows in Cymmetri to enforce approval chains before provisioning occurs. For instance, managerial approval, application owner approval, and segregation of duties (SoD) checks can be part of the process.
• Cymmetri maintains a detailed audit trail of each request. This ensures that all approvals, denials, or escalations are documented, providing an audit trail for governance and compliance reporting.
• Approval workflows should be automated and governed by pre-defined policies such as the least privilege principle or SoD rules, which prevent conflicting roles from being assigned.
• Cymmetri can be configured to check for policy violations before completing the provisioning. For example, if a user requests access to a role that creates an SoD violation, Cymmetri can trigger a violation notification and require additional approvals or corrective actions before the process can move forward.
• Cymmetri ensures that de-provisioning is part of the governance process. If a user’s access is no longer required, a de-provisioning request can be triggered either automatically or through the service desk. This will update both systems (Cymmetri and service desk) accordingly.
• Regular audits can be run through Cymmetri to ensure compliance with governance policies. Reports can show who has been granted access, what approvals were made, and if there were any violations or exceptions.
• Cymmetri can generate compliance reports for auditing, allowing organizations to meet regulatory requirements like SOX or GDPR.
• User logs into the service desk (e.g., Zoho Desk or ServiceNow) and submits a request for CRM application access.
• The service desk creates a request ticket with relevant details, such as the user’s name, department, requested application, and purpose.
• The service desk system calls Cymmetri’s API or triggers a webhook to submit the request into Cymmetri.
• Cymmetri initiates the appropriate access request workflow, considering any SoD checks or policy violations.
• The request is sent through an approval process within Cymmetri based on the organization’s policies. This may involve managerial approval, compliance checks, or application owner approval.
• If any SoD violations are detected, Cymmetri can block the request, notify the necessary stakeholders, and propose alternate access solutions.
• Once the request is approved, Cymmetri provisions access to the CRM application via its integration with the organization’s IAM system.
• Cymmetri ensures that appropriate roles or permissions are granted according to the approved request.
• Once provisioning is complete, Cymmetri sends a notification back to the service desk via API or webhook.
• The service desk automatically closes the request ticket, notifying the user that their access has been granted.
• Cymmetri logs all actions, approvals, and violations, ensuring a detailed audit trail.
• Governance reports can be generated to meet compliance standards and verify that all requests followed organizational policies.
• Policy Definition: Define access policies and approval workflows for requests.
• Role-Based Access Control (RBAC): Assign roles and permissions based on user attributes, and automate provisioning accordingly.
• Segregation of Duties (SoD) Enforcement: Prevent conflicting roles from being granted by ensuring compliance with SoD policies.
• Audit and Compliance Reporting: Keep detailed logs of all actions, approvals, and violations for audit purposes.
• Automated Lifecycle Management: Automate provisioning and de-provisioning workflows while maintaining governance controls.
This integration ensures smooth communication between the service desk and Cymmetri, enabling automated provisioning with governance controls, reducing the manual effort required to manage access requests, and ensuring compliance with policies.
Create Test Tickets
Create several test tickets in your Service Desk.
Confirm that these tickets are reflected in Cymmetri as expected.
Update Test Tickets
Modify the status or comments of the test tickets in either system and check if the changes sync properly.
Connection Issues: Double-check API keys and endpoint URLs. Ensure both systems are operational.
Data Sync Problems: Review field mappings and sync settings. Check integration logs for errors.