Summary
- LACNIC CSIRT publishes who may report, the limit of its authority over members' systems, four named services, and office hours of Monday to Friday, 9:00 to 17:00 GMT-3. Across the seven readable LACNIC CSIRT documents reviewed for this piece, none printed a priority tier, an identified tier assigner, or a numeric acknowledgement or resolution interval.
- The team's own November 2023 plan tells other organisations to define an incident taxonomy, severity levels and a triage procedure, and its 2019 retrospective says a priority is assigned after triage and a ticket monitored to closure — without publishing the ladder, the assigner or the interval.
The most precise thing LACNIC CSIRT publishes about time is two numbers on a contact page. Office hours, Monday to Friday, 9:00 to 17:00 GMT-3. Nothing in that sentence says what happens to an incident report at 02:00 on a Saturday, and nothing else on the page does either.
What the team does publish is the perimeter, and it publishes it unusually candidly.
The perimeter is generous, and honestly drawn
"LACNIC CSIRT's target community includes all LACNIC member organizations," its About page states. The same page draws the edge: "With the exception of LACNIC's own internal systems, LACNIC CSIRT does not have the authority to act on the operations of its community's systems. For this reason, LACNIC CSIRT will not provide direct remote or on-site assistance for handling security incidents, even if these involve Latin American and Caribbean IP addresses."
Sit with that for a moment, because it is the sentence most response teams leave out. A member whose address block is being used to sweep the region gets advice and coordination, not a firefighter on the wire. The registry will not reach into a member's router, and says so before anyone asks.
The services page enumerates four: incident reporting, advice brokering, a security warning service, and training. The first is framed as "a trusted environment for reporting security incidents and other sensitive information without fear that this information will be used against them" — a confidentiality promise, made to the member who is about to admit something embarrassing. The FAQ restates the team's three functions: security incident reporting, publishing statistics on the abuse of LACNIC-managed resources, and issuing security alerts. Reports arrive through an online form or an address on the contact page.
Four services, three functions, one constituency, two office-hour numbers. And not a single interval.
The ladder exists. The rungs are not printed.
Once, in public, the team described its own intake. A 2019 five-year retrospective of the WARP programme it grew out of puts the sequence in one sentence: "If a security incident that needs to be managed is identified, the incident is classified, a priority is assigned, and a ticket is created with which it will be monitored until it has been closed."
Read that for what it establishes and what it withholds. Triage happens. A priority exists. A ticket runs until closure. Missing are the three things an outsider would need: what the priority levels are, who sets one, and how long any of it is allowed to take. The same document repeats the posture — no authority over how the community operates its systems, an advisory role, assistance at no additional cost to members.
The sharper asymmetry sits in a November 2023 plan the team published for everyone else's benefit. Among its preparation-stage instructions: "Define incident taxonomy and their level of severity" and "Define a procedure for triaging reports." That is sound advice, and it is precisely the document LACNIC CSIRT has not published about itself. The organisation that prescribes the taxonomy, the severity scale and the triage procedure for its constituents keeps its own equivalent where those constituents cannot read it.
The point is not that the team is hiding something. Advice brokering on a confidential ticket is a legitimate service, and a member's incident is the member's to disclose. The point is that the only party able to test whether the advice arrived in time is the party that already holds the ticket.
The yardstick, and what it does not require
RFC 2350 is the template the question turns on. It asks a response team to make clear who belongs to its constituency, to define the services it offers and the level of support for each, and to publish operating hours and say whether a 24-hour hotline exists. Its most-quoted time line — "in all cases some response will be made within one working day" — appears in the template's filled-in example for a fictional team called XYZ-CERT. It is illustrative. Quoting it as LACNIC's commitment would be a fabrication, and a tempting one.
RFC 2350 also contemplates that part of such a description may be non-public, so silence on the public pages is not proof of silence inside the building. An internal expectations document may well exist. What can be said is narrower and still useful: on 20 November 2026 an outsider could not read the tier table, could not learn who assigns a tier, and could not find a single number to hold the team to.
Other teams do print the number. REN-ISAC, a United States research-and-education response team, publishes service level objectives of "a human-provided acknowledgement within four normal business hours and a response within 24 hours." Those are REN-ISAC's objectives. They say nothing about LACNIC CSIRT, and they are not offered here as a standard LACNIC has failed. They are offered as evidence that the publication is possible, in the same tradition, from a team of comparable size.
What the published output can and cannot show
The security alerts page is the team's outward-facing record: three entries, dated 30/11/2020, 02/10/2018 and 10/04/2018, each a day-level date and a title. No time, no incident identifier, no tier. It shows what the team decided the region needed warning about. It cannot show how quickly a report was answered, because it never claimed to be that record and is not shaped like one.
Here is the bound on the finding, stated once. Across the seven readable LACNIC CSIRT documents reviewed for this piece on 20 November 2026 — About, Contact, Services, FAQ, Security Alerts, the November 2023 plan and the 2019 retrospective — not one printed a named priority tier, an identified tier assigner, or a numeric acknowledgement or resolution interval. The statistics page linked from the team's own site could not be read for this piece, so nothing here describes its contents.
The delta, stated plainly
This publication's LACNIC coverage to date is event reporting — a credential-leak detection in 2025, phishing campaigns, RPKI key rollover, legacy BGP attributes, consultation processes. None of it reads the incident-response team's own service instrument, and a targeted search across the archive turned up no earlier reading of it.
My own beat has spent the year on clocks that were printed. The United States Nuclear Regulatory Commission's notification tiers, the Department of Energy's filing intervals, ICANN's emergency-backend operator regime, DORA's reporting chain, Singapore's one-hour notification, APRA's tolerance judgements: in each case the instrument published the tier and the interval, and the accountability failure sat one step later, in a record that never named a case. This piece moves the failure one step earlier. Before asking whether a clock ran, ask who is holding the clock.
The control that would make this checkable
Two publications would do it, and neither requires new instrumentation. The team already runs the ticketing system its own retrospective describes.
First, the tier table and the assignment rule: which levels exist, what each one means, who decides, and what a reporter is told once a level is set. Second, a measured record — arrival, tier assigned, time to first substantive response, time to closure — published as distribution rather than anecdote, so a member can place one incident in context without any other member's organisation being named.
An aggregate would be enough to start: reports received, reports closed, the tier distribution, and the measured interval at each tier. That is a small number of fields, they already exist on the ticket, and they would convert a confidentiality promise into something a board could audit without breaking the confidentiality that makes the promise worth anything.
The door to LACNIC CSIRT is open, well signposted, and honestly labelled with what lies beyond it. The clock is still in the ticket.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






