Public Sector IT Security Audit
Poland's National Interoperability Framework (KRI) regulation requires public entities to run an internal information security audit at least once a year (§ 19(2)(14)). We audit against the KRI requirements and ISO/IEC 27001, deliver compliance reports with findings, and help with remediation. Meet the legal obligation and have the evidence ready for a NIK inspection.
Describe your scope — your account manager will reply within 24 hours.
- Custom quote

What is a Public Sector IT Security Audit?
A Public Sector IT Security Audit is a compliance-focused review of security policies, access controls, backups, encryption, and technical safeguards for government agencies, municipalities, schools, and hospitals in Poland, which the National Interoperability Framework (KRI) regulation requires to run an internal information security audit at least once a year (§ 19(2)(14), Journal of Laws 2024, item 773). nFlo delivers an audit report with a prioritized list of non-conformities, a remediation plan, and documentation ready for government inspections — covering the gaps that recur most often in public entities: outdated security policies, unpatched systems, weak password rules and untested backups.
Contact your account manager
Discuss Public Sector IT Security Audit with your dedicated account manager.

Missing security audit = legal compliance violation
Comprehensive security audit compliant with regulations
Documentation Audit
Review of policies, procedures, system documentation
Security Verification
Technical controls: firewall, backup, encryption
Remediation Plan
Specific corrective actions with priorities
NIK inspections: 7 in 10 offices had skipped the mandatory audit
A public-sector security audit is governance, risk and compliance with a statutory clock on it: the obligation to audit periodically exists whether or not anyone in the office is thinking about cybersecurity, and the inspection asks for evidence, not intentions.
A missing annual audit is the single most common finding of Poland’s Supreme Audit Office (NIK) in local government. In its 2019 audit NIK examined 23 local-government offices (nine county offices and 14 municipal offices): in 16 of 23 (70%) the mandatory annual information security audit had not been carried out in 2017, contrary to what is today § 19(2)(14) of the KRI regulation (NIK report, May 2019). Six years on the picture is unchanged: covering 1 January 2023 to 20 September 2024, NIK examined 24 units (17 municipal offices and seven county offices) and found that in 9 of 24 the mandatory annual audit had either not been carried out or had been carried out unreliably (NIK statement of 17 April 2025).
Without security audit:
- Violation of the annual audit obligation (KRI § 19(2)(14))
- An irregularity in NIK’s post-inspection statement, naming the persons responsible for it - Art. 53(1)(4) of the Act on the Supreme Audit Office (NIK), consolidated text Journal of Laws 2022, item 623
- Lack of awareness about security gaps in systems: untested backups, weak passwords, missing patches
- Conclusions on removing the irregularities, to be implemented and reported back (Art. 53(1)(5)); the Act provides no fine for the irregularities found - the only fine in the Act, Art. 48, concerns a witness who fails to appear when summoned
Audit Compliant with Regulations + Support in Fixing Non-Conformities
We don’t leave you with just a report. We help fix discovered non-conformities and prepare documentation for future inspections.
What you get:
- Audit compliant with the KRI regulation (§ 19)
- Verification of IT system security controls
- Review of policies, procedures, security documentation
- Audit report with list of non-conformities and severity ratings
- Remediation plan with specific corrective actions
- Support in removing non-conformities (optional)
- Documentation ready for inspectors and auditors
Who Is It For?
This service is for you if:
- You’re a public sector organization (government agency, municipality, school, hospital)
- You must meet the KRI obligation of an internal information security audit at least once a year (§ 19(2)(14))
- You’re preparing for government inspection or external audit
- You want to verify IT system security
- You lack internal resources to conduct the audit
Regulatory Framework
Poland’s National Interoperability Framework (KRI)
Regulation of the Council of Ministers of 21 May 2024 on the National Interoperability Framework, minimum requirements for public registers and electronic information exchange, and minimum requirements for ICT systems (Journal of Laws 2024, item 773), in force since 23 May 2024. It applies to every entity performing public tasks in Poland and requires it to:
- establish, operate, monitor and improve an information security management system (§ 19(1));
- ensure, among other measures, a periodic internal information security audit at least once a year (§ 19(2)(14));
- the requirements are deemed met when the ISMS is built on PN-ISO/IEC 27001 and audited according to the related Polish Standards (§ 19(3)).
Audit Frequency
- At least once a year - statutory minimum (§ 19(2)(14))
- After significant changes - new system, migration, incident
- Before inspections - government audits, external reviews
Audit Scope
1. Security Management
- Security Policy - does it exist, is it current
- Procedures - access control, backup, incident management
- Roles and Responsibilities - administrator, DPO, users
- Awareness - IT security training
2. Technical Controls
- Access Control - authentication, passwords, permissions
- Firewall - network separation from internet
- Antivirus - malware protection, updates
- Backup - backup copies, restore testing
- Encryption - sensitive data, disks, communication
- Patching - security updates for systems
3. Physical Security
- Server Room - access control, climate, UPS
- Workstations - theft protection
- Media Destruction - disk and document disposal procedures
4. Business Continuity
- Continuity Plan - BC/DR plan
- Backup - frequency, retention, restore testing
- Redundancy - critical systems
5. Legal Compliance
- GDPR - personal data protection compliance
- KSC (Poland’s NIS2 transposition, in force since 3 April 2026, Journal of Laws 2026, item 252) - essential and important entities; public universities are important entities under Annex 2
- Sector-specific regulations - healthcare, education, etc.
Common Non-Conformities in Public Sector
Based on our audits, most common issues:
- Missing or outdated security policy - 80% of organizations
- Weak passwords - no complexity requirements, no rotation - 70%
- Excessive permissions - all admins have full access - 65%
- Irregular backups - or no restore testing - 60%
- Outdated software - missing security patches - 75%
- No event logging - nothing to review after incident - 50%
- No contingency plan - what to do when server fails - 55%
What’s in the Report
Compliant audit report contains:
- Executive Summary - summary for management
- Audit Scope - audited systems and areas
- Methodology - standards used (ISO 27001, NIST, CIS)
- Findings - list of non-conformities with severity (Critical/High/Medium/Low)
- Risk Assessment - risk evaluation for each finding
- Remediation Plan - specific corrective actions
- Annexes - checklist, screenshots, documents
Related Glossary Terms
Learn more about key concepts related to this service:
How we work
Our proven service delivery process.
Scope Definition
Define systems covered by mandatory audit
Documentation
Review policies, procedures, regulations
Technical Verification
Control verification: access, backup, encryption
Report
Audit report with list of non-conformities
Support
Assistance in removing non-conformities
Benefits for your business
What you gain by choosing this service.
Legal Compliance
Meet the mandatory annual audit requirement (KRI § 19)
Better Security
Identify and fix security gaps
Inspection Ready
Documentation ready for auditors
No NIK Findings
Missing audit = an irregularity in NIK's post-inspection statement
Related Articles
Expand your knowledge with our resources.
GRC (governance, risk, compliance): how to combine them in one cybersecurity process
The legal team keeps a list of NIS2 requirements, the security team a risk register and IT a catalogue of policies. Each table is complete, but none refers to the others. GRC combines governance, risk and compliance into one decision-making process, and NIS2, the Polish KSC Act and DORA assign responsibility for risk to senior management.
Read more →AI security best practices: an enterprise risk and control map for CISOs
The language model is rarely the weakest link. More often it is an API key in a repository, an assistant that can read all of SharePoint, or a vendor whose contract nobody read. Here is how to cover AI security with the cybersecurity controls you already have — domain by domain.
Read more →Microsoft 365 Copilot security: oversharing, permissions and labels
Copilot does not break permissions — it exposes them. If the payroll folder is shared with the whole company, the assistant will summarise it in seconds. Here is how to put permissions, labels, DLP and auditing in order before Copilot reaches your users.
Read more →Frequently Asked Questions
Common questions about Public Sector IT Security Audit.
How often must a public sector security audit be conducted?
At least once a year. § 19(2)(14) of Poland's National Interoperability Framework (KRI) regulation (Journal of Laws 2024, item 773) sets this as the statutory minimum. In practice, also audit after significant changes in IT systems and before an expected government inspection.
How long does the audit take and what exactly do you check?
The audit takes 2-4 weeks. We check security policies, access control (passwords, permissions), technical safeguards (firewall, antivirus, encryption), backup and restore testing, server room physical security and GDPR compliance.
Do you help fix the non-conformities found after the audit?
Yes. The report contains a prioritized remediation plan with specific corrective actions. Optionally, we support the implementation of fixes - from updating security policies to configuring technical safeguards.
What are the most common non-conformities in public sector organizations?
From our audits: outdated security policy (80% of organizations), weak passwords without complexity requirements (70%), excessive administrator permissions (65%), irregular backups without restore testing (60%) and missing security patches (75%).