diff --git a/docs/content/admin/user_management/PRO__audit_log_index.md b/docs/content/admin/user_management/PRO__audit_log_index.md index 05fa4e5649c..ffa828ad8b0 100644 --- a/docs/content/admin/user_management/PRO__audit_log_index.md +++ b/docs/content/admin/user_management/PRO__audit_log_index.md @@ -87,8 +87,8 @@ attributed to the user who triggered it. | Rule Filter Entry | ✅ | ✅ | ✅ | | | Rules Engine Operation | ✅ | ✅ | ✅ | | | Rules Engine Operation Message | ✅ | ✅ | ✅ | | -| Rules Engine 2.0 Rule | ✅ | ✅ | ✅ | Node based rules | -| Rules Engine 2.0 Delivery | ✅ | ✅ | ✅ | Entries in the Deliveries ledger | +| Triage Engine Rule | ✅ | ✅ | ✅ | Node based rules | +| Triage Engine Delivery | ✅ | ✅ | ✅ | Entries in the Deliveries ledger | | Scheduled Task | ✅ | ✅ | ✅ | | | Scheduled Task Run | ✅ | ✅ | ✅ | | | Mitigation Policy | ✅ | ✅ | ✅ | | diff --git a/docs/content/admin/user_management/user_permission_chart.md b/docs/content/admin/user_management/user_permission_chart.md index 72cfa0f7bae..d7fd1bbcaaa 100644 --- a/docs/content/admin/user_management/user_permission_chart.md +++ b/docs/content/admin/user_management/user_permission_chart.md @@ -76,7 +76,7 @@ The majority of Configuration Permissions give users access to certain pages in | Questionnaires | Access the **Questionnaires \> All Questionnaires** page | Add a new Questionnaire | Edit an existing Questionnaire | Delete a Questionnaire | | Questions | Access the **Questionnaires \> Questions** page | Add a new Question | Edit an existing Question | n/a | | Regulations | n/a | Add a Regulation to the **⚙️Configuration \> Regulations** page | Edit an existing Regulation | Delete a Regulation | -| Rules Engine | Access the **Rules Engine 2.0** sidebar section and everything under it (All Rules, Runs, and Deliveries) | Create a rule, including converting one from the original Rules Engine | Change, enable, schedule, run, replay, or take ownership of an existing rule | Delete a rule | +| Rules Engine | Access the **Triage Engine** sidebar section and everything under it (All Rules, Runs, and Deliveries) | Create a rule, including converting one from the original Rules Engine | Change, enable, schedule, run, replay, or take ownership of an existing rule | Delete a rule | | Scheduling Service Schedule | Access the **Scheduling** page | Superuser only | Edit an existing Schedule (change trigger, enable/disable) | Delete a Schedule | | SLA Configuration | Access the **⚙️Configuration \> SLA Configuration** page | Add a new SLA Configuration | Edit an existing SLA Configuration | Delete an SLA Configuration | | Test Types | n/a | Add a new Test Type (under **Engagements \> Test Types**) | Edit an existing Test Type | n/a | diff --git a/docs/content/automation/rules_engine/about.de.md b/docs/content/automation/rules_engine/about.de.md index 17f9da34c52..a1599292edd 100644 --- a/docs/content/automation/rules_engine/about.de.md +++ b/docs/content/automation/rules_engine/about.de.md @@ -13,7 +13,7 @@ Mit der Rules Engine von DefectDojo können Sie benutzerdefinierte Workflows und Die Rules Engine ist nur über die [Pro UI](/get_started/about/ui_pro_vs_os/) zugänglich. -**Suchen Sie den grafischen Editor?** [Rules Engine 2.0](/automation/rules_engine_2/about/) baut Automatisierung als visuelle Knotengraphen auf und fügt Verzweigungen, ausgehende Aktionen wie Tickets und Nachrichten, Spuren pro Lauf und ein Zustellungsprotokoll hinzu. Beide Engines laufen nebeneinander, und bestehende Regeln können [dorthin übertragen werden](/automation/rules_engine_2/converting_from_rules_engine/). +**Suchen Sie den grafischen Editor?** [Triage Engine](/automation/triage_engine/about/) baut Automatisierung als visuelle Knotengraphen auf und fügt Verzweigungen, ausgehende Aktionen wie Tickets und Nachrichten, Spuren pro Lauf und ein Zustellungsprotokoll hinzu. Beide Engines laufen nebeneinander, und bestehende Regeln können [dorthin übertragen werden](/automation/triage_engine/converting_from_rules_engine/). ## Rules Engine aktivieren diff --git a/docs/content/automation/rules_engine/about.es.md b/docs/content/automation/rules_engine/about.es.md index 8875fbcf58e..f18ca90d674 100644 --- a/docs/content/automation/rules_engine/about.es.md +++ b/docs/content/automation/rules_engine/about.es.md @@ -13,7 +13,7 @@ El Rules Engine de DefectDojo permite crear flujos de trabajo personalizados y a Solo se puede acceder a Rules Engine a través de la [interfaz Pro](/get_started/about/ui_pro_vs_os/). -**¿Busca el editor de grafos?** [Rules Engine 2.0](/automation/rules_engine_2/about/) construye la automatización como grafos visuales de nodos, y añade ramificaciones, acciones salientes como tickets y mensajes, rastros por ejecución y un libro de entregas. Ambos motores funcionan en paralelo, y las reglas existentes se pueden [convertir](/automation/rules_engine_2/converting_from_rules_engine/) de uno a otro. +**¿Busca el editor de grafos?** [Triage Engine](/automation/triage_engine/about/) construye la automatización como grafos visuales de nodos, y añade ramificaciones, acciones salientes como tickets y mensajes, rastros por ejecución y un libro de entregas. Ambos motores funcionan en paralelo, y las reglas existentes se pueden [convertir](/automation/triage_engine/converting_from_rules_engine/) de uno a otro. ## Enabling Rules Engine diff --git a/docs/content/automation/rules_engine/about.fr.md b/docs/content/automation/rules_engine/about.fr.md index c4f24878c10..feae79d6462 100644 --- a/docs/content/automation/rules_engine/about.fr.md +++ b/docs/content/automation/rules_engine/about.fr.md @@ -13,7 +13,7 @@ Le Moteur de règles de DefectDojo vous permet de créer des workflows personnal Le Moteur de règles n'est accessible que via l'[interface Pro](/get_started/about/ui_pro_vs_os/). -**Vous cherchez l'éditeur de graphes ?** Le [Moteur de règles 2.0](/automation/rules_engine_2/about/) construit l'automatisation sous forme de graphes de nœuds visuels, et ajoute des embranchements, des actions sortantes telles que des tickets et des messages, des traces par exécution et un registre des livraisons. Les deux moteurs fonctionnent côte à côte, et les règles existantes peuvent être [converties vers l'autre moteur](/automation/rules_engine_2/converting_from_rules_engine/). +**Vous cherchez l'éditeur de graphes ?** Le [Triage Engine](/automation/triage_engine/about/) construit l'automatisation sous forme de graphes de nœuds visuels, et ajoute des embranchements, des actions sortantes telles que des tickets et des messages, des traces par exécution et un registre des livraisons. Les deux moteurs fonctionnent côte à côte, et les règles existantes peuvent être [converties vers l'autre moteur](/automation/triage_engine/converting_from_rules_engine/). ## Activer le Moteur de règles diff --git a/docs/content/automation/rules_engine/about.it.md b/docs/content/automation/rules_engine/about.it.md index 38121153e89..782f4865ea6 100644 --- a/docs/content/automation/rules_engine/about.it.md +++ b/docs/content/automation/rules_engine/about.it.md @@ -13,7 +13,7 @@ Il Rules Engine di DefectDojo consente di creare flussi di lavoro personalizzati Rules Engine è accessibile solo tramite la [Pro UI](/get_started/about/ui_pro_vs_os/). -**Cerchi l'editor a grafo?** [Rules Engine 2.0](/automation/rules_engine_2/about/) costruisce l'automazione come grafi di nodi visuali, e aggiunge la ramificazione, azioni in uscita come ticket e messaggi, tracce per ogni run e un registro delle consegne. I due motori funzionano in parallelo, e le regole esistenti possono essere [convertite](/automation/rules_engine_2/converting_from_rules_engine/). +**Cerchi l'editor a grafo?** [Triage Engine](/automation/triage_engine/about/) costruisce l'automazione come grafi di nodi visuali, e aggiunge la ramificazione, azioni in uscita come ticket e messaggi, tracce per ogni run e un registro delle consegne. I due motori funzionano in parallelo, e le regole esistenti possono essere [convertite](/automation/triage_engine/converting_from_rules_engine/). ## Abilitare Rules Engine diff --git a/docs/content/automation/rules_engine/about.ja.md b/docs/content/automation/rules_engine/about.ja.md index 4a3c49fca73..d88042658d2 100644 --- a/docs/content/automation/rules_engine/about.ja.md +++ b/docs/content/automation/rules_engine/about.ja.md @@ -13,7 +13,7 @@ DefectDojoのRules Engineを使用すると、Findingやその他のオブジェ Rules Engineは[Pro UI](/get_started/about/ui_pro_vs_os/)からのみアクセスできます。 -**グラフエディタをお探しですか？** [Rules Engine 2.0](/automation/rules_engine_2/about/)は、自動化をビジュアルなノードグラフとして構築できるようにし、分岐、チケットやメッセージなどのアウトバウンドアクション、実行ごとのトレース、配信台帳を追加します。両エンジンは並行して稼働しており、既存のルールは[変換](/automation/rules_engine_2/converting_from_rules_engine/)することができます。 +**グラフエディタをお探しですか？** [Triage Engine](/automation/triage_engine/about/)は、自動化をビジュアルなノードグラフとして構築できるようにし、分岐、チケットやメッセージなどのアウトバウンドアクション、実行ごとのトレース、配信台帳を追加します。両エンジンは並行して稼働しており、既存のルールは[変換](/automation/triage_engine/converting_from_rules_engine/)することができます。 ## Rules Engineの有効化 diff --git a/docs/content/automation/rules_engine/about.md b/docs/content/automation/rules_engine/about.md index a725a91b3fe..ad5cffa6c86 100644 --- a/docs/content/automation/rules_engine/about.md +++ b/docs/content/automation/rules_engine/about.md @@ -12,7 +12,7 @@ DefectDojo's Rules Engine allows you to build custom workflows and bulk actions Rules Engine can only be accessed through the [Pro UI](/get_started/about/ui_pro_vs_os/). -**Looking for the graph editor?** [Rules Engine 2.0](/automation/rules_engine_2/about/) builds automation as visual node graphs, and adds branching, outbound actions such as tickets and messages, per-run traces and a delivery ledger. Both engines run side by side, and existing rules can be [converted across](/automation/rules_engine_2/converting_from_rules_engine/). +**Looking for the graph editor?** [Triage Engine](/automation/triage_engine/about/) builds automation as visual node graphs, and adds branching, outbound actions such as tickets and messages, per-run traces and a delivery ledger. Both engines run side by side, and existing rules can be [converted across](/automation/triage_engine/converting_from_rules_engine/). ## Enabling Rules Engine diff --git a/docs/content/automation/rules_engine/about.pt-br.md b/docs/content/automation/rules_engine/about.pt-br.md index fb7f2fc8d21..350a6000f78 100644 --- a/docs/content/automation/rules_engine/about.pt-br.md +++ b/docs/content/automation/rules_engine/about.pt-br.md @@ -13,7 +13,7 @@ O Rules Engine do DefectDojo permite construir workflows personalizados e açõe O Rules Engine só pode ser acessado através da [Pro UI](/get_started/about/ui_pro_vs_os/). -**Procurando o editor de grafos?** O [Rules Engine 2.0](/automation/rules_engine_2/about/) constrói automações como grafos visuais de nós, e adiciona ramificações, ações de saída como tickets e mensagens, rastros por execução e um livro-razão de entregas. Os dois mecanismos funcionam lado a lado, e regras existentes podem ser [convertidas](/automation/rules_engine_2/converting_from_rules_engine/). +**Procurando o editor de grafos?** O [Triage Engine](/automation/triage_engine/about/) constrói automações como grafos visuais de nós, e adiciona ramificações, ações de saída como tickets e mensagens, rastros por execução e um livro-razão de entregas. Os dois mecanismos funcionam lado a lado, e regras existentes podem ser [convertidas](/automation/triage_engine/converting_from_rules_engine/). ## Habilitando o Rules Engine diff --git a/docs/content/automation/rules_engine/about.zh-hans.md b/docs/content/automation/rules_engine/about.zh-hans.md index efabbc53df5..aa671a40286 100644 --- a/docs/content/automation/rules_engine/about.zh-hans.md +++ b/docs/content/automation/rules_engine/about.zh-hans.md @@ -13,7 +13,7 @@ DefectDojo 的规则引擎允许您构建自定义工作流和批量操作，用 规则引擎只能通过 [Pro UI](/get_started/about/ui_pro_vs_os/) 访问。 -**在寻找图形编辑器？** [规则引擎 2.0](/automation/rules_engine_2/about/) 以可视化节点图的形式构建自动化流程，并新增了分支、诸如工单和消息等出站操作、按运行记录的执行痕迹，以及投递台账。两套引擎并行运行，现有规则也可以[转换](/automation/rules_engine_2/converting_from_rules_engine/)到新引擎。 +**在寻找图形编辑器？** [Triage Engine](/automation/triage_engine/about/) 以可视化节点图的形式构建自动化流程，并新增了分支、诸如工单和消息等出站操作、按运行记录的执行痕迹，以及投递台账。两套引擎并行运行，现有规则也可以[转换](/automation/triage_engine/converting_from_rules_engine/)到新引擎。 ## 启用规则引擎 diff --git a/docs/content/automation/rules_engine_2/_index.de.md b/docs/content/automation/triage_engine/_index.de.md similarity index 93% rename from docs/content/automation/rules_engine_2/_index.de.md rename to docs/content/automation/triage_engine/_index.de.md index 98255528d38..bec763b49df 100644 --- a/docs/content/automation/rules_engine_2/_index.de.md +++ b/docs/content/automation/triage_engine/_index.de.md @@ -1,5 +1,5 @@ --- -title: Rules Engine 2.0 +title: Triage Engine description: Bauen Sie Automatisierungen als visuelle Node-Graphen, mit Traces je Ausführung und einem Zustellungsprotokoll summary: '' diff --git a/docs/content/automation/rules_engine_2/_index.es.md b/docs/content/automation/triage_engine/_index.es.md similarity index 93% rename from docs/content/automation/rules_engine_2/_index.es.md rename to docs/content/automation/triage_engine/_index.es.md index a2c9c266e4d..39e158d2083 100644 --- a/docs/content/automation/rules_engine_2/_index.es.md +++ b/docs/content/automation/triage_engine/_index.es.md @@ -1,5 +1,5 @@ --- -title: Rules Engine 2.0 +title: Triage Engine description: Cree automatizaciones como grafos de nodos visuales, con trazas por ejecución y un libro de registro de entregas summary: '' diff --git a/docs/content/automation/rules_engine_2/_index.fr.md b/docs/content/automation/triage_engine/_index.fr.md similarity index 100% rename from docs/content/automation/rules_engine_2/_index.fr.md rename to docs/content/automation/triage_engine/_index.fr.md diff --git a/docs/content/automation/rules_engine_2/_index.it.md b/docs/content/automation/triage_engine/_index.it.md similarity index 93% rename from docs/content/automation/rules_engine_2/_index.it.md rename to docs/content/automation/triage_engine/_index.it.md index bc3d175a90c..66161878895 100644 --- a/docs/content/automation/rules_engine_2/_index.it.md +++ b/docs/content/automation/triage_engine/_index.it.md @@ -1,5 +1,5 @@ --- -title: Rules Engine 2.0 +title: Triage Engine description: Crea automazioni come grafi di nodi visivi, con tracce per singola esecuzione e un registro delle consegne summary: '' diff --git a/docs/content/automation/rules_engine_2/_index.ja.md b/docs/content/automation/triage_engine/_index.ja.md similarity index 93% rename from docs/content/automation/rules_engine_2/_index.ja.md rename to docs/content/automation/triage_engine/_index.ja.md index fd95f600973..cf2aa7f3f29 100644 --- a/docs/content/automation/rules_engine_2/_index.ja.md +++ b/docs/content/automation/triage_engine/_index.ja.md @@ -1,5 +1,5 @@ --- -title: Rules Engine 2.0 +title: Triage Engine description: 自動化をビジュアルなノードグラフとして構築し、実行ごとのトレースと配信台帳を確認できます summary: '' date: 2026-08-02 09:00:00+00:00 diff --git a/docs/content/automation/rules_engine_2/_index.md b/docs/content/automation/triage_engine/_index.md similarity index 94% rename from docs/content/automation/rules_engine_2/_index.md rename to docs/content/automation/triage_engine/_index.md index 6e559ce77d1..21cbcae238a 100644 --- a/docs/content/automation/rules_engine_2/_index.md +++ b/docs/content/automation/triage_engine/_index.md @@ -1,5 +1,5 @@ --- -title: "Rules Engine 2.0" +title: "Triage Engine" description: "Build automation as visual node graphs, with per-run traces and a delivery ledger" summary: "" date: 2026-08-02T09:00:00+00:00 diff --git a/docs/content/automation/rules_engine_2/_index.pt-br.md b/docs/content/automation/triage_engine/_index.pt-br.md similarity index 100% rename from docs/content/automation/rules_engine_2/_index.pt-br.md rename to docs/content/automation/triage_engine/_index.pt-br.md diff --git a/docs/content/automation/rules_engine_2/_index.zh-hans.md b/docs/content/automation/triage_engine/_index.zh-hans.md similarity index 100% rename from docs/content/automation/rules_engine_2/_index.zh-hans.md rename to docs/content/automation/triage_engine/_index.zh-hans.md diff --git a/docs/content/automation/rules_engine_2/about.de.md b/docs/content/automation/triage_engine/about.de.md similarity index 84% rename from docs/content/automation/rules_engine_2/about.de.md rename to docs/content/automation/triage_engine/about.de.md index 691859f2bc2..b0c3f27466b 100644 --- a/docs/content/automation/rules_engine_2/about.de.md +++ b/docs/content/automation/triage_engine/about.de.md @@ -1,35 +1,36 @@ --- -title: Über Rules Engine 2.0 -description: Was Rules Engine 2.0 ist, wie man sie aktiviert, und die Konzepte, auf +title: Über Triage Engine +description: Was Triage Engine ist, wie man sie aktiviert, und die Konzepte, auf denen sie aufbaut weight: 1 audience: pro aliases: - /de/automation/rules_engine_v2/about/ +- /de/automation/rules_engine_2/about/ --- -Hinweis: Rules Engine 2.0 ist eine Funktion, die nur in DefectDojo Pro verfügbar ist. +Hinweis: Triage Engine ist eine Funktion, die nur in DefectDojo Pro verfügbar ist. -Rules Engine 2.0 ist ein visueller Automatisierungs-Baukasten. Statt eines Filters plus einer flachen Liste von Aktionen ist eine Regel ein **Graph**: ein Trigger-Knoten, der entscheidet, wann die Regel aufwacht, sowie eine beliebige Anzahl von Logik-, Befunde- und Egress-Knoten, die miteinander verbunden festlegen, was als Nächstes passiert. +Triage Engine ist ein visueller Automatisierungs-Baukasten. Statt eines Filters plus einer flachen Liste von Aktionen ist eine Regel ein **Graph**: ein Trigger-Knoten, der entscheidet, wann die Regel aufwacht, sowie eine beliebige Anzahl von Logik-, Befunde- und Egress-Knoten, die miteinander verbunden festlegen, was als Nächstes passiert. -Rules Engine 2.0 ist ausschließlich über die [Pro-UI](/get_started/about/ui_pro_vs_os/) zugänglich. +Triage Engine ist ausschließlich über die [Pro-UI](/get_started/about/ui_pro_vs_os/) zugänglich. ## Was sie gegenüber der Rules Engine hinzufügt -Die ursprüngliche [Rules Engine](/automation/rules_engine/about/) wendet eine geordnete Liste von Aktionen auf jeden Befund an, der auf einen Filter passt. Rules Engine 2.0 behält diese Fähigkeit bei und fügt vier Dinge hinzu: +Die ursprüngliche [Rules Engine](/automation/rules_engine/about/) wendet eine geordnete Liste von Aktionen auf jeden Befund an, der auf einen Filter passt. Triage Engine behält diese Fähigkeit bei und fügt vier Dinge hinzu: * **Verzweigung.** Ein **Wenn / Filter**-Knoten leitet Elemente in einen true-Zweig und einen false-Zweig, sodass eine Regel kritische Befunde anders behandeln kann als den Rest, ohne in zwei Regeln aufgeteilt werden zu müssen. * **Egress.** Eine Regel kann DefectDojo verlassen: ein JIRA-Issue oder ein Downstream-Ticket eröffnen, in Slack oder Microsoft Teams posten, eine E-Mail senden, einen Webhook aufrufen, eine In-App-Benachrichtigung auslösen oder einen Bericht erstellen. * **Nachvollziehbarkeit.** Jede Ausführung wird Knoten für Knoten als [Ausführung](../runs/) erfasst, und jeder ausgehende Versand wird als [Zustellung](../deliveries/) erfasst, die genau angibt, was gesendet wurde, wohin es ging und wie es endete. * **Ein Simulationsmodus.** Eine Regel kann exakt erfassen, was sie senden würde, ohne tatsächlich etwas zu senden – so testen Sie eine Regel sicher, bevor sie mit der Außenwelt in Berührung kommt. -Beide Engines laufen nebeneinander. Das Aktivieren von Rules Engine 2.0 deaktiviert oder konvertiert Ihre bestehenden Regeln nicht, und es gibt einen [Konverter](../converting_from_rules_engine/), falls Sie sie übertragen möchten. +Beide Engines laufen nebeneinander. Das Aktivieren von Triage Engine deaktiviert oder konvertiert Ihre bestehenden Regeln nicht, und es gibt einen [Konverter](../converting_from_rules_engine/), falls Sie sie übertragen möchten. -## Rules Engine 2.0 aktivieren +## Triage Engine aktivieren -Rules Engine 2.0 befindet sich in der Beta-Phase und ist standardmäßig ausgeschaltet. Ein Superuser aktiviert sie unter **Settings > Feature Flags**, sowohl auf Cloud- als auch auf On-Premise-Instanzen. Siehe [Feature Flags](/admin/feature_flags/pro__feature_flags/). +Triage Engine befindet sich in der Beta-Phase und ist standardmäßig ausgeschaltet. Ein Superuser aktiviert sie unter **Settings > Feature Flags**, sowohl auf Cloud- als auch auf On-Premise-Instanzen. Siehe [Feature Flags](/admin/feature_flags/pro__feature_flags/). -Sobald das Flag aktiviert ist, erscheint in der Seitenleiste ein Abschnitt **Rules Engine 2.0** mit drei Seiten: +Sobald das Flag aktiviert ist, erscheint in der Seitenleiste ein Abschnitt **Triage Engine** mit drei Seiten: | Page | What it is for | |------|----------------| diff --git a/docs/content/automation/rules_engine_2/about.es.md b/docs/content/automation/triage_engine/about.es.md similarity index 83% rename from docs/content/automation/rules_engine_2/about.es.md rename to docs/content/automation/triage_engine/about.es.md index 6498750c5c5..c7cb590d600 100644 --- a/docs/content/automation/rules_engine_2/about.es.md +++ b/docs/content/automation/triage_engine/about.es.md @@ -1,35 +1,36 @@ --- -title: Acerca de Rules Engine 2.0 -description: Qué es Rules Engine 2.0, cómo activarlo y los conceptos en los que se +title: Acerca de Triage Engine +description: Qué es Triage Engine, cómo activarlo y los conceptos en los que se basa weight: 1 audience: pro aliases: - /es/automation/rules_engine_v2/about/ +- /es/automation/rules_engine_2/about/ --- -Nota: Rules Engine 2.0 es una función exclusiva de DefectDojo Pro. +Nota: Triage Engine es una función exclusiva de DefectDojo Pro. -Rules Engine 2.0 es un generador visual de automatizaciones. En lugar de un filtro más una lista plana de acciones, una regla es un **grafo**: un nodo disparador que decide cuándo se activa la regla, y cualquier cantidad de nodos de lógica, de Hallazgos y de salida conectados entre sí para determinar qué ocurre a continuación. +Triage Engine es un generador visual de automatizaciones. En lugar de un filtro más una lista plana de acciones, una regla es un **grafo**: un nodo disparador que decide cuándo se activa la regla, y cualquier cantidad de nodos de lógica, de Hallazgos y de salida conectados entre sí para determinar qué ocurre a continuación. -Solo se puede acceder a Rules Engine 2.0 a través de la [interfaz de Pro](/get_started/about/ui_pro_vs_os/). +Solo se puede acceder a Triage Engine a través de la [interfaz de Pro](/get_started/about/ui_pro_vs_os/). ## Qué aporta respecto a Rules Engine -El [Rules Engine](/automation/rules_engine/about/) original aplica una lista ordenada de acciones a cada Hallazgo que coincide con un filtro. Rules Engine 2.0 conserva esa capacidad y añade cuatro cosas: +El [Rules Engine](/automation/rules_engine/about/) original aplica una lista ordenada de acciones a cada Hallazgo que coincide con un filtro. Triage Engine conserva esa capacidad y añade cuatro cosas: * **Ramificación.** Un nodo **Si / Filtro** dirige los elementos por una rama verdadera y una rama falsa, de modo que una regla puede tratar los Hallazgos Críticos de forma distinta al resto sin tener que dividirse en dos reglas. * **Salida.** Una regla puede salir de DefectDojo: abrir un issue de JIRA o un ticket en un sistema externo, publicar en Slack o Microsoft Teams, enviar un correo electrónico, llamar a un webhook, generar una alerta dentro de la aplicación o generar un informe. * **Trazabilidad.** Cada ejecución se registra nodo por nodo como una [Ejecución](../runs/), y cada envío saliente se registra como una [Entrega](../deliveries/) que indica exactamente qué se envió, adónde fue y cómo terminó. * **Un modo de simulación.** Una regla puede registrar con precisión lo que enviaría sin enviar realmente nada, que es la forma de probarla de manera segura antes de que llegue al mundo exterior. -Ambos motores funcionan en paralelo. Activar Rules Engine 2.0 no desactiva ni convierte las reglas existentes, y existe un [conversor](../converting_from_rules_engine/) para cuando se quiera migrarlas. +Ambos motores funcionan en paralelo. Activar Triage Engine no desactiva ni convierte las reglas existentes, y existe un [conversor](../converting_from_rules_engine/) para cuando se quiera migrarlas. -## Activación de Rules Engine 2.0 +## Activación de Triage Engine -Rules Engine 2.0 está en Beta y viene desactivado de forma predeterminada. Un superusuario lo activa desde **Settings > Feature Flags**, tanto en instancias Cloud como On-Premise. Consulte [Feature Flags](/admin/feature_flags/pro__feature_flags/). +Triage Engine está en Beta y viene desactivado de forma predeterminada. Un superusuario lo activa desde **Settings > Feature Flags**, tanto en instancias Cloud como On-Premise. Consulte [Feature Flags](/admin/feature_flags/pro__feature_flags/). -Una vez activado el indicador, aparece una sección **Rules Engine 2.0** en la barra lateral con tres páginas: +Una vez activado el indicador, aparece una sección **Triage Engine** en la barra lateral con tres páginas: | Página | Para qué sirve | |------|----------------| diff --git a/docs/content/automation/rules_engine_2/about.fr.md b/docs/content/automation/triage_engine/about.fr.md similarity index 84% rename from docs/content/automation/rules_engine_2/about.fr.md rename to docs/content/automation/triage_engine/about.fr.md index 57e5ba4eaa4..cd22b41670f 100644 --- a/docs/content/automation/rules_engine_2/about.fr.md +++ b/docs/content/automation/triage_engine/about.fr.md @@ -1,35 +1,36 @@ --- -title: À propos de Rules Engine 2.0 -description: Ce qu'est Rules Engine 2.0, comment l'activer, et les concepts sur lesquels +title: À propos de Triage Engine +description: Ce qu'est Triage Engine, comment l'activer, et les concepts sur lesquels il repose weight: 1 audience: pro aliases: - /fr/automation/rules_engine_v2/about/ +- /fr/automation/rules_engine_2/about/ --- -Remarque : Rules Engine 2.0 est une fonctionnalité réservée à DefectDojo Pro. +Remarque : Triage Engine est une fonctionnalité réservée à DefectDojo Pro. -Rules Engine 2.0 est un générateur d'automatisation visuel. Au lieu d'un filtre associé à une liste plate d'actions, une règle est un **graphe** : un nœud déclencheur qui décide quand la règle se réveille, et un nombre quelconque de nœuds de logique, de Constatations et de sortie reliés entre eux pour indiquer ce qui se passe ensuite. +Triage Engine est un générateur d'automatisation visuel. Au lieu d'un filtre associé à une liste plate d'actions, une règle est un **graphe** : un nœud déclencheur qui décide quand la règle se réveille, et un nombre quelconque de nœuds de logique, de Constatations et de sortie reliés entre eux pour indiquer ce qui se passe ensuite. -Rules Engine 2.0 n'est accessible que via l'[interface Pro](/get_started/about/ui_pro_vs_os/). +Triage Engine n'est accessible que via l'[interface Pro](/get_started/about/ui_pro_vs_os/). ## Ce qu'il ajoute par rapport à Rules Engine -Le [Rules Engine](/automation/rules_engine/about/) d'origine applique une liste ordonnée d'actions à chaque Constatation correspondant à un filtre. Rules Engine 2.0 conserve cette capacité et ajoute quatre éléments : +Le [Rules Engine](/automation/rules_engine/about/) d'origine applique une liste ordonnée d'actions à chaque Constatation correspondant à un filtre. Triage Engine conserve cette capacité et ajoute quatre éléments : * **Le branchement.** Un nœud **If / Filter** (Si / Filtre) dirige les éléments vers une branche vraie et une branche fausse, de sorte qu'une seule règle puisse traiter les Constatations Critiques différemment du reste sans devoir être scindée en deux règles. * **La sortie (egress).** Une règle peut sortir de DefectDojo : ouvrir un ticket JIRA ou un ticket en aval, publier sur Slack ou Microsoft Teams, envoyer un e-mail, appeler un webhook, déclencher une alerte dans l'application, ou générer un rapport. * **La traçabilité.** Chaque exécution est enregistrée nœud par nœud sous forme d'[Exécution](../runs/), et chaque envoi sortant est enregistré comme une [Livraison](../deliveries/) qui indique exactement ce qui a été envoyé, où cela a été envoyé, et comment cela s'est terminé. * **Un mode de simulation.** Une règle peut enregistrer précisément ce qu'elle aurait envoyé sans rien envoyer réellement, ce qui permet de la tester en toute sécurité avant de la laisser agir à l'extérieur. -Les deux moteurs fonctionnent côte à côte. Activer Rules Engine 2.0 ne désactive ni ne convertit vos règles existantes, et il existe un [convertisseur](../converting_from_rules_engine/) pour le jour où vous voudrez les faire migrer. +Les deux moteurs fonctionnent côte à côte. Activer Triage Engine ne désactive ni ne convertit vos règles existantes, et il existe un [convertisseur](../converting_from_rules_engine/) pour le jour où vous voudrez les faire migrer. -## Activer Rules Engine 2.0 +## Activer Triage Engine -Rules Engine 2.0 est en version bêta et est désactivé par défaut. Un superutilisateur l'active depuis **Settings > Feature Flags** (Paramètres > Indicateurs de fonctionnalités), aussi bien sur les instances Cloud que sur les instances On-Premise. Voir [Indicateurs de fonctionnalités](/admin/feature_flags/pro__feature_flags/). +Triage Engine est en version bêta et est désactivé par défaut. Un superutilisateur l'active depuis **Settings > Feature Flags** (Paramètres > Indicateurs de fonctionnalités), aussi bien sur les instances Cloud que sur les instances On-Premise. Voir [Indicateurs de fonctionnalités](/admin/feature_flags/pro__feature_flags/). -Une fois l'indicateur activé, une section **Rules Engine 2.0** apparaît dans la barre latérale avec trois pages : +Une fois l'indicateur activé, une section **Triage Engine** apparaît dans la barre latérale avec trois pages : | Page | À quoi elle sert | |------|----------------| diff --git a/docs/content/automation/rules_engine_2/about.it.md b/docs/content/automation/triage_engine/about.it.md similarity index 84% rename from docs/content/automation/rules_engine_2/about.it.md rename to docs/content/automation/triage_engine/about.it.md index f3851b80eb2..4f8b4bb4329 100644 --- a/docs/content/automation/rules_engine_2/about.it.md +++ b/docs/content/automation/triage_engine/about.it.md @@ -1,34 +1,35 @@ --- -title: Informazioni su Rules Engine 2.0 -description: Cos'è Rules Engine 2.0, come attivarlo e i concetti su cui si basa +title: Informazioni su Triage Engine +description: Cos'è Triage Engine, come attivarlo e i concetti su cui si basa weight: 1 audience: pro aliases: - /it/automation/rules_engine_v2/about/ +- /it/automation/rules_engine_2/about/ --- -Nota: Rules Engine 2.0 è una funzionalità disponibile solo in DefectDojo Pro. +Nota: Triage Engine è una funzionalità disponibile solo in DefectDojo Pro. -Rules Engine 2.0 è un builder di automazione visuale. Invece di un filtro più un elenco piatto di azioni, una regola è un **grafo**: un nodo trigger che decide quando la regola si attiva, e un numero qualsiasi di nodi logici, Riscontro ed egress collegati tra loro per stabilire cosa succede dopo. +Triage Engine è un builder di automazione visuale. Invece di un filtro più un elenco piatto di azioni, una regola è un **grafo**: un nodo trigger che decide quando la regola si attiva, e un numero qualsiasi di nodi logici, Riscontro ed egress collegati tra loro per stabilire cosa succede dopo. -Rules Engine 2.0 è accessibile solo tramite la [UI Pro](/get_started/about/ui_pro_vs_os/). +Triage Engine è accessibile solo tramite la [UI Pro](/get_started/about/ui_pro_vs_os/). ## Cosa aggiunge rispetto a Rules Engine -Il [Rules Engine](/automation/rules_engine/about/) originale applica un elenco ordinato di azioni a ogni Riscontro che corrisponde a un filtro. Rules Engine 2.0 mantiene questa capacità e aggiunge quattro cose: +Il [Rules Engine](/automation/rules_engine/about/) originale applica un elenco ordinato di azioni a ogni Riscontro che corrisponde a un filtro. Triage Engine mantiene questa capacità e aggiunge quattro cose: * **Ramificazione.** Un nodo **If / Filter** instrada gli elementi lungo un ramo vero e uno falso, così una regola può trattare i Riscontri Critica in modo diverso dal resto senza doverla dividere in due regole. * **Egress.** Una regola può uscire da DefectDojo: aprire un ticket JIRA o un ticket a valle, pubblicare su Slack o Microsoft Teams, inviare un'email, chiamare un webhook, generare un avviso in-app o produrre un report. * **Tracciabilità.** Ogni esecuzione viene registrata nodo per nodo come [Run](../runs/), e ogni invio in uscita viene registrato come [Delivery](../deliveries/) che indica esattamente cosa è stato inviato, dove è andato e come è terminato. * **Una modalità di simulazione.** Una regola può registrare esattamente cosa avrebbe inviato senza inviare nulla, ed è così che la si testa in sicurezza prima che tocchi il mondo esterno. -I due motori funzionano fianco a fianco. Attivare Rules Engine 2.0 non disabilita né converte le regole esistenti, ed esiste un [convertitore](../converting_from_rules_engine/) per quando si vuole spostarle. +I due motori funzionano fianco a fianco. Attivare Triage Engine non disabilita né converte le regole esistenti, ed esiste un [convertitore](../converting_from_rules_engine/) per quando si vuole spostarle. -## Abilitare Rules Engine 2.0 +## Abilitare Triage Engine -Rules Engine 2.0 è in Beta ed è disattivato per impostazione predefinita. Un superuser lo attiva da **Settings > Feature Flags**, sia sulle istanze Cloud che On-Premise. Vedere [Feature Flags](/admin/feature_flags/pro__feature_flags/). +Triage Engine è in Beta ed è disattivato per impostazione predefinita. Un superuser lo attiva da **Settings > Feature Flags**, sia sulle istanze Cloud che On-Premise. Vedere [Feature Flags](/admin/feature_flags/pro__feature_flags/). -Una volta attivato il flag, nella barra laterale compare una sezione **Rules Engine 2.0** con tre pagine: +Una volta attivato il flag, nella barra laterale compare una sezione **Triage Engine** con tre pagine: | Pagina | A cosa serve | |------|----------------| diff --git a/docs/content/automation/rules_engine_2/about.ja.md b/docs/content/automation/triage_engine/about.ja.md similarity index 83% rename from docs/content/automation/rules_engine_2/about.ja.md rename to docs/content/automation/triage_engine/about.ja.md index 391695c9038..245c5ab143c 100644 --- a/docs/content/automation/rules_engine_2/about.ja.md +++ b/docs/content/automation/triage_engine/about.ja.md @@ -1,34 +1,35 @@ --- -title: Rules Engine 2.0 について -description: Rules Engine 2.0 とは何か、有効化の方法、基盤となる概念について +title: Triage Engine について +description: Triage Engine とは何か、有効化の方法、基盤となる概念について weight: 1 audience: pro aliases: - /ja/automation/rules_engine_v2/about/ +- /ja/automation/rules_engine_2/about/ --- -注: Rules Engine 2.0 は DefectDojo Pro 専用の機能です。 +注: Triage Engine は DefectDojo Pro 専用の機能です。 -Rules Engine 2.0 は、ビジュアルな自動化ビルダーです。フィルターとフラットなアクションのリストの代わりに、ルールは**グラフ**として構成されます。グラフは、ルールがいつ起動するかを決めるトリガーノードと、その後の処理内容を指定する任意の数のロジックノード、Finding ノード、Egress ノードが配線されたものです。 +Triage Engine は、ビジュアルな自動化ビルダーです。フィルターとフラットなアクションのリストの代わりに、ルールは**グラフ**として構成されます。グラフは、ルールがいつ起動するかを決めるトリガーノードと、その後の処理内容を指定する任意の数のロジックノード、Finding ノード、Egress ノードが配線されたものです。 -Rules Engine 2.0 には [Pro UI](/get_started/about/ui_pro_vs_os/) からのみアクセスできます。 +Triage Engine には [Pro UI](/get_started/about/ui_pro_vs_os/) からのみアクセスできます。 ## Rules Engine と比べて追加されるもの -従来の [Rules Engine](/automation/rules_engine/about/) は、1つのフィルターに一致するすべての Finding に対して、順序付けられたアクションのリストを適用します。Rules Engine 2.0 はこの機能を維持しつつ、次の4つを追加します。 +従来の [Rules Engine](/automation/rules_engine/about/) は、1つのフィルターに一致するすべての Finding に対して、順序付けられたアクションのリストを適用します。Triage Engine はこの機能を維持しつつ、次の4つを追加します。 * **分岐。** **If / Filter** ノードは、項目を true 分岐と false 分岐に振り分けます。これにより、1つのルールを2つに分割することなく、Critical の Finding をそれ以外と異なる方法で扱うことができます。 * **Egress。** ルールは DefectDojo の外部にアクションを送信できます。JIRA の課題やダウンストリームのチケットの起票、Slack や Microsoft Teams への投稿、メールの送信、Webhook の呼び出し、アプリ内アラートの発生、レポートの生成などが可能です。 * **トレーサビリティ。** すべての実行はノードごとに [Run](../runs/) として記録され、すべての送信は [Delivery](../deliveries/) として記録されます。Delivery には、何が送信され、どこへ送られ、どのように終了したかが正確に記録されます。 * **Simulate モード。** ルールは、実際には何も送信せずに、送信するはずだった内容を正確に記録できます。これにより、外部に影響を与える前にルールを安全にテストできます。 -両方のエンジンは並行して動作します。Rules Engine 2.0 を有効にしても、既存のルールが無効化されたり変換されたりすることはありません。ルールを移行したい場合のために [converter](../converting_from_rules_engine/) が用意されています。 +両方のエンジンは並行して動作します。Triage Engine を有効にしても、既存のルールが無効化されたり変換されたりすることはありません。ルールを移行したい場合のために [converter](../converting_from_rules_engine/) が用意されています。 -## Rules Engine 2.0 の有効化 +## Triage Engine の有効化 -Rules Engine 2.0 はベータ版であり、デフォルトでは無効になっています。スーパーユーザーが、Cloud インスタンス・On-Premise インスタンスの両方で **Settings > Feature Flags** から有効化します。[Feature Flags](/admin/feature_flags/pro__feature_flags/) を参照してください。 +Triage Engine はベータ版であり、デフォルトでは無効になっています。スーパーユーザーが、Cloud インスタンス・On-Premise インスタンスの両方で **Settings > Feature Flags** から有効化します。[Feature Flags](/admin/feature_flags/pro__feature_flags/) を参照してください。 -フラグが有効になると、サイドバーに **Rules Engine 2.0** セクションが表示され、次の3つのページが含まれます。 +フラグが有効になると、サイドバーに **Triage Engine** セクションが表示され、次の3つのページが含まれます。 | ページ | 用途 | |------|----------------| diff --git a/docs/content/automation/rules_engine_2/about.md b/docs/content/automation/triage_engine/about.md similarity index 84% rename from docs/content/automation/rules_engine_2/about.md rename to docs/content/automation/triage_engine/about.md index 08102876cc8..242baa0aa62 100644 --- a/docs/content/automation/rules_engine_2/about.md +++ b/docs/content/automation/triage_engine/about.md @@ -1,20 +1,21 @@ --- -title: "About Rules Engine 2.0" -description: "What Rules Engine 2.0 is, how to turn it on, and the concepts it is built from" +title: "About Triage Engine" +description: "What Triage Engine is, how to turn it on, and the concepts it is built from" weight: 1 audience: pro aliases: - /automation/rules_engine_v2/about/ + - /automation/rules_engine_2/about/ --- -Note: Rules Engine 2.0 is a DefectDojo Pro-only feature. +Note: Triage Engine is a DefectDojo Pro-only feature. -Rules Engine 2.0 is a visual automation builder. Instead of a filter plus a flat list of actions, a rule is a **graph**: a trigger node that decides when the rule wakes up, and any number of logic, Finding and egress nodes wired together to say what happens next. +Triage Engine is a visual automation builder. Instead of a filter plus a flat list of actions, a rule is a **graph**: a trigger node that decides when the rule wakes up, and any number of logic, Finding and egress nodes wired together to say what happens next. -Rules Engine 2.0 can only be accessed through the [Pro UI](/get_started/about/ui_pro_vs_os/). +Triage Engine can only be accessed through the [Pro UI](/get_started/about/ui_pro_vs_os/). ## What it adds over Rules Engine -The original [Rules Engine](/automation/rules_engine/about/) applies an ordered list of actions to every Finding that matches one filter. Rules Engine 2.0 keeps that capability and adds four things: +The original [Rules Engine](/automation/rules_engine/about/) applies an ordered list of actions to every Finding that matches one filter. Triage Engine keeps that capability and adds four things: * **Branching.** An **If / Filter** node routes items down a true branch and a false branch, so one rule can treat Critical Findings differently from the rest without being split into two rules. * **Egress.** A rule can leave DefectDojo: open a JIRA issue or a downstream ticket, post to Slack or Microsoft Teams, send an email, call a webhook, raise an in-app alert, or generate a report. @@ -23,13 +24,13 @@ The original [Rules Engine](/automation/rules_engine/about/) applies an ordered Rules are not limited to Findings. An Asset (Product) rule reacts to Assets being created, updated or tagged, or sweeps them on a schedule, and can set their fields, move them between Organizations, tag and untag them, and place them in the Asset hierarchy. That makes recurring inventory work self-service: instead of a one-off migration to regroup Assets, a rule expresses the grouping and keeps enforcing it as new Assets arrive. -Both engines run side by side. Turning on Rules Engine 2.0 does not disable or convert your existing rules, and there is a [converter](../converting_from_rules_engine/) for when you want to move them across. +Both engines run side by side. Turning on Triage Engine does not disable or convert your existing rules, and there is a [converter](../converting_from_rules_engine/) for when you want to move them across. -## Enabling Rules Engine 2.0 +## Enabling Triage Engine -Rules Engine 2.0 is in Beta and is off by default. A superuser turns it on from **Settings > Feature Flags**, on both Cloud and On-Premise instances. See [Feature Flags](/admin/feature_flags/pro__feature_flags/). +Triage Engine is in Beta and is off by default. A superuser turns it on from **Settings > Feature Flags**, on both Cloud and On-Premise instances. See [Feature Flags](/admin/feature_flags/pro__feature_flags/). -Once the flag is on, a **Rules Engine 2.0** section appears in the sidebar with three pages: +Once the flag is on, a **Triage Engine** section appears in the sidebar with three pages: | Page | What it is for | |------|----------------| @@ -120,7 +121,7 @@ Runs and deliveries are both kept for 180 days by default, then pruned. The prod ## Where to go next * [Building Rules](../building_rules/) covers the editor, triggers, scope, conditions and templates. -* [Node Reference](../node_reference/) documents all 37 nodes. +* [Node Reference](../node_reference/) documents all 41 nodes. * [Runs](../runs/) covers execution, traces, cascading and limits. * [Deliveries](../deliveries/) covers channels, statuses, retries and replay. * [Converting from Rules Engine](../converting_from_rules_engine/) covers moving existing rules across. diff --git a/docs/content/automation/rules_engine_2/about.pt-br.md b/docs/content/automation/triage_engine/about.pt-br.md similarity index 83% rename from docs/content/automation/rules_engine_2/about.pt-br.md rename to docs/content/automation/triage_engine/about.pt-br.md index a249e0d62de..a5fe2316bc8 100644 --- a/docs/content/automation/rules_engine_2/about.pt-br.md +++ b/docs/content/automation/triage_engine/about.pt-br.md @@ -1,34 +1,35 @@ --- -title: Sobre o Rules Engine 2.0 -description: O que é o Rules Engine 2.0, como ativá-lo e os conceitos em que se baseia +title: Sobre o Triage Engine +description: O que é o Triage Engine, como ativá-lo e os conceitos em que se baseia weight: 1 audience: pro aliases: - /pt-br/automation/rules_engine_v2/about/ +- /pt-br/automation/rules_engine_2/about/ --- -Nota: O Rules Engine 2.0 é um recurso exclusivo do DefectDojo Pro. +Nota: O Triage Engine é um recurso exclusivo do DefectDojo Pro. -Rules Engine 2.0 é um construtor visual de automação. Em vez de um filtro mais uma lista simples de ações, uma regra é um **grafo**: um nó de gatilho que decide quando a regra é ativada, e qualquer número de nós de lógica, de Achado e de saída (egress) conectados entre si para dizer o que acontece a seguir. +Triage Engine é um construtor visual de automação. Em vez de um filtro mais uma lista simples de ações, uma regra é um **grafo**: um nó de gatilho que decide quando a regra é ativada, e qualquer número de nós de lógica, de Achado e de saída (egress) conectados entre si para dizer o que acontece a seguir. -O Rules Engine 2.0 só pode ser acessado pela [Pro UI](/get_started/about/ui_pro_vs_os/). +O Triage Engine só pode ser acessado pela [Pro UI](/get_started/about/ui_pro_vs_os/). ## O que ele adiciona em relação ao Rules Engine -O [Rules Engine](/automation/rules_engine/about/) original aplica uma lista ordenada de ações a cada Achado que corresponde a um filtro. O Rules Engine 2.0 mantém essa capacidade e adiciona quatro coisas: +O [Rules Engine](/automation/rules_engine/about/) original aplica uma lista ordenada de ações a cada Achado que corresponde a um filtro. O Triage Engine mantém essa capacidade e adiciona quatro coisas: * **Ramificação (branching).** Um nó **If / Filter** encaminha os itens por um ramo verdadeiro e um ramo falso, de modo que uma única regra possa tratar Achados Críticos de forma diferente do restante sem precisar ser dividida em duas regras. * **Saída (egress).** Uma regra pode sair do DefectDojo: abrir um chamado no JIRA ou em um sistema de tickets externo, publicar no Slack ou no Microsoft Teams, enviar um e-mail, chamar um webhook, disparar um alerta no aplicativo ou gerar um relatório. * **Rastreabilidade.** Cada execução é registrada nó a nó como uma [Execução](../runs/), e cada envio de saída é registrado como uma [Entrega](../deliveries/) que informa exatamente o que foi enviado, para onde foi e como terminou. * **Um modo de simulação.** Uma regra pode registrar exatamente o que enviaria sem enviar nada de fato, o que permite testá-la com segurança antes de deixá-la tocar o mundo externo. -Os dois mecanismos funcionam lado a lado. Ativar o Rules Engine 2.0 não desativa nem converte suas regras existentes, e há um [conversor](../converting_from_rules_engine/) para quando você quiser migrá-las. +Os dois mecanismos funcionam lado a lado. Ativar o Triage Engine não desativa nem converte suas regras existentes, e há um [conversor](../converting_from_rules_engine/) para quando você quiser migrá-las. -## Ativando o Rules Engine 2.0 +## Ativando o Triage Engine -O Rules Engine 2.0 está em Beta e vem desativado por padrão. Um superusuário o ativa em **Settings > Feature Flags**, tanto em instâncias Cloud quanto On-Premise. Veja [Feature Flags](/admin/feature_flags/pro__feature_flags/). +O Triage Engine está em Beta e vem desativado por padrão. Um superusuário o ativa em **Settings > Feature Flags**, tanto em instâncias Cloud quanto On-Premise. Veja [Feature Flags](/admin/feature_flags/pro__feature_flags/). -Assim que a flag é ativada, uma seção **Rules Engine 2.0** aparece na barra lateral com três páginas: +Assim que a flag é ativada, uma seção **Triage Engine** aparece na barra lateral com três páginas: | Página | Para que serve | |------|----------------| diff --git a/docs/content/automation/rules_engine_2/about.zh-hans.md b/docs/content/automation/triage_engine/about.zh-hans.md similarity index 82% rename from docs/content/automation/rules_engine_2/about.zh-hans.md rename to docs/content/automation/triage_engine/about.zh-hans.md index 4b88870e684..e4cb78fc706 100644 --- a/docs/content/automation/rules_engine_2/about.zh-hans.md +++ b/docs/content/automation/triage_engine/about.zh-hans.md @@ -1,34 +1,35 @@ --- -title: 关于 Rules Engine 2.0 -description: Rules Engine 2.0 是什么、如何启用它，以及它所基于的核心概念 +title: 关于 Triage Engine +description: Triage Engine 是什么、如何启用它，以及它所基于的核心概念 weight: 1 audience: pro aliases: - /zh-hans/automation/rules_engine_v2/about/ +- /zh-hans/automation/rules_engine_2/about/ --- -注意：Rules Engine 2.0 是 DefectDojo Pro 专属功能。 +注意：Triage Engine 是 DefectDojo Pro 专属功能。 -Rules Engine 2.0 是一个可视化自动化构建器。规则不再是“一个过滤器加一份扁平的动作列表”，而是一个**图（graph）**：一个决定规则何时被唤醒的触发器节点，以及任意数量相互连接的逻辑、发现项和出站（egress）节点，用来说明接下来会发生什么。 +Triage Engine 是一个可视化自动化构建器。规则不再是“一个过滤器加一份扁平的动作列表”，而是一个**图（graph）**：一个决定规则何时被唤醒的触发器节点，以及任意数量相互连接的逻辑、发现项和出站（egress）节点，用来说明接下来会发生什么。 -Rules Engine 2.0 只能通过 [Pro UI](/get_started/about/ui_pro_vs_os/) 访问。 +Triage Engine 只能通过 [Pro UI](/get_started/about/ui_pro_vs_os/) 访问。 ## 相较于 Rules Engine 新增了什么 -原有的 [Rules Engine](/automation/rules_engine/about/) 会将一份有序的动作列表应用到匹配某个过滤器的每一个发现项上。Rules Engine 2.0 保留了这一能力，并新增了四项内容： +原有的 [Rules Engine](/automation/rules_engine/about/) 会将一份有序的动作列表应用到匹配某个过滤器的每一个发现项上。Triage Engine 保留了这一能力，并新增了四项内容： * **分支。** **If / Filter** 节点会将条目分流到“真”分支和“假”分支，因此一条规则就能对严重发现项与其他发现项采取不同处理方式，而无需拆分成两条规则。 * **出站（Egress）。** 规则可以离开 DefectDojo：打开一个 JIRA 问题单或下游工单、发布到 Slack 或 Microsoft Teams、发送邮件、调用 Webhook、发出应用内提醒，或生成报告。 * **可追溯性。** 每次执行都会作为一次[运行（Run）](../runs/)按节点逐一记录，每次出站发送都会作为一条[投递记录（Delivery）](../deliveries/)记录下来，准确说明发送了什么、发到了哪里、结果如何。 * **模拟模式。** 规则可以精确记录它本会发送的内容而不实际发送，这就是在让规则接触外部世界之前安全测试它的方式。 -两套引擎并行运行。启用 Rules Engine 2.0 不会禁用或转换您现有的规则，并且提供了一个[转换器](../converting_from_rules_engine/)，供您在想要迁移规则时使用。 +两套引擎并行运行。启用 Triage Engine 不会禁用或转换您现有的规则，并且提供了一个[转换器](../converting_from_rules_engine/)，供您在想要迁移规则时使用。 -## 启用 Rules Engine 2.0 +## 启用 Triage Engine -Rules Engine 2.0 处于 Beta 阶段，默认关闭。超级用户可以在 **Settings > Feature Flags** 中启用它，云端和本地部署实例均适用。参见[功能标志](/admin/feature_flags/pro__feature_flags/)。 +Triage Engine 处于 Beta 阶段，默认关闭。超级用户可以在 **Settings > Feature Flags** 中启用它，云端和本地部署实例均适用。参见[功能标志](/admin/feature_flags/pro__feature_flags/)。 -标志启用后，侧边栏会出现一个 **Rules Engine 2.0** 区块，下面有三个页面： +标志启用后，侧边栏会出现一个 **Triage Engine** 区块，下面有三个页面： | Page | What it is for | |------|----------------| diff --git a/docs/content/automation/rules_engine_2/building_rules.de.md b/docs/content/automation/triage_engine/building_rules.de.md similarity index 97% rename from docs/content/automation/rules_engine_2/building_rules.de.md rename to docs/content/automation/triage_engine/building_rules.de.md index 91383c52525..7e00dcd8a8a 100644 --- a/docs/content/automation/rules_engine_2/building_rules.de.md +++ b/docs/content/automation/triage_engine/building_rules.de.md @@ -5,15 +5,16 @@ weight: 2 audience: pro aliases: - /de/automation/rules_engine_v2/building_rules/ +- /de/automation/rules_engine_2/building_rules/ --- -Note: Rules Engine 2.0 is a DefectDojo Pro-only feature. +Note: Triage Engine is a DefectDojo Pro-only feature. Eine Regel wird auf einer Zeichenfläche (Canvas) erstellt. Sie ziehen Knoten aus einer Palette, verbinden sie miteinander und konfigurieren jeden davon in einem Seitenpanel. Diese Seite behandelt die Teile dieses Prozesses, die unabhängig von den verwendeten Knoten gleich sind. Die Knoten selbst finden Sie in der [Node-Referenz](../node_reference/). ## Der Editor -Öffnen Sie **Rules Engine 2.0 > All Rules** und wählen Sie **New Rule**, oder öffnen Sie eine bestehende Regel zur Bearbeitung. +Öffnen Sie **Triage Engine > All Rules** und wählen Sie **New Rule**, oder öffnen Sie eine bestehende Regel zur Bearbeitung. Die Palette ist in vier Kategorien gegliedert, was auch der Reihenfolge entspricht, in der Elemente einen typischen Graphen durchlaufen: diff --git a/docs/content/automation/rules_engine_2/building_rules.es.md b/docs/content/automation/triage_engine/building_rules.es.md similarity index 97% rename from docs/content/automation/rules_engine_2/building_rules.es.md rename to docs/content/automation/triage_engine/building_rules.es.md index 5cb523a3c03..a55ec722182 100644 --- a/docs/content/automation/rules_engine_2/building_rules.es.md +++ b/docs/content/automation/triage_engine/building_rules.es.md @@ -6,15 +6,16 @@ weight: 2 audience: pro aliases: - /es/automation/rules_engine_v2/building_rules/ +- /es/automation/rules_engine_2/building_rules/ --- -Nota: Rules Engine 2.0 es una función exclusiva de DefectDojo Pro. +Nota: Triage Engine es una función exclusiva de DefectDojo Pro. Una regla se construye en un lienzo. Se arrastran nodos desde una paleta, se conectan entre sí y cada uno se configura en un panel lateral. Esta página cubre las partes de ese proceso que son iguales sea cual sea el nodo que se use. Los propios nodos están en la [Referencia de nodos](../node_reference/). ## El editor -Abra **Rules Engine 2.0 > Todas las reglas** y elija **Nueva regla**, o abra una regla existente para editarla. +Abra **Triage Engine > Todas las reglas** y elija **Nueva regla**, o abra una regla existente para editarla. La paleta está agrupada en cuatro categorías, que también es el orden en que los elementos fluyen a través de un grafo típico: diff --git a/docs/content/automation/rules_engine_2/building_rules.fr.md b/docs/content/automation/triage_engine/building_rules.fr.md similarity index 97% rename from docs/content/automation/rules_engine_2/building_rules.fr.md rename to docs/content/automation/triage_engine/building_rules.fr.md index 7c501ed757a..54e5a040af0 100644 --- a/docs/content/automation/rules_engine_2/building_rules.fr.md +++ b/docs/content/automation/triage_engine/building_rules.fr.md @@ -6,15 +6,16 @@ weight: 2 audience: pro aliases: - /fr/automation/rules_engine_v2/building_rules/ +- /fr/automation/rules_engine_2/building_rules/ --- -Remarque : Rules Engine 2.0 est une fonctionnalité réservée à DefectDojo Pro. +Remarque : Triage Engine est une fonctionnalité réservée à DefectDojo Pro. Une règle est construite sur un canevas. Vous glissez des nœuds depuis une palette, vous les reliez entre eux, et vous configurez chacun d'eux dans un panneau latéral. Cette page couvre les aspects de ce processus qui sont identiques quels que soient les nœuds utilisés. Les nœuds eux-mêmes sont décrits dans la [Référence des nœuds](../node_reference/). ## L'éditeur -Ouvrez **Rules Engine 2.0 > All Rules** et choisissez **New Rule** (Nouvelle règle), ou ouvrez une règle existante pour la modifier. +Ouvrez **Triage Engine > All Rules** et choisissez **New Rule** (Nouvelle règle), ou ouvrez une règle existante pour la modifier. La palette est organisée en quatre catégories, qui correspondent aussi à l'ordre dans lequel les éléments traversent un graphe typique : diff --git a/docs/content/automation/rules_engine_2/building_rules.it.md b/docs/content/automation/triage_engine/building_rules.it.md similarity index 97% rename from docs/content/automation/rules_engine_2/building_rules.it.md rename to docs/content/automation/triage_engine/building_rules.it.md index 4eb558f5ff1..ebf37c2e8ae 100644 --- a/docs/content/automation/rules_engine_2/building_rules.it.md +++ b/docs/content/automation/triage_engine/building_rules.it.md @@ -6,15 +6,16 @@ weight: 2 audience: pro aliases: - /it/automation/rules_engine_v2/building_rules/ +- /it/automation/rules_engine_2/building_rules/ --- -Nota: Rules Engine 2.0 è una funzionalità disponibile solo in DefectDojo Pro. +Nota: Triage Engine è una funzionalità disponibile solo in DefectDojo Pro. Una regola si costruisce su una canvas. Si trascinano nodi da una palette, si collegano tra loro e si configura ciascuno in un pannello laterale. Questa pagina tratta le parti di questo processo che sono le stesse indipendentemente dai nodi usati. I nodi stessi sono descritti in [Node Reference](../node_reference/). ## L'editor -Aprire **Rules Engine 2.0 > All Rules** e scegliere **New Rule**, oppure aprire una regola esistente per modificarla. +Aprire **Triage Engine > All Rules** e scegliere **New Rule**, oppure aprire una regola esistente per modificarla. La palette è raggruppata in quattro categorie, che rappresentano anche l'ordine in cui gli elementi attraversano un grafo tipico: diff --git a/docs/content/automation/rules_engine_2/building_rules.ja.md b/docs/content/automation/triage_engine/building_rules.ja.md similarity index 97% rename from docs/content/automation/rules_engine_2/building_rules.ja.md rename to docs/content/automation/triage_engine/building_rules.ja.md index 99a0d2d71d0..782addc1a15 100644 --- a/docs/content/automation/rules_engine_2/building_rules.ja.md +++ b/docs/content/automation/triage_engine/building_rules.ja.md @@ -5,15 +5,16 @@ weight: 2 audience: pro aliases: - /ja/automation/rules_engine_v2/building_rules/ +- /ja/automation/rules_engine_2/building_rules/ --- -注: Rules Engine 2.0 は DefectDojo Pro 専用の機能です。 +注: Triage Engine は DefectDojo Pro 専用の機能です。 ルールはキャンバス上で構築します。パレットからノードをドラッグして配線し、それぞれをサイドパネルで設定します。このページでは、どのノードを使う場合でも共通するプロセスの部分を扱います。ノード自体については [Node Reference](../node_reference/) を参照してください。 ## エディター -**Rules Engine 2.0 > All Rules** を開き、**New Rule** を選択するか、既存のルールを開いて編集します。 +**Triage Engine > All Rules** を開き、**New Rule** を選択するか、既存のルールを開いて編集します。 パレットは4つのカテゴリーにグループ分けされており、これは一般的なグラフの中を項目が流れていく順序でもあります。 diff --git a/docs/content/automation/rules_engine_2/building_rules.md b/docs/content/automation/triage_engine/building_rules.md similarity index 98% rename from docs/content/automation/rules_engine_2/building_rules.md rename to docs/content/automation/triage_engine/building_rules.md index fb51f01fa98..d40d690b372 100644 --- a/docs/content/automation/rules_engine_2/building_rules.md +++ b/docs/content/automation/triage_engine/building_rules.md @@ -5,14 +5,15 @@ weight: 2 audience: pro aliases: - /automation/rules_engine_v2/building_rules/ + - /automation/rules_engine_2/building_rules/ --- -Note: Rules Engine 2.0 is a DefectDojo Pro-only feature. +Note: Triage Engine is a DefectDojo Pro-only feature. A rule is built on a canvas. You drag nodes out of a palette, wire them together, and configure each one in a side panel. This page covers the parts of that process that are the same whichever nodes you use. The nodes themselves are in the [Node Reference](../node_reference/). ## Starting a rule -From **Rules Engine 2.0 > All Rules** there are two ways to begin. +From **Triage Engine > All Rules** there are two ways to begin. **From Template** opens a gallery of rules that ship with DefectDojo, grouped into packs. Each card says what the rule is for, which nodes its graph contains, and what you have to configure before it diff --git a/docs/content/automation/rules_engine_2/building_rules.pt-br.md b/docs/content/automation/triage_engine/building_rules.pt-br.md similarity index 97% rename from docs/content/automation/rules_engine_2/building_rules.pt-br.md rename to docs/content/automation/triage_engine/building_rules.pt-br.md index 52775013257..dc4bcbc1e49 100644 --- a/docs/content/automation/rules_engine_2/building_rules.pt-br.md +++ b/docs/content/automation/triage_engine/building_rules.pt-br.md @@ -5,15 +5,16 @@ weight: 2 audience: pro aliases: - /pt-br/automation/rules_engine_v2/building_rules/ +- /pt-br/automation/rules_engine_2/building_rules/ --- -Nota: O Rules Engine 2.0 é um recurso exclusivo do DefectDojo Pro. +Nota: O Triage Engine é um recurso exclusivo do DefectDojo Pro. Uma regra é construída em uma tela (canvas). Você arrasta nós de uma paleta, os conecta entre si e configura cada um em um painel lateral. Esta página aborda as partes desse processo que são iguais independentemente dos nós usados. Os próprios nós estão descritos em [Node Reference](../node_reference/). ## O editor -Abra **Rules Engine 2.0 > All Rules** e escolha **New Rule**, ou abra uma regra existente para editá-la. +Abra **Triage Engine > All Rules** e escolha **New Rule**, ou abra uma regra existente para editá-la. A paleta é agrupada em quatro categorias, que também é a ordem em que os itens fluem por um grafo típico: diff --git a/docs/content/automation/rules_engine_2/building_rules.zh-hans.md b/docs/content/automation/triage_engine/building_rules.zh-hans.md similarity index 97% rename from docs/content/automation/rules_engine_2/building_rules.zh-hans.md rename to docs/content/automation/triage_engine/building_rules.zh-hans.md index f63b1040549..c7531cbe63a 100644 --- a/docs/content/automation/rules_engine_2/building_rules.zh-hans.md +++ b/docs/content/automation/triage_engine/building_rules.zh-hans.md @@ -5,15 +5,16 @@ weight: 2 audience: pro aliases: - /zh-hans/automation/rules_engine_v2/building_rules/ +- /zh-hans/automation/rules_engine_2/building_rules/ --- -注意：Rules Engine 2.0 是 DefectDojo Pro 专属功能。 +注意：Triage Engine 是 DefectDojo Pro 专属功能。 规则是在画布上构建的。您从调色板中拖出节点，将它们连接起来，并在侧边面板中配置每一个节点。本页介绍的是这一过程中不论使用哪些节点都相同的部分。节点本身的说明请见[节点参考](../node_reference/)。 ## 编辑器 -打开 **Rules Engine 2.0 > All Rules**，选择 **New Rule**，或打开一条已有规则进行编辑。 +打开 **Triage Engine > All Rules**，选择 **New Rule**，或打开一条已有规则进行编辑。 调色板分为四个类别，这也是条目在典型图中流动的顺序： diff --git a/docs/content/automation/rules_engine_2/configuration.de.md b/docs/content/automation/triage_engine/configuration.de.md similarity index 90% rename from docs/content/automation/rules_engine_2/configuration.de.md rename to docs/content/automation/triage_engine/configuration.de.md index 6f58ca5bb20..26baffad99f 100644 --- a/docs/content/automation/rules_engine_2/configuration.de.md +++ b/docs/content/automation/triage_engine/configuration.de.md @@ -1,17 +1,18 @@ --- title: Konfiguration -description: Einstellungen auf Deployment-Ebene für Rules Engine 2.0 +description: Einstellungen auf Deployment-Ebene für Triage Engine weight: 7 audience: pro aliases: - /de/automation/rules_engine_v2/configuration/ +- /de/automation/rules_engine_2/configuration/ --- -Note: Rules Engine 2.0 is a DefectDojo Pro-only feature. +Note: Triage Engine is a DefectDojo Pro-only feature. -Rules Engine 2.0 funktioniert von Haus aus. Die Einstellungen auf dieser Seite richten sich an Deployments, die Durchsatz, Aufbewahrung oder die Richtlinie für ausgehenden Netzwerkverkehr anpassen müssen. Alle werden auf dieselbe Weise angewendet wie jede andere DefectDojo-Einstellung (siehe [Konfiguration](/get_started/open_source/configuration/)). +Triage Engine funktioniert von Haus aus. Die Einstellungen auf dieser Seite richten sich an Deployments, die Durchsatz, Aufbewahrung oder die Richtlinie für ausgehenden Netzwerkverkehr anpassen müssen. Alle werden auf dieselbe Weise angewendet wie jede andere DefectDojo-Einstellung (siehe [Konfiguration](/get_started/open_source/configuration/)). -Rules Engine 2.0 wird getrennt von der ursprünglichen Rules Engine konfiguriert. Die beiden Engines teilen sich kein Tuning, sodass eine `DD_RULES_ENGINE_*`-Einstellung sich nicht auf Rules Engine 2.0 auswirkt und eine `DD_RULES_V2_*`-Einstellung sich nicht auf die ursprüngliche Engine auswirkt. +Triage Engine wird getrennt von der ursprünglichen Rules Engine konfiguriert. Die beiden Engines teilen sich kein Tuning, sodass eine `DD_RULES_ENGINE_*`-Einstellung sich nicht auf Triage Engine auswirkt und eine `DD_RULES_V2_*`-Einstellung sich nicht auf die ursprüngliche Engine auswirkt. ```python DD_RULES_V2_EVENT_BATCH=(int, 500), diff --git a/docs/content/automation/rules_engine_2/configuration.es.md b/docs/content/automation/triage_engine/configuration.es.md similarity index 90% rename from docs/content/automation/rules_engine_2/configuration.es.md rename to docs/content/automation/triage_engine/configuration.es.md index 93c8d5027d9..dd70dcb5c12 100644 --- a/docs/content/automation/rules_engine_2/configuration.es.md +++ b/docs/content/automation/triage_engine/configuration.es.md @@ -1,17 +1,18 @@ --- title: Configuración -description: Ajustes a nivel de despliegue para Rules Engine 2.0 +description: Ajustes a nivel de despliegue para Triage Engine weight: 7 audience: pro aliases: - /es/automation/rules_engine_v2/configuration/ +- /es/automation/rules_engine_2/configuration/ --- -Nota: Rules Engine 2.0 es una función exclusiva de DefectDojo Pro. +Nota: Triage Engine es una función exclusiva de DefectDojo Pro. -Rules Engine 2.0 funciona de fábrica. Los ajustes de esta página son para despliegues que necesitan afinar el rendimiento, la retención o la política de red saliente. Todos se aplican de la misma manera que cualquier otro ajuste de DefectDojo (consulte [Configuración](/get_started/open_source/configuration/)). +Triage Engine funciona de fábrica. Los ajustes de esta página son para despliegues que necesitan afinar el rendimiento, la retención o la política de red saliente. Todos se aplican de la misma manera que cualquier otro ajuste de DefectDojo (consulte [Configuración](/get_started/open_source/configuration/)). -Rules Engine 2.0 se configura por separado del Rules Engine original. Los dos motores no comparten ningún ajuste, de modo que un ajuste `DD_RULES_ENGINE_*` no afecta a Rules Engine 2.0 y un ajuste `DD_RULES_V2_*` no afecta al motor original. +Triage Engine se configura por separado del Rules Engine original. Los dos motores no comparten ningún ajuste, de modo que un ajuste `DD_RULES_ENGINE_*` no afecta a Triage Engine y un ajuste `DD_RULES_V2_*` no afecta al motor original. ```python DD_RULES_V2_EVENT_BATCH=(int, 500), @@ -133,7 +134,7 @@ Superado este límite, el nodo registra una **omisión visible** que indica sobr ## Ajustes relacionados -Algunos nodos de Rules Engine 2.0 usan la configuración de integración de todo el sistema en lugar de la propia: +Algunos nodos de Triage Engine usan la configuración de integración de todo el sistema en lugar de la propia: * **Enviar un mensaje de Slack** usa el token de Slack del sistema, y recurre al canal de Slack del sistema cuando el nodo no indica ninguno. * **Enviar un mensaje de Microsoft Teams** usa el webhook de Microsoft Teams de los ajustes del sistema. diff --git a/docs/content/automation/rules_engine_2/configuration.fr.md b/docs/content/automation/triage_engine/configuration.fr.md similarity index 90% rename from docs/content/automation/rules_engine_2/configuration.fr.md rename to docs/content/automation/triage_engine/configuration.fr.md index c04669e81f0..162dc13a907 100644 --- a/docs/content/automation/rules_engine_2/configuration.fr.md +++ b/docs/content/automation/triage_engine/configuration.fr.md @@ -1,17 +1,18 @@ --- title: Configuration -description: Paramètres au niveau du déploiement pour Rules Engine 2.0 +description: Paramètres au niveau du déploiement pour Triage Engine weight: 7 audience: pro aliases: - /fr/automation/rules_engine_v2/configuration/ +- /fr/automation/rules_engine_2/configuration/ --- -Remarque : Rules Engine 2.0 est une fonctionnalité réservée à DefectDojo Pro. +Remarque : Triage Engine est une fonctionnalité réservée à DefectDojo Pro. -Rules Engine 2.0 fonctionne dès l'installation. Les paramètres de cette page s'adressent aux déploiements qui ont besoin d'ajuster le débit, la rétention ou la politique réseau sortante. Ils s'appliquent tous de la même manière que n'importe quel autre paramètre DefectDojo (voir [Configuration](/get_started/open_source/configuration/)). +Triage Engine fonctionne dès l'installation. Les paramètres de cette page s'adressent aux déploiements qui ont besoin d'ajuster le débit, la rétention ou la politique réseau sortante. Ils s'appliquent tous de la même manière que n'importe quel autre paramètre DefectDojo (voir [Configuration](/get_started/open_source/configuration/)). -Rules Engine 2.0 se configure séparément du Rules Engine d'origine. Les deux moteurs ne partagent aucun réglage : un paramètre `DD_RULES_ENGINE_*` n'affecte pas Rules Engine 2.0, et un paramètre `DD_RULES_V2_*` n'affecte pas le moteur d'origine. +Triage Engine se configure séparément du Rules Engine d'origine. Les deux moteurs ne partagent aucun réglage : un paramètre `DD_RULES_ENGINE_*` n'affecte pas Triage Engine, et un paramètre `DD_RULES_V2_*` n'affecte pas le moteur d'origine. ```python DD_RULES_V2_EVENT_BATCH=(int, 500), @@ -133,7 +134,7 @@ Au-delà de ce plafond, le nœud enregistre un **saut visible** indiquant combie ## Paramètres associés -Certains nœuds de Rules Engine 2.0 utilisent une configuration d'intégration à l'échelle du système plutôt que la leur propre : +Certains nœuds de Triage Engine utilisent une configuration d'intégration à l'échelle du système plutôt que la leur propre : * **Send a Slack Message** (Envoyer un message Slack) utilise le jeton Slack du système, et se rabat sur le canal Slack du système lorsque le nœud n'en nomme aucun. * **Send a Microsoft Teams Message** (Envoyer un message Microsoft Teams) utilise le webhook Microsoft Teams des paramètres système. diff --git a/docs/content/automation/rules_engine_2/configuration.it.md b/docs/content/automation/triage_engine/configuration.it.md similarity index 89% rename from docs/content/automation/rules_engine_2/configuration.it.md rename to docs/content/automation/triage_engine/configuration.it.md index 2b5f8c26c72..a157c74ac10 100644 --- a/docs/content/automation/rules_engine_2/configuration.it.md +++ b/docs/content/automation/triage_engine/configuration.it.md @@ -1,17 +1,18 @@ --- title: Configurazione -description: Impostazioni a livello di deployment per Rules Engine 2.0 +description: Impostazioni a livello di deployment per Triage Engine weight: 7 audience: pro aliases: - /it/automation/rules_engine_v2/configuration/ +- /it/automation/rules_engine_2/configuration/ --- -Nota: Rules Engine 2.0 è una funzionalità disponibile solo in DefectDojo Pro. +Nota: Triage Engine è una funzionalità disponibile solo in DefectDojo Pro. -Rules Engine 2.0 funziona subito, senza configurazione. Le impostazioni di questa pagina servono ai deployment che devono ottimizzare il throughput, la conservazione o la politica di rete in uscita. Tutte vengono applicate allo stesso modo di qualsiasi altra impostazione di DefectDojo (vedere [Configuration](/get_started/open_source/configuration/)). +Triage Engine funziona subito, senza configurazione. Le impostazioni di questa pagina servono ai deployment che devono ottimizzare il throughput, la conservazione o la politica di rete in uscita. Tutte vengono applicate allo stesso modo di qualsiasi altra impostazione di DefectDojo (vedere [Configuration](/get_started/open_source/configuration/)). -Rules Engine 2.0 viene configurato separatamente dal Rules Engine originale. I due motori non condividono alcuna impostazione: un'impostazione `DD_RULES_ENGINE_*` non influisce su Rules Engine 2.0 e un'impostazione `DD_RULES_V2_*` non influisce sul motore originale. +Triage Engine viene configurato separatamente dal Rules Engine originale. I due motori non condividono alcuna impostazione: un'impostazione `DD_RULES_ENGINE_*` non influisce su Triage Engine e un'impostazione `DD_RULES_V2_*` non influisce sul motore originale. ```python DD_RULES_V2_EVENT_BATCH=(int, 500), @@ -133,7 +134,7 @@ Oltre questo tetto il nodo registra un'**omissione visibile** che indica quanti ## Impostazioni correlate -Alcuni nodi di Rules Engine 2.0 usano la configurazione di integrazione a livello di sistema invece della propria: +Alcuni nodi di Triage Engine usano la configurazione di integrazione a livello di sistema invece della propria: * **Send a Slack Message** usa il token Slack di sistema, e ricade sul canale Slack di sistema quando il nodo non ne indica uno. * **Send a Microsoft Teams Message** usa il webhook Microsoft Teams dalle impostazioni di sistema. diff --git a/docs/content/automation/rules_engine_2/configuration.ja.md b/docs/content/automation/triage_engine/configuration.ja.md similarity index 90% rename from docs/content/automation/rules_engine_2/configuration.ja.md rename to docs/content/automation/triage_engine/configuration.ja.md index 6d85dafd129..c99911f858a 100644 --- a/docs/content/automation/rules_engine_2/configuration.ja.md +++ b/docs/content/automation/triage_engine/configuration.ja.md @@ -1,17 +1,18 @@ --- title: 設定 -description: Rules Engine 2.0 のデプロイメントレベルの設定 +description: Triage Engine のデプロイメントレベルの設定 weight: 7 audience: pro aliases: - /ja/automation/rules_engine_v2/configuration/ +- /ja/automation/rules_engine_2/configuration/ --- -注: Rules Engine 2.0 は DefectDojo Pro 専用の機能です。 +注: Triage Engine は DefectDojo Pro 専用の機能です。 -Rules Engine 2.0 は、そのままの状態で動作します。このページの設定は、スループット、保持期間、または送信先ネットワークポリシーを調整する必要があるデプロイメント向けのものです。これらはすべて、他の DefectDojo の設定と同じ方法で適用されます([設定](/get_started/open_source/configuration/) を参照)。 +Triage Engine は、そのままの状態で動作します。このページの設定は、スループット、保持期間、または送信先ネットワークポリシーを調整する必要があるデプロイメント向けのものです。これらはすべて、他の DefectDojo の設定と同じ方法で適用されます([設定](/get_started/open_source/configuration/) を参照)。 -Rules Engine 2.0 は、従来の Rules Engine とは別に設定されます。両エンジンの間でチューニングは共有されないため、`DD_RULES_ENGINE_*` の設定は Rules Engine 2.0 に影響を与えず、`DD_RULES_V2_*` の設定は従来のエンジンに影響を与えません。 +Triage Engine は、従来の Rules Engine とは別に設定されます。両エンジンの間でチューニングは共有されないため、`DD_RULES_ENGINE_*` の設定は Triage Engine に影響を与えず、`DD_RULES_V2_*` の設定は従来のエンジンに影響を与えません。 ```python DD_RULES_V2_EVENT_BATCH=(int, 500), @@ -133,7 +134,7 @@ Webhook の URL については、次の通りです。 ## 関連する設定 -一部の Rules Engine 2.0 ノードは、独自の設定ではなくシステム全体のインテグレーション設定を使用します。 +一部の Triage Engine ノードは、独自の設定ではなくシステム全体のインテグレーション設定を使用します。 * **Send a Slack Message** はシステムの Slack トークンを使用し、ノードでチャンネルが指定されていない場合はシステムの Slack チャンネルにフォールバックします。 * **Send a Microsoft Teams Message** は、システム設定の Microsoft Teams webhook を使用します。 diff --git a/docs/content/automation/rules_engine_2/configuration.md b/docs/content/automation/triage_engine/configuration.md similarity index 89% rename from docs/content/automation/rules_engine_2/configuration.md rename to docs/content/automation/triage_engine/configuration.md index 1f28ab56de0..5fe3197228f 100644 --- a/docs/content/automation/rules_engine_2/configuration.md +++ b/docs/content/automation/triage_engine/configuration.md @@ -1,16 +1,17 @@ --- title: "Configuration" -description: "Deployment level settings for Rules Engine 2.0" +description: "Deployment level settings for Triage Engine" weight: 7 audience: pro aliases: - /automation/rules_engine_v2/configuration/ + - /automation/rules_engine_2/configuration/ --- -Note: Rules Engine 2.0 is a DefectDojo Pro-only feature. +Note: Triage Engine is a DefectDojo Pro-only feature. -Rules Engine 2.0 works out of the box. The settings on this page are for deployments that need to tune throughput, retention, or outbound network policy. All of them are applied the same way as any other DefectDojo setting (see [Configuration](/get_started/open_source/configuration/)). +Triage Engine works out of the box. The settings on this page are for deployments that need to tune throughput, retention, or outbound network policy. All of them are applied the same way as any other DefectDojo setting (see [Configuration](/get_started/open_source/configuration/)). -Rules Engine 2.0 is configured separately from the original Rules Engine. The two engines share no tuning, so a `DD_RULES_ENGINE_*` setting does not affect Rules Engine 2.0 and a `DD_RULES_V2_*` setting does not affect the original engine. +Triage Engine is configured separately from the original Rules Engine. The two engines share no tuning, so a `DD_RULES_ENGINE_*` setting does not affect Triage Engine and a `DD_RULES_V2_*` setting does not affect the original engine. ```python DD_RULES_V2_EVENT_BATCH=(int, 500), @@ -132,7 +133,7 @@ Past this ceiling the node records a **visible skip** saying how many items it d ## Related settings -Some Rules Engine 2.0 nodes use system-wide integration configuration rather than their own: +Some Triage Engine nodes use system-wide integration configuration rather than their own: * **Send a Slack Message** uses the system Slack token, and falls back to the system Slack channel when the node names none. * **Send a Microsoft Teams Message** uses the Microsoft Teams webhook from system settings. diff --git a/docs/content/automation/rules_engine_2/configuration.pt-br.md b/docs/content/automation/triage_engine/configuration.pt-br.md similarity index 89% rename from docs/content/automation/rules_engine_2/configuration.pt-br.md rename to docs/content/automation/triage_engine/configuration.pt-br.md index a7347f07c89..ceaa3e4006b 100644 --- a/docs/content/automation/rules_engine_2/configuration.pt-br.md +++ b/docs/content/automation/triage_engine/configuration.pt-br.md @@ -1,17 +1,18 @@ --- title: Configuração -description: Configurações em nível de implantação para o Rules Engine 2.0 +description: Configurações em nível de implantação para o Triage Engine weight: 7 audience: pro aliases: - /pt-br/automation/rules_engine_v2/configuration/ +- /pt-br/automation/rules_engine_2/configuration/ --- -Nota: O Rules Engine 2.0 é um recurso exclusivo do DefectDojo Pro. +Nota: O Triage Engine é um recurso exclusivo do DefectDojo Pro. -O Rules Engine 2.0 funciona pronto para uso. As configurações desta página são para implantações que precisam ajustar throughput, retenção ou a política de rede de saída. Todas elas são aplicadas da mesma forma que qualquer outra configuração do DefectDojo (veja [Configuration](/get_started/open_source/configuration/)). +O Triage Engine funciona pronto para uso. As configurações desta página são para implantações que precisam ajustar throughput, retenção ou a política de rede de saída. Todas elas são aplicadas da mesma forma que qualquer outra configuração do DefectDojo (veja [Configuration](/get_started/open_source/configuration/)). -O Rules Engine 2.0 é configurado separadamente do Rules Engine original. Os dois mecanismos não compartilham nenhum ajuste, portanto uma configuração `DD_RULES_ENGINE_*` não afeta o Rules Engine 2.0, e uma configuração `DD_RULES_V2_*` não afeta o mecanismo original. +O Triage Engine é configurado separadamente do Rules Engine original. Os dois mecanismos não compartilham nenhum ajuste, portanto uma configuração `DD_RULES_ENGINE_*` não afeta o Triage Engine, e uma configuração `DD_RULES_V2_*` não afeta o mecanismo original. ```python DD_RULES_V2_EVENT_BATCH=(int, 500), @@ -133,7 +134,7 @@ Após esse limite, o nó registra uma **omissão visível (visible skip)** infor ## Configurações relacionadas -Alguns nós do Rules Engine 2.0 usam a configuração de integração de todo o sistema, em vez da própria: +Alguns nós do Triage Engine usam a configuração de integração de todo o sistema, em vez da própria: * **Send a Slack Message** usa o token do Slack do sistema, e recorre ao canal do Slack do sistema quando o nó não indica nenhum. * **Send a Microsoft Teams Message** usa o webhook do Microsoft Teams das configurações do sistema. diff --git a/docs/content/automation/rules_engine_2/configuration.zh-hans.md b/docs/content/automation/triage_engine/configuration.zh-hans.md similarity index 90% rename from docs/content/automation/rules_engine_2/configuration.zh-hans.md rename to docs/content/automation/triage_engine/configuration.zh-hans.md index e43bd7ec366..5303a6336b1 100644 --- a/docs/content/automation/rules_engine_2/configuration.zh-hans.md +++ b/docs/content/automation/triage_engine/configuration.zh-hans.md @@ -1,17 +1,18 @@ --- title: 配置 -description: Rules Engine 2.0 的部署层面设置 +description: Triage Engine 的部署层面设置 weight: 7 audience: pro aliases: - /zh-hans/automation/rules_engine_v2/configuration/ +- /zh-hans/automation/rules_engine_2/configuration/ --- -注意：Rules Engine 2.0 是 DefectDojo Pro 专属功能。 +注意：Triage Engine 是 DefectDojo Pro 专属功能。 -Rules Engine 2.0 开箱即用。本页的设置面向那些需要调整吞吐量、保留期或出站网络策略的部署环境。所有这些设置的应用方式都与其他任何 DefectDojo 设置相同（参见[配置](/get_started/open_source/configuration/)）。 +Triage Engine 开箱即用。本页的设置面向那些需要调整吞吐量、保留期或出站网络策略的部署环境。所有这些设置的应用方式都与其他任何 DefectDojo 设置相同（参见[配置](/get_started/open_source/configuration/)）。 -Rules Engine 2.0 与原有的 Rules Engine 分开配置。两套引擎不共享任何调优参数，因此 `DD_RULES_ENGINE_*` 设置不会影响 Rules Engine 2.0，`DD_RULES_V2_*` 设置也不会影响原有引擎。 +Triage Engine 与原有的 Rules Engine 分开配置。两套引擎不共享任何调优参数，因此 `DD_RULES_ENGINE_*` 设置不会影响 Triage Engine，`DD_RULES_V2_*` 设置也不会影响原有引擎。 ```python DD_RULES_V2_EVENT_BATCH=(int, 500), @@ -133,7 +134,7 @@ DD_RULES_V2_MAX_PER_ITEM_SENDS=(int, 1000), ## 相关设置 -部分 Rules Engine 2.0 节点使用的是系统级的集成配置，而不是节点自身的配置： +部分 Triage Engine 节点使用的是系统级的集成配置，而不是节点自身的配置： * **Send a Slack Message** 使用系统级的 Slack 令牌，如果节点未指定频道，则回退使用系统级的 Slack 频道。 * **Send a Microsoft Teams Message** 使用系统设置中的 Microsoft Teams Webhook。 diff --git a/docs/content/automation/rules_engine_2/converting_from_rules_engine.de.md b/docs/content/automation/triage_engine/converting_from_rules_engine.de.md similarity index 89% rename from docs/content/automation/rules_engine_2/converting_from_rules_engine.de.md rename to docs/content/automation/triage_engine/converting_from_rules_engine.de.md index 299dd19f065..f7a9cd16de7 100644 --- a/docs/content/automation/rules_engine_2/converting_from_rules_engine.de.md +++ b/docs/content/automation/triage_engine/converting_from_rules_engine.de.md @@ -5,11 +5,12 @@ weight: 6 audience: pro aliases: - /de/automation/rules_engine_v2/converting_from_rules_engine/ +- /de/automation/rules_engine_2/converting_from_rules_engine/ --- -Note: Rules Engine 2.0 is a DefectDojo Pro-only feature. +Note: Triage Engine is a DefectDojo Pro-only feature. -Beide Engines laufen nebeneinander. Das Aktivieren von Rules Engine 2.0 ändert nichts an Ihren bestehenden [Rules Engine](/automation/rules_engine/about/)-Regeln, und es gibt keine Frist, bis zu der Sie diese migrieren müssen. +Beide Engines laufen nebeneinander. Das Aktivieren von Triage Engine ändert nichts an Ihren bestehenden [Rules Engine](/automation/rules_engine/about/)-Regeln, und es gibt keine Frist, bis zu der Sie diese migrieren müssen. Wenn Sie sie migrieren möchten, gibt es dafür einen Konverter. Er übersetzt eine Rules-Engine-Regel (ein Filter plus eine geordnete Liste von Aktionen) in einen gleichwertigen Rules-Engine-2.0-Graphen. @@ -71,14 +72,14 @@ Vier Dinge, auf die Sie sich einstellen sollten. Der Konverter meldet diese als * **Der Lauf-Verlauf bleibt, wo er ist.** Der bestehende Lauf-Verlauf sowie die betroffenen und übersprungenen Datensätze verbleiben in der Rules-Engine-Benutzeroberfläche. Sie werden nicht kopiert. * **Zeitpläne werden standardmäßig nicht aktiviert.** Eine zeitplan-ausgelöste Regel wird konvertiert, aber ihr Zeitplan wird nur kopiert, wenn Sie `--activate-schedules` übergeben. Dadurch bleibt die alleinige Verantwortung für aktive Zeitpläne bei der ursprünglichen Engine, solange beide laufen, sodass eine konvertierte Regel nicht heimlich zu feuern beginnen kann. Wenn Sie einen Zeitplan tatsächlich kopieren, erhält die Kopie einen eigenen Namen, damit sie nicht mit dem Original kollidiert. -* **Das Nebenläufigkeitsmodell ist unterschiedlich.** Rules Engine hat eine instanzweite Laufsperre. Rules Engine 2.0 serialisiert pro Regel, sodass unterschiedliche Regeln gleichzeitig laufen. Eine Gruppe von Regeln, die sich früher abgewechselt hat, überlappt sich nun. +* **Das Nebenläufigkeitsmodell ist unterschiedlich.** Rules Engine hat eine instanzweite Laufsperre. Triage Engine serialisiert pro Regel, sodass unterschiedliche Regeln gleichzeitig laufen. Eine Gruppe von Regeln, die sich früher abgewechselt hat, überlappt sich nun. * **Eine Aktion hat keine Entsprechung.** Eine Aktion „Falsch-positiv auf false setzen“ kann nicht als Rules-Engine-2.0-Knoten ausgedrückt werden und muss von Hand konvertiert werden. Eine Regel, deren Eigentümer nicht gesetzt ist, wird mit einer Warnung konvertiert. Denken Sie daran, dass eine Regel ohne Eigentümer keine Befunde sieht, weisen Sie also einen zu, bevor Sie sie aktivieren. ## Eine vorgeschlagene Reihenfolge -1. Aktivieren Sie Rules Engine 2.0 und lassen Sie Ihre bestehenden Regeln weiterlaufen. +1. Aktivieren Sie Triage Engine und lassen Sie Ihre bestehenden Regeln weiterlaufen. 2. Führen Sie den Konverter mit `--dry-run` aus und lesen Sie den Bericht. 3. Konvertieren Sie. Alles landet deaktiviert. 4. Öffnen Sie jede konvertierte Regel, prüfen Sie den Graphen und belassen Sie den Modus auf **Simulate**. diff --git a/docs/content/automation/rules_engine_2/converting_from_rules_engine.es.md b/docs/content/automation/triage_engine/converting_from_rules_engine.es.md similarity index 87% rename from docs/content/automation/rules_engine_2/converting_from_rules_engine.es.md rename to docs/content/automation/triage_engine/converting_from_rules_engine.es.md index 6e6b78167a0..e3ee1dd9a04 100644 --- a/docs/content/automation/rules_engine_2/converting_from_rules_engine.es.md +++ b/docs/content/automation/triage_engine/converting_from_rules_engine.es.md @@ -1,17 +1,18 @@ --- title: Migración desde Rules Engine -description: Migrar reglas existentes de Rules Engine a grafos de Rules Engine 2.0 +description: Migrar reglas existentes de Rules Engine a grafos de Triage Engine weight: 6 audience: pro aliases: - /es/automation/rules_engine_v2/converting_from_rules_engine/ +- /es/automation/rules_engine_2/converting_from_rules_engine/ --- -Nota: Rules Engine 2.0 es una función exclusiva de DefectDojo Pro. +Nota: Triage Engine es una función exclusiva de DefectDojo Pro. -Ambos motores funcionan en paralelo. Activar Rules Engine 2.0 no cambia nada de las reglas existentes del [Rules Engine](/automation/rules_engine/about/), y no hay ningún plazo para migrarlas. +Ambos motores funcionan en paralelo. Activar Triage Engine no cambia nada de las reglas existentes del [Rules Engine](/automation/rules_engine/about/), y no hay ningún plazo para migrarlas. -Cuando llegue el momento de migrarlas, existe un conversor. Traduce una regla de Rules Engine (un filtro más una lista ordenada de acciones) en un grafo equivalente de Rules Engine 2.0. +Cuando llegue el momento de migrarlas, existe un conversor. Traduce una regla de Rules Engine (un filtro más una lista ordenada de acciones) en un grafo equivalente de Triage Engine. ## Qué garantiza el conversor @@ -71,14 +72,14 @@ Cuatro cosas para las que hay que planificar. El conversor las informa como nota * **El historial de ejecuciones permanece donde está.** El historial de ejecuciones existente, y sus registros afectados y omitidos, permanecen en la interfaz de Rules Engine. No se copian. * **Las programaciones no se activan de forma predeterminada.** Una regla activada por programación se convierte, pero su programación no se copia a menos que se pase `--activate-schedules`. Esto mantiene la propiedad exclusiva de las programaciones activas en el motor original mientras ambos están en funcionamiento, de modo que una regla convertida no puede empezar a dispararse sin que se note. Cuando sí se copia una programación, la copia recibe un nombre distinto para no colisionar con la original. -* **El modelo de concurrencia es diferente.** Rules Engine tiene un único bloqueo de ejecución para toda la instancia. Rules Engine 2.0 serializa por regla, de modo que reglas distintas se ejecutan de forma concurrente. Un conjunto de reglas que antes se turnaban ahora se solaparán. -* **Una acción no tiene equivalente.** Una acción de "establecer falso positivo en falso" no se puede expresar como un nodo de Rules Engine 2.0 y debe convertirse a mano. +* **El modelo de concurrencia es diferente.** Rules Engine tiene un único bloqueo de ejecución para toda la instancia. Triage Engine serializa por regla, de modo que reglas distintas se ejecutan de forma concurrente. Un conjunto de reglas que antes se turnaban ahora se solaparán. +* **Una acción no tiene equivalente.** Una acción de "establecer falso positivo en falso" no se puede expresar como un nodo de Triage Engine y debe convertirse a mano. Una regla sin propietario asignado se convierte, con una advertencia. Recuerde que una regla sin propietario no ve ningún Hallazgo, así que asigne uno antes de activarla. ## Un orden sugerido -1. Active Rules Engine 2.0 y deje sus reglas existentes en funcionamiento. +1. Active Triage Engine y deje sus reglas existentes en funcionamiento. 2. Ejecute el conversor con `--dry-run` y lea el informe. 3. Convierta. Todo queda desactivado. 4. Abra cada regla convertida, revise el grafo y deje el modo en **Simulación**. diff --git a/docs/content/automation/rules_engine_2/converting_from_rules_engine.fr.md b/docs/content/automation/triage_engine/converting_from_rules_engine.fr.md similarity index 88% rename from docs/content/automation/rules_engine_2/converting_from_rules_engine.fr.md rename to docs/content/automation/triage_engine/converting_from_rules_engine.fr.md index 938da1afa75..ea95cd8ef6c 100644 --- a/docs/content/automation/rules_engine_2/converting_from_rules_engine.fr.md +++ b/docs/content/automation/triage_engine/converting_from_rules_engine.fr.md @@ -6,13 +6,14 @@ weight: 6 audience: pro aliases: - /fr/automation/rules_engine_v2/converting_from_rules_engine/ +- /fr/automation/rules_engine_2/converting_from_rules_engine/ --- -Remarque : Rules Engine 2.0 est une fonctionnalité réservée à DefectDojo Pro. +Remarque : Triage Engine est une fonctionnalité réservée à DefectDojo Pro. -Les deux moteurs fonctionnent côte à côte. Activer Rules Engine 2.0 ne change rien à vos règles [Rules Engine](/automation/rules_engine/about/) existantes, et il n'y a aucune échéance à laquelle vous devriez les faire migrer. +Les deux moteurs fonctionnent côte à côte. Activer Triage Engine ne change rien à vos règles [Rules Engine](/automation/rules_engine/about/) existantes, et il n'y a aucune échéance à laquelle vous devriez les faire migrer. -Lorsque vous souhaitez les faire migrer, un convertisseur est disponible. Il traduit une règle Rules Engine (un filtre associé à une liste ordonnée d'actions) en un graphe Rules Engine 2.0 équivalent. +Lorsque vous souhaitez les faire migrer, un convertisseur est disponible. Il traduit une règle Rules Engine (un filtre associé à une liste ordonnée d'actions) en un graphe Triage Engine équivalent. ## Ce que le convertisseur garantit @@ -72,14 +73,14 @@ Quatre points à anticiper. Le convertisseur les signale sous forme de notes à * **L'historique des exécutions reste où il est.** L'historique des exécutions existant, ainsi que ses enregistrements affectés et ignorés, reste dans l'interface de Rules Engine. Il n'est pas copié. * **Les planifications ne sont pas activées par défaut.** Une règle déclenchée par planification se convertit, mais sa planification n'est pas copiée sauf si vous passez `--activate-schedules`. Cela conserve la seule propriété des planifications actives au moteur d'origine tant que les deux fonctionnent, de sorte qu'une règle convertie ne peut pas commencer à se déclencher à votre insu. Lorsque vous copiez effectivement une planification, la copie reçoit un nom distinct afin de ne pas entrer en collision avec l'original. -* **Le modèle de concurrence est différent.** Rules Engine possède un seul verrou d'exécution à l'échelle de l'instance. Rules Engine 2.0 sérialise par règle, de sorte que des règles distinctes s'exécutent simultanément. Un ensemble de règles qui se relayaient auparavant se chevauchera désormais. -* **Une action n'a pas d'équivalent.** Une action « définir faux positif sur false » ne peut pas être exprimée comme un nœud Rules Engine 2.0 et doit être convertie manuellement. +* **Le modèle de concurrence est différent.** Rules Engine possède un seul verrou d'exécution à l'échelle de l'instance. Triage Engine sérialise par règle, de sorte que des règles distinctes s'exécutent simultanément. Un ensemble de règles qui se relayaient auparavant se chevauchera désormais. +* **Une action n'a pas d'équivalent.** Une action « définir faux positif sur false » ne peut pas être exprimée comme un nœud Triage Engine et doit être convertie manuellement. Une règle dont le propriétaire n'est pas défini se convertit, avec un avertissement. Rappelez-vous qu'une règle sans propriétaire ne voit aucune Constatation ; attribuez-lui donc un propriétaire avant de l'activer. ## Un ordre suggéré -1. Activez Rules Engine 2.0 et laissez vos règles existantes en cours d'exécution. +1. Activez Triage Engine et laissez vos règles existantes en cours d'exécution. 2. Exécutez le convertisseur avec `--dry-run` et lisez le rapport. 3. Convertissez. Tout est créé désactivé. 4. Ouvrez chaque règle convertie, vérifiez le graphe, et laissez le mode sur **Simulate**. diff --git a/docs/content/automation/rules_engine_2/converting_from_rules_engine.it.md b/docs/content/automation/triage_engine/converting_from_rules_engine.it.md similarity index 87% rename from docs/content/automation/rules_engine_2/converting_from_rules_engine.it.md rename to docs/content/automation/triage_engine/converting_from_rules_engine.it.md index bb464e3ab1f..d1f0d44076b 100644 --- a/docs/content/automation/rules_engine_2/converting_from_rules_engine.it.md +++ b/docs/content/automation/triage_engine/converting_from_rules_engine.it.md @@ -6,13 +6,14 @@ weight: 6 audience: pro aliases: - /it/automation/rules_engine_v2/converting_from_rules_engine/ +- /it/automation/rules_engine_2/converting_from_rules_engine/ --- -Nota: Rules Engine 2.0 è una funzionalità disponibile solo in DefectDojo Pro. +Nota: Triage Engine è una funzionalità disponibile solo in DefectDojo Pro. -I due motori funzionano fianco a fianco. Attivare Rules Engine 2.0 non cambia nulla delle regole [Rules Engine](/automation/rules_engine/about/) esistenti, e non c'è una scadenza entro cui spostarle. +I due motori funzionano fianco a fianco. Attivare Triage Engine non cambia nulla delle regole [Rules Engine](/automation/rules_engine/about/) esistenti, e non c'è una scadenza entro cui spostarle. -Quando si vuole spostarle, esiste un convertitore. Traduce una regola di Rules Engine (un filtro più un elenco ordinato di azioni) in un grafo Rules Engine 2.0 equivalente. +Quando si vuole spostarle, esiste un convertitore. Traduce una regola di Rules Engine (un filtro più un elenco ordinato di azioni) in un grafo Triage Engine equivalente. ## Cosa garantisce il convertitore @@ -72,14 +73,14 @@ Quattro cose da tenere presenti. Il convertitore le riporta come note a ogni ese * **La cronologia dei run resta dov'è.** La cronologia di esecuzione esistente, e i relativi record interessati e saltati, rimangono nella UI di Rules Engine. Non vengono copiati. * **Le pianificazioni non vengono attivate per impostazione predefinita.** Una regola attivata da pianificazione si converte, ma la sua pianificazione non viene copiata a meno di passare `--activate-schedules`. Questo mantiene la proprietà esclusiva delle pianificazioni attive nel motore originale finché entrambi sono in esecuzione, così una regola convertita non può iniziare a scattare di nascosto. Quando si copia effettivamente una pianificazione, alla copia viene dato un nome distinto in modo che non collida con l'originale. -* **Il modello di concorrenza è diverso.** Rules Engine ha un unico lock di esecuzione a livello di istanza. Rules Engine 2.0 serializza per regola, quindi regole distinte vengono eseguite in concorrenza. Un insieme di regole che prima si alternava ora si sovrapporrà. -* **Un'azione non ha equivalente.** Un'azione "imposta falso positivo a falso" non può essere espressa come nodo di Rules Engine 2.0 e deve essere convertita a mano. +* **Il modello di concorrenza è diverso.** Rules Engine ha un unico lock di esecuzione a livello di istanza. Triage Engine serializza per regola, quindi regole distinte vengono eseguite in concorrenza. Un insieme di regole che prima si alternava ora si sovrapporrà. +* **Un'azione non ha equivalente.** Un'azione "imposta falso positivo a falso" non può essere espressa come nodo di Triage Engine e deve essere convertita a mano. Una regola il cui proprietario non è impostato si converte, con un avviso. Ricordare che una regola senza proprietario non vede alcun Riscontro, quindi assegnarne uno prima di abilitarla. ## Un ordine suggerito -1. Attivare Rules Engine 2.0 e lasciare in esecuzione le regole esistenti. +1. Attivare Triage Engine e lasciare in esecuzione le regole esistenti. 2. Eseguire il convertitore con `--dry-run` e leggere il report. 3. Convertire. Tutto viene creato disabilitato. 4. Aprire ogni regola convertita, controllare il grafo, e lasciare la modalità su **Simulate**. diff --git a/docs/content/automation/rules_engine_2/converting_from_rules_engine.ja.md b/docs/content/automation/triage_engine/converting_from_rules_engine.ja.md similarity index 86% rename from docs/content/automation/rules_engine_2/converting_from_rules_engine.ja.md rename to docs/content/automation/triage_engine/converting_from_rules_engine.ja.md index 9dde661e20e..c623b5088a1 100644 --- a/docs/content/automation/rules_engine_2/converting_from_rules_engine.ja.md +++ b/docs/content/automation/triage_engine/converting_from_rules_engine.ja.md @@ -1,17 +1,18 @@ --- title: Rules Engine からの移行 -description: 既存の Rules Engine のルールを Rules Engine 2.0 のグラフへ移行する +description: 既存の Rules Engine のルールを Triage Engine のグラフへ移行する weight: 6 audience: pro aliases: - /ja/automation/rules_engine_v2/converting_from_rules_engine/ +- /ja/automation/rules_engine_2/converting_from_rules_engine/ --- -注: Rules Engine 2.0 は DefectDojo Pro 専用の機能です。 +注: Triage Engine は DefectDojo Pro 専用の機能です。 -両方のエンジンは並行して動作します。Rules Engine 2.0 を有効にしても、既存の [Rules Engine](/automation/rules_engine/about/) のルールには何の変更もなく、それらを移行しなければならない期限もありません。 +両方のエンジンは並行して動作します。Triage Engine を有効にしても、既存の [Rules Engine](/automation/rules_engine/about/) のルールには何の変更もなく、それらを移行しなければならない期限もありません。 -実際に移行したくなったときのために、converter(変換ツール)が用意されています。これは、Rules Engine のルール(フィルターと順序付けられたアクションのリスト)を、それと同等の Rules Engine 2.0 のグラフに変換します。 +実際に移行したくなったときのために、converter(変換ツール)が用意されています。これは、Rules Engine のルール(フィルターと順序付けられたアクションのリスト)を、それと同等の Triage Engine のグラフに変換します。 ## Converter が保証すること @@ -71,14 +72,14 @@ python manage.py convert_rules_to_v2 * **Run の履歴はそのままの場所に残ります。** 既存の実行履歴、およびそれに関連する対象レコードとスキップされたレコードは、Rules Engine の UI に残ったままになります。これらはコピーされません。 * **スケジュールはデフォルトでは有効化されません。** スケジュールトリガーのルールは変換されますが、`--activate-schedules` を指定しない限り、そのスケジュールはコピーされません。これにより、両エンジンが稼働している間、稼働中のスケジュールの所有権は従来のエンジンだけが持つことになり、変換されたルールが気づかないうちに発火し始めることはありません。実際にスケジュールをコピーする場合、コピーには元のものと衝突しないよう別の名前が付けられます。 -* **並行実行モデルが異なります。** Rules Engine には、インスタンス全体で1つの実行ロックがあります。Rules Engine 2.0 はルールごとに直列化されるため、異なるルールは同時に実行されます。これまで順番に実行されていたルール群が、これからは重複して実行されるようになります。 -* **1つのアクションには相当するものがありません。** 「false positive を false に設定する」アクションは Rules Engine 2.0 のノードとして表現できないため、手動で変換する必要があります。 +* **並行実行モデルが異なります。** Rules Engine には、インスタンス全体で1つの実行ロックがあります。Triage Engine はルールごとに直列化されるため、異なるルールは同時に実行されます。これまで順番に実行されていたルール群が、これからは重複して実行されるようになります。 +* **1つのアクションには相当するものがありません。** 「false positive を false に設定する」アクションは Triage Engine のノードとして表現できないため、手動で変換する必要があります。 所有者が設定されていないルールも、警告付きで変換されます。所有者のいないルールはどの Finding も参照できないことを忘れずに、有効化する前に所有者を割り当ててください。 ## 推奨される手順 -1. Rules Engine 2.0 を有効にし、既存のルールはそのまま稼働させておきます。 +1. Triage Engine を有効にし、既存のルールはそのまま稼働させておきます。 2. `--dry-run` を付けて converter を実行し、レポートを確認します。 3. 変換します。すべて無効な状態になります。 4. 変換された各ルールを開き、グラフを確認し、モードは **Simulate** のままにしておきます。 diff --git a/docs/content/automation/rules_engine_2/converting_from_rules_engine.md b/docs/content/automation/triage_engine/converting_from_rules_engine.md similarity index 85% rename from docs/content/automation/rules_engine_2/converting_from_rules_engine.md rename to docs/content/automation/triage_engine/converting_from_rules_engine.md index 47186470a2a..f8f0971fdde 100644 --- a/docs/content/automation/rules_engine_2/converting_from_rules_engine.md +++ b/docs/content/automation/triage_engine/converting_from_rules_engine.md @@ -1,16 +1,17 @@ --- title: "Converting from Rules Engine" -description: "Move existing Rules Engine rules across to Rules Engine 2.0 graphs" +description: "Move existing Rules Engine rules across to Triage Engine graphs" weight: 6 audience: pro aliases: - /automation/rules_engine_v2/converting_from_rules_engine/ + - /automation/rules_engine_2/converting_from_rules_engine/ --- -Note: Rules Engine 2.0 is a DefectDojo Pro-only feature. +Note: Triage Engine is a DefectDojo Pro-only feature. -Both engines run side by side. Turning on Rules Engine 2.0 changes nothing about your existing [Rules Engine](/automation/rules_engine/about/) rules, and there is no deadline by which you must move them. +Both engines run side by side. Turning on Triage Engine changes nothing about your existing [Rules Engine](/automation/rules_engine/about/) rules, and there is no deadline by which you must move them. -When you do want to move them, there is a converter. It translates a Rules Engine rule (a filter plus an ordered list of actions) into an equivalent Rules Engine 2.0 graph. +When you do want to move them, there is a converter. It translates a Rules Engine rule (a filter plus an ordered list of actions) into an equivalent Triage Engine graph. ## What the converter guarantees @@ -70,14 +71,14 @@ Four things to plan for. The converter reports these as notes on every run. * **Run history stays where it is.** Existing run history, and its affected and skipped records, remain in the Rules Engine UI. They are not copied. * **Schedules are not activated by default.** A schedule-triggered rule converts, but its schedule is not copied unless you pass `--activate-schedules`. This keeps sole ownership of live schedules with the original engine while both are running, so a converted rule cannot start firing behind your back. When you do copy a schedule, the copy is given a distinct name so it does not collide with the original. -* **The concurrency model is different.** Rules Engine has one instance-wide run lock. Rules Engine 2.0 serialises per rule, so distinct rules run concurrently. A set of rules that used to take turns will now overlap. -* **One action has no equivalent.** A "set false positive to false" action cannot be expressed as a Rules Engine 2.0 node and must be converted by hand. +* **The concurrency model is different.** Rules Engine has one instance-wide run lock. Triage Engine serialises per rule, so distinct rules run concurrently. A set of rules that used to take turns will now overlap. +* **One action has no equivalent.** A "set false positive to false" action cannot be expressed as a Triage Engine node and must be converted by hand. A rule whose owner is unset converts, with a warning. Remember that a rule with no owner sees no Findings, so assign one before enabling it. ## A suggested order -1. Turn on Rules Engine 2.0 and leave your existing rules running. +1. Turn on Triage Engine and leave your existing rules running. 2. Run the converter with `--dry-run` and read the report. 3. Convert. Everything lands disabled. 4. Open each converted rule, check the graph, and leave the mode on **Simulate**. diff --git a/docs/content/automation/rules_engine_2/converting_from_rules_engine.pt-br.md b/docs/content/automation/triage_engine/converting_from_rules_engine.pt-br.md similarity index 86% rename from docs/content/automation/rules_engine_2/converting_from_rules_engine.pt-br.md rename to docs/content/automation/triage_engine/converting_from_rules_engine.pt-br.md index 60ecb42c855..dfd7acd5be1 100644 --- a/docs/content/automation/rules_engine_2/converting_from_rules_engine.pt-br.md +++ b/docs/content/automation/triage_engine/converting_from_rules_engine.pt-br.md @@ -1,17 +1,18 @@ --- title: Migrando do Rules Engine -description: Migre regras existentes do Rules Engine para grafos do Rules Engine 2.0 +description: Migre regras existentes do Rules Engine para grafos do Triage Engine weight: 6 audience: pro aliases: - /pt-br/automation/rules_engine_v2/converting_from_rules_engine/ +- /pt-br/automation/rules_engine_2/converting_from_rules_engine/ --- -Nota: O Rules Engine 2.0 é um recurso exclusivo do DefectDojo Pro. +Nota: O Triage Engine é um recurso exclusivo do DefectDojo Pro. -Os dois mecanismos funcionam lado a lado. Ativar o Rules Engine 2.0 não muda nada em suas regras existentes do [Rules Engine](/automation/rules_engine/about/), e não há um prazo até o qual você precise migrá-las. +Os dois mecanismos funcionam lado a lado. Ativar o Triage Engine não muda nada em suas regras existentes do [Rules Engine](/automation/rules_engine/about/), e não há um prazo até o qual você precise migrá-las. -Quando você quiser migrá-las, existe um conversor. Ele traduz uma regra do Rules Engine (um filtro mais uma lista ordenada de ações) em um grafo equivalente do Rules Engine 2.0. +Quando você quiser migrá-las, existe um conversor. Ele traduz uma regra do Rules Engine (um filtro mais uma lista ordenada de ações) em um grafo equivalente do Triage Engine. ## O que o conversor garante @@ -71,14 +72,14 @@ Quatro coisas para planejar. O conversor relata essas informações como notas e * **O histórico de execuções permanece onde está.** O histórico de execuções existente, junto com seus registros afetados e ignorados, permanece na interface do Rules Engine. Eles não são copiados. * **As programações não são ativadas por padrão.** Uma regra disparada por agendamento é convertida, mas sua programação não é copiada a menos que você passe `--activate-schedules`. Isso mantém a propriedade exclusiva das programações ativas com o mecanismo original enquanto os dois estão em execução, de modo que uma regra convertida não pode começar a disparar sem você perceber. Quando você copia uma programação, a cópia recebe um nome distinto para não colidir com a original. -* **O modelo de concorrência é diferente.** O Rules Engine tem um único bloqueio de execução para toda a instância. O Rules Engine 2.0 serializa por regra, portanto regras distintas são executadas simultaneamente. Um conjunto de regras que costumava se revezar agora vai se sobrepor. -* **Uma ação não tem equivalente.** Uma ação de "definir falso positivo como falso" não pode ser expressa como um nó do Rules Engine 2.0 e precisa ser convertida manualmente. +* **O modelo de concorrência é diferente.** O Rules Engine tem um único bloqueio de execução para toda a instância. O Triage Engine serializa por regra, portanto regras distintas são executadas simultaneamente. Um conjunto de regras que costumava se revezar agora vai se sobrepor. +* **Uma ação não tem equivalente.** Uma ação de "definir falso positivo como falso" não pode ser expressa como um nó do Triage Engine e precisa ser convertida manualmente. Uma regra cujo proprietário não está definido é convertida, com um aviso. Lembre-se de que uma regra sem proprietário não vê nenhum Achado, portanto atribua um antes de ativá-la. ## Uma ordem sugerida -1. Ative o Rules Engine 2.0 e deixe suas regras existentes em execução. +1. Ative o Triage Engine e deixe suas regras existentes em execução. 2. Execute o conversor com `--dry-run` e leia o relatório. 3. Converta. Tudo é criado desativado. 4. Abra cada regra convertida, verifique o grafo e deixe o modo em **Simulate**. diff --git a/docs/content/automation/rules_engine_2/converting_from_rules_engine.zh-hans.md b/docs/content/automation/triage_engine/converting_from_rules_engine.zh-hans.md similarity index 86% rename from docs/content/automation/rules_engine_2/converting_from_rules_engine.zh-hans.md rename to docs/content/automation/triage_engine/converting_from_rules_engine.zh-hans.md index 1bf859d475c..67e732a64ca 100644 --- a/docs/content/automation/rules_engine_2/converting_from_rules_engine.zh-hans.md +++ b/docs/content/automation/triage_engine/converting_from_rules_engine.zh-hans.md @@ -1,17 +1,18 @@ --- title: 从 Rules Engine 转换 -description: 将现有的 Rules Engine 规则迁移为 Rules Engine 2.0 的图 +description: 将现有的 Rules Engine 规则迁移为 Triage Engine 的图 weight: 6 audience: pro aliases: - /zh-hans/automation/rules_engine_v2/converting_from_rules_engine/ +- /zh-hans/automation/rules_engine_2/converting_from_rules_engine/ --- -注意：Rules Engine 2.0 是 DefectDojo Pro 专属功能。 +注意：Triage Engine 是 DefectDojo Pro 专属功能。 -两套引擎并行运行。启用 Rules Engine 2.0 不会改变您现有的 [Rules Engine](/automation/rules_engine/about/) 规则中的任何内容，也没有必须迁移它们的截止时间。 +两套引擎并行运行。启用 Triage Engine 不会改变您现有的 [Rules Engine](/automation/rules_engine/about/) 规则中的任何内容，也没有必须迁移它们的截止时间。 -当您确实想要迁移时，有一个转换器可以使用。它会将一条 Rules Engine 规则（一个过滤器加一份有序的动作列表）转换为一张等价的 Rules Engine 2.0 图。 +当您确实想要迁移时，有一个转换器可以使用。它会将一条 Rules Engine 规则（一个过滤器加一份有序的动作列表）转换为一张等价的 Triage Engine 图。 ## 转换器的保证 @@ -71,14 +72,14 @@ python manage.py convert_rules_to_v2 * **运行历史留在原处。** 现有的运行历史及其受影响和被跳过的记录，仍保留在 Rules Engine 的 UI 中，不会被复制。 * **计划默认不会被激活。** 一条以计划触发的规则可以转换，但除非您传入 `--activate-schedules`，否则其计划不会被复制。这样做是为了在两套引擎同时运行期间，让生效中的计划始终唯一归属于原有引擎，从而使转换后的规则不会在您不知情的情况下开始触发。当您确实复制某个计划时，副本会被赋予一个不同的名称，以免与原计划冲突。 -* **并发模型不同。** Rules Engine 只有一把实例级的运行锁。Rules Engine 2.0 则按规则各自串行化，因此不同的规则会并发运行。原本轮流执行的一组规则，现在会出现重叠。 -* **有一个动作没有对应项。** “将误报状态设为 false”这个动作无法用 Rules Engine 2.0 的节点表达，必须手动转换。 +* **并发模型不同。** Rules Engine 只有一把实例级的运行锁。Triage Engine 则按规则各自串行化，因此不同的规则会并发运行。原本轮流执行的一组规则，现在会出现重叠。 +* **有一个动作没有对应项。** “将误报状态设为 false”这个动作无法用 Triage Engine 的节点表达，必须手动转换。 所有者未设置的规则也能转换，但会附带警告。请记住，没有所有者的规则看不到任何发现项，因此请在启用之前为其指定一个所有者。 ## 建议的操作顺序 -1. 启用 Rules Engine 2.0，并让您现有的规则继续运行。 +1. 启用 Triage Engine，并让您现有的规则继续运行。 2. 用 `--dry-run` 运行转换器，并阅读报告。 3. 执行转换。所有结果都会以禁用状态落地。 4. 打开每一条转换后的规则，检查其图，并将模式保持为 **Simulate**。 diff --git a/docs/content/automation/rules_engine_2/deliveries.de.md b/docs/content/automation/triage_engine/deliveries.de.md similarity index 97% rename from docs/content/automation/rules_engine_2/deliveries.de.md rename to docs/content/automation/triage_engine/deliveries.de.md index 3dc87d89b0d..e3f7c479ec7 100644 --- a/docs/content/automation/rules_engine_2/deliveries.de.md +++ b/docs/content/automation/triage_engine/deliveries.de.md @@ -6,11 +6,12 @@ weight: 5 audience: pro aliases: - /de/automation/rules_engine_v2/deliveries/ +- /de/automation/rules_engine_2/deliveries/ --- -Hinweis: Rules Engine 2.0 ist eine Funktion, die nur in DefectDojo Pro verfügbar ist. +Hinweis: Triage Engine ist eine Funktion, die nur in DefectDojo Pro verfügbar ist. -Jeder ausgehende Nebeneffekt, den eine Regel erzeugt, ist eine Zeile im Zustellungsprotokoll. **Rules Engine 2.0 > Deliveries** listet sie auf. +Jeder ausgehende Nebeneffekt, den eine Regel erzeugt, ist eine Zeile im Zustellungsprotokoll. **Triage Engine > Deliveries** listet sie auf. Die Zeile wird geschrieben, **bevor** ein Netzwerkaufruf stattfindet, und sie enthält genau das, was gesendet werden würde oder wurde. Das macht ausgehenden Datenverkehr überprüfbar, statt sich auf eine Logzeile zu verlassen, in der Hoffnung, dass sie jemand aufbewahrt hat, und deshalb ist Simulieren kein eigener Codepfad: Ein simulierter Versand ist dieselbe Zeile, nur ohne den Versandschritt. diff --git a/docs/content/automation/rules_engine_2/deliveries.es.md b/docs/content/automation/triage_engine/deliveries.es.md similarity index 97% rename from docs/content/automation/rules_engine_2/deliveries.es.md rename to docs/content/automation/triage_engine/deliveries.es.md index 98523d99153..6654999c40a 100644 --- a/docs/content/automation/rules_engine_2/deliveries.es.md +++ b/docs/content/automation/triage_engine/deliveries.es.md @@ -6,11 +6,12 @@ weight: 5 audience: pro aliases: - /es/automation/rules_engine_v2/deliveries/ +- /es/automation/rules_engine_2/deliveries/ --- -Nota: Rules Engine 2.0 es una función exclusiva de DefectDojo Pro. +Nota: Triage Engine es una función exclusiva de DefectDojo Pro. -Cada efecto secundario saliente que produce una regla es una fila en el registro de entregas. **Rules Engine 2.0 > Entregas** las enumera. +Cada efecto secundario saliente que produce una regla es una fila en el registro de entregas. **Triage Engine > Entregas** las enumera. La fila se escribe **antes** de que ocurra cualquier llamada de red, y contiene exactamente lo que se enviaría, o lo que se envió. Eso es lo que hace que el tráfico de salida sea auditable en lugar de una línea de registro que uno espera que alguien haya conservado, y es la razón por la que **Simulate** no es una ruta de código independiente: un envío simulado es la misma fila con el paso de despacho omitido. diff --git a/docs/content/automation/rules_engine_2/deliveries.fr.md b/docs/content/automation/triage_engine/deliveries.fr.md similarity index 97% rename from docs/content/automation/rules_engine_2/deliveries.fr.md rename to docs/content/automation/triage_engine/deliveries.fr.md index 0313346d379..93ccfc3a49e 100644 --- a/docs/content/automation/rules_engine_2/deliveries.fr.md +++ b/docs/content/automation/triage_engine/deliveries.fr.md @@ -6,11 +6,12 @@ weight: 5 audience: pro aliases: - /fr/automation/rules_engine_v2/deliveries/ +- /fr/automation/rules_engine_2/deliveries/ --- -Remarque : Rules Engine 2.0 est une fonctionnalité réservée à DefectDojo Pro. +Remarque : Triage Engine est une fonctionnalité réservée à DefectDojo Pro. -Chaque effet secondaire sortant produit par une règle correspond à une ligne du registre des livraisons. **Rules Engine 2.0 > Livraisons** les répertorie. +Chaque effet secondaire sortant produit par une règle correspond à une ligne du registre des livraisons. **Triage Engine > Livraisons** les répertorie. La ligne est écrite **avant** tout appel réseau, et elle contient exactement ce qui sera, ou a été, envoyé. C'est ce qui rend les envois sortants auditables plutôt qu'une ligne de journal que l'on espère avoir conservée, et c'est pourquoi **Simulate** n'est pas un chemin de code distinct : un envoi simulé correspond à la même ligne, l'étape de dispatch étant simplement ignorée. diff --git a/docs/content/automation/rules_engine_2/deliveries.it.md b/docs/content/automation/triage_engine/deliveries.it.md similarity index 97% rename from docs/content/automation/rules_engine_2/deliveries.it.md rename to docs/content/automation/triage_engine/deliveries.it.md index 9104b44364f..83a06457c9b 100644 --- a/docs/content/automation/rules_engine_2/deliveries.it.md +++ b/docs/content/automation/triage_engine/deliveries.it.md @@ -6,11 +6,12 @@ weight: 5 audience: pro aliases: - /it/automation/rules_engine_v2/deliveries/ +- /it/automation/rules_engine_2/deliveries/ --- -Nota: Rules Engine 2.0 è una funzionalità disponibile solo in DefectDojo Pro. +Nota: Triage Engine è una funzionalità disponibile solo in DefectDojo Pro. -Ogni effetto collaterale in uscita prodotto da una regola corrisponde a una riga nel registro delle consegne. **Rules Engine 2.0 > Consegne** le elenca. +Ogni effetto collaterale in uscita prodotto da una regola corrisponde a una riga nel registro delle consegne. **Triage Engine > Consegne** le elenca. La riga viene scritta **prima** che avvenga qualsiasi chiamata di rete e contiene esattamente ciò che verrà, o è stato, inviato. Questo è ciò che rende l'uscita dei dati verificabile, invece di essere una riga di log che si spera qualcuno abbia conservato, ed è il motivo per cui **Simulazione** non è un percorso di codice separato: un invio simulato è la stessa riga con il passaggio di dispatch saltato. diff --git a/docs/content/automation/rules_engine_2/deliveries.ja.md b/docs/content/automation/triage_engine/deliveries.ja.md similarity index 97% rename from docs/content/automation/rules_engine_2/deliveries.ja.md rename to docs/content/automation/triage_engine/deliveries.ja.md index 0ba44fe2672..f97f71bd43a 100644 --- a/docs/content/automation/rules_engine_2/deliveries.ja.md +++ b/docs/content/automation/triage_engine/deliveries.ja.md @@ -5,11 +5,12 @@ weight: 5 audience: pro aliases: - /ja/automation/rules_engine_v2/deliveries/ +- /ja/automation/rules_engine_2/deliveries/ --- -注: Rules Engine 2.0 は DefectDojo Pro 限定の機能です。 +注: Triage Engine は DefectDojo Pro 限定の機能です。 -ルールが生成するすべての送信(アウトバウンド)側の副作用は、配信台帳の1行になります。**Rules Engine 2.0 > Deliveries** にその一覧が表示されます。 +ルールが生成するすべての送信(アウトバウンド)側の副作用は、配信台帳の1行になります。**Triage Engine > Deliveries** にその一覧が表示されます。 この行はネットワーク呼び出しが発生する**前**に書き込まれ、送信される(または送信された)内容を正確に保持します。これにより、送信(egress)は「誰かが保存していることを願うログ行」ではなく、監査可能なものになります。また、これが **Simulate** が別のコードパスではない理由でもあります。シミュレーション送信は、ディスパッチ手順が省略されただけの、同じ行なのです。 diff --git a/docs/content/automation/rules_engine_2/deliveries.md b/docs/content/automation/triage_engine/deliveries.md similarity index 97% rename from docs/content/automation/rules_engine_2/deliveries.md rename to docs/content/automation/triage_engine/deliveries.md index c6daace3bab..38c116b3dab 100644 --- a/docs/content/automation/rules_engine_2/deliveries.md +++ b/docs/content/automation/triage_engine/deliveries.md @@ -5,10 +5,11 @@ weight: 5 audience: pro aliases: - /automation/rules_engine_v2/deliveries/ + - /automation/rules_engine_2/deliveries/ --- -Note: Rules Engine 2.0 is a DefectDojo Pro-only feature. +Note: Triage Engine is a DefectDojo Pro-only feature. -Every outbound side effect a rule produces is one row in the delivery ledger. **Rules Engine 2.0 > Deliveries** lists them. +Every outbound side effect a rule produces is one row in the delivery ledger. **Triage Engine > Deliveries** lists them. The row is written **before** any network call happens, and it holds exactly what would be, or was, sent. That is what makes egress auditable rather than a log line you hope somebody kept, and it is why **Simulate** is not a separate code path: a simulated send is the same row with the dispatch step skipped. diff --git a/docs/content/automation/rules_engine_2/deliveries.pt-br.md b/docs/content/automation/triage_engine/deliveries.pt-br.md similarity index 97% rename from docs/content/automation/rules_engine_2/deliveries.pt-br.md rename to docs/content/automation/triage_engine/deliveries.pt-br.md index 11f004f1b60..239a4eb7c50 100644 --- a/docs/content/automation/rules_engine_2/deliveries.pt-br.md +++ b/docs/content/automation/triage_engine/deliveries.pt-br.md @@ -6,11 +6,12 @@ weight: 5 audience: pro aliases: - /pt-br/automation/rules_engine_v2/deliveries/ +- /pt-br/automation/rules_engine_2/deliveries/ --- -Nota: o Rules Engine 2.0 é um recurso exclusivo do DefectDojo Pro. +Nota: o Triage Engine é um recurso exclusivo do DefectDojo Pro. -Cada efeito colateral de saída produzido por uma regra é uma linha no registro de entregas. **Rules Engine 2.0 > Entregas** as lista. +Cada efeito colateral de saída produzido por uma regra é uma linha no registro de entregas. **Triage Engine > Entregas** as lista. A linha é gravada **antes** de qualquer chamada de rede acontecer, e contém exatamente o que seria, ou foi, enviado. É isso que torna a saída auditável, em vez de uma linha de log que você espera que alguém tenha guardado, e é por isso que **Simulate** não é um caminho de código separado: um envio simulado é a mesma linha com a etapa de despacho pulada. diff --git a/docs/content/automation/rules_engine_2/deliveries.zh-hans.md b/docs/content/automation/triage_engine/deliveries.zh-hans.md similarity index 96% rename from docs/content/automation/rules_engine_2/deliveries.zh-hans.md rename to docs/content/automation/triage_engine/deliveries.zh-hans.md index b03b85af0f6..715abadaa1c 100644 --- a/docs/content/automation/rules_engine_2/deliveries.zh-hans.md +++ b/docs/content/automation/triage_engine/deliveries.zh-hans.md @@ -5,11 +5,12 @@ weight: 5 audience: pro aliases: - /zh-hans/automation/rules_engine_v2/deliveries/ +- /zh-hans/automation/rules_engine_2/deliveries/ --- -注意：Rules Engine 2.0 是 DefectDojo Pro 专属功能。 +注意：Triage Engine 是 DefectDojo Pro 专属功能。 -规则产生的每一个对外副作用，都会在投递台账中生成一行记录。**Rules Engine 2.0 > Deliveries** 页面会列出这些记录。 +规则产生的每一个对外副作用，都会在投递台账中生成一行记录。**Triage Engine > Deliveries** 页面会列出这些记录。 该记录会在发生任何网络调用之**前**写入，其中保存的正是即将发送或已经发送的确切内容。正因如此，出站发送才是可审计的，而不是一条只能寄希望于有人保留下来的日志；这也是**模拟**并非另一条独立代码路径的原因：模拟发送使用的是同一条记录，只是跳过了实际派发步骤。 diff --git a/docs/content/automation/rules_engine_2/node_reference.de.md b/docs/content/automation/triage_engine/node_reference.de.md similarity index 96% rename from docs/content/automation/rules_engine_2/node_reference.de.md rename to docs/content/automation/triage_engine/node_reference.de.md index f0754de767e..d3edb79c6aa 100644 --- a/docs/content/automation/rules_engine_2/node_reference.de.md +++ b/docs/content/automation/triage_engine/node_reference.de.md @@ -1,15 +1,16 @@ --- title: Knotenreferenz -description: Jeder Knoten, den Rules Engine 2.0 mitbringt, und was er jeweils tut +description: Jeder Knoten, den Triage Engine mitbringt, und was er jeweils tut weight: 3 audience: pro aliases: - /de/automation/rules_engine_v2/node_reference/ +- /de/automation/rules_engine_2/node_reference/ --- -Hinweis: Rules Engine 2.0 ist eine Funktion, die nur in DefectDojo Pro verfügbar ist. +Hinweis: Triage Engine ist eine Funktion, die nur in DefectDojo Pro verfügbar ist. -Rules Engine 2.0 bringt 25 Knoten in vier Kategorien mit. Diese Seite dokumentiert sie alle. +Triage Engine bringt 25 Knoten in vier Kategorien mit. Diese Seite dokumentiert sie alle. Sofern nicht anders angegeben, nimmt ein Knoten eine Eingabe entgegen, erzeugt eine Ausgabe namens `out` und gibt jedes empfangene Element an diese Ausgabe weiter. Das ist wichtig, wenn Sie Knoten verketten: Ein Befunde-Knoten verändert den Befund und reicht das Element dann weiter, sodass mehrere davon hintereinander alle wirksam werden. @@ -217,7 +218,7 @@ Ein Knoten, der eine Nachricht pro Befund sendet, stoppt standardmäßig nach 1. ### Wenn ein Kanal nicht verfügbar ist -Ein Egress-Knoten hängt von etwas außerhalb der Regel ab: einem Slack-Token, einem Microsoft-Teams-Webhook, einer JIRA-Konfiguration, einem lizenzierten Connector. Fehlt das oder ist es abgeschaltet, kann der Knoten nicht arbeiten, und Rules Engine 2.0 macht das an drei verschiedenen Stellen deutlich, statt still zu scheitern: +Ein Egress-Knoten hängt von etwas außerhalb der Regel ab: einem Slack-Token, einem Microsoft-Teams-Webhook, einer JIRA-Konfiguration, einem lizenzierten Connector. Fehlt das oder ist es abgeschaltet, kann der Knoten nicht arbeiten, und Triage Engine macht das an drei verschiedenen Stellen deutlich, statt still zu scheitern: * **In der Palette** wird ein nicht verfügbarer Knoten als solcher markiert, mit Angabe des Grundes, bevor Sie ihn auf die Zeichenfläche ziehen. * **Beim Speichern** wird ein Graph, der einen nicht verfügbaren Knoten enthält, abgelehnt. Das ist der Moment, in dem jemand anwesend ist, um einen anderen auszuwählen. @@ -321,7 +322,7 @@ Erstellt eine In-App-Benachrichtigung über den Batch. | Einstellung | Standard | Hinweise | |---------|---------|-------| -| **Titel** | `Rules Engine 2.0: {{ctx.rule_name}}` | Wird einmal für den gesamten Batch gerendert. | +| **Titel** | `Triage Engine: {{ctx.rule_name}}` | Wird einmal für den gesamten Batch gerendert. | | **Beschreibung** | `{{ctx.count}} finding(s) matched the rule {{ctx.rule_name}}.` | Wird einmal für den gesamten Batch gerendert. | | **Empfänger** | leer | Benutzernamen, durch Kommas getrennt. Leer benachrichtigt die Administratoren. | diff --git a/docs/content/automation/rules_engine_2/node_reference.es.md b/docs/content/automation/triage_engine/node_reference.es.md similarity index 96% rename from docs/content/automation/rules_engine_2/node_reference.es.md rename to docs/content/automation/triage_engine/node_reference.es.md index f1897353bd9..9fee4d412f4 100644 --- a/docs/content/automation/rules_engine_2/node_reference.es.md +++ b/docs/content/automation/triage_engine/node_reference.es.md @@ -1,16 +1,17 @@ --- title: Referencia de nodos -description: Todos los nodos con los que se distribuye Rules Engine 2.0, y qué hace +description: Todos los nodos con los que se distribuye Triage Engine, y qué hace cada uno weight: 3 audience: pro aliases: - /es/automation/rules_engine_v2/node_reference/ +- /es/automation/rules_engine_2/node_reference/ --- -Nota: Rules Engine 2.0 es una función exclusiva de DefectDojo Pro. +Nota: Triage Engine es una función exclusiva de DefectDojo Pro. -Rules Engine 2.0 se distribuye con 25 nodos en cuatro categorías. Esta página los documenta todos. +Triage Engine se distribuye con 25 nodos en cuatro categorías. Esta página los documenta todos. A menos que se indique lo contrario, un nodo recibe una entrada, produce una salida llamada `out`, y pasa cada elemento que recibió a esa salida. Esto importa cuando se encadenan nodos: un nodo de Hallazgos modifica el Hallazgo y luego pasa el elemento hacia adelante, de modo que varios de ellos en fila se aplican todos. @@ -218,7 +219,7 @@ Un nodo que envía un mensaje por Hallazgo se detiene después de 1000 envíos e ### Cuando un canal no está disponible -Un nodo de salida depende de algo externo a la regla: un token de Slack, un webhook de Microsoft Teams, una configuración de JIRA, un conector con licencia. Cuando eso falta o está desactivado, el nodo no puede funcionar, y Rules Engine 2.0 lo indica en tres momentos distintos en lugar de fallar en silencio: +Un nodo de salida depende de algo externo a la regla: un token de Slack, un webhook de Microsoft Teams, una configuración de JIRA, un conector con licencia. Cuando eso falta o está desactivado, el nodo no puede funcionar, y Triage Engine lo indica en tres momentos distintos en lugar de fallar en silencio: * **En la paleta**, un nodo no disponible se marca como tal, con el motivo, antes de que se arrastre al lienzo. * **Al guardar**, se rechaza un grafo que contenga un nodo no disponible. Ese es el momento en que alguien está presente para elegir uno diferente. @@ -322,7 +323,7 @@ Crea una alerta en la aplicación sobre el lote. | Setting | Default | Notes | |---------|---------|-------| -| **Title** | `Rules Engine 2.0: {{ctx.rule_name}}` | Se renderiza una vez para todo el lote. | +| **Title** | `Triage Engine: {{ctx.rule_name}}` | Se renderiza una vez para todo el lote. | | **Description** | `{{ctx.count}} finding(s) matched the rule {{ctx.rule_name}}.` | Se renderiza una vez para todo el lote. | | **Recipients** | vacío | Nombres de usuario, separados por comas. Vacío alerta a los administradores. | diff --git a/docs/content/automation/rules_engine_2/node_reference.fr.md b/docs/content/automation/triage_engine/node_reference.fr.md similarity index 97% rename from docs/content/automation/rules_engine_2/node_reference.fr.md rename to docs/content/automation/triage_engine/node_reference.fr.md index a8e61a9f7ef..63aee99703c 100644 --- a/docs/content/automation/rules_engine_2/node_reference.fr.md +++ b/docs/content/automation/triage_engine/node_reference.fr.md @@ -1,15 +1,16 @@ --- title: Référence des nœuds -description: Tous les nœuds fournis avec Rules Engine 2.0, et ce que fait chacun d'eux +description: Tous les nœuds fournis avec Triage Engine, et ce que fait chacun d'eux weight: 3 audience: pro aliases: - /fr/automation/rules_engine_v2/node_reference/ +- /fr/automation/rules_engine_2/node_reference/ --- -Remarque : Rules Engine 2.0 est une fonctionnalité réservée à DefectDojo Pro. +Remarque : Triage Engine est une fonctionnalité réservée à DefectDojo Pro. -Rules Engine 2.0 est fourni avec 25 nœuds répartis en quatre catégories. Cette page les documente tous. +Triage Engine est fourni avec 25 nœuds répartis en quatre catégories. Cette page les documente tous. Sauf indication contraire, un nœud reçoit une entrée, produit une sortie appelée `out`, et transmet à cette sortie chaque élément qu'il a reçu. Cela compte lorsque vous enchaînez des nœuds : un nœud de type Constatations modifie la Constatation puis transmet l'élément à la suite, de sorte que plusieurs nœuds enchaînés s'appliquent tous. @@ -217,7 +218,7 @@ Un nœud envoyant un message par Constatation s'arrête par défaut après 1 000 ### Lorsqu'un canal est indisponible -Un nœud de sortie dépend de quelque chose d'extérieur à la règle : un jeton Slack, un webhook Microsoft Teams, une configuration JIRA, un connecteur sous licence. Lorsque cet élément est manquant ou désactivé, le nœud ne peut pas fonctionner, et Rules Engine 2.0 le signale à trois moments différents plutôt que d'échouer silencieusement : +Un nœud de sortie dépend de quelque chose d'extérieur à la règle : un jeton Slack, un webhook Microsoft Teams, une configuration JIRA, un connecteur sous licence. Lorsque cet élément est manquant ou désactivé, le nœud ne peut pas fonctionner, et Triage Engine le signale à trois moments différents plutôt que d'échouer silencieusement : * **Dans la palette**, un nœud indisponible est marqué comme tel, avec la raison, avant même que vous ne le glissiez sur le canevas. * **À l'enregistrement**, un graphe contenant un nœud indisponible est refusé. C'est le moment où quelqu'un est présent pour en choisir un autre. @@ -321,7 +322,7 @@ Crée une alerte intégrée à propos du lot. | Paramètre | Valeur par défaut | Remarques | |---------|---------|-------| -| **Titre** | `Rules Engine 2.0: {{ctx.rule_name}}` | Généré une fois pour l'ensemble du lot. | +| **Titre** | `Triage Engine: {{ctx.rule_name}}` | Généré une fois pour l'ensemble du lot. | | **Description** | `{{ctx.count}} finding(s) matched the rule {{ctx.rule_name}}.` | Généré une fois pour l'ensemble du lot. | | **Destinataires** | vide | Noms d'utilisateur, séparés par des virgules. Vide alerte les administrateurs. | diff --git a/docs/content/automation/rules_engine_2/node_reference.it.md b/docs/content/automation/triage_engine/node_reference.it.md similarity index 96% rename from docs/content/automation/rules_engine_2/node_reference.it.md rename to docs/content/automation/triage_engine/node_reference.it.md index 8052328ab0c..46704d6b169 100644 --- a/docs/content/automation/rules_engine_2/node_reference.it.md +++ b/docs/content/automation/triage_engine/node_reference.it.md @@ -1,15 +1,16 @@ --- title: Riferimento dei nodi -description: Tutti i nodi inclusi in Rules Engine 2.0, e cosa fa ciascuno +description: Tutti i nodi inclusi in Triage Engine, e cosa fa ciascuno weight: 3 audience: pro aliases: - /it/automation/rules_engine_v2/node_reference/ +- /it/automation/rules_engine_2/node_reference/ --- -Nota: Rules Engine 2.0 è una funzionalità disponibile solo in DefectDojo Pro. +Nota: Triage Engine è una funzionalità disponibile solo in DefectDojo Pro. -Rules Engine 2.0 include 25 nodi suddivisi in quattro categorie. Questa pagina li documenta tutti. +Triage Engine include 25 nodi suddivisi in quattro categorie. Questa pagina li documenta tutti. Salvo diversa indicazione, un nodo accetta un input, produce un output chiamato `out` e passa a quell'output ogni elemento ricevuto. Questo è rilevante quando si concatenano i nodi: un nodo sui Riscontri modifica il Riscontro e poi passa l'elemento avanti, quindi più nodi in sequenza vengono applicati tutti. @@ -217,7 +218,7 @@ Un nodo che invia un messaggio per ogni Riscontro si ferma per impostazione pred ### Quando un canale non è disponibile -Un nodo di uscita dipende da qualcosa esterno alla regola: un token Slack, un webhook Microsoft Teams, una configurazione JIRA, un connettore con licenza. Quando questo manca o è disattivato, il nodo non può funzionare, e Rules Engine 2.0 lo segnala in tre momenti diversi invece di fallire silenziosamente: +Un nodo di uscita dipende da qualcosa esterno alla regola: un token Slack, un webhook Microsoft Teams, una configurazione JIRA, un connettore con licenza. Quando questo manca o è disattivato, il nodo non può funzionare, e Triage Engine lo segnala in tre momenti diversi invece di fallire silenziosamente: * **Nella tavolozza**, un nodo non disponibile viene contrassegnato come tale, con il motivo, prima che venga trascinato sul canvas. * **Al salvataggio**, un grafo che contiene un nodo non disponibile viene rifiutato. È il momento in cui qualcuno è presente per sceglierne uno diverso. @@ -321,7 +322,7 @@ Crea un avviso in-app relativo al batch. | Impostazione | Predefinito | Note | |---------|---------|-------| -| **Titolo** | `Rules Engine 2.0: {{ctx.rule_name}}` | Renderizzato una volta per l'intero batch. | +| **Titolo** | `Triage Engine: {{ctx.rule_name}}` | Renderizzato una volta per l'intero batch. | | **Descrizione** | `{{ctx.count}} finding(s) matched the rule {{ctx.rule_name}}.` | Renderizzato una volta per l'intero batch. | | **Destinatari** | vuoto | Nomi utente separati da virgola. Se vuoto, avvisa gli amministratori. | diff --git a/docs/content/automation/rules_engine_2/node_reference.ja.md b/docs/content/automation/triage_engine/node_reference.ja.md similarity index 96% rename from docs/content/automation/rules_engine_2/node_reference.ja.md rename to docs/content/automation/triage_engine/node_reference.ja.md index b9d0fcaa3f8..02667b3a5cd 100644 --- a/docs/content/automation/rules_engine_2/node_reference.ja.md +++ b/docs/content/automation/triage_engine/node_reference.ja.md @@ -1,15 +1,16 @@ --- title: ノードリファレンス -description: Rules Engine 2.0に搭載されているすべてのノードと、それぞれの機能 +description: Triage Engineに搭載されているすべてのノードと、それぞれの機能 weight: 3 audience: pro aliases: - /ja/automation/rules_engine_v2/node_reference/ +- /ja/automation/rules_engine_2/node_reference/ --- -注: Rules Engine 2.0 は DefectDojo Pro 限定の機能です。 +注: Triage Engine は DefectDojo Pro 限定の機能です。 -Rules Engine 2.0には、4つのカテゴリにわたって25個のノードが搭載されています。このページではそのすべてを解説します。 +Triage Engineには、4つのカテゴリにわたって25個のノードが搭載されています。このページではそのすべてを解説します。 特に断りがない限り、ノードは1つの入力を受け取り、`out` と呼ばれる1つの出力を生成し、受け取ったすべてのアイテムをその出力へと渡します。これはノードを連結する際に重要です。検出事項ノードは検出事項を変更してからアイテムを次へ渡すため、連続して並んだ複数のノードがすべて適用されます。 @@ -217,7 +218,7 @@ Rules Engine 2.0には、4つのカテゴリにわたって25個のノードが ### チャネルが利用できない場合 -送信ノードは、Slackトークン、Microsoft Teams Webhook、JIRA設定、ライセンス済みコネクタなど、ルールの外部にある何かに依存しています。それが欠けているか無効化されている場合、ノードは動作できません。Rules Engine 2.0は黙って失敗するのではなく、3つの異なるタイミングでそれを知らせます。 +送信ノードは、Slackトークン、Microsoft Teams Webhook、JIRA設定、ライセンス済みコネクタなど、ルールの外部にある何かに依存しています。それが欠けているか無効化されている場合、ノードは動作できません。Triage Engineは黙って失敗するのではなく、3つの異なるタイミングでそれを知らせます。 * **パレット内**では、利用できないノードはキャンバスにドラッグする前に、その旨と理由がマークされています。 * **保存時**には、利用できないノードを含むグラフは拒否されます。これは、誰かがその場にいて別のノードを選び直せるタイミングです。 @@ -321,7 +322,7 @@ Webhookエンドポイントに対してJSONをPOSTします。 | 設定 | デフォルト | 備考 | |---------|---------|-------| -| **Title** | `Rules Engine 2.0: {{ctx.rule_name}}` | バッチ全体について1回レンダリングされます。 | +| **Title** | `Triage Engine: {{ctx.rule_name}}` | バッチ全体について1回レンダリングされます。 | | **Description** | `{{ctx.count}} finding(s) matched the rule {{ctx.rule_name}}.` | バッチ全体について1回レンダリングされます。 | | **Recipients** | 空 | ユーザー名をカンマ区切りで指定します。空の場合は管理者にアラートが送られます。 | diff --git a/docs/content/automation/rules_engine_2/node_reference.md b/docs/content/automation/triage_engine/node_reference.md similarity index 91% rename from docs/content/automation/rules_engine_2/node_reference.md rename to docs/content/automation/triage_engine/node_reference.md index 7391559b2d9..04c83c41de4 100644 --- a/docs/content/automation/rules_engine_2/node_reference.md +++ b/docs/content/automation/triage_engine/node_reference.md @@ -1,14 +1,15 @@ --- title: "Node Reference" -description: "Every node Rules Engine 2.0 ships with, and what each one does" +description: "Every node Triage Engine ships with, and what each one does" weight: 3 audience: pro aliases: - /automation/rules_engine_v2/node_reference/ + - /automation/rules_engine_2/node_reference/ --- -Note: Rules Engine 2.0 is a DefectDojo Pro-only feature. +Note: Triage Engine is a DefectDojo Pro-only feature. -Rules Engine 2.0 ships 38 nodes in five categories. This page documents all of them. +Triage Engine ships 41 nodes in five categories. This page documents all of them. Unless stated otherwise, a node takes one input, produces one output called `out`, and passes every item it received on to that output. That matters when you chain nodes: a Findings node changes the Finding and then hands the item onward, so several of them in a row all apply. @@ -276,6 +277,18 @@ Sets the risk, overriding the computed one. |---------|---------| | **Risk** | `Low`, `Medium`, `Needs Action`, `Urgent` | +### Set Potential Agency Impact (PAIN) + +`finding.set_pain` + +Assigns the FedRAMP Potential Agency Impact (PAIN) rating. When PAIN tiering is enabled on the Asset's SLA configuration, this rating drives the VDR remediation deadline. See [PAIN ratings](/federal_compliance/pain_ratings/) for how the rating feeds remediation timelines. + +| Setting | Options | +|---------|---------| +| **PAIN rating** | `N1 - minimal customer effect`, `N2 - narrow customer effect`, `N3 - disruptive effect on one agency`, `N4 - debilitating on one agency, or disruptive on several`, `N5 - debilitating effect on more than one agency` | + +The options carry FedRAMP's own customer-effect wording rather than the bare `N1`–`N5` codes, so a rule author judges the effect rather than a number. + ### Set a Custom Field `finding.set_custom_field` @@ -418,6 +431,18 @@ Assigns a Risk Priority — a [prioritization engine](/asset_modelling/pro_hiera Unlike the SLA action, this node does not skip an Asset that is mid-recalculation: nothing reverts its write, so the assignment lands normally either way. +### Assign to a Dedupe Pool + +`asset.assign_dedupe_pool` + +Makes the Asset deduplicate together with the rest of a [dedupe pool](/triage_findings/finding_deduplication/pro__dedupe_pools/), or removes it from one. + +| Setting | Default | Notes | +|---------|---------|-------| +| **Action** | `Assign to Pool` | `Assign to Pool` or `Remove from Pool`. | +| **Pool** | none | Shown for `Assign to Pool`. The pool these Assets should deduplicate within. Required. | +| **Matching** | `Same tool` | Which kind of matching this membership governs: `Same tool` or `Cross tool`. Reimport matching is not offered, because a pool has no effect on it. | + ## Egress Egress nodes are the nodes that leave DefectDojo. Every one of them records a [Delivery](../deliveries/) before anything is sent, and every one of them honours the rule's **Simulate** or **Live** mode. @@ -430,7 +455,7 @@ A node sending one message per item stops after 1,000 sends in a single run by d ### When a channel is unavailable -An egress node depends on something outside the rule: a Slack token, a Microsoft Teams webhook, a JIRA configuration, a licensed connector. When that is missing or switched off, the node cannot work, and Rules Engine 2.0 says so at three different moments rather than failing quietly: +An egress node depends on something outside the rule: a Slack token, a Microsoft Teams webhook, a JIRA configuration, a licensed connector. When that is missing or switched off, the node cannot work, and Triage Engine says so at three different moments rather than failing quietly: * **In the palette**, an unavailable node is marked as such, with the reason, before you drag it onto the canvas. * **On save**, a graph containing an unavailable node is refused. That is the moment somebody is present to pick a different one. @@ -526,6 +551,20 @@ Two things to know. A signing secret typed here is stored with the rule, so for Free-text URLs are validated when you save. See [Configuration](../configuration/#outbound-destination-validation) for what is rejected and how to allow private addresses. +### Publish to an SNS Topic + +`notify.sns` + +Publishes one message about the batch, or one per item, to an Amazon SNS topic, which fans it out to whatever is subscribed. + +| Setting | Default | Notes | +|---------|---------|-------| +| **Connection** | none | A [Messaging Connector](/issue_tracking/pro_integration/messaging_connectors/) for Amazon SNS. Required. Unlike the chat channels, SNS has no instance-wide fallback: a connection is the only way to address a topic. | +| **Destination** | empty | Shown once a connection is chosen. The SNS topic to publish to, as its ARN. | +| **One Message per Finding** | off | Off publishes one message about the batch. | +| **Message** | `{{finding.severity}}: {{finding.title}} ({{product.name}})` | Rendered per Finding. | +| **Findings Listed in the Digest** | `10` | Shown for batch messages. How many Findings the message lists before it says how many more there were. | + ### Raise an In-App Alert `notify.alert` @@ -534,7 +573,7 @@ Creates an in-app alert about the batch. | Setting | Default | Notes | |---------|---------|-------| -| **Title** | `Rules Engine 2.0: {{ctx.rule_name}}` | Rendered once for the whole batch. | +| **Title** | `Triage Engine: {{ctx.rule_name}}` | Rendered once for the whole batch. | | **Description** | `{{ctx.count}} finding(s) matched the rule {{ctx.rule_name}}.` | Rendered once for the whole batch. | | **Recipients** | empty | Usernames, comma separated. Empty alerts the administrators. | diff --git a/docs/content/automation/rules_engine_2/node_reference.pt-br.md b/docs/content/automation/triage_engine/node_reference.pt-br.md similarity index 96% rename from docs/content/automation/rules_engine_2/node_reference.pt-br.md rename to docs/content/automation/triage_engine/node_reference.pt-br.md index 071178df60f..0d7e462926d 100644 --- a/docs/content/automation/rules_engine_2/node_reference.pt-br.md +++ b/docs/content/automation/triage_engine/node_reference.pt-br.md @@ -1,15 +1,16 @@ --- title: Referência de Nós -description: Todos os nós com que o Rules Engine 2.0 vem, e o que cada um faz +description: Todos os nós com que o Triage Engine vem, e o que cada um faz weight: 3 audience: pro aliases: - /pt-br/automation/rules_engine_v2/node_reference/ +- /pt-br/automation/rules_engine_2/node_reference/ --- -Nota: o Rules Engine 2.0 é um recurso exclusivo do DefectDojo Pro. +Nota: o Triage Engine é um recurso exclusivo do DefectDojo Pro. -O Rules Engine 2.0 vem com 25 nós em quatro categorias. Esta página documenta todos eles. +O Triage Engine vem com 25 nós em quatro categorias. Esta página documenta todos eles. Salvo indicação contrária, um nó recebe uma entrada, produz uma saída chamada `out`, e repassa a essa saída cada item que recebeu. Isso importa quando você encadeia nós: um nó de Achados altera o Achado e então repassa o item adiante, de modo que vários deles em sequência são todos aplicados. @@ -217,7 +218,7 @@ Um nó que envia uma mensagem por Achado para por padrão após 1.000 envios em ### Quando um canal está indisponível -Um nó de saída depende de algo externo à regra: um token do Slack, um webhook do Microsoft Teams, uma configuração do JIRA, um conector licenciado. Quando isso está ausente ou desligado, o nó não consegue funcionar, e o Rules Engine 2.0 avisa disso em três momentos diferentes, em vez de falhar silenciosamente: +Um nó de saída depende de algo externo à regra: um token do Slack, um webhook do Microsoft Teams, uma configuração do JIRA, um conector licenciado. Quando isso está ausente ou desligado, o nó não consegue funcionar, e o Triage Engine avisa disso em três momentos diferentes, em vez de falhar silenciosamente: * **Na paleta**, um nó indisponível é marcado como tal, com o motivo, antes de você arrastá-lo para a tela. * **Ao salvar**, um grafo contendo um nó indisponível é recusado. Esse é o momento em que alguém está presente para escolher outro. @@ -321,7 +322,7 @@ Cria um alerta no aplicativo sobre o lote. | Setting | Default | Notes | |---------|---------|-------| -| **Title** | `Rules Engine 2.0: {{ctx.rule_name}}` | Renderizado uma vez para o lote inteiro. | +| **Title** | `Triage Engine: {{ctx.rule_name}}` | Renderizado uma vez para o lote inteiro. | | **Description** | `{{ctx.count}} finding(s) matched the rule {{ctx.rule_name}}.` | Renderizado uma vez para o lote inteiro. | | **Recipients** | vazio | Nomes de usuário, separados por vírgula. Vazio alerta os administradores. | diff --git a/docs/content/automation/rules_engine_2/node_reference.zh-hans.md b/docs/content/automation/triage_engine/node_reference.zh-hans.md similarity index 96% rename from docs/content/automation/rules_engine_2/node_reference.zh-hans.md rename to docs/content/automation/triage_engine/node_reference.zh-hans.md index 2abdf5b9851..43d9216913a 100644 --- a/docs/content/automation/rules_engine_2/node_reference.zh-hans.md +++ b/docs/content/automation/triage_engine/node_reference.zh-hans.md @@ -1,15 +1,16 @@ --- title: 节点参考 -description: Rules Engine 2.0 内置的每一个节点及其作用 +description: Triage Engine 内置的每一个节点及其作用 weight: 3 audience: pro aliases: - /zh-hans/automation/rules_engine_v2/node_reference/ +- /zh-hans/automation/rules_engine_2/node_reference/ --- -注意：Rules Engine 2.0 是 DefectDojo Pro 专属功能。 +注意：Triage Engine 是 DefectDojo Pro 专属功能。 -Rules Engine 2.0 内置了分为四大类的 25 个节点。本页对它们逐一进行说明。 +Triage Engine 内置了分为四大类的 25 个节点。本页对它们逐一进行说明。 除非另有说明，每个节点都接受一个输入，产生一个名为 `out` 的输出，并将其收到的每一项都传递给该输出。这一点在你串联多个节点时很重要：一个发现项节点会先修改该发现项，然后再将其向后传递，因此依次排列的多个此类节点都会依次生效。 @@ -217,7 +218,7 @@ Rules Engine 2.0 内置了分为四大类的 25 个节点。本页对它们逐 ### 当渠道不可用时 -出站节点依赖于规则之外的某些资源：Slack 令牌、Microsoft Teams webhook、JIRA 配置、已获得许可的连接器等。当这些资源缺失或被关闭时，该节点就无法工作，而 Rules Engine 2.0 会在三个不同的时刻明确告知这一点，而不是悄无声息地失败： +出站节点依赖于规则之外的某些资源：Slack 令牌、Microsoft Teams webhook、JIRA 配置、已获得许可的连接器等。当这些资源缺失或被关闭时，该节点就无法工作，而 Triage Engine 会在三个不同的时刻明确告知这一点，而不是悄无声息地失败： * **在节点面板中**，不可用的节点在你将其拖到画布上之前，就已经被标注为不可用并说明原因。 * **在保存时**，包含不可用节点的图会被拒绝保存。这正是有人在场、可以另选一个节点的时刻。 @@ -321,7 +322,7 @@ Rules Engine 2.0 内置了分为四大类的 25 个节点。本页对它们逐 | 设置 | 默认值 | 说明 | |-----|-----|-----| -| **标题** | `Rules Engine 2.0: {{ctx.rule_name}}` | 针对整批内容渲染一次。 | +| **标题** | `Triage Engine: {{ctx.rule_name}}` | 针对整批内容渲染一次。 | | **描述** | `{{ctx.count}} finding(s) matched the rule {{ctx.rule_name}}.` | 针对整批内容渲染一次。 | | **接收人** | 空 | 用户名，用逗号分隔。留空则提醒管理员。 | diff --git a/docs/content/automation/rules_engine_2/runs.de.md b/docs/content/automation/triage_engine/runs.de.md similarity index 96% rename from docs/content/automation/rules_engine_2/runs.de.md rename to docs/content/automation/triage_engine/runs.de.md index f80ab302c02..720c15ab094 100644 --- a/docs/content/automation/rules_engine_2/runs.de.md +++ b/docs/content/automation/triage_engine/runs.de.md @@ -6,11 +6,12 @@ weight: 4 audience: pro aliases: - /de/automation/rules_engine_v2/runs/ +- /de/automation/rules_engine_2/runs/ --- -Hinweis: Rules Engine 2.0 ist eine reine DefectDojo-Pro-Funktion. +Hinweis: Triage Engine ist eine reine DefectDojo-Pro-Funktion. -Ein **Lauf** ist eine Ausführung einer Regel. Jeder Lauf wird aufgezeichnet, unabhängig davon, ob er erfolgreich war oder fehlgeschlagen ist, und jeder Knoten darin hinterlässt eine Spur. **Rules Engine 2.0 > Läufe** listet sie auf. +Ein **Lauf** ist eine Ausführung einer Regel. Jeder Lauf wird aufgezeichnet, unabhängig davon, ob er erfolgreich war oder fehlgeschlagen ist, und jeder Knoten darin hinterlässt eine Spur. **Triage Engine > Läufe** listet sie auf. ## Was ein Lauf aufzeichnet @@ -64,7 +65,7 @@ Wenn ein Lauf auf irgendeine Weise verwaist, zum Beispiel weil der ausführende ## Kaskadierung -Eine Regel, die einen Befund ändert, erzeugt genau die Art von Ereignis, auf das eine andere Regel reagieren kann. Rules Engine 2.0 erlaubt das, sodass Ketten wie `A -> B -> C` funktionieren, und begrenzt dies auf zwei unabhängige Arten: +Eine Regel, die einen Befund ändert, erzeugt genau die Art von Ereignis, auf das eine andere Regel reagieren kann. Triage Engine erlaubt das, sodass Ketten wie `A -> B -> C` funktionieren, und begrenzt dies auf zwei unabhängige Arten: * **Tiefe.** Ein Ereignis darf höchstens **3** Kaskadierungsschritte von der Änderung entfernt zurücklegen, die es ausgelöst hat. * **Ketten-Zugehörigkeit.** Jedes Ereignis trägt die Liste der Regeln, die in seiner Kette bereits durchlaufen wurden, und eine Regel läuft nie zweimal in derselben Kette. Eine Regel kann sich also nicht selbst erneut auslösen, und zwei Regeln können nicht hin- und herspielen. diff --git a/docs/content/automation/rules_engine_2/runs.es.md b/docs/content/automation/triage_engine/runs.es.md similarity index 96% rename from docs/content/automation/rules_engine_2/runs.es.md rename to docs/content/automation/triage_engine/runs.es.md index cc68f5b61df..81fd82b3f99 100644 --- a/docs/content/automation/rules_engine_2/runs.es.md +++ b/docs/content/automation/triage_engine/runs.es.md @@ -6,11 +6,12 @@ weight: 4 audience: pro aliases: - /es/automation/rules_engine_v2/runs/ +- /es/automation/rules_engine_2/runs/ --- -Nota: Rules Engine 2.0 es una función exclusiva de DefectDojo Pro. +Nota: Triage Engine es una función exclusiva de DefectDojo Pro. -Una **ejecución** es una instancia de ejecución de una regla. Cada ejecución se registra, tanto si tuvo éxito como si falló, y cada nodo dentro de ella deja un rastro. **Rules Engine 2.0 > Runs** las enumera. +Una **ejecución** es una instancia de ejecución de una regla. Cada ejecución se registra, tanto si tuvo éxito como si falló, y cada nodo dentro de ella deja un rastro. **Triage Engine > Runs** las enumera. ## Qué registra una ejecución @@ -64,7 +65,7 @@ Si una ejecución queda abandonada de alguna forma, por ejemplo porque se mató ## Encadenamiento -Una regla que cambia un Hallazgo produce exactamente el tipo de evento sobre el que otra regla puede activarse. Rules Engine 2.0 permite esto, de modo que las cadenas `A -> B -> C` funcionan, y lo limita de dos formas independientes: +Una regla que cambia un Hallazgo produce exactamente el tipo de evento sobre el que otra regla puede activarse. Triage Engine permite esto, de modo que las cadenas `A -> B -> C` funcionan, y lo limita de dos formas independientes: * **Depth.** Un evento puede viajar como máximo **3** saltos en cascada desde el cambio que lo originó. diff --git a/docs/content/automation/rules_engine_2/runs.fr.md b/docs/content/automation/triage_engine/runs.fr.md similarity index 99% rename from docs/content/automation/rules_engine_2/runs.fr.md rename to docs/content/automation/triage_engine/runs.fr.md index 6663a3dbc31..94fb73d2504 100644 --- a/docs/content/automation/rules_engine_2/runs.fr.md +++ b/docs/content/automation/triage_engine/runs.fr.md @@ -6,6 +6,7 @@ weight: 4 audience: pro aliases: - /fr/automation/rules_engine_v2/runs/ +- /fr/automation/rules_engine_2/runs/ --- Remarque : le Moteur de règles 2.0 est une fonctionnalité réservée à DefectDojo Pro. diff --git a/docs/content/automation/rules_engine_2/runs.it.md b/docs/content/automation/triage_engine/runs.it.md similarity index 95% rename from docs/content/automation/rules_engine_2/runs.it.md rename to docs/content/automation/triage_engine/runs.it.md index 94b5051c208..3f8585d0188 100644 --- a/docs/content/automation/rules_engine_2/runs.it.md +++ b/docs/content/automation/triage_engine/runs.it.md @@ -6,11 +6,12 @@ weight: 4 audience: pro aliases: - /it/automation/rules_engine_v2/runs/ +- /it/automation/rules_engine_2/runs/ --- -Nota: Rules Engine 2.0 è una funzionalità disponibile solo in DefectDojo Pro. +Nota: Triage Engine è una funzionalità disponibile solo in DefectDojo Pro. -Un **run** è una singola esecuzione di una regola. Ogni run viene registrato, sia che abbia avuto esito positivo sia che sia fallito, e ogni nodo al suo interno lascia una traccia. **Rules Engine 2.0 > Runs** li elenca. +Un **run** è una singola esecuzione di una regola. Ogni run viene registrato, sia che abbia avuto esito positivo sia che sia fallito, e ogni nodo al suo interno lascia una traccia. **Triage Engine > Runs** li elenca. ## Cosa registra un run @@ -64,7 +65,7 @@ Se un run viene in qualche modo abbandonato, ad esempio perché il worker che lo ## Cascata -Una regola che modifica un Finding produce esattamente il tipo di evento su cui un'altra regola può attivarsi. Rules Engine 2.0 lo consente, quindi catene del tipo `A -> B -> C` funzionano, e le limita in due modi indipendenti: +Una regola che modifica un Finding produce esattamente il tipo di evento su cui un'altra regola può attivarsi. Triage Engine lo consente, quindi catene del tipo `A -> B -> C` funzionano, e le limita in due modi indipendenti: * **Profondità.** Un evento può percorrere al massimo **3** passaggi a cascata dalla modifica che lo ha originato. * **Appartenenza alla catena.** Ogni evento porta con sé l'elenco delle regole già attraversate nella sua catena, e una regola non viene mai eseguita due volte nella stessa catena. Quindi una regola non può riattivare se stessa, e due regole non possono rimbalzare tra loro. diff --git a/docs/content/automation/rules_engine_2/runs.ja.md b/docs/content/automation/triage_engine/runs.ja.md similarity index 96% rename from docs/content/automation/rules_engine_2/runs.ja.md rename to docs/content/automation/triage_engine/runs.ja.md index 011147733ce..b87a89d38e0 100644 --- a/docs/content/automation/rules_engine_2/runs.ja.md +++ b/docs/content/automation/triage_engine/runs.ja.md @@ -5,11 +5,12 @@ weight: 4 audience: pro aliases: - /ja/automation/rules_engine_v2/runs/ +- /ja/automation/rules_engine_2/runs/ --- -注: Rules Engine 2.0はDefectDojo Pro限定機能です。 +注: Triage EngineはDefectDojo Pro限定機能です。 -**実行（run）**とは、1つのルールの1回分の実行のことです。成功したか失敗したかにかかわらず、すべての実行が記録され、その内部の各ノードも痕跡を残します。**Rules Engine 2.0 > Runs**にその一覧が表示されます。 +**実行（run）**とは、1つのルールの1回分の実行のことです。成功したか失敗したかにかかわらず、すべての実行が記録され、その内部の各ノードも痕跡を残します。**Triage Engine > Runs**にその一覧が表示されます。 ## 実行が記録する内容 @@ -63,7 +64,7 @@ Egress（送出）についても同じ規則が適用されます。配信は ## カスケード -Findingを変更するルールは、まさに他のルールがトリガーとして利用できる種類のイベントを生成します。Rules Engine 2.0はこれを許可しており、`A -> B -> C`のような連鎖が機能します。ただし、これを2つの独立した方法で制限しています。 +Findingを変更するルールは、まさに他のルールがトリガーとして利用できる種類のイベントを生成します。Triage Engineはこれを許可しており、`A -> B -> C`のような連鎖が機能します。ただし、これを2つの独立した方法で制限しています。 * **Depth（深さ）。** イベントは、それを発生させた変更から最大**3**回のカスケードホップまでしか伝播できません。 * **Chain membership（チェーン所属）。** すべてのイベントは、そのチェーン内で既に通過したルールの一覧を保持しており、同じルールが同じチェーン内で2回実行されることはありません。そのため、ルールが自分自身を再トリガーすることも、2つのルールが互いにやり取りを繰り返すこと（ピンポン）もできません。 diff --git a/docs/content/automation/rules_engine_2/runs.md b/docs/content/automation/triage_engine/runs.md similarity index 96% rename from docs/content/automation/rules_engine_2/runs.md rename to docs/content/automation/triage_engine/runs.md index e0b98018362..a78eac51c2d 100644 --- a/docs/content/automation/rules_engine_2/runs.md +++ b/docs/content/automation/triage_engine/runs.md @@ -5,10 +5,11 @@ weight: 4 audience: pro aliases: - /automation/rules_engine_v2/runs/ + - /automation/rules_engine_2/runs/ --- -Note: Rules Engine 2.0 is a DefectDojo Pro-only feature. +Note: Triage Engine is a DefectDojo Pro-only feature. -A **run** is one execution of one rule. Every run is recorded, whether it succeeded or failed, and every node inside it leaves a trace. **Rules Engine 2.0 > Runs** lists them. +A **run** is one execution of one rule. Every run is recorded, whether it succeeded or failed, and every node inside it leaves a trace. **Triage Engine > Runs** lists them. ## What a run records @@ -62,7 +63,7 @@ If a run is somehow abandoned, for example because the worker executing it was k ## Cascading -A rule that changes a Finding produces exactly the kind of event another rule can trigger on. Rules Engine 2.0 allows that, so `A -> B -> C` chains work, and bounds it in two independent ways: +A rule that changes a Finding produces exactly the kind of event another rule can trigger on. Triage Engine allows that, so `A -> B -> C` chains work, and bounds it in two independent ways: * **Depth.** An event may travel at most **3** cascade hops from the change that originated it. * **Chain membership.** Every event carries the list of rules already traversed in its chain, and a rule never runs twice in the same chain. So a rule cannot re-trigger itself, and two rules cannot ping-pong. diff --git a/docs/content/automation/rules_engine_2/runs.pt-br.md b/docs/content/automation/triage_engine/runs.pt-br.md similarity index 96% rename from docs/content/automation/rules_engine_2/runs.pt-br.md rename to docs/content/automation/triage_engine/runs.pt-br.md index 7c7bc4e5c7b..dda663e5bae 100644 --- a/docs/content/automation/rules_engine_2/runs.pt-br.md +++ b/docs/content/automation/triage_engine/runs.pt-br.md @@ -6,11 +6,12 @@ weight: 4 audience: pro aliases: - /pt-br/automation/rules_engine_v2/runs/ +- /pt-br/automation/rules_engine_2/runs/ --- -Observação: o Rules Engine 2.0 é um recurso exclusivo do DefectDojo Pro. +Observação: o Triage Engine é um recurso exclusivo do DefectDojo Pro. -Um **run** (execução) é a execução de uma regra. Toda execução é registrada, tenha sido bem-sucedida ou não, e cada nó dentro dela deixa um rastro. **Rules Engine 2.0 > Runs** lista essas execuções. +Um **run** (execução) é a execução de uma regra. Toda execução é registrada, tenha sido bem-sucedida ou não, e cada nó dentro dela deixa um rastro. **Triage Engine > Runs** lista essas execuções. ## O que uma execução registra @@ -64,7 +65,7 @@ Se uma execução for de alguma forma abandonada, por exemplo porque o worker qu ## Encadeamento (cascata) -Uma regra que altera um Finding produz exatamente o tipo de evento que outra regra pode usar como gatilho. O Rules Engine 2.0 permite isso, de modo que cadeias `A -> B -> C` funcionam, e as limita de duas formas independentes: +Uma regra que altera um Finding produz exatamente o tipo de evento que outra regra pode usar como gatilho. O Triage Engine permite isso, de modo que cadeias `A -> B -> C` funcionam, e as limita de duas formas independentes: * **Depth (profundidade).** Um evento pode percorrer no máximo **3** saltos de cascata a partir da alteração que o originou. * **Pertencimento à cadeia.** Todo evento carrega a lista de regras já percorridas em sua cadeia, e uma regra nunca é executada duas vezes na mesma cadeia. Assim, uma regra não pode disparar a si mesma novamente, e duas regras não podem ficar em ping-pong. diff --git a/docs/content/automation/rules_engine_2/runs.zh-hans.md b/docs/content/automation/triage_engine/runs.zh-hans.md similarity index 99% rename from docs/content/automation/rules_engine_2/runs.zh-hans.md rename to docs/content/automation/triage_engine/runs.zh-hans.md index fda48ee0f41..47c2f00f66f 100644 --- a/docs/content/automation/rules_engine_2/runs.zh-hans.md +++ b/docs/content/automation/triage_engine/runs.zh-hans.md @@ -5,6 +5,7 @@ weight: 4 audience: pro aliases: - /zh-hans/automation/rules_engine_v2/runs/ +- /zh-hans/automation/rules_engine_2/runs/ --- 注意：规则引擎 2.0 是 DefectDojo Pro 专属功能。 diff --git a/docs/content/federal_compliance/pain_ratings.md b/docs/content/federal_compliance/pain_ratings.md index 4c2997f3b4a..b060b90b02d 100644 --- a/docs/content/federal_compliance/pain_ratings.md +++ b/docs/content/federal_compliance/pain_ratings.md @@ -121,10 +121,10 @@ two-day cell. Nothing else about the finding changed. ## Rating findings with the Rules Engine -Ratings are assigned through **Rules Engine 2.0**. The **Set Potential Agency Impact (PAIN)** action +Ratings are assigned through **Triage Engine**. The **Set Potential Agency Impact (PAIN)** action writes a rating to every finding that reaches it. -![The Set Potential Agency Impact (PAIN) action in the Rules Engine 2.0 editor](images/11-rules-engine-set-pain-node.jpg) +![The Set Potential Agency Impact (PAIN) action in the Triage Engine editor](images/11-rules-engine-set-pain-node.jpg) The rating selector offers FedRAMP's own customer-effect wording rather than bare numbers, so whoever builds the rule sees the judgment being made. @@ -140,7 +140,7 @@ The action behaves the way a compliance workflow needs it to: so a rule-set rating and a hand-set one produce the same date. * A rating outside 1 to 5 is rejected. * Every run records a per-finding trace of the change, from and to — the audit trail for each impact - decision. See [Runs](/automation/rules_engine_2/runs/). + decision. See [Runs](/automation/triage_engine/runs/). `finding.pain_rating` is also available as a condition in any filter node, which is what makes escalation rules such as "above N3 and internet-reachable" possible. @@ -148,7 +148,7 @@ escalation rules such as "above N3 and internet-reachable" possible. The rule below produced the deadline change above: a Manual Run trigger, an If / Filter node selecting the finding, and **Set Potential Agency Impact (PAIN)** set to N5, switched to Live. -![A complete PAIN rating rule in the Rules Engine 2.0 editor](images/13-pain-rating-rule.jpg) +![A complete PAIN rating rule in the Triage Engine editor](images/13-pain-rating-rule.jpg) The run trace records each node's input and output counts. This run swept 10,008 findings, one matched the filter, and one rating was written. @@ -161,14 +161,14 @@ Two templates covering the PAIN workflow ship in the template gallery, alongside scan-cadence watchdogs. Adopting a template creates a new rule of your own, disabled and in simulate mode, so nothing runs until you configure and enable it. -![The FedRAMP Class C templates in the Rules Engine 2.0 template gallery](images/15-fedramp-rule-templates.jpg) +![The FedRAMP Class C templates in the Triage Engine template gallery](images/15-fedramp-rule-templates.jpg) | Template | What it does | | --- | --- | | **FedRAMP — route unrated findings for impact review** | A scheduled sweep for active findings that carry exploit evidence — weaponized or worse — and no PAIN rating, raising an alert to the reviewers who own impact decisions. It surfaces the queue rather than assigning a rating, which is what FedRAMP's provider-judgment requirement asks for. | | **FedRAMP — escalate reportable-incident candidates** | A scheduled sweep for active findings rated above N3 that are likely exploitable and sit on exposed assets, raising a ticket for each. Class C treats such a finding as a FedRAMP Reportable Incident until it is mitigated to N3 or below. | -See [Building Rules](/automation/rules_engine_2/building_rules/) for how a template is adopted. +See [Building Rules](/automation/triage_engine/building_rules/) for how a template is adopted. ## Where the deadline shows up diff --git a/docs/content/issue_tracking/pro_integration/messaging_connectors.de.md b/docs/content/issue_tracking/pro_integration/messaging_connectors.de.md index d826bf58248..55e00fa4e78 100644 --- a/docs/content/issue_tracking/pro_integration/messaging_connectors.de.md +++ b/docs/content/issue_tracking/pro_integration/messaging_connectors.de.md @@ -6,7 +6,7 @@ weight: 4 audience: pro --- -**Verfügbarkeit:** Messaging-Connectors sind eine Beta-Funktion. Aktivieren Sie **Messaging Connectors** auf der Seite „Feature Flags“. Da Warnungen über Regeln weitergeleitet werden, muss außerdem **Rules Engine 2.0** aktiviert sein. +**Verfügbarkeit:** Messaging-Connectors sind eine Beta-Funktion. Aktivieren Sie **Messaging Connectors** auf der Seite „Feature Flags“. Da Warnungen über Regeln weitergeleitet werden, muss außerdem **Triage Engine** aktiviert sein. Messaging-Connectors senden Warnungen von DefectDojo an einen Chatdienst, an eine E-Mail-Adresse oder an ein Amazon-SNS-Topic. Sie stehen neben den Ticketing- und Incident-Management-Connectors auf derselben Seite **Downstream Connectors** und werden auf dieselbe Weise konfiguriert: Sie erstellen einmal eine Verbindung und legen dann fest, was darüber gesendet werden soll. @@ -14,7 +14,7 @@ Ticketing-Connectors und Messaging-Connectors beantworten unterschiedliche Frage ## Was Sie senden können -Warnungen werden über die Rules Engine 2.0 weitergeleitet. Eine Regel legt fest, **wann** gesendet wird (ein Trigger), **welche** Befunde infrage kommen (Bedingungen) und **wohin** die Nachricht geht (ein Notify-Knoten, der Ihre Verbindung und Ihren Kanal adressiert). +Warnungen werden über die Triage Engine weitergeleitet. Eine Regel legt fest, **wann** gesendet wird (ein Trigger), **welche** Befunde infrage kommen (Bedingungen) und **wohin** die Nachricht geht (ein Notify-Knoten, der Ihre Verbindung und Ihren Kanal adressiert). Das bedeutet, dass einer Warnung dieselben Filter zur Verfügung stehen wie einer Regel: Schweregrad, Geltungsbereich, Tags, Status und alles andere, was eine Regelbedingung ausdrücken kann. Mehrere unterschiedliche Warnungen an mehrere unterschiedliche Kanäle sind schlicht mehrere Regeln. @@ -163,7 +163,7 @@ Ein erfolgreicher Test hebt außerdem eine automatisch deaktivierte Verbindung w ## Eine Warnung erstellen -Es gibt zwei Wege dorthin. Beide führen zum selben Ergebnis: einer Regel der Rules Engine 2.0. +Es gibt zwei Wege dorthin. Beide führen zum selben Ergebnis: einer Regel der Triage Engine. ### Die Seite „Warnungen“ @@ -189,7 +189,7 @@ Warnungen sind Regeln und lassen sich daher aus derselben Liste auch im Regeledi Der vollständige Weg für alles, was das Formular nicht abdeckt. -1. Gehen Sie zu **Automation > Rules Engine 2.0** und erstellen Sie eine Regel. +1. Gehen Sie zu **Automation > Triage Engine** und erstellen Sie eine Regel. 2. Fügen Sie einen Trigger hinzu. Für Warnungen zu neu importierten Befunden verwenden Sie den Finding-Ereignis-Trigger bei **created**. Importe werden gebündelt, sodass ein Import eine Warnung erzeugt statt einer pro Befund. 3. Fügen Sie Bedingungen dafür hinzu, was infrage kommen soll, zum Beispiel einen Mindest-Schweregrad von Hoch. 4. Fügen Sie einen Nachrichtenknoten für den gewünschten Anbieter hinzu (**Send a Slack Message**, **Send a Microsoft Teams Message**, **Send an Email** oder **Publish to an SNS Topic**) und legen Sie fest: diff --git a/docs/content/issue_tracking/pro_integration/messaging_connectors.es.md b/docs/content/issue_tracking/pro_integration/messaging_connectors.es.md index ac27a1b2e64..1c2ea1de8ea 100644 --- a/docs/content/issue_tracking/pro_integration/messaging_connectors.es.md +++ b/docs/content/issue_tracking/pro_integration/messaging_connectors.es.md @@ -6,7 +6,7 @@ weight: 4 audience: pro --- -**Disponibilidad:** los Conectores de mensajería son una función en beta. Active **Messaging Connectors** en la página Feature Flags. Como las alertas se enrutan mediante reglas, **Rules Engine 2.0** también debe estar activado. +**Disponibilidad:** los Conectores de mensajería son una función en beta. Active **Messaging Connectors** en la página Feature Flags. Como las alertas se enrutan mediante reglas, **Triage Engine** también debe estar activado. Los Conectores de mensajería envían alertas desde DefectDojo a un servicio de chat, a una dirección de correo electrónico o a un topic de Amazon SNS. Se ubican junto a los conectores de tickets y de gestión de incidentes en la misma página **Downstream Connectors**, y se configuran de la misma manera: cree una conexión una vez y luego decida qué se debe enviar a ella. @@ -14,7 +14,7 @@ Los conectores de tickets y los conectores de mensajería responden preguntas di ## Qué puede enviar -Las alertas se enrutan mediante Rules Engine 2.0. Una regla decide **cuándo** enviar (un disparador), **qué** Hallazgos califican (condiciones) y **adónde** va el mensaje (un nodo de notificación que direcciona su conexión y canal). +Las alertas se enrutan mediante Triage Engine. Una regla decide **cuándo** enviar (un disparador), **qué** Hallazgos califican (condiciones) y **adónde** va el mensaje (un nodo de notificación que direcciona su conexión y canal). Esto significa que los filtros disponibles para una alerta son los mismos que están disponibles para una regla: severidad, alcance, etiquetas, estado y cualquier otra cosa que una condición de regla pueda expresar. Varias alertas distintas que van a varios canales distintos son, simplemente, varias reglas. @@ -157,7 +157,7 @@ Una prueba exitosa también reactiva una conexión que había sido deshabilitada ## Crear una alerta -Hay dos formas de hacerlo. Ambas producen lo mismo: una regla de Rules Engine 2.0. +Hay dos formas de hacerlo. Ambas producen lo mismo: una regla de Triage Engine. ### La página de alertas @@ -183,7 +183,7 @@ Las alertas son reglas, así que también pueden abrirse en el editor de reglas La vía completa, para todo lo que el formulario no cubre. -1. Vaya a **Automation > Rules Engine 2.0** y cree una regla. +1. Vaya a **Automation > Triage Engine** y cree una regla. 2. Agregue un disparador. Para alertas sobre Hallazgos recién importados, use el disparador de eventos de Hallazgo en **created**. Las importaciones se procesan por lotes, de modo que una importación produce una alerta en lugar de una por Hallazgo. 3. Agregue condiciones para lo que debe calificar, por ejemplo una severidad mínima de Alta. 4. Agregue un nodo de mensaje para el proveedor que quiera (**Send a Slack Message**, **Send a Microsoft Teams Message**, **Send an Email** o **Publish to an SNS Topic**) y configure: diff --git a/docs/content/issue_tracking/pro_integration/messaging_connectors.fr.md b/docs/content/issue_tracking/pro_integration/messaging_connectors.fr.md index edfbe782e69..3faa149ec17 100644 --- a/docs/content/issue_tracking/pro_integration/messaging_connectors.fr.md +++ b/docs/content/issue_tracking/pro_integration/messaging_connectors.fr.md @@ -6,7 +6,7 @@ weight: 4 audience: pro --- -**Disponibilité :** les connecteurs de messagerie sont une fonctionnalité bêta. Activez **Messaging Connectors** sur la page Feature Flags. Comme les alertes sont acheminées par des règles, **Rules Engine 2.0** doit également être activé. +**Disponibilité :** les connecteurs de messagerie sont une fonctionnalité bêta. Activez **Messaging Connectors** sur la page Feature Flags. Comme les alertes sont acheminées par des règles, **Triage Engine** doit également être activé. Les connecteurs de messagerie envoient des alertes de DefectDojo vers un service de chat, une adresse e-mail ou un topic Amazon SNS. Ils se trouvent à côté des connecteurs de ticketing et de gestion des incidents sur la même page **Downstream Connectors**, et se configurent de la même manière : créez une connexion une fois, puis décidez ce qui doit lui être envoyé. @@ -14,7 +14,7 @@ Les connecteurs de ticketing et les connecteurs de messagerie répondent à des ## Ce que vous pouvez envoyer -Les alertes sont acheminées par Rules Engine 2.0. Une règle détermine **quand** envoyer (un déclencheur), **quelles** Constatations sont éligibles (des conditions), et **où** le message est envoyé (un nœud de notification indiquant votre connexion et votre canal). +Les alertes sont acheminées par Triage Engine. Une règle détermine **quand** envoyer (un déclencheur), **quelles** Constatations sont éligibles (des conditions), et **où** le message est envoyé (un nœud de notification indiquant votre connexion et votre canal). Cela signifie que les filtres disponibles pour une alerte sont les mêmes que ceux disponibles pour une règle : sévérité, périmètre, étiquettes, statut, et tout ce qu'une condition de règle peut exprimer. Plusieurs alertes différentes allant vers plusieurs canaux différents ne sont donc que plusieurs règles. @@ -163,7 +163,7 @@ Un test réussi débloque également une connexion qui a été désactivée auto ## Créer une alerte -Il existe deux façons d'y arriver. Toutes deux produisent la même chose : une règle Rules Engine 2.0. +Il existe deux façons d'y arriver. Toutes deux produisent la même chose : une règle Triage Engine. ### La page des alertes @@ -189,7 +189,7 @@ Les alertes sont des règles, elles peuvent donc aussi être ouvertes dans l'éd Le chemin complet, pour tout ce que le formulaire ne couvre pas. -1. Allez dans **Automation > Rules Engine 2.0** et créez une règle. +1. Allez dans **Automation > Triage Engine** et créez une règle. 2. Ajoutez un déclencheur. Pour des alertes portant sur des Constatations nouvellement importées, utilisez le déclencheur d'événement Finding sur **created**. Les imports sont regroupés par lots, si bien qu'un import produit une seule alerte plutôt qu'une par Constatation. 3. Ajoutez des conditions déterminant l'éligibilité, par exemple une sévérité minimale de Élevée. 4. Ajoutez un nœud de message pour le fournisseur souhaité (**Send a Slack Message**, **Send a Microsoft Teams Message**, **Send an Email**, ou **Publish to an SNS Topic**) et définissez : diff --git a/docs/content/issue_tracking/pro_integration/messaging_connectors.it.md b/docs/content/issue_tracking/pro_integration/messaging_connectors.it.md index 96171ddeac1..4ef1a139cbd 100644 --- a/docs/content/issue_tracking/pro_integration/messaging_connectors.it.md +++ b/docs/content/issue_tracking/pro_integration/messaging_connectors.it.md @@ -5,7 +5,7 @@ weight: 4 audience: pro --- -**Disponibilità:** i Connettori di messaggistica sono una funzionalità beta. Abilita **Messaging Connectors** nella pagina Feature Flags. Poiché gli avvisi vengono instradati tramite regole, è necessario abilitare anche **Rules Engine 2.0**. +**Disponibilità:** i Connettori di messaggistica sono una funzionalità beta. Abilita **Messaging Connectors** nella pagina Feature Flags. Poiché gli avvisi vengono instradati tramite regole, è necessario abilitare anche **Triage Engine**. I Connettori di messaggistica inviano avvisi da DefectDojo a un servizio di chat, a un indirizzo email o a un topic Amazon SNS. Si trovano accanto ai connettori di ticketing e di gestione degli incidenti nella stessa pagina **Downstream Connectors** e si configurano allo stesso modo: si crea una connessione una sola volta, poi si decide cosa inviarle. @@ -13,7 +13,7 @@ I connettori di ticketing e i connettori di messaggistica rispondono a esigenze ## Cosa puoi inviare -Gli avvisi vengono instradati da Rules Engine 2.0. Una regola decide **quando** inviare (un trigger), **quali** Riscontri sono idonei (condizioni) e **dove** arriva il messaggio (un nodo di notifica che indirizza la connessione e il canale). +Gli avvisi vengono instradati da Triage Engine. Una regola decide **quando** inviare (un trigger), **quali** Riscontri sono idonei (condizioni) e **dove** arriva il messaggio (un nodo di notifica che indirizza la connessione e il canale). Questo significa che i filtri disponibili per un avviso sono gli stessi disponibili per una regola: gravità, ambito, tag, stato e qualsiasi altra cosa una condizione di regola possa esprimere. Più avvisi diversi indirizzati a più canali diversi sono semplicemente più regole. @@ -162,7 +162,7 @@ Un test riuscito riabilita anche una connessione che era stata disattivata autom ## Creare un avviso -Ci sono due modi per procedere. Entrambi producono lo stesso risultato: una regola di Rules Engine 2.0. +Ci sono due modi per procedere. Entrambi producono lo stesso risultato: una regola di Triage Engine. ### La pagina degli avvisi @@ -188,7 +188,7 @@ Gli avvisi sono regole, quindi possono anche essere aperti nell'editor delle reg Il percorso completo, per tutto ciò che il form non copre. -1. Vai su **Automation > Rules Engine 2.0** e crea una regola. +1. Vai su **Automation > Triage Engine** e crea una regola. 2. Aggiungi un trigger. Per gli avvisi su Riscontri appena importati, usa il trigger evento Finding su **created**. Le importazioni sono raggruppate, quindi un'importazione produce un solo avviso invece di uno per ogni Riscontro. 3. Aggiungi le condizioni per stabilire cosa deve qualificarsi, ad esempio una gravità minima Alta. 4. Aggiungi un nodo messaggio per il fornitore desiderato (**Send a Slack Message**, **Send a Microsoft Teams Message**, **Send an Email** o **Publish to an SNS Topic**) e imposta: diff --git a/docs/content/issue_tracking/pro_integration/messaging_connectors.ja.md b/docs/content/issue_tracking/pro_integration/messaging_connectors.ja.md index fe6fc903dee..6937d98e4a3 100644 --- a/docs/content/issue_tracking/pro_integration/messaging_connectors.ja.md +++ b/docs/content/issue_tracking/pro_integration/messaging_connectors.ja.md @@ -5,7 +5,7 @@ weight: 4 audience: pro --- -**利用可否:** メッセージングコネクタはベータ機能です。Feature Flagsページで**Messaging Connectors**を有効にしてください。アラートはルールによってルーティングされるため、**Rules Engine 2.0**も併せて有効にする必要があります。 +**利用可否:** メッセージングコネクタはベータ機能です。Feature Flagsページで**Messaging Connectors**を有効にしてください。アラートはルールによってルーティングされるため、**Triage Engine**も併せて有効にする必要があります。 メッセージングコネクタは、DefectDojoからチャットサービス、メールアドレス、またはAmazon SNSトピックへアラートを送信します。同じ**Downstream Connectors**ページ上で、チケッティングコネクタやインシデント管理コネクタと並んで配置されており、設定方法も同様です。まず接続を一度作成し、その後何を送信するかを決めます。 @@ -13,7 +13,7 @@ audience: pro ## 送信できる内容 -アラートはRules Engine 2.0によってルーティングされます。ルールは、**いつ**送信するか(トリガー)、**どの**検出事項が該当するか(条件)、そして**どこへ**メッセージを送るか(接続とチャンネルを指定する通知ノード)を決定します。 +アラートはTriage Engineによってルーティングされます。ルールは、**いつ**送信するか(トリガー)、**どの**検出事項が該当するか(条件)、そして**どこへ**メッセージを送るか(接続とチャンネルを指定する通知ノード)を決定します。 つまり、アラートで使えるフィルタは、ルールで使えるものと同じです。深刻度、スコープ、タグ、ステータス、その他ルール条件で表現できるあらゆる項目です。複数の異なるチャンネルへ送られる複数の異なるアラートは、単に複数のルールにすぎません。 @@ -156,7 +156,7 @@ FIFOトピック(`.fifo`で終わるARN)はサポートされていません。F ## アラートを作成する -作成方法は2通りあります。どちらも最終的にはRules Engine 2.0のルールを生成します。 +作成方法は2通りあります。どちらも最終的にはTriage Engineのルールを生成します。 ### アラートページ @@ -182,7 +182,7 @@ FIFOトピック(`.fifo`で終わるARN)はサポートされていません。F フォームでカバーされないあらゆる内容に対応する、完全な方法です。 -1. **Automation > Rules Engine 2.0**に移動し、ルールを作成します。 +1. **Automation > Triage Engine**に移動し、ルールを作成します。 2. トリガーを追加します。新規インポートされた検出事項に関するアラートには、Findingイベントトリガーの**created**を使用します。インポートはバッチ処理されるため、1回のインポートは検出事項ごとではなく1件のアラートを生成します。 3. 該当条件(例: 高以上の深刻度)を追加します。 4. 使用したいベンダーのメッセージノード(**Send a Slack Message**、**Send a Microsoft Teams Message**、**Send an Email**、または**Publish to an SNS Topic**)を追加し、以下を設定します。 diff --git a/docs/content/issue_tracking/pro_integration/messaging_connectors.md b/docs/content/issue_tracking/pro_integration/messaging_connectors.md index d7a594d1a31..b099f8a1c85 100644 --- a/docs/content/issue_tracking/pro_integration/messaging_connectors.md +++ b/docs/content/issue_tracking/pro_integration/messaging_connectors.md @@ -5,7 +5,7 @@ weight: 4 audience: pro --- -**Availability:** Messaging Connectors are a beta feature. Enable **Messaging Connectors** on the Feature Flags page. Because alerts are routed by rules, **Rules Engine 2.0** must be enabled as well. +**Availability:** Messaging Connectors are a beta feature. Enable **Messaging Connectors** on the Feature Flags page. Because alerts are routed by rules, **Triage Engine** must be enabled as well. Messaging Connectors send alerts from DefectDojo to a chat service, to an email address, or to an Amazon SNS topic. They sit beside the ticketing and incident-management connectors on the same **Downstream Connectors** page, and they are configured the same way: create a connection once, then decide what should be sent to it. @@ -13,7 +13,7 @@ Ticketing connectors and messaging connectors answer different questions. A tick ## What you can send -Alerts are routed by Rules Engine 2.0. A rule decides **when** to send (a trigger), **which** Findings qualify (conditions), and **where** the message goes (a notify node addressing your connection and channel). +Alerts are routed by Triage Engine. A rule decides **when** to send (a trigger), **which** Findings qualify (conditions), and **where** the message goes (a notify node addressing your connection and channel). This means the filters available to an alert are the same ones available to a rule: severity, scope, tags, status, and anything else a rule condition can express. Several different alerts going to several different channels are simply several rules. @@ -162,7 +162,7 @@ A successful test also clears a connection that has been automatically disabled ## Create an alert -There are two ways in. Both produce the same thing: a Rules Engine 2.0 rule. +There are two ways in. Both produce the same thing: a Triage Engine rule. ### The alerts page @@ -188,7 +188,7 @@ Alerts are rules, so they can also be opened in the rule editor from the same li The full route, for anything the form does not cover. -1. Go to **Automation > Rules Engine 2.0** and create a rule. +1. Go to **Automation > Triage Engine** and create a rule. 2. Add a trigger. For alerts about newly imported Findings, use the Finding event trigger on **created**. Imports are batched, so one import produces one alert rather than one per Finding. 3. Add conditions for what should qualify, for example a minimum severity of High. 4. Add a message node for the vendor you want (**Send a Slack Message**, **Send a Microsoft Teams Message**, **Send an Email**, or **Publish to an SNS Topic**) and set: diff --git a/docs/content/issue_tracking/pro_integration/messaging_connectors.pt-br.md b/docs/content/issue_tracking/pro_integration/messaging_connectors.pt-br.md index 5717ad229a3..2094d97a3b6 100644 --- a/docs/content/issue_tracking/pro_integration/messaging_connectors.pt-br.md +++ b/docs/content/issue_tracking/pro_integration/messaging_connectors.pt-br.md @@ -6,7 +6,7 @@ weight: 4 audience: pro --- -**Disponibilidade:** Messaging Connectors é um recurso beta. Habilite **Messaging Connectors** na página Feature Flags. Como os alertas são roteados por regras, o **Rules Engine 2.0** também precisa estar habilitado. +**Disponibilidade:** Messaging Connectors é um recurso beta. Habilite **Messaging Connectors** na página Feature Flags. Como os alertas são roteados por regras, o **Triage Engine** também precisa estar habilitado. O Messaging Connectors envia alertas do DefectDojo para um serviço de chat, para um endereço de e-mail ou para um tópico do Amazon SNS. Ele fica ao lado dos conectores de ticketing e de gestão de incidentes na mesma página **Downstream Connectors**, e é configurado da mesma forma: crie uma conexão uma vez e depois decida o que deve ser enviado para ela. @@ -14,7 +14,7 @@ Conectores de ticketing e conectores de mensagens respondem a perguntas diferent ## O que você pode enviar -Os alertas são roteados pelo Rules Engine 2.0. Uma regra decide **quando** enviar (um gatilho), **quais** Achados se qualificam (condições) e **para onde** a mensagem vai (um nó de notificação endereçando sua conexão e canal). +Os alertas são roteados pelo Triage Engine. Uma regra decide **quando** enviar (um gatilho), **quais** Achados se qualificam (condições) e **para onde** a mensagem vai (um nó de notificação endereçando sua conexão e canal). Isso significa que os filtros disponíveis para um alerta são os mesmos disponíveis para uma regra: severidade, escopo, tags, status e qualquer outra coisa que uma condição de regra possa expressar. Vários alertas diferentes indo para vários canais diferentes são simplesmente várias regras. @@ -157,7 +157,7 @@ Um teste bem-sucedido também libera uma conexão que foi desabilitada automatic ## Criar um alerta -Há duas formas de fazer isso. Ambas produzem a mesma coisa: uma regra do Rules Engine 2.0. +Há duas formas de fazer isso. Ambas produzem a mesma coisa: uma regra do Triage Engine. ### A página de alertas @@ -183,7 +183,7 @@ Alertas são regras, então também podem ser abertos no editor de regras a part O caminho completo, para qualquer coisa que o formulário não cubra. -1. Acesse **Automation > Rules Engine 2.0** e crie uma regra. +1. Acesse **Automation > Triage Engine** e crie uma regra. 2. Adicione um gatilho. Para alertas sobre Achados recém-importados, use o gatilho de evento de Achado em **created**. As importações são feitas em lote, então uma importação produz um alerta, em vez de um por Achado. 3. Adicione condições para o que deve se qualificar, por exemplo uma severidade mínima de Alto. 4. Adicione um nó de mensagem para o fornecedor desejado (**Send a Slack Message**, **Send a Microsoft Teams Message**, **Send an Email**, ou **Publish to an SNS Topic**) e defina: diff --git a/docs/content/issue_tracking/pro_integration/messaging_connectors.zh-hans.md b/docs/content/issue_tracking/pro_integration/messaging_connectors.zh-hans.md index 0a02e1303c4..c3db26301c1 100644 --- a/docs/content/issue_tracking/pro_integration/messaging_connectors.zh-hans.md +++ b/docs/content/issue_tracking/pro_integration/messaging_connectors.zh-hans.md @@ -5,7 +5,7 @@ weight: 4 audience: pro --- -**可用性：** 消息连接器是一项测试版功能。请在功能标志页面启用 **Messaging Connectors**。由于警报是通过规则路由的，因此还必须启用 **Rules Engine 2.0**。 +**可用性：** 消息连接器是一项测试版功能。请在功能标志页面启用 **Messaging Connectors**。由于警报是通过规则路由的，因此还必须启用 **Triage Engine**。 消息连接器可以将 DefectDojo 中的警报发送到聊天服务、电子邮件地址或 Amazon SNS 主题。它们与工单和事件管理连接器一起位于同一个 **下游连接器** 页面上，配置方式也相同：先创建一次连接，然后决定要向其发送哪些内容。 @@ -13,7 +13,7 @@ audience: pro ## 您可以发送的内容 -警报由规则引擎 2.0 负责路由。一条规则决定**何时**发送（触发条件）、**哪些**发现项符合条件（条件），以及消息**发送到何处**（即指向您的连接和频道的通知节点）。 +警报由Triage Engine 负责路由。一条规则决定**何时**发送（触发条件）、**哪些**发现项符合条件（条件），以及消息**发送到何处**（即指向您的连接和频道的通知节点）。 这意味着警报可用的过滤条件与规则可用的过滤条件相同：严重程度、范围、标签、状态，以及规则条件能够表达的任何其他内容。发送到多个不同频道的多条不同警报，其实就是多条规则。 @@ -156,7 +156,7 @@ SNS 目标使用的是主题的 ARN。 ## 创建警报 -有两种创建方式，最终产生的都是同一样东西：一条规则引擎 2.0 规则。 +有两种创建方式，最终产生的都是同一样东西：一条Triage Engine 规则。 ### 警报页面 @@ -182,7 +182,7 @@ SNS 目标使用的是主题的 ARN。 这是完整的方式，适用于表单未覆盖的一切情况。 -1. 前往 **自动化 > 规则引擎 2.0**，创建一条规则。 +1. 前往 **自动化 > Triage Engine**，创建一条规则。 2. 添加一个触发条件。若要针对新导入的发现项发出警报，请使用发现项事件触发器，触发条件为 **created**（已创建）。导入是批量进行的，因此一次导入只会产生一条警报，而不是每个发现项各产生一条。 3. 添加符合条件的判断规则，例如最低严重程度为高。 4. 为所需的目标服务添加消息节点（**Send a Slack Message**、**Send a Microsoft Teams Message**、**Send an Email**，或 **Publish to an SNS Topic**），并设置： diff --git a/docs/content/navigation/PRO__menu_badges.md b/docs/content/navigation/PRO__menu_badges.md index 44d9c45c216..5fc0449e345 100644 --- a/docs/content/navigation/PRO__menu_badges.md +++ b/docs/content/navigation/PRO__menu_badges.md @@ -51,7 +51,7 @@ Both badges are links, because a tooltip closes the moment your pointer leaves i **`LEGACY`** * **Connect > Jira** — the original per-Asset Jira integration, superseded by the downstream connector for Jira. See [Pro Integrations](/connectors/downstream/about/). -* **Act > Triage Engine > Classic Rules** is the original Rules Engine, superseded by Rules Engine 2.0. It carries the badge only on instances that have both engines turned on, since there is nothing to move to otherwise. See the [conversion guide](/automation/rules_engine_2/converting_from_rules_engine/). +* **Act > Triage Engine > Classic Rules** is the original Rules Engine, superseded by Triage Engine. It carries the badge only on instances that have both engines turned on, since there is nothing to move to otherwise. See the [conversion guide](/automation/triage_engine/converting_from_rules_engine/). **`DEPRECATED`** diff --git a/docs/content/navigation/PRO__page_layouts.md b/docs/content/navigation/PRO__page_layouts.md index cc5fe50d0cf..3db57dd796e 100644 --- a/docs/content/navigation/PRO__page_layouts.md +++ b/docs/content/navigation/PRO__page_layouts.md @@ -114,4 +114,4 @@ Which widgets a page offers depends on the page, and **Add Widget** shows what i - **Feeds** present a running history in date order, such as notes on a record. - **Charts** plot the record's data, such as severity breakdowns and counts over time. -Some widgets appear only when the feature behind them is available to you. For example, the **Automation History** widget on the Asset and Finding pages shows what the rules engine did to that record and why, so it is offered only when Rules Engine 2.0 is turned on and you hold Rule View. +Some widgets appear only when the feature behind them is available to you. For example, the **Automation History** widget on the Asset and Finding pages shows what the rules engine did to that record and why, so it is offered only when Triage Engine is turned on and you hold Rule View. diff --git a/docs/content/triage_findings/findings_workflows/PRO__risk_acceptance.md b/docs/content/triage_findings/findings_workflows/PRO__risk_acceptance.md index 11ba2fe4e59..40fd8f0944c 100644 --- a/docs/content/triage_findings/findings_workflows/PRO__risk_acceptance.md +++ b/docs/content/triage_findings/findings_workflows/PRO__risk_acceptance.md @@ -507,7 +507,7 @@ Notifications are reinforcement, not the mechanism: every state change is alread Risk Acceptance, in its Approvals tab and in the review queue, whether or not a message is sent or ever arrives. A send that fails is logged and does not undo the decision. -### Rules Engine 2.0 conditions +### Triage Engine conditions With both features enabled, a rule can condition on what an acceptance is doing, not just on the `Risk Accepted` flag: