From 4d108d888c5e5d07ad8d223f6c65be35a3f2ae31 Mon Sep 17 00:00:00 2001
From: v0id-space <168028880+v0id-space@users.noreply.github.com>
Date: Wed, 10 Jun 2026 14:00:49 +0300
Subject: [PATCH] Add Trent AI to Attack Modeling

Adds Trent AI ((P) per your convention) to Attack Modeling - automated threat models and security architecture reviews for applications and agentic systems. Disclosure: I work at Trent AI.
---
 README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/README.md b/README.md
index 5467d34..5764d16 100644
--- a/README.md
+++ b/README.md
@@ -258,6 +258,7 @@ DevSecOps requires a common attack modeling capability that can be done at speed
 * [SDL Threat Modeling Tool](https://www.microsoft.com/en-us/sdl/adopt/threatmodeling.aspx)
 * [SeaSponge](http://mozilla.github.io/seasponge/)
 * [Threat Risk Modeling](https://www.owasp.org/index.php/Threat_Risk_Modeling)
+* [Trent AI](https://trent.ai) (P)
 
 ## Secret Management
 To support security as code, sensitive credentials and secrets need to be managed, security, maintained and rotated using automation.  The projects below provide DevOps teams with some good options for securing sensitive details used in building and deploying full stack software deployments.