Cybersecurity disciplines evolve rapidly, and NIS2 has transformed a set of best practices into a binding regulatory framework. For thousands of organizations, public and private, the NIS2 Directive, transposed by Legislative Decree 4 September 2024, n. 138, and integrated by the determinations of the National Cybersecurity Agency (ACN), is no longer a recommendation but an operational obligation with imminent deadlines and clear responsibilities. This article explores the basic security measures defined by ACN, providing a practical reference for system administrators and security managers who must translate regulatory requirements into concrete and documented actions.
Reference versions: Legislative Decree 4 September 2024, n. 138 · ACN Determination n. 164179/2025 · ACN Determination n. 379907/2025 · ACN Determination n. 314287/2026 · FNCDP 2025 (v2.1) · documentation consulted in November 2026
NIS2 ACN Security Measures in 60 seconds
NIS2 compliance requires a structured approach. Here are the essential steps:
# 1. Identify critical assets and the NIS perimeter
# Search for unmanaged or uninventoried assets falling within the NIS2 perimeter.
# Example: Identify recently modified and unregistered file systems for critical assets
find /var/www/html -type f -mtime -7 -print # Search for files modified in the last 7 days
# 2. Review and formalize governance
# Ensure key documents are board-approved and training is planned.
# Example: Verify the existence of a training plan for the board.
# (This is a documentation process, not a direct CLI command)
# 3. Implement robust access controls (MFA, privilege management)
# Remove inactive or unnecessary accounts to reduce the attack surface.
# Example: Find user accounts without login for over 90 days
awk -F: '($3 >= 1000 && $3 < 60000) {print $1}' /etc/passwd | while read user; do
lastlog -u $user | grep -q "Never logged in" || lastlog -u $user | awk '{print $NF}' | grep -q '^[0-9]' || (
days_since_last_login=$(date -d "$(lastlog -u $user | awk '{print $NF,$5,$6,$7}')" +%s)
current_date=$(date +%s)
diff_days=$(( (current_date - days_since_last_login) / 86400 ))
if [ $diff_days -gt 90 ]; then
echo "User $user has not logged in for $diff_days days."
fi
)
done
# 4. Strengthen backups and continuity plans
# Verify RTO/RPO consistency with NIS service requirements.
# Example: Check the status of backup services.
# systemctl status rsync.service
# 5. Prepare incident management and notification
# Simulate an incident and verify notification times to CSIRT (24h/72h).
# (This is a simulation exercise, not a direct CLI command)
# 6. Evaluate supply chain security
# Identify and assess risks introduced by third-party vendors.
# (This is an analysis and audit process, not a direct CLI command)
The NIS2 Directive (EU) 2022/2555, transposed into national law with Legislative Decree 4 September 2024, n. 138 [2], has redefined the perimeter of national cybersecurity, imposing stringent obligations on a vast number of public and private entities. The National Cybersecurity Agency (ACN) has further detailed these requirements with specific determinations, particularly n. 164179/2025, which defines basic security measures and types of significant incidents [5][12]. For IT managers and sysadmins, the challenge is not only to understand the regulations but to translate them into concrete operational actions. This article provides an overview of the required basic security measures, organized according to the National Framework for Cybersecurity and Data Protection (FNCDP) 2025 edition (v2.1) [9], and indicates crucial responsibilities and timelines for adaptation.
Prerequisites
Before implementing the measures, it is essential that the organization has completed the following steps:
- Self-identification: Verify whether the organization falls within the scope of essential or important entities according to the size and sectoral criteria in Annexes I, II, III, and IV of Legislative Decree 138/2024 [1].
- Registration on the ACN Portal: Identified entities must register on the ACN Portal, designating a NIS contact point, according to the procedures defined by ACN Determination 314287/2026 [6][10].
- Communication of Qualification: Await official communication from ACN regarding inclusion in the list of essential or important entities, which triggers the deadlines for fulfilling the measures [1].
Who must apply them: essential and important entities
The national NIS2 legislation significantly extends the scope of application compared to the previous directive, involving a wide range of public and private entities. These operate in key sectors such as energy, transport, digital infrastructure, healthcare, and essential public services, provided they exceed specific size thresholds (medium or large enterprises). Micro and small enterprises are generally excluded, except for specific exceptions [1].
The distinction between “essential entities” and “important entities” is crucial. The former, operating in highly critical sectors or playing strategic roles (e.g., central administrations, public communication network providers), are subject to a more stringent supervisory regime and higher penalties. Important entities, while under a less intense supervisory regime, must still implement basic security measures, with deadlines for the first round set for October 2026 [5].
The basic security measures for important entities are listed in Annex 1 of ACN Determination 164179/2025, while for essential entities, Annex 2 applies, which includes additional and more stringent requirements [5][12]. It is important to note that 27 measures have identical requirements for both categories, demonstrating a common core of fundamental controls [12].
Governance: roles, responsibilities, and training
Article 23 of Legislative Decree 138/2024 places administrative and management bodies at the center of responsibility for cybersecurity [4][12]. This means that NIS2 compliance is not merely a technical issue delegable to IT, but a strategic obligation involving the corporate board. Responsibility for violations falls on senior management, even in the presence of operational delegations [4].
Administrative bodies, NIS contact point, and delegations
Administrative and management bodies must approve the methods for implementing risk management measures, oversee their execution, and ensure that cybersecurity training is adequately disseminated [4]. The NIS “contact point,” whose designation is governed by ACN Determination 314287/2026, serves as the operational interface with ACN, overseeing the implementation of obligations but not assuming ultimate responsibility [6].
Governance documents to be approved and their content
ACN guidelines and FAQs specify the documents requiring formal board approval [4][12]:
- Cybersecurity Organization (GV.RR-02): defines roles, responsibilities, and processes.
- Cybersecurity Policies (GV.PO-01): establishes principles and rules.
- Risk Assessment (ID.RA-05): identifies threats and vulnerabilities.
- Risk Treatment Plan (ID.RA-06): defines mitigation actions.
- Vulnerability Management Plan (ID.RA-08): describes the identification and remediation process.
- Adaptation Plan (ID.IM-01): schedules the implementation of measures.
- Business Continuity Plan (ID.IM-04): ensures service resilience.
- Training Plan (PR.AT-01): defines training content and recipients.
For a system administrator, drafting these documents requires not only technical competence but also the ability to translate complex concepts into language comprehensible to management, ensuring they are based on updated risk analyses and consistent with ACN specifications. Read also: GDPR System Admin: Role, Obligations & Compliance
Board and employee training
Article 23 requires management bodies to undergo cybersecurity training and to promote regular and consistent training for all employees [4][12]. This training must enable them to identify risks and evaluate risk management practices, aligning awareness at all levels of the organization. This obligation is an opportunity to elevate the corporate security culture.
Asset and risk management
ACN’s basic security measures apply to all information and network systems used by the organization [12]. Effective management of these elements begins with clear identification and risk assessment.
Asset inventory and NIS perimeter
An accurate asset inventory is the foundation for NIS2 security. It must include physical and virtual infrastructures, applications, databases, network devices, and cloud services, with particular attention to those which, if compromised, could cause significant incidents [9][12]. The FNCDP, in the IDENTIFY function, guides the structuring of this inventory, which must be dynamic and integrated with configuration management tools.
An effective inventory is not just a static list, but a living database that includes:
- Unique identifiers (hostname, IP, UUID)
- Owners and responsible parties
- Criticality classification (impact on NIS services)
- Dependencies on other assets or services (internal and external)
- Location (on-premise, cloud provider, data center)
- Basic configuration and patch status
For essential entities, the granularity of the inventory may require additional details, such as national impact classifications or tracking complex dependencies in the digital supply chain [12].
Risk assessment and risk treatment process
The “Risk Assessment” (ID.RA-05) and the “Risk Treatment Plan” (ID.RA-06) are fundamental documents, approved by the board, that guide the implementation of measures [4][12]. The risk assessment must be regular, identifying threats, vulnerabilities, likelihood of occurrence, and potential impact on NIS assets and services. The treatment plan must then define strategies for mitigating, accepting, transferring, or avoiding risk [9].
A common mistake is to perform a one-off risk assessment. NIS2, aligning with best practices, requires a continuous process that adapts to technological changes and the evolving threat landscape. Read also: NIS2 Compliance: Obligations for EU Businesses
Vulnerability management and adaptation plan
The “Vulnerability Management Plan” (ID.RA-08) and the “Adaptation Plan” (ID.IM-01) are essential for a proactive approach to security [4][12]. The first describes how the organization identifies, classifies, prioritizes, and remediates vulnerabilities (e.g., through periodic scans, security bulletin analysis). The second, instead, outlines the path to achieving compliance with ACN basic specifications, planning infrastructural interventions, updates, and implementation of new controls.
An example of vulnerability management can include the use of scanning tools and the definition of patching windows:
# Example: vulnerability scanning with Nmap (for informational purposes only, in test environments)
# nmap -sV --script vuln <target_IP>
# Example: security update on a Debian/Ubuntu system
sudo apt update && sudo apt upgrade -y
sudo apt autoremove --purge -y
The trap to avoid is considering vulnerability management as a simple patch installation. It is a cyclical process that requires constant monitoring, analysis of new threats (e.g., CISA KEV), and integration with the risk management process.
Access control and authentication
Access management is one of the cornerstones of cybersecurity. NIS2 basic measures require stringent control over who can access what and how [5][12].
Multi-factor authentication (MFA) and privileged account management
Implementing multi-factor authentication (MFA) is a fundamental requirement to protect access, particularly privileged access [12]. MFA drastically reduces the risk of account compromise, even in the event of credential theft. Privileged account management requires special attention:
- Principle of least privilege: Assign only strictly necessary permissions.
- Separation of duties: Prevent a single user from having complete control over a critical process.
- Monitoring: Log and analyze privileged account activity.
- Just-in-Time Access: Grant privileged access only for the strictly necessary time.
Inactive accounts represent a vulnerability. It is good practice to identify and disable/remove them periodically. A Linux command to find accounts that have not logged in for 90 days was provided in the “In 60 seconds” section.
Network segregation (VLAN) and system hardening
Network segregation, typically via VLANs, is an essential measure to limit the propagation of an attack [12]. Dividing the network into logical segments (e.g., user network, server network, DMZ network, OT network) reduces the attack surface and allows specific security controls to be applied to each segment. Read also: Network Microsegmentation: VLANs & Firewalls in Production
Hardening operating systems and applications is equally critical. This includes:
- Removal of unnecessary services and software.
- Secure configuration of system parameters.
- Timely application of security patches.
- Use of host firewalls (e.g., UFW on Linux) to limit connections.
An example of basic UFW configuration on Ubuntu:
sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow ssh # Allows SSH connections
sudo ufw enable
Backup, continuity, and recovery
Operational resilience is a pillar of NIS2. Basic measures require a solid backup strategy and well-defined continuity and recovery plans [12].
Business Continuity Plans (BCP) and Disaster Recovery Plans (DRP)
The “Business Continuity Plan” (ID.IM-04) and the “Disaster Recovery Plan” are key documents outlining procedures to ensure the availability of NIS services even in the event of a serious incident [4][12]. These plans must define:
- Recovery Time Objective (RTO): The maximum acceptable time to restore a service.
- Recovery Point Objective (RPO): The maximum amount of data willing to be lost.
- Roles and responsibilities of the response team.
- Detailed procedures for system and data recovery.
- Internal and external communication strategies.
It is crucial that these plans are tested regularly. An untested plan is an ineffective plan. Read also: Backup 3-2-1-1-0: Rule Explained with Real Example
Tested backup and recovery strategies
Backups must be performed regularly, consistent with RPO and RTO, and stored in secure, isolated locations [12]. The 3-2-1 backup rule is a good starting point (3 copies of data, on 2 different media, with 1 copy off-site). Even more important is testing the recovery process. Many organizations discover their backups are invalid only when they desperately need them. This is a mistake NIS2 aims to prevent.
Incident management and notification
The ability to detect, analyze, and respond to cybersecurity incidents is a central requirement of NIS2, with specific notification obligations to CSIRT [3][12].
Incident detection, analysis, and response processes
ACN measures require the implementation of structured processes for incident management, which include [12]:
- Detection: Use of SIEM, EDR, log monitoring to identify anomalies.
- Analysis: Assessment of impact, root cause, and extent of the incident.
- Containment: Isolation of compromised systems to prevent propagation.
- Eradication: Removal of the threat.
- Recovery: Restoration of systems and data.
- Post-mortem: Analysis of lessons learned to improve security.
An example of log monitoring with journalctl for failed authentication events:
journalctl _COMM=sshd | grep "Failed password"
Notification obligations to CSIRT (24h/72h)
Notification of significant incidents to CSIRT has been fully operational since January 1, 2026. Timelines are strict:
- Within 24 hours: Initial notification after becoming aware of the incident.
- Within 72 hours: Update of the notification, with a preliminary assessment of the incident and indication of any cross-border compromises.
- Within 1 month: Detailed final report on the incident, its causes, and the remediation measures adopted.
ACN Determination 379907/2025 specifies the types of basic significant incidents to be notified [3]. Timeliness and accuracy of information are crucial to avoid penalties and contribute to national security.
Vendors and supply chain
Digital supply chain security is a critical aspect of NIS2. Article 24 of Legislative Decree 138/2024 requires considering risks arising from suppliers and service providers [2].
Assessment of third-party vendor risks
Organizations must identify and assess cybersecurity risks associated with their providers of digital products and services, particularly those supporting critical NIS services [12]. This includes:
- Due diligence: Evaluation of vendor security maturity before contract signing.
- Contractual requirements: Include security clauses, incident notification obligations, and audit rights in contracts with vendors.
- Continuous monitoring: Periodically verify vendor compliance with security requirements.
The trap here is to completely delegate security to the vendor. Ultimate responsibility remains with the NIS entity, which must ensure its vendors meet adequate standards. Read also: SSH Hardening Linux: Complete Guide 2026 (10 Critical Settings)
Security of digital products and services
ACN measures require considering the security of digital products and services used, including software, hardware, and cloud services. This implies verifying compliance with security standards, analyzing known vulnerabilities, and adopting secure development practices by vendors [12].
How to document compliance
Documentation is a key element of NIS2 compliance. It’s not enough to implement measures; you must demonstrate it.
Evidence of compliance and records
Each basic security measure must be supported by documentary evidence demonstrating its implementation and effectiveness. These may include:
- Approved policies and procedures.
- Risk assessment reports and treatment plans.
- System and security logs.
- Records of maintenance and patching activities.
- Audit and vulnerability scan reports.
- Vendor certifications and attestations.
- Personnel and board training records.
ACN Determination 314287/2026 also establishes the methods for recording and updating information on the ACN Portal, which constitute a further form of formal documentation [6][10].
Common Errors and Troubleshooting
| Exact Error or Message | Cause | Solution |
|---|---|---|
| “NIS2 is only for large companies” | Misinterpretation of size and sectoral criteria. | Carefully check the annexes of Legislative Decree 138/2024 and ACN FAQs on sectors and size thresholds. Many SMEs might be included. |
| “I delegated everything to IT/Consultant” | Lack of involvement of administrative and management bodies. | Administrative bodies retain responsibility. Ensure they approve key documents and participate in training. |
| “My backups work, no need to test them” | Lack of periodic testing of recovery plans. | Backups must be regularly tested to verify their integrity and ability to restore within defined RTO/RPO. |
| “I don’t have an updated asset inventory” | Underestimation of the importance of inventory for risk management. | Implement a continuous asset discovery and management process integrated with monitoring and security tools. |
| “I don’t know what to notify CSIRT” | Lack of knowledge of significant incident types. | Refer to Annexes 3 and 4 of ACN Determination 164179/2025 and Determination 379907/2025 for definitions of significant incidents. |
Frequently Asked Questions
What is the difference between essential and important entities for NIS2 purposes?
Essential entities operate in highly critical sectors (e.g., energy, transport) and exceed the size parameters of medium-sized enterprises, or hold specific roles (e.g., central administrations). They are subject to more stringent supervision. Important entities fall into other sectors and meet the size criteria, with a less intense supervisory regime but significant security obligations.
When do I need to register on the ACN Portal?
Entities that self-identify as falling within the scope of Legislative Decree 138/2024 must register on the ACN platform from January 1 to February 28 of each year following the decree’s entry into force. For the first application, the deadline was February 28, 2025, with some exceptions for specific sectors with earlier deadlines.
What happens if I don’t meet the deadlines for implementing the measures?
Non-compliance with NIS2 obligations can lead to supervisory actions by ACN, including requests for information, inspections, and the adoption of corrective measures. Significant monetary penalties are foreseen, especially for essential entities, and responsibility falls on the administrative and management bodies.
Is the National Framework for Cybersecurity and Data Protection (FNCDP) mandatory?
ACN’s basic specifications are built in close coherence with the FNCDP 2025 (v2.1), which serves as a methodological reference. While not a direct obligation to adopt the Framework, the organization of measures according to the FNCDP functions (Govern, Identify, Protect, Detect, Respond, Recover) is strongly implicit and recommended for compliance.
Do I need to provide specific training to my board?
Yes, Article 23 of Legislative Decree 138/2024 requires administrative and management bodies to undergo cybersecurity training and to promote regular training offerings for employees. The training must be adequate to enable them to understand risks and evaluate risk management practices.
Conclusions with Operational Takeaways
NIS2 is not merely a compliance exercise but an opportunity to elevate an organization’s cybersecurity level. For system administrators and security managers, the operational takeaways are clear:
- Involve the Board: Responsibility is strategic. Ensure administrative bodies are informed, trained, and approve key governance documents.
- Continuous Inventory and Risk Assessment: You cannot protect what you do not know. Maintain an updated asset inventory and conduct regular risk assessments, aligned with the FNCDP.
- Documented and Tested Processes: Every measure must be supported by clear, documented, and regularly tested procedures, from backups to incident management.
- Attention to the Supply Chain: Extend due diligence and security requirements to third-party vendors, which represent a potential entry point for attacks.
- Timely Notifications: Prepare the team and processes to ensure notification of significant incidents to CSIRT within the prescribed time windows (24h/72h/1 month).
NIS2 adaptation is a journey that requires commitment and resources, but one that, if approached with a systematic and proactive strategy, will strengthen the organization’s digital resilience and security.
Sources
- [1] ACN FAQ – NIS2 Procedures
- [2] Legislative Decree 4 September 2024 n. 138 – Normattiva
- [3] ACN Determination 379907/2025 – Obligations for Important Entities
- [4] ACN FAQ – NIS2 Governance
- [5] NIS2: ACN basic security measures explained point by point – Confindustria
- [6] ACN Determination 314287/2026 – ACN Portal and NIS contact point
- [7] NIS Guidelines – Basic Specifications – ACN
- [9] National Framework for Cybersecurity and Data Protection (FNCDP) – ACN
- [10] ACN Note on Determination 314287/2026 – ACN
- [12] ACN Determination n. 164179/2025 – ACN
- [13] Annex 1 ACN Determination 164179/2025 – Measures for Important Entities
- [14] Annex 3 ACN Determination 164179/2025 – Incidents for Important Entities
- [16] CSIRT Italia – Incident Notification Guide
Updated: November 2026