Versatile AI Risk Assessment
Customer service, marketing and platforms

Automated content moderation

Platforms automatically identify unlawful content or breaches of their rules and remove, restrict or refer posts for human review.

Explore the interactive model

Export handout

A concise PDF covering how the system works, its data flows and points to investigate, ready to share.

The explanations and measures describe the typical system design. Extensive personal changes add an appendix.

Understand the use case

What defines this use case?

Models check text, images and videos against laws or terms of service and determine what disappears immediately and what a person reviews. Major platforms use this approach; a German federal agency uses it to detect offensive language on its intranet.

This page describes a typical system design. Actual data flows and permissions depend on your implementation.

System design
Analysis and processing
Ability to act
Can act within applications
Fields of use
online platforms, public administration
Also known as
content moderation, toxicity detection, comment filter

How it works, step by step

System design and data flows

  1. Input data

    Posts, comments, images and videos are checked on upload or after a report.

    All reviewed posts come from users, including those deliberately seeking to bypass moderation. The system reviews text, images and videos, often including text within images.

  2. Processing

    The system matches them against known prohibited content; models assess whether they violate laws or terms of service.

    The model detects characteristics in text, images, audio or video and assigns them to the platform's moderation categories. Rules and thresholds then determine whether content is flagged, held for review or restricted. Detecting a characteristic and making a moderation decision are separate steps.

  3. Results

    The post is removed, restricted, referred to a person or left in place.

    The result describes the defined model task. A match, category or forecast acquires its professional significance only in conjunction with the underlying data and intended use.

  4. Use and impact

    The decision determines what remains publicly visible and can suspend accounts or reduce earnings.

    Write or execution permissions allow the system to change a state within an application. Model responses, tool calls and changes actually executed must therefore be considered separately.

Explore the system design: Select a component to see its task, incoming and outgoing data, and role in the use case. The guided walkthrough explains each phase. Then use Yes, Uncertain and No to represent your specific system variant.

How the system is built

9 review first13 clarify8 baseline threats

InputProcessingResultImpact Externalaccess 03 Input 50 Third-partycontent 00 AI model 05 Providerservice 03 Documentcollection 01 Memory 00 Training andfeedback 30 OtherAI agents 00 Tools andinterfaces 00 Result 00 Business appor equipment 10 person 00 Affectedperson 00 AI serviceswithout approval 01 Externalaccess 03 Input 50 Third-partycontent 00 AI model 05 Providerservice 03 Documentcollection 01 Memory 00 Training andfeedback 30 OtherAI agents 00 Tools andinterfaces 00 Result 00 Business appor equipment 10 person 00 Affectedperson 00 AI serviceswithout approval 01
  • Present
  • Depends on your system
  • Absent
  • Review first
  • To clarify

In this system design: 9 to review first, 13 to clarify, 8 baseline threats.

Architecture as a list

How it differs from similar use cases

Data and information

Input data and information sources

All reviewed posts come from users, including those deliberately seeking to bypass moderation. Posts, accounts and reports are linked to specific people.

Processing and operating environment

Smaller deployers use ready-made third-party services such as Perspective API.

Storage and further use

To match known content, the system searches a collection of previously removed images and videos. Major platforms train their models on their own previously moderated posts.

Results and data sharing

The system removes posts, restricts their reach or suspends accounts, often without prior human review.

Using a provider does not automatically determine where processing takes place. Storage location, subcontractors, deletion periods and use for training must be checked for the specific deployment.

Assess risks and determine measures

From understanding the system to analysing risks

  1. Define the system boundary

    Record data, participants, interfaces and permissions. Resolve uncertain characteristics in the model.

  2. Investigate threats

    Relate review candidates to actual data flows: what could happen, and who would be affected?

  3. Assess risk

    Assess impacts and likelihood in the deployment context. The number of review candidates is not a risk score.

  4. Provide evidence of measures

    Select appropriate controls, assign responsibilities and define effectiveness checks. Document residual risks and approvals.

Key threats in the application context

  • 4 particularly important
  • 5 typical
  • 13 depending on the system
  • 8 additional threats for every AI system

A total of 30 threats from the threat catalogue may be relevant to this use case.

Also review: whether the system disadvantages groups

Check whether selection, ranking or assessment disadvantages people with protected characteristics, such as sex, age or origin.

Priority review points

  1. Adversarial Inputs

    Users replace letters in insults with digits or change a known image by a few pixels. The post passes review and remains online.

  2. Targeted Poisoning / Label Poisoning

    An organised group mass-reports a minority's legitimate posts as hate speech. If these reports enter training, the model learns to remove such posts itself.

  3. Multimodal Attacks

    A prohibited call appears as text in an image or only as speech in a video. Checking image, audio and text separately misses the violation.

  4. Excessive Agency

    The system can suspend accounts without human review. An error then affects many people at once before anyone notices.

5 further review candidates in the typical design

Other relevant threats

  1. Training Data Poisoning

    Your own training or operational feedback can introduce manipulated data into training datasets.

    Listed because of these characteristics

    • Learns from your own data
    • Uses operational feedback
  2. Backdoor ML Model

    Training data or an adopted base model can introduce hidden triggers for misbehaviour.

    Listed because of this characteristic

    • Learns from your own data
  3. Model Denial of Service

    Complex or high-volume inputs can exhaust model computing resources.

    Listed because of this characteristic

    • Processes text, images and speech together
  4. Privacy Attacks

    Targeted queries can recover some personal or protected training data from the model.

    Listed because of this characteristic

    • Processes personal data
  5. Sensitive Information Disclosure

    Confidential content can appear in answers, supplied context or logs.

    Listed because of this characteristic

    • Processes personal data

Up to 13 further threats may apply, depending on your system design. Nine threats need to be reviewed for every AI system. One of these is particularly important here and is therefore listed above.

System features and open questions

Each Yes adds further threats to your checklist, up to 13 in total. If you cannot yet answer a question, include its threats in your review.

How many threats a Yes adds
  • Added by this Yes

How your system is built

Does the system search its own collection of documents or records for relevant content?

To match known content, the system searches a collection of previously removed images and videos.

If yes, add

Does the system process confidential information such as trade secrets, health or financial data?

Posts often concern authors' health, religion or political views.

If yes, add

How you operate the system

These questions arise for almost every AI system.

Controls and implementation

Measures for the priority review areas are expanded. Each linked measure explains how to implement it.

Controls for the remaining threats are available on their pages in the threat catalogue.

AI Act provisions

Beyond AI literacy (Article 4), no other AI Act provision is relevant to this use case.

Applies to every AI system

Art. 4: AI literacy

Applies if staff or appointed representatives operate or use AI systems.

Applies since 2 February 2025.

Obligations and details for Art. 4: AI literacy
Who bears the obligations
Provider, Deployer, Product manufacturer, Provider of a general-purpose AI model

Detailed obligations

Other legal requirements

  • Articles 17 and 20 DSA

    Platforms must explain moderation decisions, state whether they were automated and offer a complaint process whose decisions are not made solely by a machine.

    Open the legislation Articles 17 and 20 DSA

Classify your system with the quick checker All obligations in the obligations compass

Cross-cutting threats

Review these threats for every AI system, whatever its purpose.

Why these threats always belong on the checklist

Atypical system features

View 14 further questions

If any of these features does apply to your system, add the listed threats.

Sources

Related use cases

Also in the field of Customer service, marketing and platforms

Updated: 30 September 2026. Review checklist rules version 0.3.2, threat catalogue version 2026.10.24.2. How these pages are structured