Good to know

Security & management

Informatie over veilige gegevensuitwisseling, toegangsrechten, authenticatie, monitoring, foutafhandeling en het betrouwbaar beheren van koppelingen tussen Exact en andere applicaties.

How can I check which external applications have access to our company data?

An overview of external access begins with identifying all active integrations, technical accounts and API registrations.

For each connection, specify which application is connecting, what data is being exchanged, who is responsible for its management, and what rights have been granted.

Depending on the Exact product used, application registrations, user rights and access methods can be managed in different places.

Check periodically to ensure that all registered links are still in use. Obsolete accounts and unused access keys may be revoked following a thorough review.

How can I prevent unauthorised users from accessing our Exact links?

Restricting access starts with a clear authorisation policy. Not every employee, supplier or external developer needs the same rights.

A good approach is to use separate accounts or technical identities for different integrations. This allows access to be managed on a per-application basis and revoked where necessary without disrupting other integrations.

Additional measures include strong authentication, secure storage of API keys, restricted network access and the regular monitoring of active accounts.

When external parties are granted access to Exact or Clickker, it is advisable to specify in advance which data they are permitted to use and which actions they are permitted to carry out.

How secure is it to grant external software access to Exact Globe or Exact Online?

External software can be safely integrated with Exact, provided that the integration is carefully developed and managed.

Key points to consider are the authentication method used, the application’s permissions, the security of the connection and the way in which data is stored.

It is also important to assess whether the external software supplier pays sufficient attention to security updates, error handling and access management.

When setting up a new integration, it is advisable to first determine which data is actually necessary. By making only the necessary data available, you minimise the risks.

How is data secured when exchanging information between Exact and other applications?

When integrating Exact software with external applications, data security is an essential part of the technical setup. Business data, financial information and personal data must be protected against unauthorised access, interception and accidental alterations.

A secure integration makes use of encrypted connections wherever possible, for example via HTTPS with TLS. In addition, API keys, access tokens or other authentication methods are used to determine which application is permitted to access which data.

Access rights are also important. For example, an external application that only needs to read customer data should not be granted rights to amend financial entries.

For organisations that use multiple integrations, it is advisable to review security measures on a regular basis. This includes checking user permissions, changing access credentials and reviewing technical log files.

How is personal data protected during automated data exchange?

Where a link processes personal data, the General Data Protection Regulation (GDPR) must be taken into account.

Among other things, this means that there must be a valid legal basis for the processing and that only data necessary for the business process in question may be exchanged.

In addition, appropriate technical and organisational measures are required. These include access restrictions, encryption, logging, retention periods and agreements with external data processors.

When developing an integration, it is advisable to set out in advance which personal data will be processed, where it will be stored and how long it will be retained.

Can a link be restricted to specific departments or data?

Yes, with many integration solutions, it is possible to restrict access to certain systems, data types or operations. The exact options available depend on the software used.

An organisation with multiple Exact systems may, for example, wish to prevent an online shop from accessing data from other business units.

A distinction can also be made between read and write permissions. A reporting tool does not usually need to be able to amend financial transactions.

Defining access rights on a per-link basis creates a clearer and more manageable integration environment.

What happens when an API key or access token expires?

API keys and access tokens are used to grant applications access to data or functionalities. Some tokens have a limited validity period and must be renewed periodically.

If a token expires and is not renewed correctly, a connection will no longer be able to retrieve or send new data. This may result in error messages, outstanding orders or out-of-date customer data.

For connections that support token renewal, this process can be automated. The exact procedure varies depending on the platform and authentication method.

If a connection is unexpectedly lost, it is therefore advisable to check not only the network connection but also the validity of the authentication credentials being used.

What is the difference between authentication and authorisation in an API integration?

Authentication and authorisation are two different security mechanisms that are often used in conjunction with one another.

Authentication determines who or what is attempting to gain access to a system. This could be, for example, a user, an external application or an automated process. User credentials, API keys or access tokens may be used for this purpose.

Authorisation It then determines which actions this user or application is permitted to carry out. For example, a connection may be able to retrieve product details and stock levels, but not delete sales orders.

This distinction is important because a technically valid connection does not automatically mean that all data must be accessible.

By setting up authorisations to be as restrictive as possible, the risk of unintended data changes or misuse is reduced.

What security measures are important when managing multiple API connections?

When an organisation integrates multiple applications, the importance of centralised management increases.

It is advisable to document, for each integration, which systems are involved, what authentication method is used, what data is processed and who is responsible for making changes.

In addition, monitoring, security updates, controlled change management procedures and regular checks of access rights are important.

A structured approach helps to minimise security risks and makes it easier to investigate problems when a connection exhibits unexpected behaviour.

Are data exchanges between systems logged automatically?

Whether data exchanges are automatically logged depends on the software used and the configuration of the integration.

Logging can provide insight into API calls made, processing times, error messages and the status of data transfers. This is particularly important when multiple systems automatically exchange information.

Within the Clickker ecosystem, CAS and Watcher can be used for workflow logging, monitoring and analysis of data flows. The details available depend on the chosen configuration.

Privacy must also be taken into account when configuring logging. Sensitive data, passwords and access tokens should not end up in log files unless absolutely necessary.