Complyance Support

Required informationTo setup the integration connector, the following information is required: API base URL (ex: https://api.eu-1.crowdstrike.com) Client ID Client secret  Follow the instructions b...

IntroductionJIRA tends to hold a large percentage of documentation and evidence that typically needs to be pulled in manually every audit.Especially with JIRA, manually setting up JQL queries to ca...

Re-ordering your fields is an effective way to ensure your workspace maintains a streamlined flow.Follow these steps to re-order your fields:Navigate to your Organization Settings on the left-hand ...

Users can report Manual Findings on controls. These are commonly used by GRC teams to log findings on Evidence uploaded - or by Internal Audit teams to report opportunities for improvement and non-...

You can use AI to create a task that will help you remediate and action findings you have reported.Creating a Task From a Finding using AI:Navigate to the relevant program on the left-hand side nav...

Cross-mapping your controls helps to streamline your compliance efforts and improve audit readiness. The most common approach to cross-map controls is to use evidence items as the link between fram...

A policy exception is a formal, documented approval to deviate from a policy - typically for a specific reason, for a defined period of time, and under certain conditions.Instead of ignoring or vio...

Bringing the right team members into Complyance is key to successful platform adoption. Complyance comes with 3 systems fields: admin, member and auditor, but also supports Role-Based Access Contro...

Complyance comes with a number of system fields by default when you first enter your environment. In addition, you can create custom fields to tailor the platform to your organization’s specific ne...

IntroductionThe Risks module gives you a clear view of your risk profile and makes it easy to track, manage and review tasks.You’ll find the Risk module in the left-hand sidebar of Complyance. Ther...