Back to Articles

EASM

When CSIRT Italia tells you a service is exposed: what to do in the first 24 hours

11 min read

In 2025 CSIRT Italia reported 31,050 at-risk devices and services and 10,312 potentially compromised ones to their owners. What a notice means, an hour-by-hour plan for the first 24 hours, the 15-day rule for some entities, and how to stop being surprised.

csirt-italia
acn

Every month, thousands of Italian organisations receive an email they did not expect: CSIRT Italia, the national computer security incident response team within the National Cybersecurity Agency (ACN), has found one of their devices or services exposed on the internet with a known vulnerability, or behaving as if it were already compromised. ACN's annual report on 2025, transmitted to Parliament in May 2026, puts numbers on this activity for the first time in such detail, and the monthly summaries published since show it growing. This article explains what such a notice means and gives a practical plan for the first 24 hours, written for IT managers who have received one or will. The same logic applies to notices from other national CSIRTs and from security researchers. If the notice turns into an incident, our guide to NIS2 incident reporting covers the deadlines.

Key Takeaways

  • In 2025 CSIRT Italia reported 31,050 at-risk devices and services to their owners (7,545 communications, 72% to private organisations) and 10,312 potentially compromised ones (486 communications, 88% to private organisations).
  • "At risk" and "potentially compromised" are different notices. The first means a vulnerable exposure; the second means activity associated with malicious behaviour has already been seen. Treat the second as an incident.
  • For public administrations and some regulated operators, Law 90/2024 sets a deadline: the remediation indicated in a specific ACN vulnerability notice must be adopted without delay and in any case within 15 days.
  • Patching is not the end. If the service was exposed during an exploitation window, check for compromise before you close the ticket.
  • The best notice is the one you never receive, because you found and closed the exposure first.

What ACN's annual report says

The ACN report on its 2025 activity (Camera dei Deputati, Doc. CCXVIII n. 5) counts 2,729 cyber events handled by CSIRT Italia, an average of 227 a month and about 38% more than in 2024, and 615 incidents with confirmed impact, up about 7%. There were 3,907 victims, 1,901 of them unique; unique victims rose by more than 50%. ACN attributes the gap between the growth of events and the slower growth of incidents partly to its preventive alerting.

That alerting is large. In 2025 CSIRT Italia sent 46,867 communications to the organisations it monitors, published 738 alerts and bulletins on its public portal and 804 on its reserved services portal, and shared more than 5,800 specific vulnerability notices under Law 90/2024. Its proactive monitoring of Italian systems produced:

CategoryDevices and servicesCommunications sentPublic / private
At risk (for example, vulnerable software versions)31,0507,54528% / 72%
Potentially compromised (activity associated with malicious behaviour)10,31248612% / 88%
Phishing web addresses targeting Italian organisationsabout 2,457reported to over 1,000 organisations

According to the report, the highest numbers of vulnerabilities among the at-risk devices and services were in network devices and firewall and proxy solutions, followed by cybersecurity and data protection systems and remote-work technologies, with further concentrations in collaboration platforms, email, file sharing and virtualisation.

The pace has not slowed in 2026. ACN's operational summary for August 2026, as reported by ICT Security Magazine, records exposed at-risk services rising from 3,210 in July to 9,121 in August, after an alert on a cPanel flaw, with 2,666 communications to the organisations concerned, 82% of them private companies.

What a notice is, and what it is not

A CSIRT notice tells you that, from the outside, a specific IP address, hostname or service appears to be exposed with a problem: a vulnerable version, a service that should not be public, or traffic consistent with a compromise. It is not an accusation and it is not an audit. It is also not complete: the CSIRT sees what it can see from the internet, at one moment. It may not know that the address now belongs to someone else, or that three other systems share the same weakness.

Two practical points before you start. Verify that the message really comes from CSIRT Italia's official channels; if in doubt, use the contacts published on the official ACN and CSIRT Italia websites, never the links or numbers in the message itself. And for public administrations and certain regulated operators, Article 2 of Law 90/2024 requires the remediation indicated in a specific ACN vulnerability notice to be adopted "without delay and in any case within fifteen days", unless technical or organisational reasons are promptly communicated to ACN. Check whether your organisation is in that list.

The first 24 hours, step by step

Hour 0 to 1: ownership and current exposure

  • Is the asset ours? Map the IP or hostname to a system, a site, a supplier or a cloud account. Addresses change hands; services managed by suppliers are still yours to answer for.
  • Who owns it? Name one person responsible for the asset and one for the response.
  • Is it still exposed? Check from outside your network whether the service still answers and which version it reports.
  • Which type of notice is it? At risk, or potentially compromised. The second changes everything that follows.

Hour 1 to 4: contain without destroying evidence

  • Reduce exposure first: restrict access with an allow-list, move the service behind a VPN or disable it if it is not needed.
  • Apply the vendor's mitigation if a patch cannot be installed immediately.
  • Before rebooting or reinstalling, preserve evidence: logs, configuration, and if possible a snapshot of the system. A reboot can erase exactly what you will need to understand what happened.

Hour 4 to 12: vulnerable, or already compromised?

This is the step most often skipped. A vulnerable service that was reachable during an exploitation window may already have been used. Check the vendor's indicators of compromise and integrity tools, look for new accounts, unexpected configuration changes, web shells, scheduled tasks, unusual outbound connections and gaps in the logs. If the notice was "potentially compromised", or you find any of these signs, treat it as an incident and follow your incident response plan.

Hour 12 to 24: fix, rotate, document, decide

  • Install the fix or upgrade, then verify from the outside that the problem is really gone.
  • Rotate credentials, keys and certificates stored on or used by the system.
  • Write a short timeline: when the notice arrived, what you found, what you did and when.
  • Reply to CSIRT Italia if it asked for feedback.
  • Decide on notifications. If you are a NIS entity and the event qualifies as a significant incident, D.Lgs. 138/2024 requires an early warning to CSIRT Italia within 24 hours of becoming aware of it and a notification within 72 hours. If personal data were affected, GDPR requires notifying the Garante within 72 hours unless the breach is unlikely to result in a risk.

After the first day: one system is rarely alone

A notice describes one address. The weakness behind it is usually a pattern: the same appliance model at three branches, the same CMS plugin on five sites, the same forgotten management interface copied from a template. Search for the same product and version across your whole perimeter, not only the one address you were told about. Our article on exposed management interfaces shows how often the root cause is exposure rather than a single bug.

Prepare before the notice arrives

Most of the first hour is lost to questions that could have been answered in advance. A one-page runbook removes them:

  • A monitored contact address. Make sure the address CSIRT Italia has for you, and the abuse contact registered for your IP ranges and domains, reach someone who reads them every working day, not a former employee.
  • An asset register that maps addresses to owners. For every public IP and hostname: the system, the business owner, the technical owner and, if a supplier runs it, the supplier's emergency contact.
  • Pre-agreed emergency changes. Decide in advance who can take an exposed service offline or restrict it without waiting for a change board.
  • Logs that last. Keep logs from edge devices and exposed servers off the device and for long enough to look back at least several weeks.
  • Supplier clauses. Managed firewalls, hosting and websites are often run by third parties. Their contracts should say how fast they act on a CSIRT notice that concerns you.

Stop being surprised

CSIRT Italia's notices are a public service, and a valuable one. But if the first time you learn about an exposed system is an email from the national CSIRT, someone else has already scanned your perimeter, and attackers scan it more often. The goal is to find and close exposures before anyone has to tell you.

  • Inventory from the outside, starting from your domains and public IP ranges, and repeat it on a schedule.
  • Prioritise known-exploited vulnerabilities on exposed systems. They are what the CSIRT notices and what attackers use.
  • Verify, do not assume. A version banner is not proof; a test on the target is.
  • Keep evidence. Dated results show an inspector, a customer or your board that you find and fix exposures as a process.

Where Orizon fits

RECON External starts from your domain name and finds every subdomain, port and service you expose, matches detected products to known CVEs weighed by CISA KEV, Exploit-DB, Metasploit and EPSS, and then tests each finding from the scan's own isolated server. Proven means the verification confirmed the problem exists on the target, with the evidence attached; To verify comes with the commands for a manual check; Closed means the finding was disproved or excluded. RECON also gives you a proof script you can download and run yourself: it only reads, and tells you whether the problem is still there, which is exactly what you need at hour 12. Scans can run daily, weekly or on any schedule you choose. RECON confirms that a vulnerability exists; it does not exploit it. For the internal network and the cloud, the same vulnerability assessment approach applies with RECON Internal and RECON Cloud.

Checklist

  1. Confirm the notice's authenticity through official channels.
  2. Identify the asset, its owner and whether it is still exposed.
  3. Distinguish "at risk" from "potentially compromised".
  4. Contain the exposure and preserve evidence before rebooting.
  5. Check for compromise, not only vulnerability.
  6. Fix, verify from the outside, rotate secrets.
  7. Document the timeline and decide on NIS2 and GDPR notifications.
  8. Search the whole perimeter for the same product and version.
  9. Put continuous external monitoring in place so the next notice is no surprise.

If you would rather find your exposed services before CSIRT Italia does, run RECON External on your domains: you get the list of what you expose and, for each finding, proof of whether it is real.

csirt-italia
acn
exposed-services
incident-response
attack-surface
nis2