Skip to main content

Guide

Recurring ISMS reports: Plan an API integration instead of full exports

Build useful recurring ISMS reports: data state, API access, retention and failure handling. Distinguish complete Space exports from reporting.

Recurring ISMS reports: Plan an API integration instead of full exports
Julian Köhn
|Read time: 3 minutes

A monthly report does not automatically need every ISMS attachment. It needs information supporting a decision. Separate a complete data export from a recurring management report.

First plan purpose, scope and acceptance. This guide describes an external API integration; Kopexa’s full Space export is currently started manually.

What Kopexa already documents

In Space settings, you can manually start a ZIP data export. One export runs per Space at a time. A finished archive remains available for seven days; a new export removes the previous archive.

That serves a different purpose from permanent report storage. Save and protect required snapshots promptly in an appropriate repository. Test data portability, including attachments and relationships.

Define the report around its recipient

Specify the decision to support. Open risk decisions, overdue measures and changes in agreed KPIs may suffice for a review. A full extract of every record makes interpretation harder.

Define period, cutoff, filters and treatment of missing values. “No data” must not resemble “no open risks”. Our ISMS metrics guide helps with selection.

Design a dependable external workflow

First use the API Playground to check availability of required fields and relationships. Then decide which query an external scheduler can run. A dedicated read-only Space token suits queries; store it in a secrets manager, not the report or source code.

The workflow should produce four separate outcomes: confirmed retrieval, verified completeness, generated report and confirmed storage. Retries must not distribute conflicting report versions accidentally.

Make failures visible

Fictional example: API access has expired. The scheduler starts on time but retrieves no current data. The run must fail and notify an owner. Last month’s report must not appear under a new date.

Also test incomplete pagination, missing permissions and unavailable storage. Record the last successful data import separately from the last execution.

Agree a reporting contract

Before configuring a scheduler, agree the output substantively. A report definition includes:

  • purpose and recipient group;
  • cutoff with time zone and reporting period;
  • affected Spaces and permitted data scope;
  • each metric’s definition, including missing values;
  • an owner for data errors and retention.

Store retrieval time and completeness-check status with every result. Successfully retrieving the first page of a paginated source is not a complete report. If partial retrieval is acceptable, explicitly state its scope in the output.

Do not distort monthly comparisons with new definitions

When a metric changes, the report should identify its definition. “Overdue measures”, for example, may include only active measures or also deferred ones. A decline after changing the filter is not demonstrated improvement.

Kopexa objectives and KPIs can provide a substantive basis. For external reporting, still check which fields and historical states the current API exposes. If something necessary is missing, improve the data model or limit the report first. A plausible number does not replace confirmed retrieval.

Accept before continuous operation

Manually compare one report with the source system. Review roles, retention and access to sensitive content. Start recurring execution afterwards. The management review should support a decision without anyone needing to understand the integration code.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

How do I plan recurring ISMS reports with Kopexa?

Define recipients, metrics, period and completeness checks. Then verify required API fields and configure external retrieval with failure monitoring. The documented complete Space export is started manually and is not a recurring reporting job.

Sources

  1. Space data export — Kopexa [Accessed ]