Zum Hauptinhalt springen
Risk source · ISO/IEC 27005

RS07 Avengers and insiders

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27005ISO 27001BSI IT-Grundschutz

After a long conflict, an administrator is given notice. His personal accounts are disabled the same day. A service account he set up years earlier for a backup job, however, appears on no list. Two weeks later, at three in the morning, someone logs in through remote access with this account, deactivates the backup job and deletes several tables of the inventory management system. An avenger knows the weak spots precisely, because he used to manage them himself.

In Annex A, ISO/IEC 27005 describes the avenger as an attacker driven by a strong sense of grievance or injustice. What makes this attacker dangerous is the combination of determination and knowledge of the organization’s systems and processes. Where the data sits and how to cover tracks is already known.

What is behind it?

This covers employees, former employees, agency workers and service providers who feel they have been treated unfairly. The standard gives as examples the person dismissed for serious misconduct and the service provider whose contract runs out. The triggers are almost always events inside the organization: a dismissal, a missed promotion, disciplinary proceedings, a lost tender.

Resources and approach

  • Existing rights. The easiest route is one’s own access while it still exists, or rights that go beyond the job.
  • Forgotten access. Service accounts, shared passwords, remote maintenance access and keys that nobody had in mind at the departure.
  • Knowledge of the weak spots. An insider knows which backup does not work, which logs nobody reads and when nobody is in the building.
  • Concealed actions. Shared accounts, colleagues’ credentials and deleted logs make it hard to prove who did something.
  • Physical routes. A badge that was kept, a key or simply being known at reception open doors even after departure.

Impact

Avengers mostly target integrity and availability: deleted data, sabotaged systems, destroyed devices. Confidentiality is often affected too, when customer data or internal documents get out or colleagues’ data is exposed. The damage is hard to contain because the perpetrator also knows the countermeasures, such as where the backups are kept. In rare cases the anger turns against people, and a security problem becomes a question of occupational safety.

Practical examples

Service provider at contract end. An IT service provider loses the support contract to a competitor. On the last day, its technician deletes the firewall configuration through the still active remote maintenance access, claiming it is his company’s intellectual property. The new provider rebuilds it from scratch in two days.

Grievance in sales. An employee in sales is passed over for a promotion. Over the following weeks she forwards customer lists to her private address and posts a salary overview, which she found in a wrongly shared folder, in an internal chat.

One account for everyone. At an operator terminal in production, all shifts share a single account. Several recipe parameters are changed and a batch is ruined. Because everyone uses the same account, nobody can establish who made the change.

Typical threats

This risk source typically uses these BSI elementary threats:

Effective controls

Prevention:

Detection:

Response:

Risk sources in ISO 27005

ISO/IEC 27005 describes risk sources in Annex A by motivation and ability to act. With the avenger, the ability to act is closely tied to their position in the organization. In Table A.13 the standard shows an example scenario with an administrator as the risk source, who uses his rights to destroy sensitive documents directly in the database. As an event that can be monitored, it names direct database access outside normal working hours. For likelihood it matters that the motivation arises from events and can fade again. The standard provides for a fresh assessment of likelihood when circumstances change or new actors appear. A dismissal in the IT team or an escalating conflict with a service provider is exactly such an occasion (→ ISO/IEC 27005 Information Security Risk Management).

Sources

Frequently asked questions

May we monitor employees to spot avengers early?

Only within the limits of employee data protection law and, where there is a works council, with its involvement. Logging privileged actions and alerting on unusually high numbers of accesses are common and easy to justify. Purpose, access to the logs and retention periods should be set down in writing.

What needs to happen when someone in the IT team is dismissed?

Plan the removal of all access before the meeting and carry it out during it: personal accounts, remote access, administrator rights, badge and keys. Change shared passwords and keys and review service accounts the person created. Also look at the changes of recent weeks, such as new accounts or scheduled tasks.

Do service providers count as insiders too?

Yes. The standard explicitly mentions the discontented service provider whose contract was not renewed. Anyone with remote maintenance, administrator rights or access to the building often knows your systems better than some of your own departments. The end of a contract therefore deserves the same care as an employee's departure.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.