Sightadel

Platform · Integrations

Your data is already there.
Sightadel collects it.

Much of what an audit requires has long been in your systems: tasks in the ticket system, policies in the wiki, servers and applications in the cloud and in the ERP. Sightadel imports this data instead of someone retyping it, and keeps it in sync with your systems. The AI then uses it for its suggestions.

No retyping

Assets, evidence and tasks come from the systems in which they are maintained anyway.

Current rather than a snapshot

If something changes in Jira or Azure, Sightadel sees it at the next sync. The status in the audit is the status in operation.

Better suggestions

The more data there is in Sightadel, the more precisely the AI suggests content for assessments and documents.

Your system is missing?

Sightadel is built on its own interface. That is why we connect further systems quickly on request.

How it works

Set up in 4 steps.

  1. 1

    Select a system

    You choose which system to connect and sign in there with an account that has read access.

  2. 2

    Define the scope

    You decide what is imported: for example a Jira project, a Confluence space or an Azure subscription.

  3. 3

    Assign

    Sightadel creates the data as assets, evidence or tasks. You link them to the controls they support.

  4. 4

    Sync runs

    After that, Sightadel syncs regularly. New and changed entries appear without any action on your part.

Before and after

What changes with integrations.

The work does not disappear – the searching, asking around and chasing people does.

Without Sightadel

  • Asset lists are copied together from the cloud console and the ERP for every audit.
  • Policies are in the wiki, copies of them in the audit folder – at different versions.
  • Measures are completed in the ticket system but ticked off by hand in the compliance tool.
  • What has changed since the last audit only becomes apparent at the next one.
  • Someone has to remember to update lists and evidence regularly.

With Sightadel

  • Assets come from Azure, SAP or Dynamics and stay in sync.
  • Policies from Confluence appear as evidence at the matching controls.
  • Tickets from Jira and Zendesk appear as tasks on the measures.
  • Changes in the systems arrive in Sightadel at the next sync.
  • The AI uses the imported data for its suggestions.
  • Reminders and deadlines run automatically.

Integrations

Which systems Sightadel connects

The integrations cover the systems in which most audit-relevant data is held at SMEs.

  • Jira – tasks and tickets
  • Confluence – policies and documentation as evidence
  • Zendesk – tickets, for example on incidents
  • Microsoft Azure – resources as assets
  • SAP and Microsoft Dynamics – data from the ERP
  • Salesforce – data from the CRM
  • Further systems on request

Integrations

What is imported – and what is not

Integrations deliver assets, evidence and tasks. User accounts are not included: you deliberately create the people who work in Sightadel yourself, so that roles and permissions do not come unchecked from another system.

  • Assets, for example servers, applications and cloud resources
  • Evidence, for example policies and logs
  • Tasks, for example tickets on measures and incidents
  • Users manually or as a CSV list
  • Import and export for Excel and Word

Integrations

What then runs automatically

Once the data is in Sightadel, the platform takes over the routine that someone would otherwise have to trigger.

  • Reminders to the people responsible before deadlines
  • A notice when a piece of evidence expires
  • Vendor reassessment at the interval you set
  • Dates for internal audit and management review

In detail

Integrations: what you should know.

Why integrations make compliance cheaper

The greatest effort in a management system rarely arises when things are first written down, but when keeping them up to date. Asset lists become outdated as soon as someone orders a new server. Policies are revised in the wiki, while the copy in the audit folder stays old. Measures have long been completed in the ticket system but are still shown as open in the compliance tool.

Integrations address exactly this. Sightadel imports the data from the systems in which it is maintained anyway and syncs it regularly. This means there is one source instead of two versions, and the status the auditor sees matches the status in operation.

The second effect concerns the AI. It makes suggestions based on what is already in Sightadel. The more complete assets, evidence and tasks are, the more precise these suggestions become, for example for the Statement of Applicability (SoA) or for the answers in the assessment.

What you should clarify before connecting

Define which part of a system belongs in the scope. Not every Jira project and not every Azure subscription is audit-relevant. If you import everything, you will later be searching for what matters in a long list.

Use an account with read-only access for the connection and document who manages it. That is itself a measure an auditor will want to see.

Also clarify who decides on deviations. If a new system appears, someone has to decide whether it falls within the scope, how it is classified and who is responsible. This decision stays with you. Sightadel makes it visible and reminds you of it.

If your system is not included

The existing integrations cover the systems in which most of our customers hold their audit-relevant data. If you work with a different ticket system, wiki or ERP, talk to us. Sightadel is built on its own interface, so further systems can be connected quickly.

Until then, import and export for Excel and Word remain available. You create users manually anyway or upload them as a CSV list. This way you keep control over who works in Sightadel and with which permissions.

Questions and answers

Questions about integrations

More in our FAQ or directly via our contact form.

Which systems can I connect to Sightadel?

Jira, Confluence, Zendesk, Microsoft Azure, SAP, Microsoft Dynamics and Salesforce. We connect further systems quickly on request.

Which data does Sightadel import?

Assets, evidence and tasks. User accounts are not imported. You create them manually or upload them as a CSV list.

Is there an open API?

We do not currently offer an API for customers. Internally, Sightadel uses its own interface. Through it, we connect further systems on request.

How up to date is the imported data?

Sightadel syncs the connected systems regularly. New and changed entries then appear without any action on your part.

Does an integration cost extra?

Prices for integrations are available on request. Tell us which system you would like to connect.

Start with one standard.

14 days, full access, no payment details. Everything you set up carries over into the paid plan.