Accountability

Our Impact

An organisation that asks to be trusted should show what its work changes. We are publishing how we will count before we publish any counts.

FISRO has not yet published impact figures. Numbers will appear here only after the underlying records have been checked by someone other than the person who produced them, and each figure will link to its definition, period and verification date.

Large organisations in this field are careful to separate what they receive from what they confirm, and what they send from what others act upon. We follow the same discipline: a notice sent is not a threat removed.

What we will count, and how

Every published figure carries its period, data source, verification date and the identity of the reviewer in our internal audit record.
Measure	Definition	Counting rule
Reports received `reports_received`	Submissions through the FISRO report form in the period, including duplicates and out-of-scope reports.	Count of intake records created in the period. Duplicates are reported separately and not subtracted.
Reports triaged `reports_triaged`	Reports that completed first review: assessed for credibility, novelty and scope.	Count of reports whose status left “received” during the period.
Threat reports verified `reports_verified`	Reports in which FISRO independently confirmed that the threat described was real.	Count of reports moved to “verified” in the period, each with recorded evidence.
Original investigations and research reports `original_investigations_published`	Published pieces of type FISRO Investigation or Research Report.	Count of such pieces first published in the period. Updates are not counted again.
Notifications sent `external_notices_sent`	Notices sent by FISRO to infrastructure operators, platforms, maintainers or CERTs about a verified threat.	One per recipient per threat. A notice sent is not an action taken.
Actions confirmed by others `external_actions_confirmed`	Cases where the recipient of a FISRO notice took action, for example by removing a phishing site, confirmed by evidence.	Counted only with evidence of the action (recipient confirmation or independent observation).
Indicators verified `indicators_verified`	Technical indicators of compromise (domains, URLs, file hashes, addresses) that FISRO verified as malicious.	Unique indicators verified in the period.
Countries covered by published work `countries_covered_by_published_research`	Countries where events described in FISRO publications took place or whose residents were affected.	Unique countries tagged on publications first published in the period. Not offices or staff locations.
Verified citations `research_citations`	Citations of FISRO work by independent publications, researchers or official bodies that we have checked.	Counted only with a link to the citing source.
People helped directly `assistance_cases_supported`	Cases in which FISRO gave documented, individual assistance to a person affected by a threat.	Counted only where the assistance is recorded in the case file.

Report a threat

Tell us about malware, phishing, fraud or exposed systems. Reports are encrypted the moment they arrive and read only by authorised staff. We cannot promise to investigate every report or to respond quickly.

Send a report

Get help

FISRO is not an emergency or incident-response service. Our help page points you to organisations that can act: national CERTs, platform reporting channels and specialist services. If anyone is in immediate danger, contact local emergency services.

Find help