For county labour offices
ISMS and KSC incidents in a labour office — before the deadline
The office director is personally accountable for implementing the information security management system, and the deadline is 3 April 2027. LS PUPportal guides the office through the KSC Act obligations step by step: an implementation wizard, a requirements catalogue, document templates, training and incident reports within the statutory deadlines.
142
days to the ISMS implementation deadline
3 April 2027
Built for labour offices
How LS PUPportal differs from generic NIS2 tools
Data and AI stay in the office
The system runs on the office's server, without the cloud. The AI assistant uses a language model running in the office network and masks PESEL numbers, e-mail addresses and phone numbers.
ISMS wizard with a plan to 3 April 2027
A dozen or so questions about the office, people, infrastructure and safeguards. Once saved, the system sets the office's KSC status, records the head and the security officer and marks the requirements the office already meets.
Threats typical of a labour office
The risk register with a 5×5 matrix suggests threats matched to labour office assets, and the ICT asset and supplier registers come with a ready security questionnaire.
CSIRT and data protection reports on time
Early warning within 24 h, notification within 72 h and the final report, calculated from the office's KSC status, with e-mail reminders and ready report content in PDF.
Auditor package
A single ZIP archive: compliance score, requirements with evidence, registers, documents in force, review records and audit reports. The director gets a PDF compliance status report.
Active Directory as evidence
The AD Administration module shows inactive accounts, non-expiring passwords, privileged groups and workstation sessions, and records every change in the operations log.
One system for the whole office
KSC next to the modules the office uses every day
LS PUPportal already runs in several county labour offices in the West Pomeranian Voivodeship. The Incidents (KSC) and ISMS modules use the same data as the GDPR authorization register, asset records, contracts, certificates and the PULS and SEWIB archives, with a single login.
Webinar: ISMS in labour offices before 3 April 2027
45 minutes online: the key KSC Act obligations for a labour office, a live demo of the Incidents and ISMS modules and answers to questions. After you sign up, we will send the available dates.
Frequently asked questions
Questions and answers
Is a county labour office subject to the KSC Act?
The amended Act covers public entities, and the status of a given office follows from its self-identification and entry in the register of entities. The entity status (essential, important or public important under Art. 12c) is set in the system once, and the requirements catalogue and reporting deadlines adjust to it automatically.
How can an office buy the system?
Below the Public Procurement Law threshold (PLN 130,000 net), the office buys according to its own procurement rules. We will prepare an offer with a description of the subject of the contract for the selected modules.
What server do we need?
We install the system on the office's server (Windows or Linux). Extra hardware is needed only for the AI assistant, e.g. a virtual machine with 8 vCPU, 16 GB RAM and 40 GB of disk. All other features work without it.
Does the system work with Syriusz and PULS?
Yes. The CV Builder reads data from Syriusz STD, and the PULS archive provides data imported from the PULS system. The KSC and ISMS modules can be bought separately or together with them.
Can we try the system before buying?
Yes. The demo version includes the ISMS dashboard, wizard, requirements catalogue, documents, training and the AI assistant, with registers limited to 3 entries.
Will your ISMS be ready by the deadline?
We will show the Incidents (KSC) and ISMS modules on sample labour office data and help you plan the implementation.
Book a presentation