Zum Hauptinhalt springen
Risk source · ISO/IEC 27005

RS04 Ideological activists (hacktivists)

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

An engineering firm is planning the extension of a controversial motorway. One Monday morning, internal emails, site plans and minutes of meetings with the authority appear on a protest website. The firm’s home page shows a banner with slogans, and twenty protesters are sitting in the entrance hall. The activists had gained access to the mailbox weeks earlier through a fake invitation to a public consultation meeting. Hacktivists want to be seen: their success is measured in attention, and the targeted organization becomes their stage.

ISO/IEC 27005 lists ideologically motivated activists in Annex A as a risk source of their own. Their methods resemble those of terrorists, while their intent is less destructive. They want to spread a message, expose wrongdoing or stop a project, and they use social networks as an amplifier.

What is behind it?

This covers groups and individuals with political, environmental, religious or social causes. Alongside hacktivists, the standard also counts interest groups and sects. Some collectives are loosely organized and agree on actions spontaneously, others work on one topic for years. The trigger almost always lies outside IT: a decision, a project, a customer or a public debate.

Resources and approach

  • Leaks. Internal documents, emails and personal data are published to make contradictions or wrongdoing visible.
  • Defacement. Websites and social media accounts are taken over and display slogans or mockery.
  • Flooding. Volunteers or rented services flood websites with requests, often for a few hours at a symbolic moment.
  • Deception. Fake invitations, requests from supposed journalists or undercover job applications open doors.
  • Presence on site. Occupations, blockades and covert recordings inside companies combine the digital action with images from the real world.

Impact

Confidentiality and reputation take the hardest hit. Published documents cannot be retrieved, and the public then decides how to read them. Defaced websites and fake content damage integrity. Employee data is especially sensitive: once the names and addresses of executives are published, an image problem turns into a question of personal safety.

Practical examples

Defaced careers portal. A pharmaceutical company runs its careers portal on an outdated content management system. Activists against animal testing use a known gap and replace the job ads with pictures and slogans. By the time the site is taken offline, screenshots are already circulating in several networks.

Undercover in the plant. An activist applies for a temporary job at a poultry farm. Over several weeks he films with a hidden camera and records conversations in meetings. The material appears, edited, in a television report.

Executives’ addresses. Under a pretext, activists call the reception desk and the HR department and gather private addresses and phone numbers of the management piece by piece. The list is published together with calls for protests outside their homes.

Typical threats

This risk source typically uses these BSI elementary threats:

Effective controls

Prevention:

Detection:

Response:

Risk sources in ISO 27005

In Annex A, ISO/IEC 27005 describes risk sources by two features: what drives them and what they are capable of. For activists, the target objective “Influence” from Table A.9 fits. The standard groups under it operations that aim to sway opinion, spread false information, reveal confidential information or damage an organization’s standing. Table A.8 offers categories for the desired end state. Anyone who wants to stop a construction project, for example, aims to limit what a third party can do. In the event-based approach you then ask which assets the group has to hit to get there and whether a partner or service provider is the easier route. For likelihood, the capabilities matter, and above all how attractive your organization is as a symbol (→ ISO/IEC 27005 Information Security Risk Management).

Sources

Frequently asked questions

When does an organization become interesting to hacktivists?

When it is connected to a topic that people are currently fighting about. That can be the sector, a single project, a well-known customer or a statement by top management. Suppliers and service providers of controversial projects also come into view, because they are often less well protected than the actual addressee.

Are hacktivists dangerous if their technical skills are limited?

Yes, because their success depends on attention. A simple flooding attack or a single published document can be enough to keep an organization in the headlines for days. The reputational damage is then often greater than the technical damage.

How do we respond when internal documents are published?

First check whether the documents are genuine and where they came from, and close the path through which they leaked. Coordinate the public response with communications and legal counsel. If the documents contain personal data, the deadline for notifying the data protection authority under Art. 33 GDPR is running.

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.