Skip to main content

Guide

ISMS software for critical infrastructure: Assess critical services and dependencies

Assess ISMS software for critical infrastructure: installation context, protection needs, attack detection and evidence with clearly separated scopes.

ISMS software for critical infrastructure: Assess critical services and dependencies
Julian Köhn
|Read time: 3 minutes

A central identity service supports both administration and a critical installation. If recorded only as a general IT service, its effect on essential service delivery can disappear from the ISMS.

Assess ISMS software starting with the essential service. Three tests show whether shared services, maintenance exceptions and installation changes remain traceable through to affected safeguards.

Scope starts with the service

First describe the relevant service and affected installation scope. Then trace necessary processes, information, systems and external services. An organisation chart differs from a dependency model: one central service may be needed across several organisational boundaries.

Germany’s BSIG provisions contain special requirements and sectoral distinctions. Clarify the applicable evidence procedure and methodology before selection. A vendor claim of “suitable for critical infrastructure” is too vague.

Distinguish protection needs from outage consequences

An information asset can have high protection needs without requiring constant availability. Conversely, a technical service can be time-critical for operations. Assess protection requirements analysis and BIA as related but distinct evaluations.

Kopexa provides information assets, other assets and their dependencies, protection requirements analysis and guided BIA. Selection should reveal how a model change is substantively assessed. Recording a dependency is insufficient if nobody reviews the consequences for measures.

Use this template in these measures

Implementation measure

Handle and review security incidents

Mapped requirements (3)
  • A.5.26 · Reaktion auf Informationssicherheitsvorfälle (DE)

    Supporting contribution

    The guidance connects coordinated response, records, communication, handover and reasoned closure in the existing case. The organisation provides suitable competence, technical interventions and actual results.

  • A.5.27 · Erkenntnisse aus Informationssicherheitsvorfällen (DE)

    Supporting contribution

    Review connects causes, types, frequency and costs to changes in risks, safeguards, procedures and briefings and their effect. An archived review alone is insufficient.

  • A.5.28 · Sammlung von Beweismaterial (DE)

    Supporting contribution

    The work connects authority, preservation suitable for the medium and state, origin, integrity checks, protected storage and traceable transfers. Competent acquisition and case-specific legal admissibility still require checking.

Further framework mappings of this measure
  • TISAX · 1.6.2

    VDA ISA 6.0.3 · Partial contribution

    Coordinated handling, reasoned prioritisation, communication and learning contribute to managing reported events. Other applicable categories, protection-need additions, partner responses and organisational requirements remain to be addressed.

    Read the source ↗

Implementation measure

Maintain security contacts and use threat intelligence

Mapped requirements (3)
  • A.5.5 · Kontakt mit Behörden (DE)

    Supporting contribution

    The workflow establishes relevant authorities, triggers, ownership and official usable routes, maintains them and uses authority information to understand expectations. Actual contact and reporting follow the circumstances.

  • A.5.6 · Kontakt mit speziellen Interessengruppen (DE)

    Supporting contribution

    Maintained specialist contacts enable relevant information flow, exchange and support. Significant findings reach the responsible roles; no mandatory membership catalogue is required.

  • A.5.7 · Bedrohungsintelligenz (DE)

    Supporting contribution

    Information needs, suitable internal and external sources, preparation and contextual analysis produce understandable actionable intelligence. Strategic, tactical and operational perspectives and use in risks, safeguards and testing are included.

Implementation measure

Prepare and exercise incident readiness

Mapped requirements (3)
Further framework mappings of this measure
  • TISAX · 1.6.1

    VDA ISA 6.0.3 · Partial contribution

    Reachable staffed reporting and feedback routes are prepared and exercised with actual roles. Awareness, usable internal and external channels and applicable protection-need additions still require checking.

    Read the source ↗
  • TISAX · 1.6.2

    VDA ISA 6.0.3 · Partial contribution

    The work prepares classification, responsibilities, suitable response objectives, escalation and communication and exercises the decision route. It does not demonstrate actual handling, specific reporting obligations or all applicable protection-need and testing requirements.

    Read the source ↗

Implementation measure

Prepare IT emergency response and recovery

Mapped requirements (3)
  • A.5.30 · IKT-Bereitschaft für Business Continuity (DE)

    Supporting contribution

    Prepared service cards connect BIA objectives with responsibilities, dependencies, recovery and planned exercises. Suitable infrastructure, competence and actual testing must still be implemented in operation.

  • A.5.29 · Informationssicherheit bei Störungen (DE)

    Supporting contribution

    The plan defines safeguards, approved alternative controls and security checks during emergency operation. Their suitability and actual application must still be verified.

  • A.8.13 · Sicherung von Informationen (DE)

    Supporting contribution

    The existing service workflow connects required backups, protected copies, monitored execution and safe regular restore tests to business requirements.

Further framework mappings of this measure
  • TISAX · 5.2.8

    VDA ISA 6.0.3 · Partial contribution

    Activation, alternative communications, accessible recovery procedures and planned testing support continuity planning. Applicable protection-need additions, technical implementation, partner coordination and actual test results must still be addressed separately.

    Read the source ↗

Three situations a demo should handle

Shared service: Trace the central identity service to the critical service. The relationship must not disappear because another department owns it.

Restricted maintenance window: A necessary technical change cannot be deployed immediately. Record interim safeguards, the decision and review date. “Open” must show responsible handling beyond a red status.

Installation modification: A system is replaced. Check which information assets, assessments and evidence remain valid and which need reconsideration. Earlier documentation should stay traceable.

What Kopexa connects

BPMN processes can describe operational approvals and handovers. Risks are treated through measures; evidence belongs to those measures, which are mapped to controls. This connects an operational intervention with its security requirement. The Kopexa ISMS software page shows how this works day to day.

The platform replaces neither installation control nor technical attack detection. Their results and ensuing work need to enter a defined workflow. A management review should derive decisions about resources and residual risks from it.

Procurement and maintenance belong together

Check the specific procedure needed, catalogue versions, evidence formats, roles and export. After initial setup, have an employee update an installation change themselves. If every change requires external modelling, include that effort in the calculation.

Implementation responsibilities should therefore be established during the pilot. Use Kopexa’s guided trial for one critical service and a few selected dependencies. Acceptance should show whether operations and the information security officer can identify the next measure from the same data.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

Does ISMS software replace technical attack detection?

No. It can organise responsibilities, requirements and evidence. Detection and response require suitable technical and organisational procedures.

Sources

  1. BSIG section 28: Scope — Bundesministerium der Justiz [Accessed ]