Checked Does Not Mean Tested: The First Hour After an Incident

Checked Does Not Mean Tested: What Happens in the First Hour After an Incident

It’s 7:00 AM. The management system is no longer responding, you can’t process payments, and you have no access to the customer database. Nobody answers the phone at your IT provider.

We use this scenario as a testing exercise in companies because it reveals exactly what’s missing: a phone number that is no longer valid, a responsibility that nobody takes ownership of, or a backup that nobody knows how to restore.

In Fitness Business Romania Magazine (issue 5, October–December 2026), Delia Necula, CEO of FORT Cyber, explained what this means for a fitness club. Her conclusions apply to any company whose daily operations depend on a handful of systems.

 

Why the industry no longer matters

Attackers are bold: they use AI to scan potential victims in record time. The time between the discovery of a vulnerability and its exploitation is now measured in hours, if not minutes.

Therefore, exposure no longer depends on how large or well-known a business is. It depends on what data it holds and how quickly a vulnerability can be found.

 

What the “Radiografia Securității Cibernetice” study reveals

The study was conducted in 2026 together with Data Diggers and Promocrat, covering more than 200 organizations in Romania. Over 80% already had basic security measures in place: antivirus, firewall, multi-factor authentication, and backup. Nevertheless, 15% had implemented 8 or 9 of the 9 technical measures analyzed but had never tested their incident response plan.

A building doesn’t become safe just because you’ve purchased fire extinguishers. You need to check that they work, establish who responds, and conduct drills.

 

Where attacks come from

  • Compromised accounts: through phishing or credentials leaked in other breaches, which attackers automatically try to exploit.
  • The website: a website that hasn’t been updated in years, built by someone who no longer answers the phone.
  • Shared accounts: when several people use the same username and password, you no longer know who accessed, exported, or deleted data.

 

What is the real cost of an incident?

The fine is just one line item in the total cost and sometimes not even the most significant one. On top of that, you also pay for:

  • Operations:halted or disrupted.
  • Recovery: of systems and data.
  • Investigation: technical, legal, and specialist expertise.
  • Notifications: to affected individuals, when required.
  • Trust: lost customers and reputational damage.

 

Even paying the ransom doesn’t solve the problem. According to the ENISA Threat Landscape 2026 report, organizations that paid and recovered their data were affected at least twice as badly because, in the meantime, their information had been copied and exfiltrated from the company.

 

The first hour: what to do and what not to do

  • Don’t automatically assume it’s an attack: it could be a technical issue or a service outage at your provider.
  • Activate the procedure: immediately contact the person or provider responsible for IT and security.
  • Preserve information: the time, on-screen messages, affected systems, and what happened beforehand.
  • Don’t delete or reinstall anything: otherwise, you could destroy exactly the data needed for the investigation.
  • Don’t make decisions on your own: neither about paying a ransom nor about contacting the attackers.

 

Five things to do this month, without a budget

  • Multi-factor authentication: on email, business applications, and all important accounts.
  • Individual accounts: every employee has their own account and only the access they need.
  • Revoke access when people leave:for former employees and old or unused accounts.
  • Test your backups:verify that data can actually be restored from them.
  • Written procedure:who gets called first, who decides to shut down a system, and where contact details can be found.

 

What the list doesn’t cover

The steps above do not replace technical security measures. Depending on your company’s risk profile, you also need periodic penetration testing, vulnerability scans, and traffic monitoring.

The list also doesn’t tell you what reporting obligations apply, because these depend on the incident, the data affected, and the regulations that apply to your organization. That’s why it’s worth having at least a framework Incident Response contract in place, so you have specialists by your side exactly when you need them.

 

The next step

Do you know who does what on the morning when your systems stop responding?

Schedule a TAPLETOP exercise with the Fort team here.

The full article can be read in Fitness Business Romania Magazine and dwonloaded here.

Related articles