INFRASTRUCTURE RECORDS AND CYBERSECURITY
Start by knowing what you have and how it connects.
Protecting infrastructure starts with being able to describe it. RackDocs helps organise IT/OT equipment, locations and physical connections — a practical part of preparation for NIS2 and Poland’s KSC requirements.
A straightforward way to start organising asset records.
Instead of assembling the picture from disconnected spreadsheets, start with one location in RackDocs. Link equipment to mounting places, document ports and cables, agree descriptive fields and define an update process. This is a concrete task you can connect with everyday infrastructure maintenance.
NIS2 / KSC
Why does this matter for NIS2 and KSC?
Article 21(2)(i) of the NIS2 Directive includes asset management among cybersecurity risk-management measures. In Poland’s KSC Act, Article 8(1)(2)(m), as amended by the Act of 23 January 2026, also identifies asset management. These are parts of a wider security framework, not a requirement to purchase any particular application.
Start now, with the scope that applies to your organisation.
The KSC amendment entered into force on 3 April 2026. Poland’s Ministry of Digital Affairs identifies 3 April 2027 as the adaptation deadline for entities meeting the criteria when the new provisions entered into force. This is not a universal deadline for every organisation: applicability, scope and relevant transitional rules need to be established for the individual entity first.
Ministry of Digital Affairs — key KSC dates (in Polish) ↗DOCUMENTATION THAT SUPPORTS SECURITY
Connect organisational needs with everyday work.
These examples explain practical documentation support. They are not a complete legal checklist or a compliance assessment.
| The team’s need | How RackDocs helps | What the organisation defines and performs |
|---|---|---|
| Know which equipment exists and where it is installed | Customers, locations, mounting places, racks and device records create a structured infrastructure inventory. | Asset scope, completeness, responsible people and the update process. |
| Describe assets consistently | Types, templates and custom fields hold agreed details, such as a technical contact or criticality classification. | Classification methodology, value definitions and review. Fields do not perform an automatic risk assessment. |
| Understand physical dependencies | Ports, cables, fibre paths, topology and plans show the documented layout. | Physical verification, risk and service impact assessment, including logical dependencies beyond these records. |
| Check that records remain current | QR labels, inventory rounds and result comparisons support field verification. | Review frequency, investigation of discrepancies and approval of updates. |
| Review changes and prepare documentation for assessment | Before-and-after history, reports and available exports help assemble selected information. | Retention rules, evidence scope and assessment of sufficiency. History is not a certified evidence repository. |
| Share documentation with the right people | Roles and customer access assignments help restrict access within the application. | Correct configuration, access reviews and security of the full deployment. |
Practical workflow
Begin with a concrete task instead of postponing the whole project.
- Define scope: choose the first location and equipment to document.
- Agree identifiers, names, custom fields and responsibility for maintaining records.
- Link devices to their places and document relevant ports and connections.
- Verify the records on site and investigate discrepancies.
- Prepare a suitable report and make inventory updates part of change handling and periodic reviews.
Information the team can work with.
inventory and asset records
Inventory support is part of a wider programme.
RackDocs does not automatically ensure NIS2 or KSC compliance or issue a compliance certificate. The organisation must separately address applicability, its ISMS and risk assessment, policies, incident handling and reporting, continuity, backups, training and the effectiveness of safeguards. The full asset scope can also include information, software and cloud services beyond physical infrastructure records.
This page describes product use and general legislative context. Determine obligations and their implementation for the individual organisation.
Security and audit teams — Explore the scenario →Sources and information currency
Legal information checked: 6 November 2026. Review current legislation and official guidance before making decisions.
THE EASIEST WAY TO EXPLORE RACKDOCS
See how to start organising your inventory.
In around 30 minutes, we will show example assets, connections and data verification. No installation or customer data required. You can mention NIS2/KSC preparation as the topic for the meeting.